Hello list-users When I running in to these problem, i used a available grml live CD (grml64_2009.10 - kernel 2.6.31.5 http://grml.org/changelogs/README-grml-2009.10/) to fix the problem.
Within the live-CD i - opened the luks partiotion - mounted the lvm logical volumes - mount -o bind /dev /mnt/chroot/dev - mount -o bind /sys /mnt/chroot/sys - mount -o bind /proc /mnt/chroot/proc - chrooted into /mnt/chroot - update-initramfs -k all -u - get a working initrd The only difference between the initrd created when chrooting with help of the live-CD and the pure system should be found within /dev or /proc or /sys. As mentioned above, grml 2009.10 uses kernel 2.6.31.5, where the actual squeeze kernel is: 2.6.32-5. May be there is a different handling of UUIDs in later kernels? The cryptroot file, created within the working initrd contains the following line: target=cryptedlvm,source=UUID=89569373-xxxx-xxxx-xxxx-xxxxxxxxxxxx,key=none,rootdev,lvm=vgmolchi-lvrootdir LLAP Andreas