From: Mike Hardy <mhardy@h3c.com>
To: Guy <bugzilla@watkins-home.com>
Cc: 'Gordon Henderson' <gordon@drogon.net>,
"'T. Ermlich'" <pelegrine@gmx.net>,
linux-raid@vger.kernel.org
Subject: Re: Broken harddisk
Date: Sat, 29 Jan 2005 10:31:40 -0800 [thread overview]
Message-ID: <41FBD68C.4040701@h3c.com> (raw)
In-Reply-To: <200501291617.j0TGHG918839@www.watkins-home.com>
Guy wrote:
> For future reference:
>
> Everyone should do a nightly disk test to prevent bad blocks from hiding
> undetected. smartd, badblocks or dd can be used. Example:
> dd if=/dev/sda of=/dev/null bs=64k
>
> Just create a nice little script that emails you the output. Put this
> script in a nighty cron to run while the system is idle.
While I agree with your purpose 100% Guy, I respectfully disagree with
the method. If at all possible, you should use tools that access the
SMART capabilities of the device so that you get more than a read test -
you also get statistics on the various other health parameters the drive
checks some of which can serve fair warning of impending death before
you get bad blocks.
http://smartmontools.sf.net is the source for fresh packages there, and
smartd can be set up with a config file to do tests on any schedule you
like, emailing you urgent results as it gets them, or just putting
information of general interest in the logs that Logwatch picks up.
If you're drives don't talk SMART (older ones don't, it doesn't work
through all interfaces either) then by all means take Guy's advice. A
'dd' test is certainly valuable. But if they do talk SMART, I think its
better
-Mike
next prev parent reply other threads:[~2005-01-29 18:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 0:22 Broken harddisk T. Ermlich
2005-01-29 12:46 ` Gordon Henderson
2005-01-29 15:34 ` T. Ermlich
2005-01-29 15:56 ` Gordon Henderson
2005-01-29 16:19 ` Guy
2005-01-29 18:31 ` Mike Hardy [this message]
2005-01-29 23:30 ` berk walker
2005-02-01 15:02 ` Robin Bowes
2005-02-01 22:57 ` Luca Berra
2005-02-01 23:24 ` Robin Bowes
2005-01-29 16:47 ` T. Ermlich
2005-01-29 18:18 ` T. Ermlich
2005-01-29 23:12 ` T. Ermlich
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=41FBD68C.4040701@h3c.com \
--to=mhardy@h3c.com \
--cc=bugzilla@watkins-home.com \
--cc=gordon@drogon.net \
--cc=linux-raid@vger.kernel.org \
--cc=pelegrine@gmx.net \
/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;
as well as URLs for NNTP newsgroup(s).