public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jbradford@dial.pipex.com
To: degger@fhm.edu (Daniel Egger)
Cc: linux-kernel@vger.kernel.org
Subject: Re: ide drive dying?
Date: Sat, 7 Sep 2002 14:08:53 +0100 (BST)	[thread overview]
Message-ID: <200209071308.g87D8sii000799@darkstar.example.net> (raw)
In-Reply-To: <1031401883.12089.41.camel@sonja.de.interearth.com> from "Daniel Egger" at Sep 07, 2002 02:31:23 PM

> > The tests showed bad sectors, i'm currently running a disk erase.
> 
> This is exactly the mistake I've been meaning to warn you of.
> The disk will corrupt sooner or later again and you'll have to go
> through all the torture (possible backup/restore, missing data) again
> and if you're unlucky (which is quite possible with your frequency of
> use) the warranty is void until the problems appear the next time.

There are two separate issues here, though:

* Buggy firmware
* Unreliable media

We have confirmed, (I believe), that the drive did have the buggy firmware.  We do not know yet whether the media is defective or not, but we do know that the drives are not the best in the world.

Alan also confirmed that the errors were direct from the device, and so it is not a kernel bug.

However, I raise the question of whether the new kernel version caused different access patterns to the device, and showed up the firmware bug that was there all the time.  Or maybe the compilation of the new kernel thrashed the disk and showed up the firmware bug.  If the machine has been on for some time, (months), doing not very much, maybe a lot of disk data was cached in RAM, and the kernel compile caused it to be re-read from disk, showing up media defects.

I was hoping that he would actually post the output of:

smartctl -a /dev/hda?

because that tells you all sorts of things, like, for example, reallocated sector count, and calibration retry count.

Obviously, it is not a good idea to use the drive for anything important until it has been tested in a non-critical application first.

Besides, you *do* backup, don't you?  (Or do what Linus suggested a while ago, and upload your stuff to an ftp site that is mirrored worldwide.)

I don't see the point of returning a disk that turns out not to be faulty after the firmware upgrade, for replacement under the warranty, even if it qualifies for a warranty replacement, (which it shouldn't do), because you might be exchanging a good disk for a bad disk.

John.

  reply	other threads:[~2002-09-07 12:57 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-06 15:13 ide drive dying? DevilKin
2002-09-06 15:26 ` Mike Dresser
2002-09-06 15:39   ` Alan Cox
2002-09-06 15:42     ` Mike Dresser
2002-09-06 16:14       ` Billy Harvey
2002-09-06 16:41         ` Mike Dresser
2002-09-06 18:00         ` jbradford
2002-09-06 17:58           ` Mike Dresser
2002-09-06 15:44   ` Richard B. Johnson
2002-09-06 16:19     ` Craig Ruff
2002-09-06 17:28   ` Daniel Egger
2002-09-06 15:36 ` jbradford
2002-09-06 15:55   ` DevilKin
2002-09-06 17:22     ` jbradford
2002-09-06 19:22       ` DevilKin
2002-09-07  9:30         ` Anders Fugmann
2002-09-07  9:37           ` Udo A. Steinberg
2002-09-07 15:54           ` Holger Lubitz
2002-09-07 16:31             ` jbradford
2002-09-07 12:31         ` Daniel Egger
2002-09-07 13:08           ` jbradford [this message]
2002-09-07 13:50             ` Daniel Egger
2002-09-07 15:02               ` jbradford
2002-09-07 20:19                 ` Daniel Egger
2002-09-07 20:41                   ` jbradford
2002-09-07 21:41                     ` Alan Cox
2002-09-07 21:41                   ` Alan Cox
2002-09-07 22:00                     ` jbradford
2002-09-07 23:19                       ` David Forrest
2002-09-08 10:56                         ` Henning P. Schmiedehausen
2002-09-08 14:14                           ` jbradford
2002-09-09 21:59                             ` Alan Cox
2002-09-07 22:05                   ` Andre Hedrick
2002-09-07  7:08     ` Andre Hedrick
2002-09-06 15:37 ` mbs
2002-09-06 15:54   ` Alan Cox
2002-09-06 15:38 ` Alan Cox
2002-09-06 17:33   ` Daniel Egger
2002-09-06 20:31     ` Alan Cox
2002-09-06 15:44 ` mbs
2002-09-06 17:46 ` mbs
2002-09-06 20:32   ` Alan Cox
2002-09-07 12:34     ` Daniel Egger
2002-09-07  7:02 ` Andre Hedrick
2002-09-07  7:42   ` jbradford
2002-09-07  7:50     ` Andre Hedrick
  -- strict thread matches above, loose matches on Subject: below --
2002-09-06 20:40 Hell.Surfers
2002-09-06 21:01 ` Alan Cox
2002-09-07  1:02   ` Jason L Tibbitts III
     [not found] <Pine.LNX.4.33.0209062017230.14523-100000@coffee.psychology.mcmaster.ca>
2002-09-07  6:09 ` jbradford
2002-09-08  0:02 Dieter Nützel
2002-09-08 17:42 ` jbradford
2002-09-09  1:31   ` Nuitari
2002-09-08 19:27     ` Ed Sweetman
2002-09-08 20:11       ` jbradford
2002-09-09  2:37         ` Nuitari
2002-09-09 12:26   ` Joachim Breuer
2002-09-09 18:17   ` Thunder from the hill
2002-09-09 18:55     ` Mike Dresser
2002-09-10 12:48   ` Ookhoi
2002-09-10 13:59     ` Mike Dresser
2002-09-10 14:56       ` jbradford
2002-09-10 15:21         ` Mike Dresser
2002-09-10 15:29           ` Larry McVoy
2002-09-10 20:21     ` Andre Hedrick

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=200209071308.g87D8sii000799@darkstar.example.net \
    --to=jbradford@dial.pipex.com \
    --cc=degger@fhm.edu \
    --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