From: Stephen Satchell <list@satchell.net>
To: Michael Joy <mdj00b@acu.edu>
Cc: "'Nathan Scott'" <nathans@sgi.com>,
"'Nico Schottelius'" <nico-kernel@schottelius.org>,
"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: RE: another hard disk broken or xfs problems?
Date: Sat, 28 Feb 2004 13:43:06 -0800 [thread overview]
Message-ID: <1078004585.3347.14.camel@ssatchell1.pyramid.net> (raw)
In-Reply-To: <20040225231045.LJJM25915.lakemtao08.cox.net@nagasaki>
On Wed, 2004-02-25 at 15:10, Michael Joy wrote:
> One thing I've run into recently is that Hitachi drives come from the
> factory with bad sectors out of the box. If you run a full format on the
> drive checking for bad sectors the first time you use the drive, it will
> occasionally find an error, the format will die, and the next time you
> format nothing will be found.
>
> It's a symptom of Hitachi not properly QC'ing their drives by fully
> formatting them several times. The problem can reoccur over the first few
> days until the drive finds all the questionable bad sectors and reallocates
> backup sectors to cover for it.
It's not just Hitachi drives, either. I just purchased a NEW (not
reburbed) Maxtor 80-GB drive to replace a Fujitsu that finally reached
end of life, and found that I had to zero the drive before it would mkfs
properly. The command I used to make this happen is:
dd if=/dev/zero of=/dev/hdb bs=1M
I'm used to doing this because I've discovered that the refurb drives my
employer has been buying have been needing zeroing before use. I know
that's not as good as using a worst-case pattern specific to the drive,
but it's good enough to get the known bad sectors remapped at the start,
then let the drive discover other bad sectors as it goes. To that end,
the systems under my control run a weekly CRON job that looks something
like this:
/bin/nice -n 15 /bin/dd if=/dev/hda of=/dev/null bs=128k
/bin/nice -n 15 /bin/dd if=/dev/hdc of=/dev/null bs=128k
/bin/nice -n 15 /bin/dd if=/dev/sda of=/dev/null bs=128k
This ensures that all sectors are readable, regardless of file system
state, and relocates and reassigns those sectors that can be read in any
way.
I also have started installing smartmontools into all my systems, and
configuring them to e-mail me when a critical parameter changes -- I'm
getting tired of coming in to work and discovering that a hard drive has
finally bit the big one. (It doesn't help prevent a crisis, because a
thrown head is such a catastropic event, but it does help with
end-of-life discovery, so a disk change can be scheduled.)
next prev parent reply other threads:[~2004-02-28 21:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 22:00 Nico Schottelius
2004-02-25 22:34 ` Nathan Scott
2004-02-25 23:10 ` Michael Joy
2004-02-28 21:43 ` Stephen Satchell [this message]
2004-02-29 8:07 ` John Bradford
2004-02-25 23:49 ` Nico Schottelius
2004-02-26 3:27 ` Nathan Scott
2004-02-26 8:25 ` Nico Schottelius
2004-02-26 9:46 ` Nathan Scott
2004-02-26 19:26 ` Mike Fedyk
2004-02-27 5:53 ` Nathan Scott
2004-02-26 10:02 ` Rogier Wolff
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=1078004585.3347.14.camel@ssatchell1.pyramid.net \
--to=list@satchell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mdj00b@acu.edu \
--cc=nathans@sgi.com \
--cc=nico-kernel@schottelius.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
all inboxes | Powered by JetHome®