From: Phil Turmel <philip@turmel.org>
To: Dave Gomboc <dave_gomboc@acm.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid10 recovery assistance requested
Date: Sun, 22 Sep 2013 23:51:14 -0400 [thread overview]
Message-ID: <523FBAB2.7070506@turmel.org> (raw)
In-Reply-To: <CA+dwz-31yG3Y4xzmUoiMNtLw=q1pE_GTyNqSk5WBAsGDCGT9iw@mail.gmail.com>
On 09/22/2013 11:34 PM, Dave Gomboc wrote:
>> If you'll generate the following for each member, we'll see what we can do:
>>
>> dd if=/dev/sdX1 bs=512 skip=2048 count=16 2>/dev/null |hexdump -C
>> dd if=/dev/sdX1 bs=512 skip=3072 count=16 2>/dev/null |hexdump -C
Ok. I can't determine how the superblocks ended up the way they did,
but the first two chunks appear to follow the proper patterns.
I think you're best bet is to disconnect two of the drives, leaving one
that identifies as "0" and one that identifies as "3".
Then use "mdadm -Af /dev/mdX /dev/sdY1 /dev/sdZ1"
The "-f" will force the assembly without regard to the event counts.
Then you can take a backup. Finally you can add devices as "new" ones
to rebuild back to full redundancy. (Fix your timeouts before
attempting the latter.)
Phil
next prev parent reply other threads:[~2013-09-23 3:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 3:30 raid10 recovery assistance requested Dave Gomboc
2013-09-19 3:20 ` Dave Gomboc
2013-09-19 4:29 ` Stan Hoeppner
2013-09-20 5:29 ` Dave Gomboc
2013-09-22 17:15 ` Dave Gomboc
2013-09-22 21:52 ` Phil Turmel
2013-09-22 22:45 ` Dave Gomboc
2013-09-22 23:04 ` Dave Gomboc
2013-09-22 23:25 ` Phil Turmel
[not found] ` <CA+dwz-0eskPSQ44v0vgwfjwRpTbQaokQ3Q258Em1W2eRi1SO4w@mail.gmail.com>
2013-09-23 2:54 ` Phil Turmel
2013-09-23 3:19 ` Dave Gomboc
2013-09-23 3:27 ` Phil Turmel
2013-09-23 3:34 ` Dave Gomboc
2013-09-23 3:51 ` Phil Turmel [this message]
2013-09-23 4:04 ` Dave Gomboc
2013-09-23 4:12 ` Phil Turmel
2013-09-23 4:55 ` Dave Gomboc
2013-09-23 5:07 ` Dave Gomboc
2013-09-23 5:19 ` Adam Goryachev
2013-09-23 12:32 ` Phil Turmel
2013-09-23 12:57 ` Dave Gomboc
2013-09-24 0:29 ` Adam Goryachev
2013-09-24 5:55 ` Dave Gomboc
2013-09-28 15:47 ` Dave Gomboc
2013-09-28 16:01 ` Phil Turmel
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=523FBAB2.7070506@turmel.org \
--to=philip@turmel.org \
--cc=dave_gomboc@acm.org \
--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).