From: Derek Piper <derek.piper@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 drive failure, please verify my commands
Date: Tue, 18 Jan 2005 10:46:26 -0500 [thread overview]
Message-ID: <eaa6dfe050118074677f4bd6f@mail.gmail.com> (raw)
In-Reply-To: <cshj5a$21v$4@sea.gmane.org>
Since we're on the subject of RMA'ing hard drives, I have this
question: I have a Seagate drive that during the course of running dd
if=/dev/zero (a simple write-test I've done on all the 4 drives I am
planning on using in my RAID1 set-up) on it has been shown to have
errors (Drive Ready, Seek Complete .. blah blah). I used smartctl to
have a look at the information the drive is giving and to get it to
run a self-test. It apparently has reallocated 136 sectors, has 3
uncorrectable sector errors and failed the read part of the short
self-test with 90% to go. It says its health status is 'PASSED'
though. 2 of the other drives have just a couple of errors and
reallocated sectors, and one has never had an error.
My question is this, to you knowledgable people, should I RMA it or do
disk mfrs only replace drives if they are really DEAD? It's under
warranty until June. Since I've never done it before I thought I'd
ask, I'm thinking yes. The chick at Seagate kept telling me how to do
the RMA process when I was asking if a few unrecoverable sectors were
covered. Has anyone RMA'd a drive only to have it sent back with 'nah,
it's working fine'?
Opinions are appreciated by anyone. Anyone that's dealt with Seagate,
all the better :)
Thanks,
Derek
On Mon, 17 Jan 2005 23:53:15 +0000, Robin Bowes
<robin-lists@robinbowes.com> wrote:
> Mike Hardy wrote:
> >
> >
> > Gerd Knops wrote:
> >
> >> Hello all,
> >>
> >> One of the dreaded Maxtor SATA drives in my RAID5 failed, after just 3
> >> months of light use. Anyhow I neither have the disk capacity nor the
> >> money to buy it to make a backup. To make sure I do it correctly,
> >> could you folks please double-check my intended course of action? I
> >> would really appreciate that.
> >
> >
> > Failed how? I have tons and tons of Maxtor drives in service, and only
> > one actually had a complete failure (verified by their utility, which is
> > present on some bootable CD I got called "UltimateBootDisk").
>
> Mike,
>
> When one of my drives fails I test it with the Maxtor Powermax tool -
> it's this tool that is confirming that the drive(s) is(are) dieing.
>
> The only saving grace is the three-year warranty.
>
> R.
> --
> http://robinbowes.com
>
> -
> 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
>
--
Derek Piper - derek.piper@gmail.com
http://doofer.org/
next prev parent reply other threads:[~2005-01-18 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 18:14 RAID5 drive failure, please verify my commands Gerd Knops
2005-01-16 20:34 ` Robin Bowes
2005-01-16 22:08 ` Gerd Knops
2005-01-16 21:25 ` Mike Hardy
2005-01-16 22:14 ` Gerd Knops
2005-01-16 23:13 ` Mike Hardy
2005-01-17 0:39 ` Mike Hardy
2005-01-17 23:53 ` Robin Bowes
2005-01-18 15:46 ` Derek Piper [this message]
2005-01-18 17:10 ` Guy
[not found] ` <eaa6dfe050118094248eb03ad@mail.gmail.com>
2005-01-18 17:42 ` Fwd: " Derek Piper
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=eaa6dfe050118074677f4bd6f@mail.gmail.com \
--to=derek.piper@gmail.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 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.