From: Cry <cry_regarder@yahoo.com>
To: linux-raid@vger.kernel.org
Subject: Re: Two Drive Failure on RAID-5
Date: Thu, 22 May 2008 00:05:22 +0000 (UTC) [thread overview]
Message-ID: <loom.20080522T000506-188@post.gmane.org> (raw)
In-Reply-To: 09ed01c8bb83$ec3f7230$9300a8c0@dcccs
Janos Haar <janos.haar <at> netcenter.hu> writes:
> Cry i only have this idea:
> dd_rescue -v -m 128k -r /dev/source -S 128k superblock.bin
> losetup /dev/loop0 superblock.bin
> mdadm --build -l linear --raid-devices=2 /dev/md1 /dev/sdg1 /dev/loop0
Janos,
The correct information should already be in /dev/sdg1 since I copied the entire
/dev/sda there (probably overwrote stuff in /dev/sdg2 since /dev/sda was 160K
bigger than /dev/sdg1).
This means I the superblock should already be there at the start of /dev/sdg1.
so the steps above should result in two superblocks being stacked back to back?
should I use an losetup offset into /dev/sdg1 to get to the real data and bypass
the MBR copied in from /dev/sda? I am a bit confuse don how these things are
laid out.
Where on the disk does the information printed from mdadm -E /dev/sda and mdadm
-E /dev/sdg1 come from?
Thanks!
Cry
next prev parent reply other threads:[~2008-05-22 0:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 22:49 Two Drive Failure on RAID-5 Cry
2008-05-20 7:37 ` David Greaves
2008-05-20 15:32 ` Cry
2008-05-20 17:18 ` David Lethe
2008-05-20 19:01 ` Cry
2008-05-20 20:09 ` David Lethe
2008-05-20 23:11 ` Keith Roberts
2008-05-20 19:40 ` Janos Haar
2008-05-20 17:27 ` David Lethe
2008-05-20 19:28 ` Brad Campbell
2008-05-20 9:14 ` David Greaves
2008-05-20 12:17 ` Janos Haar
2008-05-21 14:14 ` Cry
2008-05-21 20:15 ` David Greaves
2008-05-21 20:47 ` Janos Haar
2008-05-21 21:21 ` Cry
2008-05-22 8:38 ` David Greaves
2008-05-31 9:27 ` Cry
2008-05-22 0:05 ` Cry [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-21 0:24 Re: " David Lethe
2008-05-22 14:42 ` Ric Wheeler
2008-05-22 16:16 ` David Lethe
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=loom.20080522T000506-188@post.gmane.org \
--to=cry_regarder@yahoo.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).