From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: smartmontools-support@lists.sourceforge.net,
Remy Card <Remy.Card@linux.org>,
"Theodore Ts'o" <tytso@alum.mit.edu>,
David Beattie <dbeattie@softhome.net>,
linux-kernel@vger.kernel.org, apiszcz@solarrain.com
Subject: Re: The Death and Diagnosis of a Dying Hard Drive - Is S.M.A.R.T. useful?
Date: Sat, 10 Jun 2006 12:51:41 +0200 [thread overview]
Message-ID: <20060610105141.GE30775@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0606100615500.15475@p34.internal.lan>
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
On Sat, 2006-06-10 06:23:32 -0400, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
> SUMMARY:
> I pose the following question in the subject, as over the years running
> smartd and having failed disks, I have always first been alerted of bad
> sectors and such through dmesg or logcheck. Even with a bad disk I
> currently have, smartd does not pickup any errors, except those with the
> kernel writes to syslog.
What do
smartctl -H
smartctl --all
tell you?
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-06-10 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 10:23 Justin Piszcz
2006-06-10 10:51 ` Jan-Benedict Glaw [this message]
2006-06-10 10:59 ` Justin Piszcz
2006-06-11 3:15 ` [smartmontools-support] " Bruce Allen
2006-06-11 12:59 ` Theodore Tso
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=20060610105141.GE30775@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=Remy.Card@linux.org \
--cc=apiszcz@solarrain.com \
--cc=dbeattie@softhome.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®