From: drtebi@drtebi.com
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID1 always resyncs at boot???
Date: Sat, 29 Nov 2003 22:19:29 -0800 [thread overview]
Message-ID: <hp5iwh.92a5p7@mail.drtebi.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0311292206580.13188-100000@sweetums.bluetronic.net>
I ended up using Maxtor's "Powermax" program to check the drive, and it turned
out to be bad.
So I will return it and install another one. I am glad I was doing all this as
a "testing phase", before I actually deleted the data I was going to put on
the RAID.
Although I do have more trust in SCSI drives, only one of about 8 failed in my
"career", I will go ahead and get another IDE.
I bought it and it's "powermax" test failed--quite a bad reputation it should
be, however... they're cheap. So I will try again ;)
Thanks for everybody helping me! I really appreciate it.
DrTebi
--- Ricky Beam <jfbeam@bluetronic.net> wrote:
> On Thu, 27 Nov 2003 drtebi@drtebi.com wrote:
> >Trying to mark the drive faulty and add it back in (as described in the man
> >page) does not work. But I suppose that couldn't, since it's already
faulty.
>
> Of course, you could remove it completely (RAID doesn't even know it exists)
> and proceed. I would suggest this followed by a zero'ing (dd if=/dev/zero)
> of the suspect drive. If you still see errors, check it's warantee status.
>
> >However, if I do the "unplugged concert" again, and the RAID fails to
> >reconstruct again, what do you suggest? Try another power supply? Give it
up,
> >spend $200 more on SCSI drives? ...
>
> No, buy more cheap IDE drives. One chooses IDE because they are cheap
> with the understanding they will need to be replaced about once every one
> to two years. Your mileage may vary... I've been around computers for
> 20 years; I've never seen a SCSI drive bad right out of the box. I've
> seen dozens of still-born IDE drives. (and at least one that should never
> have been boxed. the low-level format of that drive failed, why they
> put a controller on it and sold it is beyond me.)
>
> Personally, when I care about the bits, I'll gladly pay more for drives
> that have actually been tested and certified to last more than a week.
> However, most people only see $$$ and don't see the headaches that
> come from lost data.
>
> --Ricky
>
>
>
prev parent reply other threads:[~2003-11-30 6:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 15:13 RAID1 always resyncs at boot??? drtebi
2003-11-27 23:14 ` Neil Brown
2003-11-27 23:29 ` drtebi
2003-11-28 0:00 ` Neil Brown
2003-11-28 4:33 ` drtebi
2003-11-28 4:40 ` Neil Brown
2003-11-28 4:57 ` drtebi
2003-11-30 3:31 ` Ricky Beam
2003-11-30 6:19 ` drtebi [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=hp5iwh.92a5p7@mail.drtebi.com \
--to=drtebi@drtebi.com \
--cc=jfbeam@bluetronic.net \
--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).