Reopening again. Please don't make bugs as invalid without first making
sure that you understand the problem, and that the bug report is
actually invalid. Because in this case it is not. Thanks.
Yes, devmapper exposes the unencrypted partition ... once the partition
is unlocked. At boot time it is not unlocked. In order to unlock it, the
init scripts wait for sda4 (that is, a LUKS block device) to appear with
a UUID in /dev/disks/by-uuid. This happened in the past (with a wrong
UUID, but at least it appeared to work), and does not happen anymore.
It is not possible to use the UUID of the unencrypted device before it
is unencrypted. Init scripts need the UUID of the LUKS device in order
to unlock it.
Also note that this already correctly works for sda3, which is the root
device. It fails for sda4, which is the swap/hibernate partition.
** Changed in: udev (Ubuntu)
Status: Invalid => Confirmed
--
udev fails to identify crypt_LUKS swap partition by uuid
https://bugs.launchpad.net/bugs/362315
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
