From: Theodore Tso <tytso@mit.edu>
To: Bruce Allen <ballen@gravity.phys.uwm.edu>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
Jan-Benedict Glaw <jbglaw@lug-owl.de>,
apiszcz@solarrain.com,
smartmontools-support@lists.sourceforge.net,
Remy Card <Remy.Card@linux.org>,
linux-kernel@vger.kernel.org,
"Theodore Ts'o" <tytso@alum.mit.edu>,
David Beattie <dbeattie@softhome.net>
Subject: Re: [smartmontools-support] The Death and Diagnosis of a Dying Hard Drive - Is S.M.A.R.T. useful?
Date: Sun, 11 Jun 2006 08:59:29 -0400 [thread overview]
Message-ID: <20060611125929.GA8438@thunk.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0606102212060.17718@trinity.phys.uwm.edu>
On Sat, Jun 10, 2006 at 10:15:59PM -0500, Bruce Allen wrote:
> I am surprised that the extended self-test does not detect the bad sectors
> on your disk. Our experience is that the typical SYSLOG 'seek failure'
> error messages do correlate very well with the failing LBAs found via
> SMART self-tests.
My guess is that it didn't detect the errors for the same reason that
a read-only scan using badblocks didn't detect the problems, while a
read/write scan did.
What *did* surprise me a little is that after the bad block had been
detected by badblocks -w and was remapped by the disk drive, but
before it had been forcibly rewritten (so that now reads of the block
would return errors to the OS) that the extended self-test didn't
return an error. I guess as far as the disk was concerned, the block
had been remapped, so everything was OK.
The real question though is whether the disk continues to work OK from
this point forward, or whether it is a prelude to an ever-increasing
number of bad blocks. If it is the latter, and S.M.A.R.T. still
didn't give any warning, then it would certainly be an indictment of
that particular manufacturer's S.M.A.R.T. implementation.
- Ted
next prev parent reply other threads:[~2006-06-11 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 10:23 The Death and Diagnosis of a Dying Hard Drive - Is S.M.A.R.T. useful? Justin Piszcz
2006-06-10 10:51 ` Jan-Benedict Glaw
2006-06-10 10:59 ` Justin Piszcz
2006-06-11 3:15 ` [smartmontools-support] " Bruce Allen
2006-06-11 12:59 ` Theodore Tso [this message]
2006-06-11 16:22 ` Bruce Allen
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=20060611125929.GA8438@thunk.org \
--to=tytso@mit.edu \
--cc=Remy.Card@linux.org \
--cc=apiszcz@solarrain.com \
--cc=ballen@gravity.phys.uwm.edu \
--cc=dbeattie@softhome.net \
--cc=jbglaw@lug-owl.de \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=smartmontools-support@lists.sourceforge.net \
--cc=tytso@alum.mit.edu \
/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.