From: Olivier Galibert <galibert@pobox.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: "Hack inc." <linux-kernel@vger.kernel.org>
Subject: Re: What does this scsi error mean ?
Date: Mon, 15 Jan 2007 22:45:03 +0100 [thread overview]
Message-ID: <20070115214503.GA56952@dspnet.fr.eu.org> (raw)
In-Reply-To: <20070115184540.2b3c4f78@localhost.localdomain>
On Mon, Jan 15, 2007 at 06:45:40PM +0000, Alan wrote:
> On Mon, 15 Jan 2007 18:16:02 +0100
> Olivier Galibert <galibert@pobox.com> wrote:
>
> > sd 0:0:0:0: SCSI error: return code = 0x08000002
> > sda: Current: sense key: Hardware Error
> > ASC=0x42 ASCQ=0x0
>
> I'll give you a clue: The words "Hardware Error".
>
> Run a SCSI verify pass on the drive with some drive utilities and see
> what happens. If you are lucky it'll just reallocate blocks and decide
> the drive is ok, if not well see what the smart data thinks.
Both smart and the internal blade diagnostics say "everything is a-ok
with the drive, there hasn't been any error ever except a bunch of
corrected ECC ones, and no more than with a similar drive in another
working blade". Hence my initial post. "Hardware error" is kinda
imprecise, so I was wondering whether it was unexpected controller
answer, detected transmission error, block write error, sector not
found... Is there a way to have more information?
OG.
next prev parent reply other threads:[~2007-01-15 21:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 17:16 What does this scsi error mean ? Olivier Galibert
2007-01-15 18:45 ` Alan
2007-01-15 21:45 ` Olivier Galibert [this message]
2007-01-15 23:14 ` Alan
2007-01-16 0:10 ` Olivier Galibert
2007-01-18 14:08 ` Olivier Galibert
2007-02-07 17:43 ` Olivier Galibert
2007-01-16 15:16 ` linux-os (Dick Johnson)
2007-01-16 15:47 ` Alan
2007-01-16 17:25 ` Olivier Galibert
2007-01-15 23:27 ` Stefan Richter
2007-01-15 23:35 ` Olivier Galibert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070115214503.GA56952@dspnet.fr.eu.org \
--to=galibert@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.