Re: RAID 5 array recovery - two drives errors in external enclosure

["Majed B." <majedb@gmail.com>]

> I received the error : mdadm: superblock on /dev/sdc1 doesn't match
> others - assembly aborted.

I got that when using an older version of mdadm (2.6.7.1). According
to Neil, it's been fixed already so try using the latest version (3.0)
and do this:
mdadm -Af /dev/md0 /dev/sdf1 /dev/sdc1 /dev/sdb1 /dev/sdd1

(No need to specify a missing one).

I avoided creating another array. No matter what the situation is, it
would be the last thing I'd ever do, because I want to keep the
metadata as intact as possible to get the most info I can out of it to
fix the situation.
And my motherboard keeps changing names like crazy, so if I create a
new array, I may not be able to find the original disks' order again
(not easily).

On Mon, Sep 21, 2009 at 7:40 AM, Tim Bostrom <tbostrom@gmail.com> wrote:
> Well, thank god I copied everything off the array this weekend, but strange:
>
> I had gotten the array up finally with the correct order and missing drive:
>
> mdadm -C /dev/md0 -l 5 -n 5 -c 256 /dev/sdf1 /dev/sdc1 /dev/sdb1
> /dev/sdd1 missing
>
> ------------
> After copying everything off, I power-cycled my server and tried to
> bring the array back up again using:
>
> mdadm -A /dev/md0 /dev/sdf1 /dev/sdc1 /dev/sdb1 /dev/sdd1 missing
>
> I received the error : mdadm: superblock on /dev/sdc1 doesn't match
> others - assembly aborted.
>
> This is strange since I had this seemingly working and was able to
> copy all the data offline this weekend.
> Drives haven't changed order - I haven't unplugged anything or changed
> any cords.
>
> Another issue of the command that worked before on the array:
> mdadm -C /dev/md0 -l 5 -n 5 -c 256 /dev/sdf1 /dev/sdc1 /dev/sdb1
> /dev/sdd1 missing
>
> yields my old problem of not being able to mount.
> EXT3-fs: md0: couldn't mount because of unsupported optional features
> (3fd18e00).
> mount: wrong fs type, bad option, bad superblock on /dev/md0,
>       missing codepage or helper program, or other error
>       In some cases useful info is found in syslog - try
>       dmesg | tail  or so
-- 
       Majed B.
--
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