How to run multiple Ubuntu 18.x with separate partition encryption and UEFI/Secure Boot?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
To have a clear separation of concerns for different tasks (work, open source programming, gaming), without investing in multiple computers, I prefer installing parallel operating systems on separately encrypted partitions.
Wishlist, goals:
- Use a single machine with a single hard drive.
- Use UEFI with Secure Boot.
- Install multiple, highly separated instances of Linux in parallel.
- Separately encrypted partitions to ensure no (easy) access to the disks of other instances.
- Keeps own software, settings, and home folders.
- Currently Ubuntu 18.x Desktop.
- Could be other distributions, but that's not covered here.
- Install one instance of Windows.
- Not the main focus.
- Currently Windows 10.
- Optionally use other partitions or disks for general (shared) storage.
- Not covered here.
dual-boot uefi encryption luks refind
add a comment |
To have a clear separation of concerns for different tasks (work, open source programming, gaming), without investing in multiple computers, I prefer installing parallel operating systems on separately encrypted partitions.
Wishlist, goals:
- Use a single machine with a single hard drive.
- Use UEFI with Secure Boot.
- Install multiple, highly separated instances of Linux in parallel.
- Separately encrypted partitions to ensure no (easy) access to the disks of other instances.
- Keeps own software, settings, and home folders.
- Currently Ubuntu 18.x Desktop.
- Could be other distributions, but that's not covered here.
- Install one instance of Windows.
- Not the main focus.
- Currently Windows 10.
- Optionally use other partitions or disks for general (shared) storage.
- Not covered here.
dual-boot uefi encryption luks refind
add a comment |
To have a clear separation of concerns for different tasks (work, open source programming, gaming), without investing in multiple computers, I prefer installing parallel operating systems on separately encrypted partitions.
Wishlist, goals:
- Use a single machine with a single hard drive.
- Use UEFI with Secure Boot.
- Install multiple, highly separated instances of Linux in parallel.
- Separately encrypted partitions to ensure no (easy) access to the disks of other instances.
- Keeps own software, settings, and home folders.
- Currently Ubuntu 18.x Desktop.
- Could be other distributions, but that's not covered here.
- Install one instance of Windows.
- Not the main focus.
- Currently Windows 10.
- Optionally use other partitions or disks for general (shared) storage.
- Not covered here.
dual-boot uefi encryption luks refind
To have a clear separation of concerns for different tasks (work, open source programming, gaming), without investing in multiple computers, I prefer installing parallel operating systems on separately encrypted partitions.
Wishlist, goals:
- Use a single machine with a single hard drive.
- Use UEFI with Secure Boot.
- Install multiple, highly separated instances of Linux in parallel.
- Separately encrypted partitions to ensure no (easy) access to the disks of other instances.
- Keeps own software, settings, and home folders.
- Currently Ubuntu 18.x Desktop.
- Could be other distributions, but that's not covered here.
- Install one instance of Windows.
- Not the main focus.
- Currently Windows 10.
- Optionally use other partitions or disks for general (shared) storage.
- Not covered here.
dual-boot uefi encryption luks refind
dual-boot uefi encryption luks refind
asked Mar 29 at 12:14
Joel PurraJoel Purra
1166
1166
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Ideas
- Use
refind
rather thangrub
to manage system selection during UEFI/Secure Boot. - Don't use a separate
/boot
partition per Linux instance. Letrefind
boot the kernel directly from the EFI system partition (ESP). - Set up Linux Unified Key Setup (LUKS) from the Ubuntu installer.
- Note that the current solution doesn't encrypt the kernel files, as booting directly to encrypted disks is not supported by
refind
.
Overview
- Obviously create multiple backups of any valuable data beforehand. Changing the boot procedure, formatting disks, enabling encryption, etcetera can be hazardous and care needs to be taken.
- Install Windows first.
- Seems to be a general recommendation, though should matter less with UEFI.
- It will prepare the GPT and ESP, this can also be done manually using GNOME Partition Editor from the Ubuntu USB/DVD.
- The ESP created by the Windows installer might not be big enough, depending on the number of Ubuntu instances and kernel sizes. 512 MB seems enough for 2 Ubuntu-instances, but 1 GB would be safer and allow more instances.
- Install
refind
and make sure it boots with Secure Boot. - For each desired Ubuntu system instance:
- Run the default Ubuntu installer from USB or DVD.
- Select the option "Something else" to manually set up encryption and select partitions.
- Don't reboot after the installation, but stay to setup the
refind
boot process.
- Over time, perform maintenance tasks if there are kernel or driver updates.
Per-instance installation
Assumes that the GUID Partition Table (GPT) and the ESP has been set up by the Windows installer, and that there are additional partitions(s) or empty disk space for the Ubuntu instance(s).
Partition paths and names
For consistency I'll use this partition path naming below. Paths will be different on your system, and will vary by instance, so please keep notes.
/dev/nvme0n1p11
is your ESP.
/dev/nvme0n1p22
is your temporary/boot
partition.
/dev/nvme0n1p33
is your per-instance "physical volume for encryption" (locked) root/
partition.
/dev/mapper/nvme0n1p33_crypt
is your (unlocked) root/
partition.
Partition and install a new (additional) Ubuntu instance
- Get Ubuntu on USB or DVD, boot it selecting "Try out Ubuntu".
- Open a terminal to update and start the installer.
sudo apt update && sudo apt dist-upgrade -y
ubiquity --no-bootloader
- When asked about installation type (co-existing with other operating systems) and disk formatting/partitioning, select "Something else" to see a list of disks and partitions.
- Find the partition with type
efi
, the ESP.
- On my system this is
/dev/nvme0n1p11
. - Make a note of the partition path name as you'll need it below.
- Check that it has at least 200 MB free before continuing, as it will be needed for the new instance kernel.
- On my system this is
- Select or create a boot partition.
- On my system this is
/dev/nvme0n1p22
. - Make a note of the boot partition path name as you'll need it below.
- Will be reused for subsequent Ubuntu instance installations.
- Create or select a small (maximum 512 MB) partition.
- Erase/format as EXT4.
- Click "change" and mount it as
/boot
.
- On my system this is
- Select or create a root partition for Ubuntu.
- On my system this is
/dev/nvme0n1p33
. - Make a note of the root partition path name as you'll need it below.
- It will be erased.
- 5 GB for minimal, 25+ GB for a full installation.
- Click "change" and make it an "physical volume for encryption".
- Choose a password which is not the same as for the other instances.
- On my system this is
- Find the new, unlocked partition ending with
_crypt
.
- On my system this is
/dev/mapper/nvme0n1p33_crypt
. - Change the mount point to root
/
.
- On my system this is
- Let the installer finish, but do not reboot at the end by selecting "Continue testing".
Set up refind
for the new instance.
Enter
chroot
to the new operating system to make more changes.
# NOTE: create temporary mount directories.
sudo mkdir /mnt/bootpartition /mnt/ospartition
# NOTE: Mount the newly created encrypted partition.
sudo mount -o subvol=@ /dev/mapper/nvme0n1p33_crypt /mnt/ospartition
sudo mount /dev/nvme0n1p22 /mnt/bootpartition
# NOTE: Copy the boot files into the encrypted partition.
# NOTE: Watch those trailing slashes! rsync is very sensitive to them.
sudo rsync -aXAH /mnt/bootpartition/ /mnt/ospartition/boot/
sudo mount /dev/nvme0n1p11 /mnt/ospartition/boot/efi
sudo mount --bind /dev /mnt/ospartition/dev
sudo mount --bind /proc /mnt/ospartition/proc
sudo mount --bind /sys /mnt/ospartition/sys
# NOTE: change root to the newly installed Ubuntu.
sudo chroot /mnt/ospartition
- Edit
/etc/fstab
and comment out the line for/boot
. The other entries are correct. - Optional: make other low-level system file changes, such as workarounds for broken drivers1.
- Create an EFI-bootable copy of the kernel (
vmlinuz
) and the initial ramdisk (initrd
) forrefind
. Remember to replaceubuntu-instance
with something of our own. I use "ubuntu-work" and similar. Do not use just "ubuntu" as it might get overwritten by the Ubuntu installer.
# NOTE: Choose your own per-instance directory name.
sudo mkdir /boot/efi/EFI/ubuntu-instance/
sudo cp /boot/vmlinuz* /boot/initrd* /boot/efi/EFI/ubuntu-instance/
- Look for
/dev/nvme0n1p33
, the physical volume for encryption for this instance. Make a note of (or copy to the clipboard) the UUID (but not the PARTUUID).
sudo blkid
- Prepare
refind
's Ubuntu instance kernel boot options for the encrypted partition inrefind_linux.conf
. Create/boot/efi/EFI/ubuntu-instance/refind_linux.conf
from the below template, but with your path and UUID.
"Boot with standard options" "root=/dev/mapper/nvme0n1p33_crypt cryptdevice=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:nvme0n1p33_crypt ro quiet splash"
"Boot to single-user mode" "root=/dev/mapper/nvme0n1p33_crypt cryptdevice=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:nvme0n1p33_crypt ro single"
"Boot with minimal options" "root=/dev/mapper/nvme0n1p33_crypt cryptdevice=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:nvme0n1p33_crypt ro"
- Exit
chroot
and reboot. Remember to select the new kernel inrefind
.
exit
sudo reboot
Cleanup
Optional. This will remove unused boot options in refind
. I like to keep them around as a backup until the system is stable.
- Remove any leftover shared Ubuntu Grub bootloader.
# NOTE: The shared Ubuntu Grub EFI loader might be leftover from previous installations.
#sudo rm -r /boot/efi/EFI/ubuntu/
- Remove files from the unused boot partition.
# NOTE: Optionally clean up files from the Ubuntu installer.
#sudo mkdir /mnt/bootpartition
#sudo mount /dev/nvme0n1p22 /mnt/bootpartition
#sudo rm -r /mnt/bootpartition/*
Maintenance after kernel or driver updates
As Ubuntu doesn't know about refind
, kernel+driver updates require a manual copy step for vmlinuz+initrd.
- After installing updates, but before rebooting, copy the new vmlinuz+initrd from the encrypted
/boot
to the unencrypted ESP'subuntu-instance
like above. - If you forget to do this, and the system broke or new drivers didn't load, boot either:
- Single-user mode from
refind
by choosing custom boot options. - The Ubuntu installer USB/DVD, and mount to temporary locations:
- The encrypted disk which contains
/boot
. - The ESP.
- The encrypted disk which contains
- Copy the vmlinuz+initrd from your
/boot
to the ESP'subuntu-instance
like above.
- Single-user mode from
Future improvements
- If/when there are EFI file system drivers so
refind
can read encrypted LUKS partitions, investigate not keeping the kernels on the unencrypted ESP. This might greatly simplify the above setup. - Figure out if kernel+driver updates can automatically trigger updating the per-instance ESP vmlinuz+initrd copy for
refind
. - Improve temporary boot partition usage with one of:
- Configure the temporary boot partition as encrypted swap space in each of the Linux instances.
- Reusing the ESP for temporary
/boot
files. Didn't want the added risk of destroying the ESP by accidentally formatting it or similar, but might work just as well.
Inspiration
Thank you!
@Aleksandr Dubinsky's answer to "Ubuntu full disk encryption with encrypted /boot".
@StefK's answer to "Installing Ubuntu 12.04 without installing Grub".
@Rod Smith's answer to "How do I install two independent Ubuntu installations on a single hard drive with UEFI?"- Many more answers, articles, documentation written by Roderick W. Smith, who is the author of
refind
. - Ubuntu's installation documentation for desktop usage.
1 This Wayland plus Nvidia grapics driver problem caught me. It causes a black screen after the disk has been unlocked. Luckily it's easy to fix and Wayland can be restored once updated Nvidia drivers have been installed -- just remember to copy the updated kernel+initrd to your ESP.
1
See also: help.ubuntu.com/community/ManualFullSystemEncryption Full-system encryption with manual control and dual-booting Paddy Landau ubuntuforums.org/showthread.php?t=2357627
– oldfred
Mar 29 at 13:42
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1129672%2fhow-to-run-multiple-ubuntu-18-x-with-separate-partition-encryption-and-uefi-secu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Ideas
- Use
refind
rather thangrub
to manage system selection during UEFI/Secure Boot. - Don't use a separate
/boot
partition per Linux instance. Letrefind
boot the kernel directly from the EFI system partition (ESP). - Set up Linux Unified Key Setup (LUKS) from the Ubuntu installer.
- Note that the current solution doesn't encrypt the kernel files, as booting directly to encrypted disks is not supported by
refind
.
Overview
- Obviously create multiple backups of any valuable data beforehand. Changing the boot procedure, formatting disks, enabling encryption, etcetera can be hazardous and care needs to be taken.
- Install Windows first.
- Seems to be a general recommendation, though should matter less with UEFI.
- It will prepare the GPT and ESP, this can also be done manually using GNOME Partition Editor from the Ubuntu USB/DVD.
- The ESP created by the Windows installer might not be big enough, depending on the number of Ubuntu instances and kernel sizes. 512 MB seems enough for 2 Ubuntu-instances, but 1 GB would be safer and allow more instances.
- Install
refind
and make sure it boots with Secure Boot. - For each desired Ubuntu system instance:
- Run the default Ubuntu installer from USB or DVD.
- Select the option "Something else" to manually set up encryption and select partitions.
- Don't reboot after the installation, but stay to setup the
refind
boot process.
- Over time, perform maintenance tasks if there are kernel or driver updates.
Per-instance installation
Assumes that the GUID Partition Table (GPT) and the ESP has been set up by the Windows installer, and that there are additional partitions(s) or empty disk space for the Ubuntu instance(s).
Partition paths and names
For consistency I'll use this partition path naming below. Paths will be different on your system, and will vary by instance, so please keep notes.
/dev/nvme0n1p11
is your ESP.
/dev/nvme0n1p22
is your temporary/boot
partition.
/dev/nvme0n1p33
is your per-instance "physical volume for encryption" (locked) root/
partition.
/dev/mapper/nvme0n1p33_crypt
is your (unlocked) root/
partition.
Partition and install a new (additional) Ubuntu instance
- Get Ubuntu on USB or DVD, boot it selecting "Try out Ubuntu".
- Open a terminal to update and start the installer.
sudo apt update && sudo apt dist-upgrade -y
ubiquity --no-bootloader
- When asked about installation type (co-existing with other operating systems) and disk formatting/partitioning, select "Something else" to see a list of disks and partitions.
- Find the partition with type
efi
, the ESP.
- On my system this is
/dev/nvme0n1p11
. - Make a note of the partition path name as you'll need it below.
- Check that it has at least 200 MB free before continuing, as it will be needed for the new instance kernel.
- On my system this is
- Select or create a boot partition.
- On my system this is
/dev/nvme0n1p22
. - Make a note of the boot partition path name as you'll need it below.
- Will be reused for subsequent Ubuntu instance installations.
- Create or select a small (maximum 512 MB) partition.
- Erase/format as EXT4.
- Click "change" and mount it as
/boot
.
- On my system this is
- Select or create a root partition for Ubuntu.
- On my system this is
/dev/nvme0n1p33
. - Make a note of the root partition path name as you'll need it below.
- It will be erased.
- 5 GB for minimal, 25+ GB for a full installation.
- Click "change" and make it an "physical volume for encryption".
- Choose a password which is not the same as for the other instances.
- On my system this is
- Find the new, unlocked partition ending with
_crypt
.
- On my system this is
/dev/mapper/nvme0n1p33_crypt
. - Change the mount point to root
/
.
- On my system this is
- Let the installer finish, but do not reboot at the end by selecting "Continue testing".
Set up refind
for the new instance.
Enter
chroot
to the new operating system to make more changes.
# NOTE: create temporary mount directories.
sudo mkdir /mnt/bootpartition /mnt/ospartition
# NOTE: Mount the newly created encrypted partition.
sudo mount -o subvol=@ /dev/mapper/nvme0n1p33_crypt /mnt/ospartition
sudo mount /dev/nvme0n1p22 /mnt/bootpartition
# NOTE: Copy the boot files into the encrypted partition.
# NOTE: Watch those trailing slashes! rsync is very sensitive to them.
sudo rsync -aXAH /mnt/bootpartition/ /mnt/ospartition/boot/
sudo mount /dev/nvme0n1p11 /mnt/ospartition/boot/efi
sudo mount --bind /dev /mnt/ospartition/dev
sudo mount --bind /proc /mnt/ospartition/proc
sudo mount --bind /sys /mnt/ospartition/sys
# NOTE: change root to the newly installed Ubuntu.
sudo chroot /mnt/ospartition
- Edit
/etc/fstab
and comment out the line for/boot
. The other entries are correct. - Optional: make other low-level system file changes, such as workarounds for broken drivers1.
- Create an EFI-bootable copy of the kernel (
vmlinuz
) and the initial ramdisk (initrd
) forrefind
. Remember to replaceubuntu-instance
with something of our own. I use "ubuntu-work" and similar. Do not use just "ubuntu" as it might get overwritten by the Ubuntu installer.
# NOTE: Choose your own per-instance directory name.
sudo mkdir /boot/efi/EFI/ubuntu-instance/
sudo cp /boot/vmlinuz* /boot/initrd* /boot/efi/EFI/ubuntu-instance/
- Look for
/dev/nvme0n1p33
, the physical volume for encryption for this instance. Make a note of (or copy to the clipboard) the UUID (but not the PARTUUID).
sudo blkid
- Prepare
refind
's Ubuntu instance kernel boot options for the encrypted partition inrefind_linux.conf
. Create/boot/efi/EFI/ubuntu-instance/refind_linux.conf
from the below template, but with your path and UUID.
"Boot with standard options" "root=/dev/mapper/nvme0n1p33_crypt cryptdevice=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:nvme0n1p33_crypt ro quiet splash"
"Boot to single-user mode" "root=/dev/mapper/nvme0n1p33_crypt cryptdevice=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:nvme0n1p33_crypt ro single"
"Boot with minimal options" "root=/dev/mapper/nvme0n1p33_crypt cryptdevice=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:nvme0n1p33_crypt ro"
- Exit
chroot
and reboot. Remember to select the new kernel inrefind
.
exit
sudo reboot
Cleanup
Optional. This will remove unused boot options in refind
. I like to keep them around as a backup until the system is stable.
- Remove any leftover shared Ubuntu Grub bootloader.
# NOTE: The shared Ubuntu Grub EFI loader might be leftover from previous installations.
#sudo rm -r /boot/efi/EFI/ubuntu/
- Remove files from the unused boot partition.
# NOTE: Optionally clean up files from the Ubuntu installer.
#sudo mkdir /mnt/bootpartition
#sudo mount /dev/nvme0n1p22 /mnt/bootpartition
#sudo rm -r /mnt/bootpartition/*
Maintenance after kernel or driver updates
As Ubuntu doesn't know about refind
, kernel+driver updates require a manual copy step for vmlinuz+initrd.
- After installing updates, but before rebooting, copy the new vmlinuz+initrd from the encrypted
/boot
to the unencrypted ESP'subuntu-instance
like above. - If you forget to do this, and the system broke or new drivers didn't load, boot either:
- Single-user mode from
refind
by choosing custom boot options. - The Ubuntu installer USB/DVD, and mount to temporary locations:
- The encrypted disk which contains
/boot
. - The ESP.
- The encrypted disk which contains
- Copy the vmlinuz+initrd from your
/boot
to the ESP'subuntu-instance
like above.
- Single-user mode from
Future improvements
- If/when there are EFI file system drivers so
refind
can read encrypted LUKS partitions, investigate not keeping the kernels on the unencrypted ESP. This might greatly simplify the above setup. - Figure out if kernel+driver updates can automatically trigger updating the per-instance ESP vmlinuz+initrd copy for
refind
. - Improve temporary boot partition usage with one of:
- Configure the temporary boot partition as encrypted swap space in each of the Linux instances.
- Reusing the ESP for temporary
/boot
files. Didn't want the added risk of destroying the ESP by accidentally formatting it or similar, but might work just as well.
Inspiration
Thank you!
@Aleksandr Dubinsky's answer to "Ubuntu full disk encryption with encrypted /boot".
@StefK's answer to "Installing Ubuntu 12.04 without installing Grub".
@Rod Smith's answer to "How do I install two independent Ubuntu installations on a single hard drive with UEFI?"- Many more answers, articles, documentation written by Roderick W. Smith, who is the author of
refind
. - Ubuntu's installation documentation for desktop usage.
1 This Wayland plus Nvidia grapics driver problem caught me. It causes a black screen after the disk has been unlocked. Luckily it's easy to fix and Wayland can be restored once updated Nvidia drivers have been installed -- just remember to copy the updated kernel+initrd to your ESP.
1
See also: help.ubuntu.com/community/ManualFullSystemEncryption Full-system encryption with manual control and dual-booting Paddy Landau ubuntuforums.org/showthread.php?t=2357627
– oldfred
Mar 29 at 13:42
add a comment |
Ideas
- Use
refind
rather thangrub
to manage system selection during UEFI/Secure Boot. - Don't use a separate
/boot
partition per Linux instance. Letrefind
boot the kernel directly from the EFI system partition (ESP). - Set up Linux Unified Key Setup (LUKS) from the Ubuntu installer.
- Note that the current solution doesn't encrypt the kernel files, as booting directly to encrypted disks is not supported by
refind
.
Overview
- Obviously create multiple backups of any valuable data beforehand. Changing the boot procedure, formatting disks, enabling encryption, etcetera can be hazardous and care needs to be taken.
- Install Windows first.
- Seems to be a general recommendation, though should matter less with UEFI.
- It will prepare the GPT and ESP, this can also be done manually using GNOME Partition Editor from the Ubuntu USB/DVD.
- The ESP created by the Windows installer might not be big enough, depending on the number of Ubuntu instances and kernel sizes. 512 MB seems enough for 2 Ubuntu-instances, but 1 GB would be safer and allow more instances.
- Install
refind
and make sure it boots with Secure Boot. - For each desired Ubuntu system instance:
- Run the default Ubuntu installer from USB or DVD.
- Select the option "Something else" to manually set up encryption and select partitions.
- Don't reboot after the installation, but stay to setup the
refind
boot process.
- Over time, perform maintenance tasks if there are kernel or driver updates.
Per-instance installation
Assumes that the GUID Partition Table (GPT) and the ESP has been set up by the Windows installer, and that there are additional partitions(s) or empty disk space for the Ubuntu instance(s).
Partition paths and names
For consistency I'll use this partition path naming below. Paths will be different on your system, and will vary by instance, so please keep notes.
/dev/nvme0n1p11
is your ESP.
/dev/nvme0n1p22
is your temporary/boot
partition.
/dev/nvme0n1p33
is your per-instance "physical volume for encryption" (locked) root/
partition.
/dev/mapper/nvme0n1p33_crypt
is your (unlocked) root/
partition.
Partition and install a new (additional) Ubuntu instance
- Get Ubuntu on USB or DVD, boot it selecting "Try out Ubuntu".
- Open a terminal to update and start the installer.
sudo apt update && sudo apt dist-upgrade -y
ubiquity --no-bootloader
- When asked about installation type (co-existing with other operating systems) and disk formatting/partitioning, select "Something else" to see a list of disks and partitions.
- Find the partition with type
efi
, the ESP.
- On my system this is
/dev/nvme0n1p11
. - Make a note of the partition path name as you'll need it below.
- Check that it has at least 200 MB free before continuing, as it will be needed for the new instance kernel.
- On my system this is
- Select or create a boot partition.
- On my system this is
/dev/nvme0n1p22
. - Make a note of the boot partition path name as you'll need it below.
- Will be reused for subsequent Ubuntu instance installations.
- Create or select a small (maximum 512 MB) partition.
- Erase/format as EXT4.
- Click "change" and mount it as
/boot
.
- On my system this is
- Select or create a root partition for Ubuntu.
- On my system this is
/dev/nvme0n1p33
. - Make a note of the root partition path name as you'll need it below.
- It will be erased.
- 5 GB for minimal, 25+ GB for a full installation.
- Click "change" and make it an "physical volume for encryption".
- Choose a password which is not the same as for the other instances.
- On my system this is
- Find the new, unlocked partition ending with
_crypt
.
- On my system this is
/dev/mapper/nvme0n1p33_crypt
. - Change the mount point to root
/
.
- On my system this is
- Let the installer finish, but do not reboot at the end by selecting "Continue testing".
Set up refind
for the new instance.
Enter
chroot
to the new operating system to make more changes.
# NOTE: create temporary mount directories.
sudo mkdir /mnt/bootpartition /mnt/ospartition
# NOTE: Mount the newly created encrypted partition.
sudo mount -o subvol=@ /dev/mapper/nvme0n1p33_crypt /mnt/ospartition
sudo mount /dev/nvme0n1p22 /mnt/bootpartition
# NOTE: Copy the boot files into the encrypted partition.
# NOTE: Watch those trailing slashes! rsync is very sensitive to them.
sudo rsync -aXAH /mnt/bootpartition/ /mnt/ospartition/boot/
sudo mount /dev/nvme0n1p11 /mnt/ospartition/boot/efi
sudo mount --bind /dev /mnt/ospartition/dev
sudo mount --bind /proc /mnt/ospartition/proc
sudo mount --bind /sys /mnt/ospartition/sys
# NOTE: change root to the newly installed Ubuntu.
sudo chroot /mnt/ospartition
- Edit
/etc/fstab
and comment out the line for/boot
. The other entries are correct. - Optional: make other low-level system file changes, such as workarounds for broken drivers1.
- Create an EFI-bootable copy of the kernel (
vmlinuz
) and the initial ramdisk (initrd
) forrefind
. Remember to replaceubuntu-instance
with something of our own. I use "ubuntu-work" and similar. Do not use just "ubuntu" as it might get overwritten by the Ubuntu installer.
# NOTE: Choose your own per-instance directory name.
sudo mkdir /boot/efi/EFI/ubuntu-instance/
sudo cp /boot/vmlinuz* /boot/initrd* /boot/efi/EFI/ubuntu-instance/
- Look for
/dev/nvme0n1p33
, the physical volume for encryption for this instance. Make a note of (or copy to the clipboard) the UUID (but not the PARTUUID).
sudo blkid
- Prepare
refind
's Ubuntu instance kernel boot options for the encrypted partition inrefind_linux.conf
. Create/boot/efi/EFI/ubuntu-instance/refind_linux.conf
from the below template, but with your path and UUID.
"Boot with standard options" "root=/dev/mapper/nvme0n1p33_crypt cryptdevice=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:nvme0n1p33_crypt ro quiet splash"
"Boot to single-user mode" "root=/dev/mapper/nvme0n1p33_crypt cryptdevice=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:nvme0n1p33_crypt ro single"
"Boot with minimal options" "root=/dev/mapper/nvme0n1p33_crypt cryptdevice=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:nvme0n1p33_crypt ro"
- Exit
chroot
and reboot. Remember to select the new kernel inrefind
.
exit
sudo reboot
Cleanup
Optional. This will remove unused boot options in refind
. I like to keep them around as a backup until the system is stable.
- Remove any leftover shared Ubuntu Grub bootloader.
# NOTE: The shared Ubuntu Grub EFI loader might be leftover from previous installations.
#sudo rm -r /boot/efi/EFI/ubuntu/
- Remove files from the unused boot partition.
# NOTE: Optionally clean up files from the Ubuntu installer.
#sudo mkdir /mnt/bootpartition
#sudo mount /dev/nvme0n1p22 /mnt/bootpartition
#sudo rm -r /mnt/bootpartition/*
Maintenance after kernel or driver updates
As Ubuntu doesn't know about refind
, kernel+driver updates require a manual copy step for vmlinuz+initrd.
- After installing updates, but before rebooting, copy the new vmlinuz+initrd from the encrypted
/boot
to the unencrypted ESP'subuntu-instance
like above. - If you forget to do this, and the system broke or new drivers didn't load, boot either:
- Single-user mode from
refind
by choosing custom boot options. - The Ubuntu installer USB/DVD, and mount to temporary locations:
- The encrypted disk which contains
/boot
. - The ESP.
- The encrypted disk which contains
- Copy the vmlinuz+initrd from your
/boot
to the ESP'subuntu-instance
like above.
- Single-user mode from
Future improvements
- If/when there are EFI file system drivers so
refind
can read encrypted LUKS partitions, investigate not keeping the kernels on the unencrypted ESP. This might greatly simplify the above setup. - Figure out if kernel+driver updates can automatically trigger updating the per-instance ESP vmlinuz+initrd copy for
refind
. - Improve temporary boot partition usage with one of:
- Configure the temporary boot partition as encrypted swap space in each of the Linux instances.
- Reusing the ESP for temporary
/boot
files. Didn't want the added risk of destroying the ESP by accidentally formatting it or similar, but might work just as well.
Inspiration
Thank you!
@Aleksandr Dubinsky's answer to "Ubuntu full disk encryption with encrypted /boot".
@StefK's answer to "Installing Ubuntu 12.04 without installing Grub".
@Rod Smith's answer to "How do I install two independent Ubuntu installations on a single hard drive with UEFI?"- Many more answers, articles, documentation written by Roderick W. Smith, who is the author of
refind
. - Ubuntu's installation documentation for desktop usage.
1 This Wayland plus Nvidia grapics driver problem caught me. It causes a black screen after the disk has been unlocked. Luckily it's easy to fix and Wayland can be restored once updated Nvidia drivers have been installed -- just remember to copy the updated kernel+initrd to your ESP.
1
See also: help.ubuntu.com/community/ManualFullSystemEncryption Full-system encryption with manual control and dual-booting Paddy Landau ubuntuforums.org/showthread.php?t=2357627
– oldfred
Mar 29 at 13:42
add a comment |
Ideas
- Use
refind
rather thangrub
to manage system selection during UEFI/Secure Boot. - Don't use a separate
/boot
partition per Linux instance. Letrefind
boot the kernel directly from the EFI system partition (ESP). - Set up Linux Unified Key Setup (LUKS) from the Ubuntu installer.
- Note that the current solution doesn't encrypt the kernel files, as booting directly to encrypted disks is not supported by
refind
.
Overview
- Obviously create multiple backups of any valuable data beforehand. Changing the boot procedure, formatting disks, enabling encryption, etcetera can be hazardous and care needs to be taken.
- Install Windows first.
- Seems to be a general recommendation, though should matter less with UEFI.
- It will prepare the GPT and ESP, this can also be done manually using GNOME Partition Editor from the Ubuntu USB/DVD.
- The ESP created by the Windows installer might not be big enough, depending on the number of Ubuntu instances and kernel sizes. 512 MB seems enough for 2 Ubuntu-instances, but 1 GB would be safer and allow more instances.
- Install
refind
and make sure it boots with Secure Boot. - For each desired Ubuntu system instance:
- Run the default Ubuntu installer from USB or DVD.
- Select the option "Something else" to manually set up encryption and select partitions.
- Don't reboot after the installation, but stay to setup the
refind
boot process.
- Over time, perform maintenance tasks if there are kernel or driver updates.
Per-instance installation
Assumes that the GUID Partition Table (GPT) and the ESP has been set up by the Windows installer, and that there are additional partitions(s) or empty disk space for the Ubuntu instance(s).
Partition paths and names
For consistency I'll use this partition path naming below. Paths will be different on your system, and will vary by instance, so please keep notes.
/dev/nvme0n1p11
is your ESP.
/dev/nvme0n1p22
is your temporary/boot
partition.
/dev/nvme0n1p33
is your per-instance "physical volume for encryption" (locked) root/
partition.
/dev/mapper/nvme0n1p33_crypt
is your (unlocked) root/
partition.
Partition and install a new (additional) Ubuntu instance
- Get Ubuntu on USB or DVD, boot it selecting "Try out Ubuntu".
- Open a terminal to update and start the installer.
sudo apt update && sudo apt dist-upgrade -y
ubiquity --no-bootloader
- When asked about installation type (co-existing with other operating systems) and disk formatting/partitioning, select "Something else" to see a list of disks and partitions.
- Find the partition with type
efi
, the ESP.
- On my system this is
/dev/nvme0n1p11
. - Make a note of the partition path name as you'll need it below.
- Check that it has at least 200 MB free before continuing, as it will be needed for the new instance kernel.
- On my system this is
- Select or create a boot partition.
- On my system this is
/dev/nvme0n1p22
. - Make a note of the boot partition path name as you'll need it below.
- Will be reused for subsequent Ubuntu instance installations.
- Create or select a small (maximum 512 MB) partition.
- Erase/format as EXT4.
- Click "change" and mount it as
/boot
.
- On my system this is
- Select or create a root partition for Ubuntu.
- On my system this is
/dev/nvme0n1p33
. - Make a note of the root partition path name as you'll need it below.
- It will be erased.
- 5 GB for minimal, 25+ GB for a full installation.
- Click "change" and make it an "physical volume for encryption".
- Choose a password which is not the same as for the other instances.
- On my system this is
- Find the new, unlocked partition ending with
_crypt
.
- On my system this is
/dev/mapper/nvme0n1p33_crypt
. - Change the mount point to root
/
.
- On my system this is
- Let the installer finish, but do not reboot at the end by selecting "Continue testing".
Set up refind
for the new instance.
Enter
chroot
to the new operating system to make more changes.
# NOTE: create temporary mount directories.
sudo mkdir /mnt/bootpartition /mnt/ospartition
# NOTE: Mount the newly created encrypted partition.
sudo mount -o subvol=@ /dev/mapper/nvme0n1p33_crypt /mnt/ospartition
sudo mount /dev/nvme0n1p22 /mnt/bootpartition
# NOTE: Copy the boot files into the encrypted partition.
# NOTE: Watch those trailing slashes! rsync is very sensitive to them.
sudo rsync -aXAH /mnt/bootpartition/ /mnt/ospartition/boot/
sudo mount /dev/nvme0n1p11 /mnt/ospartition/boot/efi
sudo mount --bind /dev /mnt/ospartition/dev
sudo mount --bind /proc /mnt/ospartition/proc
sudo mount --bind /sys /mnt/ospartition/sys
# NOTE: change root to the newly installed Ubuntu.
sudo chroot /mnt/ospartition
- Edit
/etc/fstab
and comment out the line for/boot
. The other entries are correct. - Optional: make other low-level system file changes, such as workarounds for broken drivers1.
- Create an EFI-bootable copy of the kernel (
vmlinuz
) and the initial ramdisk (initrd
) forrefind
. Remember to replaceubuntu-instance
with something of our own. I use "ubuntu-work" and similar. Do not use just "ubuntu" as it might get overwritten by the Ubuntu installer.
# NOTE: Choose your own per-instance directory name.
sudo mkdir /boot/efi/EFI/ubuntu-instance/
sudo cp /boot/vmlinuz* /boot/initrd* /boot/efi/EFI/ubuntu-instance/
- Look for
/dev/nvme0n1p33
, the physical volume for encryption for this instance. Make a note of (or copy to the clipboard) the UUID (but not the PARTUUID).
sudo blkid
- Prepare
refind
's Ubuntu instance kernel boot options for the encrypted partition inrefind_linux.conf
. Create/boot/efi/EFI/ubuntu-instance/refind_linux.conf
from the below template, but with your path and UUID.
"Boot with standard options" "root=/dev/mapper/nvme0n1p33_crypt cryptdevice=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:nvme0n1p33_crypt ro quiet splash"
"Boot to single-user mode" "root=/dev/mapper/nvme0n1p33_crypt cryptdevice=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:nvme0n1p33_crypt ro single"
"Boot with minimal options" "root=/dev/mapper/nvme0n1p33_crypt cryptdevice=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:nvme0n1p33_crypt ro"
- Exit
chroot
and reboot. Remember to select the new kernel inrefind
.
exit
sudo reboot
Cleanup
Optional. This will remove unused boot options in refind
. I like to keep them around as a backup until the system is stable.
- Remove any leftover shared Ubuntu Grub bootloader.
# NOTE: The shared Ubuntu Grub EFI loader might be leftover from previous installations.
#sudo rm -r /boot/efi/EFI/ubuntu/
- Remove files from the unused boot partition.
# NOTE: Optionally clean up files from the Ubuntu installer.
#sudo mkdir /mnt/bootpartition
#sudo mount /dev/nvme0n1p22 /mnt/bootpartition
#sudo rm -r /mnt/bootpartition/*
Maintenance after kernel or driver updates
As Ubuntu doesn't know about refind
, kernel+driver updates require a manual copy step for vmlinuz+initrd.
- After installing updates, but before rebooting, copy the new vmlinuz+initrd from the encrypted
/boot
to the unencrypted ESP'subuntu-instance
like above. - If you forget to do this, and the system broke or new drivers didn't load, boot either:
- Single-user mode from
refind
by choosing custom boot options. - The Ubuntu installer USB/DVD, and mount to temporary locations:
- The encrypted disk which contains
/boot
. - The ESP.
- The encrypted disk which contains
- Copy the vmlinuz+initrd from your
/boot
to the ESP'subuntu-instance
like above.
- Single-user mode from
Future improvements
- If/when there are EFI file system drivers so
refind
can read encrypted LUKS partitions, investigate not keeping the kernels on the unencrypted ESP. This might greatly simplify the above setup. - Figure out if kernel+driver updates can automatically trigger updating the per-instance ESP vmlinuz+initrd copy for
refind
. - Improve temporary boot partition usage with one of:
- Configure the temporary boot partition as encrypted swap space in each of the Linux instances.
- Reusing the ESP for temporary
/boot
files. Didn't want the added risk of destroying the ESP by accidentally formatting it or similar, but might work just as well.
Inspiration
Thank you!
@Aleksandr Dubinsky's answer to "Ubuntu full disk encryption with encrypted /boot".
@StefK's answer to "Installing Ubuntu 12.04 without installing Grub".
@Rod Smith's answer to "How do I install two independent Ubuntu installations on a single hard drive with UEFI?"- Many more answers, articles, documentation written by Roderick W. Smith, who is the author of
refind
. - Ubuntu's installation documentation for desktop usage.
1 This Wayland plus Nvidia grapics driver problem caught me. It causes a black screen after the disk has been unlocked. Luckily it's easy to fix and Wayland can be restored once updated Nvidia drivers have been installed -- just remember to copy the updated kernel+initrd to your ESP.
Ideas
- Use
refind
rather thangrub
to manage system selection during UEFI/Secure Boot. - Don't use a separate
/boot
partition per Linux instance. Letrefind
boot the kernel directly from the EFI system partition (ESP). - Set up Linux Unified Key Setup (LUKS) from the Ubuntu installer.
- Note that the current solution doesn't encrypt the kernel files, as booting directly to encrypted disks is not supported by
refind
.
Overview
- Obviously create multiple backups of any valuable data beforehand. Changing the boot procedure, formatting disks, enabling encryption, etcetera can be hazardous and care needs to be taken.
- Install Windows first.
- Seems to be a general recommendation, though should matter less with UEFI.
- It will prepare the GPT and ESP, this can also be done manually using GNOME Partition Editor from the Ubuntu USB/DVD.
- The ESP created by the Windows installer might not be big enough, depending on the number of Ubuntu instances and kernel sizes. 512 MB seems enough for 2 Ubuntu-instances, but 1 GB would be safer and allow more instances.
- Install
refind
and make sure it boots with Secure Boot. - For each desired Ubuntu system instance:
- Run the default Ubuntu installer from USB or DVD.
- Select the option "Something else" to manually set up encryption and select partitions.
- Don't reboot after the installation, but stay to setup the
refind
boot process.
- Over time, perform maintenance tasks if there are kernel or driver updates.
Per-instance installation
Assumes that the GUID Partition Table (GPT) and the ESP has been set up by the Windows installer, and that there are additional partitions(s) or empty disk space for the Ubuntu instance(s).
Partition paths and names
For consistency I'll use this partition path naming below. Paths will be different on your system, and will vary by instance, so please keep notes.
/dev/nvme0n1p11
is your ESP.
/dev/nvme0n1p22
is your temporary/boot
partition.
/dev/nvme0n1p33
is your per-instance "physical volume for encryption" (locked) root/
partition.
/dev/mapper/nvme0n1p33_crypt
is your (unlocked) root/
partition.
Partition and install a new (additional) Ubuntu instance
- Get Ubuntu on USB or DVD, boot it selecting "Try out Ubuntu".
- Open a terminal to update and start the installer.
sudo apt update && sudo apt dist-upgrade -y
ubiquity --no-bootloader
- When asked about installation type (co-existing with other operating systems) and disk formatting/partitioning, select "Something else" to see a list of disks and partitions.
- Find the partition with type
efi
, the ESP.
- On my system this is
/dev/nvme0n1p11
. - Make a note of the partition path name as you'll need it below.
- Check that it has at least 200 MB free before continuing, as it will be needed for the new instance kernel.
- On my system this is
- Select or create a boot partition.
- On my system this is
/dev/nvme0n1p22
. - Make a note of the boot partition path name as you'll need it below.
- Will be reused for subsequent Ubuntu instance installations.
- Create or select a small (maximum 512 MB) partition.
- Erase/format as EXT4.
- Click "change" and mount it as
/boot
.
- On my system this is
- Select or create a root partition for Ubuntu.
- On my system this is
/dev/nvme0n1p33
. - Make a note of the root partition path name as you'll need it below.
- It will be erased.
- 5 GB for minimal, 25+ GB for a full installation.
- Click "change" and make it an "physical volume for encryption".
- Choose a password which is not the same as for the other instances.
- On my system this is
- Find the new, unlocked partition ending with
_crypt
.
- On my system this is
/dev/mapper/nvme0n1p33_crypt
. - Change the mount point to root
/
.
- On my system this is
- Let the installer finish, but do not reboot at the end by selecting "Continue testing".
Set up refind
for the new instance.
Enter
chroot
to the new operating system to make more changes.
# NOTE: create temporary mount directories.
sudo mkdir /mnt/bootpartition /mnt/ospartition
# NOTE: Mount the newly created encrypted partition.
sudo mount -o subvol=@ /dev/mapper/nvme0n1p33_crypt /mnt/ospartition
sudo mount /dev/nvme0n1p22 /mnt/bootpartition
# NOTE: Copy the boot files into the encrypted partition.
# NOTE: Watch those trailing slashes! rsync is very sensitive to them.
sudo rsync -aXAH /mnt/bootpartition/ /mnt/ospartition/boot/
sudo mount /dev/nvme0n1p11 /mnt/ospartition/boot/efi
sudo mount --bind /dev /mnt/ospartition/dev
sudo mount --bind /proc /mnt/ospartition/proc
sudo mount --bind /sys /mnt/ospartition/sys
# NOTE: change root to the newly installed Ubuntu.
sudo chroot /mnt/ospartition
- Edit
/etc/fstab
and comment out the line for/boot
. The other entries are correct. - Optional: make other low-level system file changes, such as workarounds for broken drivers1.
- Create an EFI-bootable copy of the kernel (
vmlinuz
) and the initial ramdisk (initrd
) forrefind
. Remember to replaceubuntu-instance
with something of our own. I use "ubuntu-work" and similar. Do not use just "ubuntu" as it might get overwritten by the Ubuntu installer.
# NOTE: Choose your own per-instance directory name.
sudo mkdir /boot/efi/EFI/ubuntu-instance/
sudo cp /boot/vmlinuz* /boot/initrd* /boot/efi/EFI/ubuntu-instance/
- Look for
/dev/nvme0n1p33
, the physical volume for encryption for this instance. Make a note of (or copy to the clipboard) the UUID (but not the PARTUUID).
sudo blkid
- Prepare
refind
's Ubuntu instance kernel boot options for the encrypted partition inrefind_linux.conf
. Create/boot/efi/EFI/ubuntu-instance/refind_linux.conf
from the below template, but with your path and UUID.
"Boot with standard options" "root=/dev/mapper/nvme0n1p33_crypt cryptdevice=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:nvme0n1p33_crypt ro quiet splash"
"Boot to single-user mode" "root=/dev/mapper/nvme0n1p33_crypt cryptdevice=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:nvme0n1p33_crypt ro single"
"Boot with minimal options" "root=/dev/mapper/nvme0n1p33_crypt cryptdevice=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:nvme0n1p33_crypt ro"
- Exit
chroot
and reboot. Remember to select the new kernel inrefind
.
exit
sudo reboot
Cleanup
Optional. This will remove unused boot options in refind
. I like to keep them around as a backup until the system is stable.
- Remove any leftover shared Ubuntu Grub bootloader.
# NOTE: The shared Ubuntu Grub EFI loader might be leftover from previous installations.
#sudo rm -r /boot/efi/EFI/ubuntu/
- Remove files from the unused boot partition.
# NOTE: Optionally clean up files from the Ubuntu installer.
#sudo mkdir /mnt/bootpartition
#sudo mount /dev/nvme0n1p22 /mnt/bootpartition
#sudo rm -r /mnt/bootpartition/*
Maintenance after kernel or driver updates
As Ubuntu doesn't know about refind
, kernel+driver updates require a manual copy step for vmlinuz+initrd.
- After installing updates, but before rebooting, copy the new vmlinuz+initrd from the encrypted
/boot
to the unencrypted ESP'subuntu-instance
like above. - If you forget to do this, and the system broke or new drivers didn't load, boot either:
- Single-user mode from
refind
by choosing custom boot options. - The Ubuntu installer USB/DVD, and mount to temporary locations:
- The encrypted disk which contains
/boot
. - The ESP.
- The encrypted disk which contains
- Copy the vmlinuz+initrd from your
/boot
to the ESP'subuntu-instance
like above.
- Single-user mode from
Future improvements
- If/when there are EFI file system drivers so
refind
can read encrypted LUKS partitions, investigate not keeping the kernels on the unencrypted ESP. This might greatly simplify the above setup. - Figure out if kernel+driver updates can automatically trigger updating the per-instance ESP vmlinuz+initrd copy for
refind
. - Improve temporary boot partition usage with one of:
- Configure the temporary boot partition as encrypted swap space in each of the Linux instances.
- Reusing the ESP for temporary
/boot
files. Didn't want the added risk of destroying the ESP by accidentally formatting it or similar, but might work just as well.
Inspiration
Thank you!
@Aleksandr Dubinsky's answer to "Ubuntu full disk encryption with encrypted /boot".
@StefK's answer to "Installing Ubuntu 12.04 without installing Grub".
@Rod Smith's answer to "How do I install two independent Ubuntu installations on a single hard drive with UEFI?"- Many more answers, articles, documentation written by Roderick W. Smith, who is the author of
refind
. - Ubuntu's installation documentation for desktop usage.
1 This Wayland plus Nvidia grapics driver problem caught me. It causes a black screen after the disk has been unlocked. Luckily it's easy to fix and Wayland can be restored once updated Nvidia drivers have been installed -- just remember to copy the updated kernel+initrd to your ESP.
edited Mar 30 at 12:51
answered Mar 29 at 12:14
Joel PurraJoel Purra
1166
1166
1
See also: help.ubuntu.com/community/ManualFullSystemEncryption Full-system encryption with manual control and dual-booting Paddy Landau ubuntuforums.org/showthread.php?t=2357627
– oldfred
Mar 29 at 13:42
add a comment |
1
See also: help.ubuntu.com/community/ManualFullSystemEncryption Full-system encryption with manual control and dual-booting Paddy Landau ubuntuforums.org/showthread.php?t=2357627
– oldfred
Mar 29 at 13:42
1
1
See also: help.ubuntu.com/community/ManualFullSystemEncryption Full-system encryption with manual control and dual-booting Paddy Landau ubuntuforums.org/showthread.php?t=2357627
– oldfred
Mar 29 at 13:42
See also: help.ubuntu.com/community/ManualFullSystemEncryption Full-system encryption with manual control and dual-booting Paddy Landau ubuntuforums.org/showthread.php?t=2357627
– oldfred
Mar 29 at 13:42
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1129672%2fhow-to-run-multiple-ubuntu-18-x-with-separate-partition-encryption-and-uefi-secu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown