1

I'm trying to install Kubuntu 20.04 with LVM encryption on a dual-boot machine. Previously, I'd done this on Mint per these simple steps. In brief, all you have to do setup your partitions manually during the install process: you choose "physical volume for encryption," it prompts you for the password, & creates an ext4 encrypted volume which I then set its mount point to "/" (& change to btrfs).

But in the Kubuntu installer this doesn't work. If you select "physical volume for encryption," nothing happens. After some googling, I found this bug report showing that their installer has had this bug for nearly half a decade.

So the question: since it doesn't seem like the Kubuntu team will be fixing their installer anytime soon, how would one manually setup a similar partition layout - ideally in the Kubuntu live OS (prior to running the installer)? Can the same installation result be safely achieved in this way?

And for clarity, what exactly is the Mint installer doing when you tell it to create a "physical volume for encryption," & then follow its prompts per above?

3 Answers 3

1

There's a workaround that worked for me:

  1. Install ubiquity-frontend-gtk
  2. Run the command:
    ubiquity gtk_ui
    
    in the terminal

This is working fine in the Ubiquity GTK version.

1

I followed this guide to manual partition with encryption and now I have dual boot, with full LVM encryption on the Linux side and BitLocker enabled on the Windows side: link

0

Finally figured out a working solution:

1) Follow the extremely thorough instructions here...

2) ...But instead of using his installation script, grab the btrfs-friendly alternative from here...

3) ...And make one manual edit: change the invocation of "cryptsetup luksFormat" to add "--type=luks1". Because per here:

The default LUKS (Linux Unified Key Setup) format used by the cryptsetup tool has changed since the release of 18.04 Bionic. 18.04 used version 1 ("luks1") but more recent Ubuntu releases default to version 2 ("luks2"). GRUB only supports version 1 so we have to be explicit in the commands we use or else GRUB will not be able to install to, or unlock, the encrypted device.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .