From: Tim Small <tim@buttersideup.com>
To: Ludovico Cavedon <ludovico.cavedon@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: understanding the cause of ATA failures
Date: Thu, 18 Mar 2010 22:00:30 +0000 [thread overview]
Message-ID: <4BA2A27E.9040704@buttersideup.com> (raw)
In-Reply-To: <4BA2A02F.7040200@gmail.com>
Ludovico Cavedon wrote:
> Is there any way to understand what caused the failures? Is it possible
> to exclude that is was the hard drive, or cable, or controller, or
> kernel fault?
>
Do the drives have any SMART errors logged? Any reallocated sectors?
Do you run smartd, or any other smart data collection? I've had a load
of trouble with WD drives when smart data collection was enabled.
Haven't had time to get to the bottom of it, but I suspect a firmware bug.
Tim.
next prev parent reply other threads:[~2010-03-18 22:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 21:50 understanding the cause of ATA failures Ludovico Cavedon
2010-03-18 22:00 ` Tim Small [this message]
2010-03-18 22:13 ` Ludovico Cavedon
2010-03-18 22:33 ` Stan Hoeppner
2010-03-18 23:03 ` Ludovico Cavedon
2010-03-18 23:39 ` Stan Hoeppner
2010-03-19 3:38 ` Ludovico Cavedon
2010-03-19 10:26 ` Stan Hoeppner
2010-03-25 0:52 ` Tejun Heo
2010-03-26 2:22 ` Ludovico Cavedon
2010-03-22 3:37 ` Robert Hancock
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=4BA2A27E.9040704@buttersideup.com \
--to=tim@buttersideup.com \
--cc=linux-ide@vger.kernel.org \
--cc=ludovico.cavedon@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox