Bug#659647: [pkg-cryptsetup-devel] Bug#659647: initramfs-tools/hooks/cryptroot get_lvm_deps can't cope with vg name containing -
On 13/02/12 18:48, Jonas Meurer wrote: this bug should be fixed with the upload of cryptsetup 2:1.4.1-2. Can you verify that? I'll see what I can do - I'd like to try and avoid reinstalling my nice new laptop once again! I may be able to duplicate the problem in a VM. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659647: [pkg-cryptsetup-devel] Bug#659647: initramfs-tools/hooks/cryptroot get_lvm_deps can't cope with vg name containing -
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 13.02.2012 10:09, schrieb John Hughes: On 12/02/12 21:27, Ben Hutchings wrote: On Sun, 2012-02-12 at 20:57 +0100, John Hughes wrote: Package: initramfs-tools Version: 0.99 Severity: normal Dear Maintainer, * What led up to the situation? I made a volume group called coal-vg holding a root volume called root. (i.e. /dev/mapper/root--vg-root) * What was the outcome of this action? update-initramfs gave the error: cryptsetup: WARNING: failed to find deps for /dev/mapper/root--vg-root [...] Surely this should be coal--vg-root? Yes, cut'n'paste by eye error. Anyway, if the cryptsetup hook is broken then that's a bug in, er, cryptsetup. Yup. You're right - dpkg -S confirms it. Hey John, this bug should be fixed with the upload of cryptsetup 2:1.4.1-2. Can you verify that? Regards, jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPOUz9AAoJEFJi5/9JEEn+AU4P/0qtp7P8VRgKpAwlY7mnZUuk fS056TSexFhoWZZrdPTQxkQW+GIoBUiYH7/xCzrHj7QuMD+B5UvAkuOM34bZn4r3 dWIu2hJbZsbP2UVy2y69IKyHD23RRafe87YodwWIWMV8HqtW3O1k58j6RWyS9jv4 9OZNsLABUcjA68x0Gp2IusGLQptCYh0z85s3fL/iefs2ymLpNX+GylUS3vxdA1GJ 1J51Pe81CPHjAqtU4suNMkNY4uz+1/YUWyysdw9m+qZ3RZh7IKSM7GI0z6yUg9i0 VLDCQKxfdbn7F3PszedEOqIMO3ZZn7dPV9jHv4p8J2pK4G4QwxmSegUtpHWqUYFF hRtxFjmxkY6UaB5G3IMjAIvWLV778Q2ONkr2WkTYbuLEaum+quC+VVgDrNJaz1sT 4O5B8jI4lAs2k5DPS0C+mOvU1U54aZoflL3114VXbaKID0pahljrGu6IdCz1AeHP iBI3ZvW6TTXR9ooP29Us4kicPWgkdPJpInl4C5UuzG+FKa5SqdAXyMc3XIH0nlAF 66HU18RMWYh87yeFagENScv31augeessme/++UHCVqoOH2wgZ65o90hTswVfBt7m zX8wIU98Vx5103YkyUgJmTr0GTmwq6Xyo49Os0es00GByfOsi5uI8t1W1dIXse67 sf2n9Efkd9H0YH8olcvv =NhRU -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659647: [pkg-cryptsetup-devel] Bug#659647: initramfs-tools/hooks/cryptroot get_lvm_deps can't cope with vg name containing -
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 13.02.2012 19:06, schrieb John Hughes: On 13/02/12 18:48, Jonas Meurer wrote: this bug should be fixed with the upload of cryptsetup 2:1.4.1-2. Can you verify that? I'll see what I can do - I'd like to try and avoid reinstalling my nice new laptop once again! I guess that you're dropped to a busybox emergency shell after unlocking the encrypted disk failed early at the boot process, right? You should be able to boot after unlocking the encrypted disk and enabling the LVM volume group manually from within the emergency shell: unlock the encrypted disk: # cryptsetup luksOpen /dev/DEVICE DEVICE_crypt (where DEVICE is something like sda1 or sdb5) enable the LVM volume group: # vgchange -a y resume the boot process: # CTRL+d Don't hesitate to ask if you've any further questions. Regards, jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPOYY4AAoJEFJi5/9JEEn+tDEQAIAdV3m8+pMzhVSYEvsuVqOo 5Ng4A8nqej09AhWeTOVo9fTh3xC0/KuWK2xOPS6LNUqJCkuVCI2/HSRZh9kj2B9W bIenXXg8SVgq6TLsQ2Zsh0ZM877e02dx8Apb19rcmmCanytcGdLcYiK4Aqa92+Sx LM/IRAt09jTNVN5UP8NkFBppONScVkPhaUDY20gEqbPI/pLqckWPwpXv1a37dBUX 9I4yVWqWcxYLUklyV+ENh+JssCzycYqcyUu0OU7uh6rnl6qcQMh6kHUhK7K1MdAR +heRjxvF7yJttlmNqkWzKa9z+Eb1UUL7RNax7lxQhYK2fSSF8yp98/VRioJuzFZa 8cVnACwOh1tMpkD6E1mxaRvQC5uN0Tgw4/4KlAe61JK8vexRzuz93BP1fa4+dFoW Ly+coR8eL0JEILTGnYcK9T6xRObAHoNcEvOMEKQEhhCzKgaG83t4EIoQlZHKOsR3 lxGOF5XKztOS+NiqouVUlrrzw/aMzjplRw6nLw8SMtvgnu6Hb2VrY9MLlzPdBXQp YOkfzJUq75RF9MIrpjkrGeWo4p4174LuUUM8l101t6jrvfp/rJFAQhVfSPwUf6VR zorRezA4DDkM5BDcJR+vjUmF0quddCVOOhR+SgpXNcOvsyecfZa4pXv4DdGI77ag RS1E8oG7qCy8E2G6Qjgd =q5Tv -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659647: [pkg-cryptsetup-devel] Bug#659647: initramfs-tools/hooks/cryptroot get_lvm_deps can't cope with vg name containing -
On 02/13/2012 10:53 PM, Jonas Meurer wrote: I guess that you're dropped to a busybox emergency shell after unlocking the encrypted disk failed early at the boot process, right? Yeah, I did all that. But since then I've reinstalled from scratch (with simpler vg name). Like I say, I'll try to duplicate the problem in a vm and then try the new version. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
