From: TJ <systemloc@earthlink.net>
To: linux-raid@vger.kernel.org
Subject: Re: Good news / bad news - The joys of RAID
Date: Thu, 2 Dec 2004 11:47:12 -0500 [thread overview]
Message-ID: <200412021147.12410.systemloc@earthlink.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0411201657570.19120-100000@coffee.psychology.mcmaster.ca>
> afaikt, the deathstar incident was actually bad firmware
> (didn't correctly flush data when hard powered off, resulting in
> blocks on disk with bogus ECC, which had to be considered bad from
> then on, even if the media was perfect.)
I do not think the deathstar incident was due to a firmware problem as you
describe at all. I had a lot of these drives fail, and I read as much as I
could find on the subject. The problem was most likely caused by the fact
that these drives used IBM's new glass substrate technology. This substrate
had heat expansion issues which caused the heads to misalign on tracks and
eventually cross write over tracks, corrupting data. The classic "click of
death" was the sound of the drive searching for a track repetitively. In some
cases a format would allow the drive to be used again, in many cases it would
not. It is my belief that formatting was inneffective at fixing the drive
because the cross writing probably hit some of the low level data, which the
drive cannot repair on a format.
next prev parent reply other threads:[~2004-12-02 16:47 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 21:06 Good news / bad news - The joys of RAID Robin Bowes
2004-11-19 21:28 ` Guy
2004-11-20 18:42 ` Mark Hahn
2004-11-20 19:37 ` Guy
2004-11-20 20:03 ` Mark Klarzynski
2004-11-20 22:17 ` Mark Hahn
2004-11-20 23:09 ` Guy
2004-12-02 16:47 ` TJ [this message]
2004-12-02 17:29 ` Stephen C Woods
2004-12-03 3:37 ` Mark Hahn
2004-12-03 4:16 ` Guy
2004-12-03 4:46 ` Alvin Oga
2004-12-03 5:24 ` Richard Scobie
2004-12-03 5:40 ` Konstantin Olchanski
2004-12-09 0:17 ` H. Peter Anvin
2004-11-20 23:30 ` Mark Hahn
2004-11-20 19:40 ` David Greaves
2004-11-21 4:33 ` Guy
2004-11-21 1:01 ` berk walker
2004-11-23 19:10 ` H. Peter Anvin
2004-11-23 20:03 ` Guy
2004-11-23 21:18 ` Mark Hahn
2004-11-23 23:02 ` Robin Bowes
2004-11-24 0:33 ` Guy
2004-11-24 1:45 ` berk walker
2004-11-24 2:00 ` H. Peter Anvin
2004-11-24 8:01 ` Good news / bad news - The joys of hardware Guy
2004-11-24 8:57 ` Robin Bowes
2004-11-19 21:42 ` Good news / bad news - The joys of RAID Guy
2004-11-28 13:15 ` Robin Bowes
2004-11-30 2:05 ` Neil Brown
2004-12-01 3:34 ` Doug Ledford
2004-12-01 11:50 ` Robin Bowes
2004-11-19 21:58 ` Gordon Henderson
[not found] <037401c4cf3b$ee75bc90$030a0a0a@musicroom>
2004-11-21 4:33 ` Guy
2004-11-22 14:13 ` Yu Chen
2004-11-22 14:34 ` Gordon Henderson
2004-11-22 17:51 ` Guy
2004-11-22 23:26 ` Gordon Henderson
2004-11-22 23:48 ` Guy
2004-11-23 0:09 ` Måns Rullgård
2004-11-23 15:33 ` Gordon Henderson
2004-11-23 0:17 ` berk walker
2004-11-23 9:24 ` Robin Bowes
2004-11-23 12:31 ` Bob Hillegas
2004-11-23 13:00 ` berk walker
[not found] <Pine.LNX.4.44.0411201655400.19120-100000@coffee.psychology.mcmaster.ca>
2004-11-21 21:28 ` Mark Klarzynski
2004-11-21 21:58 ` Mark Hahn
2004-11-22 6:29 ` Mikael Abrahamsson
[not found] <04Nov26.172857est.30052@gpu.utcc.utoronto.ca>
2004-11-26 22:41 ` Robin Bowes
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=200412021147.12410.systemloc@earthlink.net \
--to=systemloc@earthlink.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).