Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Nicolas Jungers <nicolas@jungers.net>
To: "Tor Arne Vestbø" <torarnv@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: RAID5 disk failure during rebuild of spare, any chance of recovery when one of the failed devices is suspected to be intact?
Date: Mon, 16 Aug 2010 07:29:45 +0200	[thread overview]
Message-ID: <4C68CCC9.2050604@jungers.net> (raw)
In-Reply-To: <AANLkTimEOFMh=TvQ2VqbPME+S2hNuiR3RNEbOGepBoH4@mail.gmail.com>

I'd try to recreate the array with a copy of the disks

do a ddrescue of the 3 good disks and then try a mdadm -C with the exact 
parameters of the array creation with the same mdadm version (use 
missing for slot 2).  It saved my raid10 array.

N.


On 08/16/2010 12:33 AM, Tor Arne Vestbø wrote:
> On Sun, Aug 15, 2010 at 10:06 PM, Tor Arne Vestbø<torarnv@gmail.com>  wrote:
>> On Sun, Aug 15, 2010 at 8:52 PM, Tor Arne Vestbø<torarnv@gmail.com>  wrote:
>>> Hey,
>>>
>>> Hoping for some crisis help here :)
>>
>> Here's a few logs if it helps...
>
> After reading various tips on recovering I tried the following:
>
> # mdadm -Afv /dev/md0 /dev/sdb1 /dev/sdc1 /dev/sde1
> mdadm: looking for devices for /dev/md0
> mdadm: /dev/sdb1 is identified as a member of /dev/md0, slot 4.
> mdadm: /dev/sdc1 is identified as a member of /dev/md0, slot 1.
> mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 3.
> mdadm: no uptodate device for slot 0 of /dev/md0
> mdadm: no uptodate device for slot 2 of /dev/md0
> mdadm: added /dev/sde1 to /dev/md0 as 3
> mdadm: added /dev/sdb1 to /dev/md0 as 4
> mdadm: added /dev/sdc1 to /dev/md0 as 1
> mdadm: /dev/md0 assembled from 2 drives and 1 spare - not enough to
> start the array.
>
> Thinking that since sdb1 was more or less intact it would be able to
> jump in and work together with sdc1 and sde1 to form a degraded array
> I could pull data off of.
>
> But it seems that when I added sdb1 to the array earlier after it
> initially was kicked for being "non-fresh", it got added as a spare,
> in slot 4.
>
> The message about no uptodoate device for slot 2 is correct, that's
> the sdd1 device that failed. But for slot 0 it should be sdb1.
>
> Is ther any way I can tell mdadm to assume sdb1 is up to date, and use
> that at slot 0?
>
> Thanks!
>
> Tor Arne
>
> PS: Pastebin.com seems to be down, so here's a repaste of mdadm -E:
> http://pastebin.org/518816
> --
> 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

--
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

  reply	other threads:[~2010-08-16  5:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-15 18:52 RAID5 disk failure during rebuild of spare, any chance of recovery when one of the failed devices is suspected to be intact? Tor Arne Vestbø
2010-08-15 20:06 ` Tor Arne Vestbø
2010-08-15 22:33   ` Tor Arne Vestbø
2010-08-16  5:29     ` Nicolas Jungers [this message]
2010-08-16  5:59       ` Tor Arne Vestbø
     [not found]       ` <AANLkTim9gUa95AR1KZcyBp7qM8_PeO1O7Bh99R2P8ON9@mail.gmail.com>
2010-08-16  6:12         ` Nicolas Jungers
2010-08-16  8:43           ` Tim Small
2010-08-16 16:27             ` Tor Arne Vestbø
2010-08-16 16:37               ` Nicolas Jungers
2010-08-16 12:13           ` Tor Arne Vestbø
2010-08-16  5:49     ` Tor Arne Vestbø

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=4C68CCC9.2050604@jungers.net \
    --to=nicolas@jungers.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=torarnv@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