Public bug reported:
Binary package hint: cryptsetup
After upgrading cryptsetup from 1.0.3 to 1.0.4+svn26-1ubuntu1~edgy1 my
system could no longer boot (it did not find the root device). My setup:
I have a logical volume (/dev/mapper/VG01-crypted-root), which is
encrypted as /dev/mapper/cryptroot. I have tried to find the reason for
the problem and came to the following result: in 1.0.3 the variable
$ROOT was set to the new root (/dev/mapper/cryptroot in my case). 1.0.4
added the possibility to set up more than one device (for the resume
partition), but the information which should be the new root device is
not there (we do not want the resume partition as the root device).
I came up with a patch which solved th problem for me.
--Swen
** Affects: cryptsetup (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
crypted root on lvm volume stopped working
https://launchpad.net/bugs/93237
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
