Bug#678262: mdadm: fails to honour INITRDSTART='none' in /etc/default/mdadm

[Michael Stapelberg]

Hi Chris,

On Wed, 20 Jun 2012 21:42:14 +1000
Chris Donoghue <cdonoghu at gmail.com> wrote:
> It looks like the /usr/share/initramfs-tools/hooks/mdadm fails to
> honour the setting of INITRDSTART='none' in /etc/default/mdadm which
> led to an unbootable system.
I can’t confirm that observation. On my system (with mdadm 3.2.5-1), I
get MD_DEVS=none in the initramfs’s /conf/conf.d/md, which is a
code-path only taken when INITRDSTART is none (provided that devpairs
is non-empty, which it is on my system).

> The initramfs panic'ed from the script in 
> /usr/share/initramfs-tools/scripts/local-top/mdadm.
Can you please provide more information about this panic? A picture
would be most helpful. I can’t reproduce it on my system.

Best regards,
Michael