LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alan <alan@lxorguk.ukuu.org.uk>
To: Olivier Galibert <galibert@pobox.com>
Cc: "Hack inc." <linux-kernel@vger.kernel.org>
Subject: Re: What does this scsi error mean ?
Date: Mon, 15 Jan 2007 23:14:52 +0000	[thread overview]
Message-ID: <20070115231452.3528bd32@localhost.localdomain> (raw)
In-Reply-To: <20070115214503.GA56952@dspnet.fr.eu.org>

> 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

  reply	other threads:[~2007-01-15 23:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15 17:16 Olivier Galibert
2007-01-15 18:45 ` Alan
2007-01-15 21:45   ` Olivier Galibert
2007-01-15 23:14     ` Alan [this message]
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=20070115231452.3528bd32@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=galibert@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: What does this scsi error mean ?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).