From: jbradford@dial.pipex.com
To: devilkin-lkml@blindguardian.org (DevilKin)
Cc: linux-kernel@vger.kernel.org
Subject: Re: ide drive dying?
Date: Fri, 6 Sep 2002 16:36:49 +0100 (BST) [thread overview]
Message-ID: <200209061536.g86FaniW004326@darkstar.example.net> (raw)
In-Reply-To: <200209061713.51387.devilkin-lkml@blindguardian.org> from "DevilKin" at Sep 06, 2002 05:13:51 PM
> I've looked up these errors on the net, and as far as i can tell it means
> that the drive has some bad sectors at the given addresses and that it will
> probably die on me sooner or later.
>
> Can someone either confirm this to me or tell me what to do to fix it?
>
> The drive involved is an IBM-DTLA-307060, which has served me without
> problems now for about 2 years.
Have a look at:
http://csl.cse.ucsc.edu/smart.shtml
there you will find software for interrogating and monitoring the S.M.A.R.T. data available from your drive. It's a little late to start monitoring it, if the drive is already dying, but if, for example, it shows a lot of re-allocated sectors, or spin retries, you'll know something is wrong.
John.
next prev parent reply other threads:[~2002-09-06 15:24 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 [this message]
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
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=200209061536.g86FaniW004326@darkstar.example.net \
--to=jbradford@dial.pipex.com \
--cc=devilkin-lkml@blindguardian.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.