Bug#731884: Problem is order of partitions seen by mdadm
When the system works it builds the devices from sda and sdb.
When it fails its because it tries to build a container from sda3 and sdb.
To mdadm sda3 looks like it is part of an imsm container, but it's not.
It isn't even a partition! sda and sdb contain a imsm raid0 device that
is partitioned. Since "sda3" extends beyond the end of sda it gets
truncated by the kernel, and if mdadm examines it it looks like it is
part of the imsm device.
My problem can be "fixed" by adding :
DEVICE /dev/sda /dev/sdb containers
to the mdadm.conf (and rebuilding the initramfs).
I guess the bug report should be reassigned to mdadm.
Reply to: