[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#266591: initrd-tools: mkinitrd assumes /dev/mapper/* == LVM device



Hi,

On Thursday 28 April 2005 04:43 am, you wrote:
> current initrd-tools > 0.1.76 seems to have cryptsetup support.
> can you please report back if aboves pain still subsist?

I'm very sorry I haven't followed up sooner.  Here's the result of attempting 
to install a new kernel-image now:

Selecting previously deselected package kernel-image-2.6.10-1-386.
(Reading database ... 139937 files and directories currently installed.)
Unpacking kernel-image-2.6.10-1-386 
(from .../kernel-image-2.6.10-1-386_2.6.10-6_i386.deb) ...
Setting up kernel-image-2.6.10-1-386 (2.6.10-6) ...
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 "vg02"
ldd: /lib/libdevmapper.so.1.00: No such file or directory
Failed to create initrd image.
dpkg: error processing kernel-image-2.6.10-1-386 (--configure):
 subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
 kernel-image-2.6.10-1-386
E: Sub-process /usr/bin/dpkg returned an error code (1)
12:29:08 nturner@millhouse(~)$

I'm not sure if the problems above are due to mkinitrd or some other part of 
the kernel-image postinst; hopefully someone reading this will have a better 
idea.

Note that on my system, there is a /lib/libdevmapper.so.1.01, so perhaps there 
is a dependency problem here.

Cheers,
nate

-- 
Nathaniel W. Turner
http://www.houseofnate.net/
Tel: +1 508 579 1948 (mobile)

Attachment: pgpQ9PXeHhlTo.pgp
Description: PGP signature


Reply to: