On Tue, 01 May 2012 18:34:10 +1200 Andrew Thrift <andrew@xxxxxxxxxxxxxxxxx> wrote: > Hi, ... > And the /dev/md0 array is now corrupt. The /dev/md1 array appears > fine, but obviously without the /dev/md0 that the LV was spanned across > it is not usable. > > Each drive that was previously in /dev/md0 has the following output: > > mdadm --examine /dev/sdh1 > /dev/sdh1: > Magic : a92b4efc > Version : 0.90.00 > UUID : 00000000:00000000:00000000:00000000 > Creation Time : Tue May 1 14:44:06 2012 > Raid Level : -unknown- > Raid Devices : 0 > Total Devices : 2 > Preferred Minor : 0 > > Update Time : Tue May 1 16:24:56 2012 > State : active > Active Devices : 0 > Working Devices : 2 > Failed Devices : 0 > Spare Devices : 2 > Checksum : bccafbfb - correct > Events : 1 > > > Number Major Minor RaidDevice State > this 0 8 113 0 spare /dev/sdh1 > > 0 0 8 113 0 spare /dev/sdh1 > 1 1 8 81 1 spare /dev/sdf1 > > > e.g. Raid Level is -unknown- and the UUID is > 00000000:00000000:00000000:00000000 > > This appears to be a quite major bug, is this known, and is there any > way I can recover my data ? Yes, it is known and fixed in 3.3.4 and elsewhere. Only the metadata is corrupt, not the data You should be able to get your data back with mdadm -S /dev/md0 mdadm -C /dev/md0 -e 0.90 -5 -n 4 --assume-clean --chunk 64 \ /dev/sdf1 /dev/sdg1 /dev/sdi1 /dev/sdh1 Then activate the LVM and check the filesystem just to be sure before doing anything that would write to the array. I'm guessing the '64K' chunk size - I think that was the default when 0.90 was the default. Maybe you know better or have some old copy of "/proc/mdstat" output to check. I think the order of devices is correct. I got it from > May 1 00:09:37 blackbox kernel: [ 3712.863217] RAID conf printout: > May 1 00:09:37 blackbox kernel: [ 3712.863222] --- level:5 rd:4 wd:1 > May 1 00:09:37 blackbox kernel: [ 3712.863225] disk 0, o:0, dev:sdf1 > May 1 00:09:37 blackbox kernel: [ 3712.863227] disk 1, o:0, dev:sdg1 > May 1 00:09:37 blackbox kernel: [ 3712.863229] disk 2, o:1, dev:sdi1 > May 1 00:09:37 blackbox kernel: [ 3712.863231] disk 3, o:0, dev:sdh1 Note that you also seem to have a serious problem with your drives or controllers that is producing IO errors. This is nothing to do with md, but it probably making it more likely for the md but to hurt you. To avoid the md bug (until you can get a bug-free kernel) it is safest to stop all md arrays before rebooting or shutting down. NeilBrown
Attachment:
signature.asc
Description: PGP signature
