Hi, > I certainly believe you. thank you! > That is really odd! Both the kernel ext3 module (triggered by '-text3') > and the 'mount' program use exactly the same test - look for the magic > number in the superblock at 1K into the device. Today I tried: blkid -p /dev/md1 (this time the live CD autoassembled the md device) and it returned something like: ambivalent result (probably more than one filesystem...) Strange thing is that, the HDDs were brand new, no older partitions or filesystem were there. Anyway, I've one small correction, the RAID is not 10 f2, on this PC, but (due to different installation) a RAID-1 with superblock 0.9 and the device partitions are set to 0xFD (RAID autoassemble). > Would you be able to get the first 4K from each device in the raid10: > dd if=/dev/whatever of=/tmp/whatever bs=1K count=4 > > and the tar/gz those up and send them to me. That might give some clue. > Unless the raid metadata is 1.1 or 1.2 - then I would need blocks further in > the device, as the 'data offset'. > The --detail output of the array might help too. I dumped the first 4K of each device, they're identical (so no mismatch there, at least), I'll send them to you, together with the detail output. > > Running a fsck did not find anything wrong, but it did > > not repair anything too. > > Did you use "fsck -f" ?? Yep. > Until we know what is wrong, it is hard to suggest a fix. Thanks a lot (also because this could turn out to be unrelated with this mailing list). bye, -- piergiorgio -- 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
