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 16:39:08 -0800 [thread overview]
Message-ID: <41EB092C.7080305@h3c.com> (raw)
In-Reply-To: <41EAF526.2000707@h3c.com>
Mike Hardy wrote:
> At that point, do a dd if=/dev/zero of=/dev/sda bs=4096 skip=(sector
> address divided by 8) count=1
I messed this command up, if you didn't catch it. You use skip to skip
on the input, you use that for reading in. When you're writing the zeros
out, you use "seek=..." to seek into the output to the right spot.
Its all in the bad block howto though - that's the definitive guide
-Mike
next prev parent reply other threads:[~2005-01-17 0:39 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
2005-01-17 0:39 ` Mike Hardy [this message]
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=41EB092C.7080305@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 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).