Bug#485989: I can reproduce this

2008-07-04 Thread martin f krafft
also sprach Russell Coker <[EMAIL PROTECTED]> [2008.07.03.0028 +0100]: > Does "correct" mean being with or without the metadata=1 part of the line? Without, does it reflect your system? > So it seems that simply running sed on the mdadm.conf file when > preparing the initramfs would be sufficient

Bug#485989: I can reproduce this

2008-07-02 Thread Russell Coker
On Wednesday 02 July 2008 20:58, martin f krafft <[EMAIL PROTECTED]> wrote: > also sprach Russell Coker <[EMAIL PROTECTED]> [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 > >

Bug#485989: I can reproduce this

2008-07-02 Thread martin f krafft
also sprach Russell Coker <[EMAIL PROTECTED]> [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 /c

Bug#485989: I can reproduce this

2008-07-02 Thread Russell Coker
/etc/mdadm# diff mdadm.conf mdadm.conf.broken 21c21 < ARRAY /dev/md2 level=raid1 num-devices=2 UUID=52978f9a52:9540e417:e3565b0a:1da235 name=bluebottle:2 --- > ARRAY /dev/md2 level=raid1 metadata=1 num-devices=2 UUID=52978f9a52:9540e417:e3565b0a:1da235 name=bluebottle:2 The above is a diff betwe