public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Niehusmann <jan@gondor.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: IDE error on 2.4.17
Date: Wed, 27 Feb 2002 19:47:58 +0100	[thread overview]
Message-ID: <20020227184758.GA9260@gondor.com> (raw)
In-Reply-To: <20020227102544.GA3226@codepoet.org> <E16g5YG-0004gk-00@the-village.bc.nu>
In-Reply-To: <E16g5YG-0004gk-00@the-village.bc.nu>

On Wed, Feb 27, 2002 at 02:59:28PM +0000, Alan Cox wrote:
> This is the wrong approach. That information is available properly if and
> when the vendors install the smart utilities

Doesn't necessarily help. I recently saw a hard drive which made funny
noises and got really slow reading some parts of the drive (~30MB/s on
some parts, ~300kB/s on others), but ide-smart didn't report failed
tests. Two days later the drive was dead...

It was an IBM 60GB drive, but I don't remember the exact type. It
called itself "IC35L060AVER07-0".

Jan


  reply	other threads:[~2002-02-27 18:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 17:38 IDE error on 2.4.17 Simon Turvey
2002-02-26 17:58 ` André Dahlqvist
2002-02-26 18:20 ` Mohammad A. Haque
2002-02-26 18:27 ` Alan Cox
2002-02-26 18:50   ` Simon Turvey
2002-02-26 19:01     ` David Rees
2002-02-26 19:12       ` Simon Turvey
2002-02-26 20:48         ` Chris Friesen
2002-02-26 19:10     ` Alan Cox
2002-02-26 19:09       ` Simon Turvey
2002-02-26 20:03     ` Hans-Christian Armingeon
2002-02-26 20:05     ` Skip Ford
2002-02-27  9:47     ` Vojtech Pavlik
2002-02-27 10:25       ` [PATCH] " Erik Andersen
2002-02-27 14:59         ` Alan Cox
2002-02-27 18:47           ` Jan Niehusmann [this message]
2002-02-27 18:53             ` Andre Hedrick
2002-02-27 19:26               ` Jan Niehusmann
2002-02-27 19:54             ` Chris Friesen

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=20020227184758.GA9260@gondor.com \
    --to=jan@gondor.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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