At the time I asked a few colleagues about it and no one had hit it so I assumed something wrong with my own setup. My original setup was Alternate Install + LVM encrypted root (Jaunty).
My workaround was to add this to kernel options to test botting once:
cryptopts=target=sda1_crypt,source=/dev/sda1,lvm=bianca-root root=/dev/mapper/bianca-root ro
Then once I confirmed it worked, I made it permanent by adding it to kopts in /boot/grub/menu.lst (I don't use grub2):
# kopt=cryptopts=target=sda1_crypt,source=/dev/sda1,lvm=bianca-root root=/dev/mapper/bianca-root ro
Make sure cryptopts is before root= or else this won't work.
I hit this a few weeks ago when upgrading from Jaunty to Karmic beta, here is the upstream I found: bugs.debian. org/cgi- bin/bugreport. cgi?bug= 541823
http://
At the time I asked a few colleagues about it and no one had hit it so I assumed something wrong with my own setup. My original setup was Alternate Install + LVM encrypted root (Jaunty).
My workaround was to add this to kernel options to test botting once: target= sda1_crypt, source= /dev/sda1, lvm=bianca- root root=/dev/ mapper/ bianca- root ro
cryptopts=
Then once I confirmed it worked, I made it permanent by adding it to kopts in /boot/grub/menu.lst (I don't use grub2): target= sda1_crypt, source= /dev/sda1, lvm=bianca- root root=/dev/ mapper/ bianca- root ro
# kopt=cryptopts=
Make sure cryptopts is before root= or else this won't work.