What do:
mdadm -E /dev/sda1
mdadm -E /dev/sdb1
mdadm -E /dev/sda2
mdadm -E /dev/sdb2
show, if anything ?
If they report they belonged once to an array with superblock positioned
at the end (so either 0.9 or 1.0), you could create RAID1 array missing
one component. In your case, something like:
umount /dev/mapper/VolGroup00-LogVol00
umount /dev/mapper/VolGroup00-LogVol01
vgchange -an VolGroup00
mdadm -C /dev/md/1 -l1 -n2 -e0 /dev/sdb2 missing
-e0 assuming it was v0.9 superblock
-e1.0 assuming it was v1.0
and then:
mdadm /dev/md/1 --add /dev/sda2
..wait for resync, then:
vgscan --mknodes
vgchange -ay
..should use /dev/md/1 - but doublecheck /etc/lvm/lvm.conf as well.
Of course it's potentially risky, so doublecheck everything and if it's
possible somehow (considering remote location), backup /dev/sdb2 first
(actually, you could use /dev/sda2 for that, as it's unused at this
moment anyway).
/dev/sd{a,b}1 case will be difficult w/o physical access, if they were
part of another raid1 array.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
