From: Phil Turmel <philip@turmel.org>
To: Sam Bingner <sam@bingner.com>
Cc: Gimpbully <gimpbully@gmail.com>,
"<linux-raid@vger.kernel.org>" <linux-raid@vger.kernel.org>
Subject: Re: array went wonky
Date: Tue, 30 Apr 2013 10:45:15 -0400 [thread overview]
Message-ID: <517FD8FB.7000006@turmel.org> (raw)
In-Reply-To: <71F985BA-11B9-45E8-A17B-03F9CB5C8F52@bingner.com>
On 04/30/2013 02:20 AM, Sam Bingner wrote:
> On Apr 29, 2013, at 4:33 PM, "Gimpbully" <gimpbully@gmail.com>
> wrote:
>> On Apr 13, 2013, at 7:20 AM, Sam Bingner <sam@bingner.com> wrote:
>>
>>> After that you can try to recreate the array with the proper
>>> order (sdc1, sdb1, sde1, missing, sda1) and copy data off or add
>>> the spare in again depending on if you were able to recover all
>>> the data wih GNU ddrescue.
>>
>>
>> What do you mean recreate? what's the specific command? something
>> like:
>> mdadm --create --assume-clean --level=5 --raid-devices=5 /dev/md127
>> /dev/sdc1 /dev/sdb1 /sdv/sde1 missing /dev/sda1
>
> Don't recreate it - I said the wrong thing... You want to do an
> assemble on them with force if possible... Recreate is last ditch and
> make sure you have another copy if you do the previous command in
> case it doesn't work right due to offsets etc...
>
> try:
> mdadm --stop /dev/md127
> mdadm --assemble --force /dev/md127 /dev/sd{c,b,e,a}1
Yes.
> If you DO need to recreate it, what you showed looks correct.
NO!
The OP has *not* shared sufficient information on the array members to
say that. Since it has "worked for years", the odds of an offset error
is *very* high. Chunk size defaults are also likely to be different.
*Complete* output of "mdadm -E" for the array members is needed before
any "--create" operation is attempted. Plus the distro info, kernel
version, and mdadm version .
Phil
next prev parent reply other threads:[~2013-04-30 14:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 5:41 array went wonky Gimpbully
2013-04-13 14:20 ` Sam Bingner
2013-04-13 15:46 ` Robin Hill
2013-04-13 16:09 ` John White
2013-04-30 2:33 ` Gimpbully
2013-04-30 6:20 ` Sam Bingner
2013-04-30 14:45 ` Phil Turmel [this message]
2013-04-30 14:48 ` Gimpbully
2013-05-01 18:59 ` Gimpbully
2013-05-02 14:18 ` Gimpbully
2013-05-02 14:29 ` Gimpbully
2013-05-03 6:47 ` Gimpbully
2013-05-03 14:24 ` Phil Turmel
2013-05-03 7:40 ` Robin Hill
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=517FD8FB.7000006@turmel.org \
--to=philip@turmel.org \
--cc=gimpbully@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=sam@bingner.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.