From: "NeilBrown" <neilb@suse.de>
To: Erik Boettcher <tehfoo@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid 5 Recovery
Date: Mon, 29 Dec 2008 08:31:13 +1100 (EST) [thread overview]
Message-ID: <0751481ab32bd9084154902b6ca31e9f.squirrel@neil.brown.name> (raw)
In-Reply-To: <125ed8800812281013t59a3dc8cte44091d262cb8905@mail.gmail.com>
On Mon, December 29, 2008 5:13 am, Erik Boettcher wrote:
> ---------- Forwarded message ----------
> From: Erik Boettcher <tehfoo@gmail.com>
> Date: Sun, Dec 28, 2008 at 1:04 PM
> Subject: Re: Raid 5 Recovery
> To: Dylan Distasio <interzone@gmail.com>
>
>
> On Sun, Dec 28, 2008 at 1:02 PM, Erik Boettcher <tehfoo@gmail.com> wrote:
>> On Sun, Dec 28, 2008 at 10:53 AM, Dylan Distasio <interzone@gmail.com>
>> wrote:
>>> Have you tried assembling the array degraded to see if you can force
>>> it without sdd3? I don't know if this is the best solution, but if
>>> that works, you can then readd sdd3 and have the array rebuild.
>>
>> I tried forcing the assembly without sdd3, and it complains about sde3!
>>
>> I find it interesting that before the first command sdc3 failed but
>> now it's not the fault point....
>>
>
> I guess I should specify how it complains: the exact same error
> message but sde3 instead.
Yes, specifics are good. I'm afraid I need a few more though.
mdadm -Esvvv
and
dmesg | tail -20
after the failed --assemble attempt would be a good start.
NeilBrown
>
> mack ~ # mdadm -A --force --no-degraded /dev/md0 /dev/sd{a,b,c,e}3
> mdadm: superblock on /dev/sde3 doesn't match others - assembly aborted
>
> eek, and I tried with the first 3 hdds and got this:
> mack ~ # mdadm -A --force --no-degraded /dev/md0 /dev/sd{a,b,c}3
> mdadm: clearing FAULTY flag for device 2 in /dev/md0 for /dev/sdc3
> mdadm: clearing FAULTY flag for device 1 in /dev/md0 for /dev/sdb3
> mdadm: clearing FAULTY flag for device 0 in /dev/md0 for /dev/sda3
> mdadm: failed to add /dev/sdb3 to /dev/md0: Invalid argument
> mdadm: failed to add /dev/sda3 to /dev/md0: Invalid argument
> mdadm: failed to add /dev/sdc3 to /dev/md0: Invalid argument
> mdadm: /dev/md0 assembled from 0 drives (out of 5), but not started.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-12-28 21:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-28 6:21 Raid 5 Recovery Erik Boettcher
2008-12-28 15:33 ` Redeeman
2008-12-28 15:53 ` Dylan Distasio
[not found] ` <125ed8800812281002t6eecb5cbu2173efab36418c92@mail.gmail.com>
2008-12-28 18:12 ` Erik Boettcher
[not found] ` <125ed8800812281004o4d179064r735e46315481775a@mail.gmail.com>
2008-12-28 18:13 ` Erik Boettcher
2008-12-28 21:31 ` NeilBrown [this message]
[not found] ` <125ed8800812281359r3050d001g5936a65e2fa27d21@mail.gmail.com>
2008-12-28 23:53 ` Erik Boettcher
2008-12-30 5:23 ` Erik Boettcher
[not found] ` <20081228183921.GA5815@csy.ca>
2008-12-28 22:15 ` Justin Piszcz
2009-03-22 3:15 ` Erik Boettcher
2009-03-22 7:15 ` Max Amanshauser
2009-03-22 9:05 ` Erik Boettcher
2009-03-22 16:49 ` Erik Boettcher
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=0751481ab32bd9084154902b6ca31e9f.squirrel@neil.brown.name \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=tehfoo@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox