From: Daniel Egger <degger@fhm.edu>
To: Anton Altaparmakov <aia21@cantab.net>
Cc: Thunder from the hill <thunder@ngforever.de>,
venom@sns.it, linux-kernel@vger.kernel.org
Subject: Re: IBM Desktar disk problem?
Date: 05 Jul 2002 17:32:27 +0200 [thread overview]
Message-ID: <1025883147.17269.24.camel@sonja.de.interearth.com> (raw)
In-Reply-To: <5.1.0.14.2.20020705152010.00aa2af0@pop.cus.cam.ac.uk>
Am Fre, 2002-07-05 um 16.29 schrieb Anton Altaparmakov:
> Um, the solution is already known. Upgrade the firmware on the drive, low
> level format if the drive thinks there are bad sectors, and be happy. At
> least it worked for me...
> The very first question when making a support call for my broken deathstar
> was "Have you installed the firmware update?" "No." "Download it here and
> install, come back if it still doesn't work."
> I never thought it would work but it did! It seems there is something wrong
> in the firmware the drives are shipped with and some suppliers obviously
> know this considering my experience... When I was running the DFT test
> utility it was telling me my drive is broken and needs to be returned.
> After the firmware update the same test utility passed all tests repeatedly!
This is unacceptable; if my problem is really fixable by a firmware
upgrade IBM should have pushed this very upgrade publically after they
started to learn about the problem. Saying "Hey, BTW: if you had this
firmware version you would never have experienced your data loss" is
a very strong argument to never buy any IBM hardware again.
Still, the techsupport insisted on a software problem and didn't mention
a firmware upgrade; up to now I didn't even knew such a thing exists.
And letting customers lowlevel-format a drive, restore their data,
and experience the same problem again a week later is anything but
professional.
Though the timespan makes me curious: Why is there a magnitude
difference in runtime between the first problem on a fresh drive
and after a lowlevel format?
--
Servus,
Daniel
next prev parent reply other threads:[~2002-07-05 15:35 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
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 [this message]
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=1025883147.17269.24.camel@sonja.de.interearth.com \
--to=degger@fhm.edu \
--cc=aia21@cantab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder@ngforever.de \
--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