From: Ludovico Cavedon <ludovico.cavedon@gmail.com>
To: Tim Small <tim@buttersideup.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: understanding the cause of ATA failures
Date: Thu, 18 Mar 2010 15:13:36 -0700 [thread overview]
Message-ID: <4BA2A590.4030505@gmail.com> (raw)
In-Reply-To: <4BA2A27E.9040704@buttersideup.com>
Tim Small wrote:
> Do the drives have any SMART errors logged? Any reallocated sectors?
No SMART errors logged.
No reallocated sector for all the hard drives.
Well, I forgot to mention another weired thing. This is what happneded:
* sdc failed and got removed from the RAID array (I pasted the log in my
previous email)
* sda got removed (no logs available)
* sdb got removed (no logs available)
When I realized tha machine was down, I found that the *sdd* was giving
IO errors. So I had to replace sdd, but sda, sdb and sdc, who were those
drives that "failed" first, are working good.
> 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.
No smartd running.
> Haven't had time to get to the bottom of it, but I suspect a firmware bug.
SATA controller firmware bug?
Do you think changing the controller mode from "AHCI" to "IDE" in the
BIOS might help to prevent these errors?
Thanks for your answer,
Ludovico
next prev parent reply other threads:[~2010-03-18 22:13 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
2010-03-18 22:13 ` Ludovico Cavedon [this message]
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=4BA2A590.4030505@gmail.com \
--to=ludovico.cavedon@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=tim@buttersideup.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