Re: Recovering an Array with inconsistent Superblocks

[Fabian Knorr <knorrfab@fim.uni-passau.de>]

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

> Try this:
> 
> mdadm --stop /dev/md0
> 
> mdadm -Afv /dev/md0 /dev/sd[bcefghi]1
> 
> It leaves out /dev/sda, which appears to have been the spare in the
> original setup.
> 
> If MD is happy after that, use fsck -n on your logical volumes to verify
> your FS integrity, and/or see the extent of the damage (little or none,
> I think).

This had the same result as simply trying --assemble --scan, see
"assemble.log". I tried using sda1 instead of sdb1 as well as the both
seem to have ID 4 ("assemble2.log"), same thing again.

Do you have any idea why mdadm seems to ignore --force and does not add
the outdated disks? (Or am I misinterpreting --force?)

Thanks.

Fabian

[-- Attachment #2: assemble.log --]
[-- Type: text/x-log, Size: 910 bytes --]

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 5.
mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 6.
mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 0.
mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sdh1 is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sdi1 is identified as a member of /dev/md0, slot 3.
mdadm: added /dev/sdg1 to /dev/md0 as 1
mdadm: added /dev/sdh1 to /dev/md0 as 2
mdadm: added /dev/sdi1 to /dev/md0 as 3
mdadm: added /dev/sdb1 to /dev/md0 as 4 (possibly out of date)
mdadm: added /dev/sdc1 to /dev/md0 as 5 (possibly out of date)
mdadm: added /dev/sde1 to /dev/md0 as 6 (possibly out of date)
mdadm: added /dev/sdf1 to /dev/md0 as 0
mdadm: /dev/md0 assembled from 4 drives - not enough to start the array.

[-- Attachment #3: assemble2.log --]
[-- Type: text/x-log, Size: 910 bytes --]

mdadm: looking for devices for /dev/md0
mdadm: /dev/sda1 is identified as a member of /dev/md0, slot 4.
mdadm: /dev/sdc1 is identified as a member of /dev/md0, slot 5.
mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 6.
mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 0.
mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sdh1 is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sdi1 is identified as a member of /dev/md0, slot 3.
mdadm: added /dev/sdg1 to /dev/md0 as 1
mdadm: added /dev/sdh1 to /dev/md0 as 2
mdadm: added /dev/sdi1 to /dev/md0 as 3
mdadm: added /dev/sda1 to /dev/md0 as 4 (possibly out of date)
mdadm: added /dev/sdc1 to /dev/md0 as 5 (possibly out of date)
mdadm: added /dev/sde1 to /dev/md0 as 6 (possibly out of date)
mdadm: added /dev/sdf1 to /dev/md0 as 0
mdadm: /dev/md0 assembled from 4 drives - not enough to start the array.