Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Redeeman <redeeman@metanurb.dk>
To: Erik Boettcher <tehfoo@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid 5 Recovery
Date: Sun, 28 Dec 2008 16:33:31 +0100	[thread overview]
Message-ID: <1230478411.23771.5.camel@localhost> (raw)
In-Reply-To: <125ed8800812272221y44e77849l886a80f32cbcfbec@mail.gmail.com>

On Sun, 2008-12-28 at 01:21 -0500, Erik Boettcher wrote:
> Hello everyone, I'm trying to recover a raid-5 array that suffered
> from a powerloss (and possibly de-seating of a SATA card that 3 out of
> the 5 drives were on).
> As far as I can tell, the drives themselves are still okay.
> At first this is what happened when I tried mounting it from a livecd:
> 
> md: Autodetecting RAID arrays.
> Bad version number 0.88 on sda3
> md: sda3 does not have a valid v0.90 superblock, not importing!
> Bad version number 0.88 on sdb3
> md: sdb3 does not have a valid v0.90 superblock, not importing!
> Bad version number 0.88 on sdc3
> md: sdc3 does not have a valid v0.90 superblock, not importing!
> md: Scanned 5 and added 2 devices.
> md: autorun ...
> md: considering sde3 ...
> md:  adding sde3 ...
> md:  adding sdd3 ...
> md: created md0
> md: bind<sdd3>
> md: bind<sde3>
> md: running: <sde3><sdd3>
> raid5: device sde3 operational as raid disk 2
> raid5: device sdd3 operational as raid disk 1
> raid5: not enough operational devices for md0 (3/5 failed)
> RAID5 conf printout:
>  --- rd:5 wd:2
>  disk 1, o:1, dev:sdd3
>  disk 2, o:1, dev:sde3
> raid5: failed to run raid set md0
> md: pers->run() failed ...
> md: do_md_run() returned -5
> md: md0 stopped.
> md: unbind<sde3>
> md: export_rdev(sde3)
> md: unbind<sdd3>
> md: export_rdev(sdd3)
> md: ... autorun DONE.
> 
> At this point I sought help on ##linux on freenode, running this:
> mack ~ # mdadm -D /dev/md0
> mdadm: md device /dev/md0 does not appear to be active.
> mack ~ # mdadm --assemble /dev/md0 --scan
> mdadm: superblock on /dev/sdc3 doesn't match others - assembly aborted
> mack ~ # mdadm -A --force /dev/md0
> mdadm: superblock on /dev/sdc3 doesn't match others - assembly aborted
> mack ~ # mdadm -A --force /dev/md0 /dev/sd{a,b,c,d,e}3
> mdadm: superblock on /dev/sdd3 doesn't match others - assembly aborted
> 

Im by no means an expert in this, but i think you need to force an
assembly of all the disks..

but, wait for the opinions of other more knowledgable people in this
area...


> At this point I said WOAH -- time to stop with the freenode help --
> I'm hoping I didn't cause too much more damage there...
> 
> I'm trying to get this array up and any help would be greatly
> appreciated -- I don't want to do anything more to write to the drive
> without expert advice.
> Many thanks,
> Erik Boettcher
> --
> 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:[~2008-12-28 15:33 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 [this message]
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
     [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=1230478411.23771.5.camel@localhost \
    --to=redeeman@metanurb.dk \
    --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