From: Michael Stumpf <mjstumpf@pobox.com>
To: linux-raid@vger.kernel.org
Subject: detecting/correcting _slightly_ flaky disks
Date: Mon, 05 Mar 2007 08:56:09 -0600 [thread overview]
Message-ID: <45EC2F89.2070703@pobox.com> (raw)
In-Reply-To: <45EBCA83.40106@eyal.emu.id.au>
I'm trying to assemble an array (raid 5) of 8 older, but not yet old age
ATA 120 gig disks, but there is intermittent flakiness in one or more of
the drives. Symptoms:
* Won't boot sometimes. Even after moving to 2 power supplies and
monitoring the amp spikes, sometimes I get "clicking" from 1-2 of the
drives after the startup.
* When initiating a SMART long test, so far two of them have:
+ passed 50-75% of the time
+ when "failed", didn't actually fail, just perpetually were
stuck at an arbitrary % of test remain.
+ If I cancel and restart the test, often they pass.
I've heard clicking from some drives when executing SMART long tests.
Doing 4 drives at a time, but still can't
isolate and don't want to use laborious "sit and listen by computer"
method to determine which are dying--would prefer a tool to detect the
issue.
I know there's a problem with one or more because my issues with my
primary array disappeared the minute I used LVM to remove these devices
(and upgrade to some larger/newer ones).
Two questions:
1) Is it smartest to isolate which drives are clicking and chuck them
into the wood chipper, given the circumstances?
2) Are there tools that are designed to determine if a drive is fit for
duty? dd_rescue et all seem focused on saving a dying drive; spinrite
seems to be controversial black magic marketing, etc. I could try the
manufacturer shipped tools but given their black box nature I have no
idea how much (or little) is being done by their tests. What do you
folks recommend?
Thanks in advance.
--Michael Stumpf
next prev parent reply other threads:[~2007-03-05 14:56 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 ` Michael Stumpf [this message]
2007-03-05 15:09 ` detecting/correcting _slightly_ flaky disks 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
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=45EC2F89.2070703@pobox.com \
--to=mjstumpf@pobox.com \
--cc=linux-raid@vger.kernel.org \
/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).