Non-LUKS is not really an issue here, the initramfs script supports it, it's just not as clean solution: with LUKS you would not need to give encryption parameters in crypttab, for example, and it can be reliably detected by fstype in initramfs. Current scripts don't really care about the difference, but future developments of making cryptsetup automated from udev by FS type can't just work with non-luks partitions: you can't recognize the partition as encrypted.
I think your setup is completely different from mine: I have the LVM PV as encrypted, you have a logical volume inside LVM encrypted. This setup does not differ from cryptsetup's point of view from encrypting just a partition, as long as the LVM is initialized properly. Since lvm initialization for you is done by udev, and we now wait for udev to finish, the latest fix should fix your booting problems. -- crypted root on lvm volume stopped working https://bugs.launchpad.net/bugs/93237 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
