From: Mike Tran <mhtran@us.ibm.com>
To: linux-raid@vger.kernel.org
Cc: hn75@gmx.d
Subject: Re: recorvery from Raid5 multiple disk failture
Date: Fri, 16 Dec 2005 07:40:18 -0600 [thread overview]
Message-ID: <1134740418.17084.39.camel@star2.austin.ibm.com> (raw)
In-Reply-To: <200512161345.33159.hn75@gmx.de>
On Fri, 2005-12-16 at 06:45, Hendrik Naumann wrote:
> Hi
>
> I have a Linux-Software-Raid5 consisting of three partitions (hda2,
> hde2 and hdf2). After a failure of hdf I replaced the disk and added
> hdf2 into the raid again. During the resynchronization process hda
> broke down.
>
> I am not completely shure how much of the synchronization
> was already done, but I think it was quite at the end, because the
> gzipped dd-image of hdf2 and hde2 have very similar sizes.
>
> mdadm shows hde2 as a active, clean disk within the raid and hdf2 as a
> clean spare disk. In the Software-Raid-Howto it was stated that
> rewriting the superblocks (I suspect hdf2 to clean active) could be a
> possibility to regain some data from the Raid.
>
> How is this possible with mdadm? Or is there some other tool for
> manipulation the superblocks?
>
> Many thanks in advance
>
> Hendrik Naummann
>
> PS. Please add a CC hn75@gmx.de because up to now I am no subscriber
> to this list.
Since the recovery did not finish, I would do the followings:
mdadm --examine /dev/hde2 to display the raid5 configuration and note
the chunksize, parity layout, disks order,..
Recreate the array using mdadm -C with "missing" keyword
Mount the raid5 array read-only (hope that it will mount :)
--
Mike T.
prev parent reply other threads:[~2005-12-16 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 12:45 recorvery from Raid5 multiple disk failture Hendrik Naumann
2005-12-16 13:40 ` Mike Tran [this message]
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=1134740418.17084.39.camel@star2.austin.ibm.com \
--to=mhtran@us.ibm.com \
--cc=hn75@gmx.d \
--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).