From: Mike Hardy <mhardy@h3c.com>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 drive failure, please verify my commands
Date: Sun, 16 Jan 2005 15:13:42 -0800 [thread overview]
Message-ID: <41EAF526.2000707@h3c.com> (raw)
In-Reply-To: <F856C764-680B-11D9-9A87-00039363AEBE@bitart.com>
Gerd Knops wrote:
> Seems to be a whole slew of bad sectors, here is what the log says:
I typically get bad sectors in little mini-batches. Under a hundred -
typically 40 or so in one chunk. There are 8 sectors per block, and I
guess when a block goes, whatever took it out (some dust or something? a
bad alignment of metal in the media?) gets the blocks near it too.
Anyway, it still looks to me like its semi-normal. Definitely check out
the bad block howto and (after removing the drive from the array) try
doing a dd if=/dev/sda of=/dev/null bs=4096 skip=(whatever the sector is
divided by 8) count=1
You should see the read errors in the log then, that verifies that
you've got the right offset in the disk.
At that point, do a dd if=/dev/zero of=/dev/sda bs=4096 skip=(sector
address divided by 8) count=1
If you repeat the read after that block write, the read should succeed -
you've told the drive you don't need that data any more (you wrote into
the block) so it shouuld be able to reallocate
If you take that single-block idea, and expand it to the first block
address and a count= number that includes all the bad blocks, you should
clear them all
??
Or the drive is shot :-). Without a SMART self-test and a check of the
results where you can really interrogate the drive, its hard to say
Glad this helps though
-Mike
next prev parent reply other threads:[~2005-01-16 23:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 18:14 RAID5 drive failure, please verify my commands Gerd Knops
2005-01-16 20:34 ` Robin Bowes
2005-01-16 22:08 ` Gerd Knops
2005-01-16 21:25 ` Mike Hardy
2005-01-16 22:14 ` Gerd Knops
2005-01-16 23:13 ` Mike Hardy [this message]
2005-01-17 0:39 ` Mike Hardy
2005-01-17 23:53 ` Robin Bowes
2005-01-18 15:46 ` Derek Piper
2005-01-18 17:10 ` Guy
[not found] ` <eaa6dfe050118094248eb03ad@mail.gmail.com>
2005-01-18 17:42 ` Fwd: " Derek Piper
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=41EAF526.2000707@h3c.com \
--to=mhardy@h3c.com \
--cc=linux-raid@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.