All of lore.kernel.org
 help / color / mirror / Atom feed
From: berk walker <berk@panix.com>
To: mjstumpf@pobox.com
Cc: Bill Davidsen <davidsen@tmr.com>,
	Justin Piszcz <jpiszcz@lucidpixels.com>,
	linux-raid@vger.kernel.org
Subject: Re: detecting/correcting _slightly_ flaky disks
Date: Wed, 07 Mar 2007 08:57:31 -0500	[thread overview]
Message-ID: <45EEC4CB.1070804@panix.com> (raw)
In-Reply-To: <45EE1775.7020906@pobox.com>



Michael Stumpf wrote:
> 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.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
One nice thing, if your cables are OK, and your power is OK, then you 
can trash the electronics and transplant from a similar drive with bad 
sectors.
-

"load head
seek spindle
unload head"
is not a nice thing for the hardware.

b-


  reply	other threads:[~2007-03-07 13:57 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-04 11:22 mismatch_cnt questions Christian Pernegger
2007-03-04 11:50 ` Neil Brown
2007-03-04 12:01   ` Christian Pernegger
2007-03-04 22:19     ` Neil Brown
2007-03-06 10:04       ` mismatch_cnt questions - how about raid10? Peter Rabbitson
2007-03-06 10:20         ` Neil Brown
2007-03-06 10:56           ` Peter Rabbitson
2007-03-06 10:59             ` Justin Piszcz
2007-03-12  5:35             ` Neil Brown
2007-03-12 14:26               ` Peter Rabbitson
2007-03-04 21:21   ` mismatch_cnt questions Eyal Lebedinsky
2007-03-04 22:30     ` Neil Brown
2007-03-05  7:45       ` Eyal Lebedinsky
2007-03-05 14:56         ` detecting/correcting _slightly_ flaky disks Michael Stumpf
2007-03-05 15:09           ` Justin Piszcz
2007-03-05 17:01             ` Michael Stumpf
2007-03-05 17:11               ` Justin Piszcz
2007-03-07  0:14               ` Bill Davidsen
2007-03-07  1:37                 ` Michael Stumpf
2007-03-07 13:57                   ` berk walker [this message]
2007-03-07 15:01                   ` Bill Davidsen
2007-03-05 23:40         ` mismatch_cnt questions Neil Brown
2007-03-07  0:22           ` Bill Davidsen
2007-03-08  6:39           ` H. Peter Anvin
2007-03-08 13:54             ` Martin K. Petersen
2007-03-09  2:00               ` Bill Davidsen
2007-03-09  4:20                 ` H. Peter Anvin
2007-03-09  5:20                   ` Bill Davidsen
2007-03-08  6:34         ` H. Peter Anvin
2007-03-08  7:00           ` H. Peter Anvin
2007-03-08  8:21             ` H. Peter Anvin
2007-03-13  9:58               ` Andre Noll
2007-03-13 23:46                 ` H. Peter Anvin
2007-03-06  6:27       ` Paul Davidson
2008-05-12 11:16   ` Bas van Schaik
2008-05-12 14:31     ` Justin Piszcz

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=45EEC4CB.1070804@panix.com \
    --to=berk@panix.com \
    --cc=davidsen@tmr.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mjstumpf@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.