From: "Måns Rullgård" <mru@kth.se>
To: linux-raid@vger.kernel.org
Subject: Re: Hard drive Reliability?
Date: Wed, 19 May 2004 22:49:57 +0200 [thread overview]
Message-ID: <yw1xd650cfbe.fsf@ford.guide> (raw)
In-Reply-To: 1084996693.4021.8.camel@ws101.darkcore.net
John Lange <john.lange@bighostbox.com> writes:
> I have a few discussions recently with technical service people and we
> all come to the conclusion that Hard Drives are far less reliable than
> they used to be.
>
> Case in point, I have a 120G Maxtor drive in a server that began to fail
> less than 8 months into service. Major headache.
>
> I've heard similar stories from other people. I guy I know that sells
> both desktop and file server systems now says he now only builds
> motherboards with some kind of RAID 1 and dual drives because drives
> fail so often this saves loads of headaches. After a their system has
> died and they 'lost everything' people are more than willing to pay the
> extra $150 for redundancy.
>
> I know drive manufactures were sued recently in a class action for
> shipping drives which they knew were going to fail prematurely but that
> was a few years back.
>
> So what are other peoples feelings about drive reliability and are some
> brands better than others?
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.
--
Måns Rullgård
mru@kth.se
-
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
next prev parent reply other threads:[~2004-05-19 20:49 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 [this message]
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
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=yw1xd650cfbe.fsf@ford.guide \
--to=mru@kth.se \
--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).