exactly the same bug on a completely different set-up. dmesg attached. n.b. SEGFAULTS in the middle.
this is a serious bug! raid10 is an installation option, not an obscure corner case, and it results in a non-booting system. no idea if this bug is also corrupting data silently. ** Attachment added: "dmesg.txt" http://launchpadlibrarian.net/24199546/dmesg.txt -- 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
