[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070115231452.3528bd32@localhost.localdomain>
Date: Mon, 15 Jan 2007 23:14:52 +0000
From: Alan <alan@...rguk.ukuu.org.uk>
To: Olivier Galibert <galibert@...ox.com>
Cc: "Hack inc." <linux-kernel@...r.kernel.org>
Subject: Re: What does this scsi error mean ?
> 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?
Well the right place to look would indeed have been the SMART data
providing the drive didn't get into a state it couldn't update it.
Hardware error comes from the drive deciding something is wrong (or a
raid card faking it I guess). That covers everything from power
fluctuations and overheating through firmware consistency failures and
more.
If you pull the drive and test it in another box does it show the same ?
And what does a scsi verify have to say ?
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists