I'm having a weird problem using mdadm to create a RAID1 array on my newly- rebuilt Debian box.
My mdadm.conf shows: DEVICE /dev/hde* /dev/hdi* /dev/hdg* /dev/hdk* # 250GB ARRAY /dev/md0 devices=/dev/hde1,/dev/hdi1 level=1 num-devices=2 # 200GB ARRAY /dev/md1 devices=/dev/hdg1,/dev/hdk1 level=1 num-devices=2 I created them using: mdadm --create --raid-devices=2 --level=1 /dev/md0 /dev/hde1 /dev/hdi1 mdadm --create --raid-devices=2 --level=1 /dev/md1 /dev/hdg1 /dev/hdk1 Both have completed mirroring. /dev/md1 is perfectly fine, placed in /etc/fstab and mounts properly. /dev/md0 (the 250Gb) isn't. When I run a fsck /dev/md0, it returns: fsck 1.37 (21-Mar-2005) e2fsck 1.37 (21-Mar-2005) The filesystem size (according to the superblock) is 60243742 blocks The physical size of the device is 60243712 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? yes Stopping /dev/md0, doing individual fsck /dev/hde1 and fsck /dev/hdi1 shows it is fine. What's up with the array being all messed up then? Any ideas? alex
