From: Steve Fairbairn <steve@fairbairn-family.com>
To: Linux-Raid <linux-raid@vger.kernel.org>
Cc: Stefan Heinrichsen <gelbemauer@gmx.de>
Subject: Re: Recovering RAID-5 from images
Date: Mon, 10 Nov 2008 10:06:39 +0000 [thread overview]
Message-ID: <491807AF.7040508@fairbairn-family.com> (raw)
Stefan Heinrichsen wrote:
> Hello,
>
> I have a RAID-5 with 3 devices. One disked failed and I added a new one. During sync a second disc failed. This second "Disc" is a RAID-0 consisting of to 120GB IDE Discs. I handled to dump an image of both disc with ddrescue. Only a few kilobytes of the broken disk could not been read (some where in the middle of the disc).
> For my recovering experiments I made an Image of the remaining disc of the RAID-5 (/dev/loop3). No I tried to assemble the both RAIDs using loopbackdevice. The RAID-0 (/dev/md0) started without any problems. But the RAID-5 is not starting. It seems like both discs are marked as spare (see below).
>
I'm no md/mdadm expert, but I suspect you first need to stop the
/dev/md0 and restart it as /dev/md1 (I hope you can do that). The
reason I would do this is that the examines of the array elements you
sent us show that what you have now as /dev/md0 was /dev/md1.
Then you need to force the assembly of the array with just the 2
'working' discs (/dev/loop3 && /dev/md1)
eg. (PLEASE check these with someone else before using them)...
mdadm --stop /dev/d0
mdadm --assemble /dev/md1 <component devices)
mdadm --assemble /dev/<dev> /dev/loop3 /dev/md1 --force
The --force will tell it to ignore that fact that /dev/md1 was marked as
failed and insert it anyway.
Hope this helps,
Steve.
PS. Sorry for repeat send. I forgot to include the list address.
next reply other threads:[~2008-11-10 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 10:06 Steve Fairbairn [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-09 23:10 Recovering RAID-5 from images Stefan Heinrichsen
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=491807AF.7040508@fairbairn-family.com \
--to=steve@fairbairn-family.com \
--cc=gelbemauer@gmx.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).