From: Phil Turmel <philip@turmel.org>
To: Digimer <lists@alteeve.ca>
Cc: linux-raid@vger.kernel.org
Subject: Re: Broken array, trying to assemble enough to copy data off
Date: Thu, 10 Oct 2013 12:36:03 -0400 [thread overview]
Message-ID: <5256D773.2010808@turmel.org> (raw)
In-Reply-To: <5256D3C4.5010109@alteeve.ca>
On 10/10/2013 12:20 PM, Digimer wrote:
>> Phil
>
> Ya, I have no plan at all to use these drives or the server they came
> from anymore. In fact, they've already been replaced. :)
That's good.
> I tried the --assemble --force (and --assemble --force --run) without
> success. It fails saying that sde2 thinks sdb2 has failed, leaving two
> dead members. If I try to start with just sd[bcd], it says that it has
> two drives and one spare, so still refuses to start.
Ok.
> Any other options/ideas? I'm not in any rush, so I am happy to test things.
Well, you have rock-solid knowledge of the device order and array
parameters. So a --create operation is the next step. Given that sdd2
is marked as spare, and therefore of unknown value, I'd leave it out.
mdadm --stop /dev/md1
mdadm --create --level=5 -n 4 --chunk=512 /dev/md1 \
/dev/sd{c,e,b}2 missing
(--assume-clean isn't needed when creating a degraded raid5)
The brace syntax is needed, not brackets, as the order matters.
After creation, use mdadm -E to verify the Data Offset is 2048. If not,
get a new version of mdadm that lets you specify it.
Only after that should you use "fsck -n" to verify your filesystem and
mount it.
HTH,
Phil
next prev parent reply other threads:[~2013-10-10 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 23:25 Broken array, trying to assemble enough to copy data off Digimer
2013-10-09 23:41 ` Digimer
2013-10-10 12:44 ` Phil Turmel
2013-10-10 16:20 ` Digimer
2013-10-10 16:36 ` Phil Turmel [this message]
2013-10-10 16:54 ` Digimer
2013-10-10 17:58 ` 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=5256D773.2010808@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lists@alteeve.ca \
/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).