Bug#731884: Problem is order of partitions seen by mdadm

[Ben Hutchings]

On Wed, 2013-12-11 at 14:19 +0100, John Hughes wrote:
> 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).

But this can go wrong if you have another device plugged in at boot time
and the device names change...

> I guess the bug report should be reassigned to mdadm.

Right, I don't think it is correct to look for firmware RAID signatures
inside partitions.

Ben.

-- 
Ben Hutchings
Knowledge is power.  France is bacon.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20131214/00f81f1e/attachment.sig>