From: john <john4lists@gmail.com>
To: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
Cc: linux-raid@vger.kernel.org
Subject: Re: emergency recovery
Date: Thu, 10 Apr 2008 12:09:28 -0400 [thread overview]
Message-ID: <47FE3BB8.5010300@gmail.com> (raw)
In-Reply-To: <ftkclu$t6f$1@ger.gmane.org>
Mario 'BitKoenig' Holbe wrote:
> jeff sacksteder <jsacksteder@gmail.com> wrote:
>
>> It is essential that I not make this worse than it is. Is the
>>
>
> Well, this in mind the first thing you should do is taking raw images
> from all the component drives before even thinking about any kind of
> recovery.
Thanks. I'll try to use a fresh drive with a ddrescue(ed) image on it
with the corrupt drive. I may do the same with the stale(evms
terminology?) drive.
Do I need to dd image all 6 dives somewhere to be safe?
I want to force assemble 4 good +1stale +1 corrupt to a degraded raid5
array with 5 good +1 corrupt. I could avoid dd imaging the 4 good
drives if I could mark these 4 drives read-only. Is that possible or
with the forced assembly does it need to write new md meta data to all
the drives and therefore need to modify these drives?
Tell me to start a new thread if this doesn't pertain to the OP's
question.
next prev parent reply other threads:[~2008-04-10 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 6:29 emergency recovery jeff sacksteder
2008-04-10 6:38 ` Mario 'BitKoenig' Holbe
2008-04-10 13:08 ` john
2008-04-10 13:17 ` Mario 'BitKoenig' Holbe
2008-04-10 16:09 ` john [this message]
2008-04-10 23:13 ` jeff sacksteder
2008-04-10 23:45 ` jeff sacksteder
2008-04-11 14:35 ` Bill Davidsen
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=47FE3BB8.5010300@gmail.com \
--to=john4lists@gmail.com \
--cc=Mario.Holbe@TU-Ilmenau.DE \
--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).