[pkg-cryptsetup-devel] Bug#582481: initramfs-tools: System won't boot anymore if it was encrypted by debian squeeze setup

[Andre Pawlowski]

Today I could copy all the output the error does.

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:


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.

Regards

Andre Pawlowski

-------------------------------------------------------------------

Warum fallen wir?
Damit wir lernen können, uns wieder aufzurappeln.
	-Batman Begins (Thomas Wayne)

On 05/25/2010 08:59 AM, maximilian attems wrote:
> tags 582481 moreinfo
> stop
> 
> On Tue, May 25, 2010 at 07:46:16AM +0200, Andre Pawlowski wrote:
>> Hi,
>>
>> if it is a bug in udev, why does the system start with the old initramfs?
>>
> 
> dude you  have not provided the error message or presumed failure
> of the new initramfs!?
> 
> how about telling that as a start.
> can you still reproduce it with latest initramfs-tools?
> 
> thanks.