Same problems here and manually creating raids with mdadm seems to lead to same problems.
Looks like the raid driver thinks the last raid's superblock is actually the superblock for the entire disk! In our case, we have /dev/md3 consisting of sda6, sdb6. The array was made manually with 'mdadm --create' AFTER installing the machine, not from installer! I've done this because partitioning the disk right from the installer always leaded to broken arrays after reboot. After creating the array in the next boot we get md3 device assembled from sda and sdb and several other arrays created from md3p1 md3p2 ... so on... a real mess checking with 'mdadm --examine' shows that the metainfo for sda6, sdb6 is exactly the same as the one for sda, sdb! same components and UUID If I remember right, the kernel should only auto-assemble arrays only from partitions of type FD ( Linux raid), so its unclear why it will assemble the array from sda and sdb!! -- mount: mounting /dev/md0 on /root/ failed: Invalid argument https://bugs.launchpad.net/bugs/569900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
