Bug#266591: initrd-tools: mkinitrd assumes /dev/mapper/* == LVM device
tags 266591 moreinfo thanks On Wed, 18 Aug 2004, Nathaniel W. Turner wrote: Package: initrd-tools Version: 0.1.73 Severity: important I have cryptsetup installed and my /etc/crypttab contains: swap0 /dev/hda7 /dev/urandom swap This creates an encrypted device /dev/mapper/swap0 (which I mount as swap in /etc/fstab). When installing kernel-image-2.6.8-1-k7, I get the following error: Setting up kernel-image-2.6.8-1-k7 (2.6.8-1) ... /usr/sbin/mkinitrd: /dev/mapper/swap0: Cannot find LVM device Failed to create initrd image. dpkg: error processing kernel-image-2.6.8-1-k7 (--configure): subprocess post-installation script returned error exit status 9 As far as I can tell, mkinitrd is assuming that anything in /dev/mapper is an LVM device, which is not a safe assumption. current initrd-tools 0.1.76 seems to have cryptsetup support. can you please report back if aboves pain still subsist? thanks for your feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 [EMAIL PROTECTED](~)$ 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) pgpV2XwsAgwCV.pgp Description: PGP signature
Bug#266591: initrd-tools: mkinitrd assumes /dev/mapper/* == LVM device
thanks for your feedback. :) On Thu, 28 Apr 2005, Nathaniel W. Turner wrote: 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: ok so previous breakage seems cured. cool. 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 [EMAIL PROTECTED](~)$ 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. what arch are you using (plain i386 or amd64)? google found a similar bug report out there - http://www.sslug.se/emailarkiv/sikkerhed/2005_04/msg00010 but i have a hard time to decipher swedish and their solutions. which kernel are you trying to install above? if it's not a debian one please send in it's .config. please provide a strace of aboves trial? which libc6 and libdevmapper is installed on aboves box? dpkg -l libc6 dpkg -l libdevmapper1.01 thanks for your feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#266591: initrd-tools: mkinitrd assumes /dev/mapper/* == LVM device
On Thu, 28 Apr 2005, maximilian attems wrote: On Thu, 28 Apr 2005, Nathaniel W. Turner wrote: snipp 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 [EMAIL PROTECTED](~)$ 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. indeed found the trouble in the current mkinitrd script libdevmapper.so.1.00 is hardcoded there. no need for the demanded info, will try to fix that shortly. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
