hey andre, On 25/05/2010 Andre Pawlowski wrote: > Today I could copy all the output the error does. thanks, let's see ... > Here is what the system shows when I boot with the new > initrd.img-2.6.32-trunk-amd64: > > Loading, please wait... > Volume group "laptop-vg" not found > Skipping volume group laptop-vg > Unable to find LVM volume laptop-vg/root > Unlocking the disk > /dev/disk/by-uuid/e7bf2609-7a87-447c-9827-694bc164debb (sda2_crypt) > Enter passphrase: > udevd-work[422]: kernel-provided name 'dm-0' and NAME= > 'mapper/temporary-cryptsetup-414' disagree, please use SYMLINK+= or > change the kernel to provide the proper name > udevd-work[422]: kernel-provided name 'dm-0' and NAME= > 'mapper/temporary-cryptsetup-414' disagree, please use SYMLINK+= or > change the kernel to provide the proper name > No key available with this passphrase > cryptsetup: cryptsetup failed, bad password or options? > Unlocking the disk > /dev/disk/by-uuid/e7bf2609-7a87-447c-9827-694bc164debb (sda2_crypt) > Enter passphrase: did you try to submit the correct passphrase at all? as already written, these udevd-work messages are just warnings, they shouldn't have any impact on the functionality after all. in fact, they appear on my system as well since last udev upgrade. but unlocking the disk still works. > Ok, now the output when I use the initrd.img-2.6.32-trunk-amd64.bak: > > Loading, please wait... > Volume group "laptop-vg" not found > Skipping volume group hantuch-vg > Unable to find LVM volume laptop-vg/root > Unlocking the disk > /dev/disk/by-uuid/e7bf2609-7a87-447c-9827-694bc164debb (sda2_crypt) > Enter passphrase: > Key slot 0 unlocked > [normal booting output follows] > > The system is up to date with the newest squeeze packets. so unlocking the disk works with old initramfs, while it fails with the new initramfs (ignoring the udev warnings)? or does it work with the new initramfs as well, despite cluttering the passphrase prompt with udev warnings? in the former case you most probably spotted another bug (or misconfigured your system), in the latter case this bugreport should be reassigned to package dmsetup, where the respective udev rules need to be updated. greetings, jonas
Attachment:
signature.asc
Description: Digital signature