From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Stumpf Subject: Re: detecting/correcting _slightly_ flaky disks Date: Tue, 06 Mar 2007 19:37:57 -0600 Message-ID: <45EE1775.7020906@pobox.com> References: <17898.45673.573800.56474@notabene.brown> <45EB3867.8050907@eyal.emu.id.au> <17899.18568.523543.478792@notabene.brown> <45EBCA83.40106@eyal.emu.id.au> <45EC2F89.2070703@pobox.com> <45EC4CFD.3050106@pobox.com> <45EE03E2.5000309@tmr.com> Reply-To: mjstumpf@pobox.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <45EE03E2.5000309@tmr.com> Sender: linux-raid-owner@vger.kernel.org To: Bill Davidsen Cc: Justin Piszcz , linux-raid@vger.kernel.org List-Id: linux-raid.ids Bill Davidsen wrote: > Michael Stumpf wrote: >> This is the drive I think is most suspect. What isn't obvious, >> because it isn't listed in the self test log, is between #1 and #2 >> there was an aborted, hung test. The #4 short test that was aborted >> was also a hung test that I eventually, manually aborted--heard >> clicking from drives at that time, can't swear it was from this drive >> though. >> >> Not sure I fully understand the nuances of this report. If anything >> jumps out at you, I'd appreciate a tip on how you read it. (to me, >> looks mostly healthy) >> > For what it's worth, if you are getting hung tests, either your drive > or power supply should be redeployed as a paperweight. My opinion... > I don't disagree but I'd like to find something more concrete or repeatable, especially given that these give an audible click when failing. The problem I'm having is that I can't nail down precisely where the problem is, although your suggestion makes a lot of sense. After running Justin's suggested badblocks test, I'm kind-of-disturbed to see that all these drives are passing with flying colors. Firmware issue? WD had it in the past.