From: Daniel Egger <degger@fhm.edu>
To: venom@sns.it
Cc: linux-kernel@vger.kernel.org
Subject: Re: IBM Desktar disk problem?
Date: 05 Jul 2002 14:50:20 +0200 [thread overview]
Message-ID: <1025873421.16768.20.camel@sonja.de.interearth.com> (raw)
In-Reply-To: <Pine.LNX.4.43.0207051217160.8506-100000@cibs9.sns.it>
Am Fre, 2002-07-05 um 12.27 schrieb venom@sns.it:
> Has anyone had a similar experience with this kind of disks?
I suspect it's the usual IBM crap phenomenon; three discs died in the
last two weeks (1 DTLA and 2 IC35) here, that's a whooping 33% of the
IBM drives I use. No TCQ involved and on one not even Linux and the
other two had two different stable 2.4 kernels.
<problemdescription>
The drives started developping bad sectors, one of the drives to a
degree over 10% of the total amount sectors; according to IBM it's
a "software failure" of the device driver and can be fixed by what
they call "Erase Disc" i.e. a lowlevel format. Needless to say I
tried this on one drive and the problems started again one week
later. The drives are between 3 and 12 months old and are now on
their way to IBM.
</problemdescription>
<advise>
Buy decent drives, then get DriveFitnessTest (DFT) from their website
and check the harddrives, note the TRC number, request an RMA on their
website and ship the drives as soon as possible to IBM. Wait for the
replacement drives and sell them ASAP on Ebay to some freaks who don't
give a dime about data security.
</advise>
--
Servus,
Daniel
next prev parent reply other threads:[~2002-07-05 12:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-05 10:27 IBM Desktar disk problem? venom
2002-07-05 10:40 ` Jens Axboe
2002-07-05 10:50 ` Anton Altaparmakov
2002-07-05 12:36 ` Jens Axboe
2002-07-05 13:27 ` venom
2002-07-05 14:15 ` Tomas Konir
2002-07-05 14:26 ` Jens Axboe
2002-07-05 14:48 ` Tomas Konir
2002-07-05 15:38 ` Daniel Egger
2002-07-05 15:42 ` Tomas Konir
2002-07-05 20:11 ` Matthias Andree
2002-07-05 20:21 ` Tomas Konir
2002-07-05 20:39 ` Matthias Andree
2002-07-05 20:50 ` Tomas Konir
2002-07-05 22:58 ` Matthias Andree
[not found] ` <Pine.LNX.4.44L0.0207052216410.3293-100000@moje.ich.vabo.cz >
2002-07-05 21:05 ` Anton Altaparmakov
2002-07-05 21:08 ` Tomas Konir
2002-07-07 12:46 ` Timo Jantunen
2002-07-11 15:14 ` Thunder from the hill
2002-07-10 16:15 ` Bill Shirley
2002-07-10 17:09 ` Matthias Andree
2002-07-05 23:00 ` Mohammad A. Haque
2002-07-05 12:50 ` Daniel Egger [this message]
2002-07-05 14:03 ` Thunder from the hill
2002-07-05 13:50 ` Zwane Mwaikambo
2002-07-05 15:18 ` Bartlomiej Zolnierkiewicz
2002-07-05 16:58 ` Thunder from the hill
2002-07-05 15:23 ` Daniel Egger
2002-07-05 20:23 ` Matthias Andree
[not found] ` <Pine.LNX.4.44.0207050801190.10105-100000@hawkeye.luckynet. adm>
2002-07-05 14:29 ` Anton Altaparmakov
2002-07-05 15:32 ` Daniel Egger
2002-07-05 16:57 ` Thunder from the hill
2002-07-09 13:23 ` Bill Davidsen
2002-07-09 20:35 ` Daniel Egger
-- strict thread matches above, loose matches on Subject: below --
2002-07-05 15:04 Randal, Phil
2002-07-05 18:01 Voluspa
2002-07-05 18:05 ` Bartlomiej Zolnierkiewicz
2002-07-05 18:19 ` Voluspa
2002-07-11 19:29 Iain Thomas
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=1025873421.16768.20.camel@sonja.de.interearth.com \
--to=degger@fhm.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=venom@sns.it \
/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