Bug#328167: initrd-tools: completely broken with regard to LVM devices on EVMS

[Horms <horms@debian.org>]

On Wed, Sep 14, 2005 at 01:23:11AM +0200, Steinar H. Gunderson wrote:
> Package: initrd-tools
> Version: 0.1.82
> Severity: important
> 
> When running mkinitrd, I get:
> 
>   sesse@pannekake:~$ sudo mkinitrd -o /boot/initrd.img-2.6.12-1-amd64-k8-smp 2.6.12-1-amd64-k8-smp
>   File descriptor 3 left open
>   File descriptor 4 left open
>   File descriptor 5 left open
>   File descriptor 6 left open
>   File descriptor 7 left open
>   Finding all volume groups
>   Finding volume group "pannekake"
>   /usr/sbin/mkinitrd: /dev/evms/lvm2/pannekake/root: Cannot find LVM device
> 
> Obviously, /dev/evms/lvm2/pannekake/root is managed by EVMS here, so it
> should not just see that /sbin/lvmiopversion exists and thus try to use
> the LVM userspace.
> 
> Anyhow, I removed lvm-common as I don't need it, but still I get
> 
>   Unknown DM device 254:2
> 
> since it looks for /etc/mkinitrd/scripts/evms, which to the best of my
> knowledge is not in the evms packages anymore (evms has a probe.d script
> instead). Removing the "exit 1" appears to give a valid initrd.

Hi,

first up you should know that we are currently trying really
hard to kill mkinitrd in sid/etch. But initrd-tools is
in Sarge, so I guess that means fixes are still important.

If /etc/mkinitrd/scripts/evms doesn't exist, should
something else be run instead? Or is just removing
the exit 1, as you suggest, sufficient?

-- 
Horms