I have exactly the same problem. The only quirk is that it is a three disk raid 10. The same disks (750, 500 and 250G) also hold a raid 0 array which works absolutely fine.
The /dev/mdadm/mdadm.conf file had an incorrect UUID after I'd had to rebuild the arrays. I have fixed this using mdadm --detail /dev/md0, to get the correct UUID, but others beware. N.b. re-assembling, and re-creating the array (with assume clean) left all my data intact, and I could mount the ext4 LVM volumes. here's a snip of my dmesg [ 16.345255] md: bind<sda1> [ 16.346671] mdadm[2286]: segfault at 0 ip 000000000040839b sp 00007fff6106a5d0 error 4 in mdadm[400000+2a000] [ 16.384062] md: bind<sdb1> [ 16.391313] mdadm[2305]: segfault at 0 ip 000000000040839b sp 00007fffa55e70d0 error 4 in mdadm[400000+2a000] [ 16.432732] md: bind<sdc1> [ 16.440382] mdadm[2306]: segfault at 0 ip 000000000040839b sp 00007fff1feb49a0 error 4 in mdadm[400000+2a000] let me know how to help debug this. -- Raid10 array not assembled at boot, all disks are marked as spare https://bugs.launchpad.net/bugs/316670 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
