Bug#396159: initramfs-tools: alters behaviour of mdadm on initramfs
reassign 396159 mdadm
tags 396159 moreinfo
stop
On Mon, Oct 30, 2006 at 08:38:31AM +0200, Juha Jäykkä wrote:
> Package: initramfs-tools
> Version: 0.84
> Severity: critical
> Justification: breaks unrelated software
you are reporting against the wrong package,
the mdadm initramfs hook is done by the mdadm maintainer.
i haven't look since long into it. hope it gets more solid for release.
leaving the severity to the mdadm maintainer to judge.
> Initramfs-tools modifies the behaviour of mdadm when mdadm is run from initramfs.
> There is a debconf question for mdadm which defines the raid arrays to start from
> initramfs, however initramfs-tools not only disregards this when updating the
> images, but it also somehow changes the administrator-supplied answer to mdadm's
> debconf question!
>
> >From debconf's config.dat:
> Name: mdadm/initrdstart
> Template: mdadm/initrdstart
> Value: /dev/md0
> Owners: mdadm
>
> However, after upgrading initramfs-tools, it's postinst script says
>
> update-initramfs: Generating /boot/initrd.img-2.6.17-2-amd64
> I: mdadm: using configuration file: /etc/mdadm/mdadm.conf
> I: mdadm: will start all available MD arrays from the initial ramdisk.
> I: mdadm: use `dpkg-reconfigure --priority=low mdadm` to change this.
>
> Note that mdadm was not upgraded at the time. On my particular system, this will
> render the system unbootable, since initramfs, for some reason, mixes the two raid
> arrays: what should be /dev/md0 becomes /dev/md1 and vice versa. This, of course,
> makes the system unbootable since next thin the initramfs tries is mount the wrong
> filesystem as /. The only way around this is to make initramfs only start one raid
> array, /dev/md0.
aboves messages are from the mdadm initramfs hook.
> Please feel free to downgrade, if you think this is not critical. I think
> running "apt-get upgrade" on a healthy system and ending up with a non-bootable
> one certainly merits critical.
>
> -Juha
>
> -- Package-specific info:
> -- /proc/cmdline
> auto BOOT_IMAGE=Linux ro root=fd00 root=/dev/mapper/system-root
what do you expect by setting the root twice??
that doesn't make any sense, if your root is an lvm inside of md
you need to pass the second boot arg and the mdadm hook
should initialize the raids.
please tell which version of mdadm you are using:
dpkg -l mdadm
--
maks
Reply to: