The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Daniel Egger <degger@fhm.edu>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IBM Desktar disk problem?
Date: 09 Jul 2002 22:35:37 +0200	[thread overview]
Message-ID: <1026246937.931.17.camel@sonja.de.interearth.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1020709091938.27294A-100000@gatekeeper.tmr.com>

Am Die, 2002-07-09 um 15.23 schrieb Bill Davidsen:

> Not so. More people would mess up the firmware upgrade and destroy drives
> which were working (for them) without error than would be helped. Two old
> adages apply here, "first, do no harm," and "if it ain't broken don't fix
> it." I never upgrade firmware unless I have a problem or need a new
> capability, new firmware can have new bugs.

Granted, but since the older firmware *is* known to have some radical
bugs, the chance that the new one with just this bug fixed is more buggy
than the old one is close to zero. And since this upgrade is said to be 
a possible candidate to prevent most of the failures (which I doubt,
really), this would be the sensible way to go. However I do not see 
how an error corrupting the drive on a S.M.A.R.T. offline test could
possibly affect a drive in a system that doesn't even have S.M.A.R.T.
software installed.

So I stand by my claim that the latest IBM drives are piss-poor in
quality and the way IBM acts is irresponsible and unacceptable.

Depending on how they replace my broken (non-OEM) drives in the next
days (or weeks) I'll be deciding whether to go to court or not. In the
meantime I'll replace all remaining IBM drives by other brands and sell
the chunk on Ebay....

-- 
Servus,
       Daniel


  reply	other threads:[~2002-07-09 20:44 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
2002-07-05 16:57         ` Thunder from the hill
2002-07-09 13:23         ` Bill Davidsen
2002-07-09 20:35           ` Daniel Egger [this message]
  -- 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=1026246937.931.17.camel@sonja.de.interearth.com \
    --to=degger@fhm.edu \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@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