Bug#485989: I can reproduce this

[Russell Coker]

On Wednesday 02 July 2008 20:58, martin f krafft <madduck at debian.org> wrote:
> also sprach Russell Coker <russell at coker.com.au> [2008.07.02.1047 +0200]:
> > The above is a diff between two versions of mdadm.conf.  The presence
> > of "metadata=1" results in mkinitramfs producing an image that won't
> > boot.
>
> Why won't it boot? Is /etc/mdadm/mdadm.conf in the initramfs
> correct? Does /conf/md.conf look alright?

Does "correct" mean being with or without the metadata=1 part of the line?

> Does it boot if you add break=mount to the kernel command line and
> remove the metadata=1 from /etc/mdadm/mdadm.conf in the initramfs
> before exiting the shell to continue?

I change the mdadm.conf file to not have metadata=1 and it is copied directly 
to the initramfs in that way.  Then it works.

So it seems that simply running sed on the mdadm.conf file when preparing the 
initramfs would be sufficient to make things work.  Not an ideal solution but 
adequate until upstream gives us a better solution (making mdadm accept 
metadata=1).