linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: maarten van den Berg <maarten@vbvb.nl>
To: linux-raid@vger.kernel.org
Subject: Re: Hard drive Reliability?
Date: Thu, 20 May 2004 01:44:31 +0200	[thread overview]
Message-ID: <200405200144.31418.maarten@vbvb.nl> (raw)
In-Reply-To: <40ABD186.5030905@atella.com>

On Wednesday 19 May 2004 23:28, Sevatio wrote:
> Måns Rullgård wrote:
> > John Lange <john.lange@bighostbox.com> writes:

> > I'd agree that drives are not as good as they used to be.  I recently
> > had a one year old Western Digital disk suddenly drop dead while
> > running.  Nothing could be recovered from it.  Shortly after that I
> > bought four Seagate Barracuda ATA disks, one of which was defective.
> > It would work flawlessly for an hour to a month, then shut itself
> > down.  Rebooting made it run for a while before it repeated.
> >
> > Compare this to the 1GB Quantum Fireball SCSI disk sitting in my
> > firewall.  It's been running 24/7 since some time around 1996.
> >
> >>Does anyone know of any web sites with statistics or test data?
> >
> > That would be interesting.
>
> I would also concur.  I had a Western Digital that failed after 10
> months.  Western Digital sent me another one that failed in exactly 10
> months again.  I didn't want to send it in to get yet another piece of
> WD junk.  So, lesson learned to stay away form WD drives; correct or not.

<aol mode>  Me too !  </aol mode>

My current vendor gives me a hard time everytime I order a new drive since 
they sell WD predominantly.  I still do not give in, no WD for me anymore.

Maarten

-- 
Yes of course I'm sure it's the red cable. I guarante[^%!/+)F#0c|'NO CARRIER

-
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

  parent reply	other threads:[~2004-05-19 23:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19 19:58 Hard drive Reliability? John Lange
2004-05-19 20:49 ` Måns Rullgård
2004-05-19 21:28   ` Sevatio
2004-05-19 22:02     ` John Lange
2004-05-19 22:42       ` jim
2004-05-19 22:26     ` Guy
2004-05-19 23:53       ` maarten van den Berg
2004-05-20  0:49         ` TJ Harrell
2004-05-20  1:13           ` berk walker
2004-05-20  6:39           ` Måns Rullgård
2004-05-19 23:44     ` maarten van den Berg [this message]
2004-05-19 22:04 ` berk walker
2004-05-19 22:18 ` Guy
2004-05-19 23:40   ` maarten van den Berg
2004-05-20  0:34     ` Guy
2004-05-20  1:46       ` John Lange
2004-05-20 22:27       ` Russ Price
2004-05-20 15:51     ` Sevatio
2004-05-20  4:39 ` Mark Hahn
2004-05-20  7:15   ` John Lange
2004-05-20 12:15     ` Mark Hahn
2004-05-20 13:26       ` jim
2004-05-20 13:31       ` John Lange
2004-05-20 14:20         ` Mark Hahn
2004-05-20 13:32       ` Tim Grant
2004-05-20 14:38         ` Robin Bowes
2004-05-22  5:15           ` Brad Campbell
2004-05-24 13:25             ` Frank van Maarseveen
2004-05-24 18:35               ` Brad Campbell
2004-05-24 22:38                 ` maarten van den Berg
  -- strict thread matches above, loose matches on Subject: below --
2004-05-20 13:54 Cress, Andrew R

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=200405200144.31418.maarten@vbvb.nl \
    --to=maarten@vbvb.nl \
    --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).