I have a RAID 1 setup using xfs.
The array is mounted on boot (though it's obviously not a boot partition) but during the last boot I got the message (something like):
'/dev/md1: xfs: Can't read superblock'.
I boot the machine in rescue mode and the array is mounted. I unmount the filesystem, run xfs_repair which doesn't report anything wrong. From the rescue session I can mount and unmount the partition, no problems whatsoever.
Only when 'normally' booting do I get the above message and the filesystem doesn't get mounted.
The 2.16.18-2798 kernel is still on the system and I believe this is the same kernel used for resuce mode, but even when I boot (nonrescue) to this kernel version I get the same 'can't read superblock' message and the filesystem remains unmounted.
I've disabled selinux for normal boots but still the 'can't read superblock' persists. I checked the partition tables for the disks involved in the array and there's no inconsistency there (both partitions on the different disks have equal size).
I ran smartctl on the disks and there's nothing (physically) wrong with them.
Regretfully '/var' resides on this partition so the machine isn't able to completely boot and I thus can't try to mount the filesystem from a normal boot.
I have no idea why the filesystem can be (cleanly) mounted from rescue mode while the normal boot of fedora gives me this message. This is an fc6, i386 system.
Any tips appreciated,