I'll just add that, as a workaround, I installed Ubuntu only into boot (/boot) and root (/). I then booted into the installed Ubuntu and created a new auto-mountable LUKS-encrypted volume formatted with Ext4, to which I moved my home directory.
The above approach works, but for some reason, System Monitor displays /dev/dm-0 as the identifier for the LUKS-encrypted volume that was created with Ext4 during installation, but displays /dev/mapper/vda3_crypt as the identifier for a LUKS-encrypted volume that created with Ext4 after installation. Strangely, System Monitor displays /dev/mapper/vda2_crypt as the identifier for the LUKS-encrypted volume that was created with Btrfs during installation, and displays /dev/mapper/vda3_crypt as the identifier for a LUKS-encrypted volume that created with Ext4 after installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1523194 Title: Can't install /home into separate LUKS encrypted volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1523194/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
