From: Tejun Heo <tj@kernel.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-ide@vger.kernel.org, linux-raid@vger.kernel.org,
smartmontools-support@lists.sourceforge.net
Subject: Re: Velociraptor biting the dust (9th disk, continued to use it, and..)
Date: Mon, 24 Nov 2008 14:29:45 +0900 [thread overview]
Message-ID: <492A3BC9.5080006@kernel.org> (raw)
In-Reply-To: <4928B40A.6020508@shaw.ca>
Robert Hancock wrote:
> Justin Piszcz wrote:
>> I have several questions, to make things more clear I have segmented this
>> e-mail a bit-- any help with this issue would be greatly appreciated,
>> thank you.
>> ================================================================================
>>
>> So I continued to use the disk and it started failing again:
>> A Fail event had been detected on md device /dev/md2.
>> It could be related to component device /dev/sda3.
>> This is as it happened according to the kernel/dmesg:
>
> (snip)
>
>> BTW: I have already submitted an RMA for this disk (9th RMA!) I just
>> cannot get
>> over how many of these are failing.
>
> That many bad drives in a row seems unlikely. I would tend to suspect
> some kind of other cause such as power issues, etc. though maybe it's
> some kind of design flaw..
Also, in many cases, simple resync is often enough to remove media
related errors as it makes the drive to rewrite and allows it to remap
if necessary but I admit I tend to have quite low standard regarding
hard drive quality.
Thanks.
--
tejun
prev parent reply other threads:[~2008-11-24 5:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 21:45 Velociraptor biting the dust (9th disk, continued to use it, and..) Justin Piszcz
2008-11-22 21:55 ` Alan Cox
2008-12-16 12:31 ` [smartmontools-support] " Bruce Allen
2008-12-16 13:07 ` Justin Piszcz
2008-12-16 13:16 ` Bruce Allen
2008-12-16 22:49 ` Justin Piszcz
2008-12-17 3:52 ` Bruce Allen
2008-11-23 1:38 ` Robert Hancock
2008-11-24 5:29 ` Tejun Heo [this message]
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=492A3BC9.5080006@kernel.org \
--to=tj@kernel.org \
--cc=hancockr@shaw.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=smartmontools-support@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).