From: David Greaves <david@dgreaves.com>
To: Leon Woestenberg <leon.woestenberg@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Multiple disk failure, but slot numbers are corrupt and preventing assembly.
Date: Tue, 24 Apr 2007 14:06:53 +0100 [thread overview]
Message-ID: <462E00ED.3050006@dgreaves.com> (raw)
In-Reply-To: <c384c5ea0704240544vd15e939kdf46bd75d341f30a@mail.gmail.com>
Leon Woestenberg wrote:
> David,
>
> thanks for all the advice so far.
No problem :)
> In first instance we were searching for ways to tell mdadm what we
> know about the array (through mdadm.conf) but from all advice we got
> we have to take the 'usual' non-syncing-recreate approach.
>
> We will try to make disk clones first. Will dd suffice or do I need
> something more fancy that maybe copes with source drive read errors in
> a better fashion?
ddrescue and dd_rescue are *much* better.
I favour the gnu ddrescue - it's much easier. But sometimes, on some kernels
with some hardware I've had kernel locks that dd_rescue (eventually, after many
minutes) times out from.
The RIP iso is a good place to start.
http://www.tux.org/pub/people/kent-robotti/looplinux/rip/
David
next prev parent reply other threads:[~2007-04-24 13:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 17:17 Multiple disk failure, but slot numbers are corrupt and preventing assembly Leon Woestenberg
2007-04-23 17:55 ` David Greaves
2007-04-24 7:04 ` Leon Woestenberg
2007-04-24 7:17 ` Leon Woestenberg
2007-04-24 8:32 ` David Greaves
2007-04-24 12:44 ` Leon Woestenberg
2007-04-24 13:06 ` David Greaves [this message]
2007-04-25 22:31 ` Bill Davidsen
2007-04-26 19:46 ` David Greaves
2007-04-26 23:36 ` Leon Woestenberg
2007-04-27 19:01 ` Bill Davidsen
2007-04-26 6:47 ` Neil Brown
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=462E00ED.3050006@dgreaves.com \
--to=david@dgreaves.com \
--cc=leon.woestenberg@gmail.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).