Difference between revisions of "Install LVM LUKS on UEFI GPT"

From Void Linux Wiki
Jump to: navigation, search
m (made the warning about UEFI more severe)
(Wikified. Hopefully clarified some points too.)
Line 1: Line 1:
<p>This guide describes how to install <code>Void Linux</code> on a UEFI system with root over encrypted LVM.</p>
+
This guide describes how to install [[Void Linux]] on a UEFI system with root over encrypted LVM.
  
<h2>Introduction</h2>
+
==Introduction==
 
{{Warning|If you do not boot from UEFI mode, the bootloader installation will fail!}}
 
{{Warning|If you do not boot from UEFI mode, the bootloader installation will fail!}}
<p>To follow this guide, first you need to boot from a Linux live CD/USB of your choice in UEFI mode.</p>
 
  
<p>For UEFI boot, the disk needs to be <code>GPT</code> partitioned and an <code>EFI System Partition</code> (ESP) must be present.
+
To follow this guide, first you need to boot from a Linux live CD/USB of your choice in UEFI mode.
The size of the ESP must be at least <code>260M</code> or more, type <code>EF00</code>, and formatted with <code>FAT32</code>.</p>
 
  
<p>This partition will serve as your <code>/boot</code> filesystem as well as the partition that the UEFI firmware can read to load the bootloader.</p>
+
For UEFI boot, the disk needs to be {{ic|GPT}} partitioned and an {{ic|EFI System Partition}} (ESP) must be present. The size of the ESP must be at least {{ic|260M}} or more, type {{ic|EF00}}, and formatted with {{ic|FAT32}}.
  
<p>From now on, <code>/dev/sda1</code> will be the ESP (<code>/boot</code>) and <code>/dev/sda2</code> will be the encrypted partition with LVM.</p>
+
This partition will serve as your {{ic|/boot}} filesystem as well as the partition that the UEFI firmware can read to load the bootloader.
  
<h2>Installation</h2>
+
From now on, {{ic|/dev/sda1}} will be the ESP ({{ic|/boot}}) and {{ic|/dev/sda2}} will be the encrypted partition with LVM.
  
<h3>Preparing the installer</h3>
+
==Installation==
  
<p>Make sure the local install media is up to date before starting.</p>
+
===Preparing the installer===
  
<pre># xbps-install -Su
+
Make sure the local install media is up to date before starting:
</pre>
 
  
<h3>Preparing the disk</h3>
+
# xbps-install -Su
  
<p>The first step is to use <code>gdisk</code> (or <code>cgdisk</code>) to create the GPT partitions:</p>
+
===Preparing the disk===
  
<pre># gdisk /dev/sda
+
The first step is to use {{ic|gdisk}} (or {{ic|cgdisk}}) to create the GPT partitions:
</pre>
 
  
<blockquote>
+
# gdisk /dev/sda
<p><strong>Tip</strong>: you can also use <code>fdisk/cfdisk</code> (needs <code>util-linux&gt;=2.25</code>).</p>
 
</blockquote>
 
  
<h3>Encrypting the partition</h3>
+
{{Note|You can also use {{ic|fdisk}} or {{ic|cfdisk}} (needs {{pkg|util-linux}} 2.25 or newer)}}
  
<p>We will encrypt the entire <code>/dev/sda2</code> partition and then unlock the container to start setting up LVM:</p>
+
===Encrypting the partition===
  
<pre># cryptsetup luksFormat /dev/sda2
+
We will encrypt the entire {{ic|/dev/sda2}} partition and then unlock the container to start setting up LVM:
# cryptsetup luksOpen /dev/sda2 crypt
 
</pre>
 
  
<p>The decrypted container will be now available at <code>/dev/mapper/crypt</code>.</p>
+
# cryptsetup luksFormat /dev/sda2
 +
# cryptsetup luksOpen /dev/sda2 crypt
  
<blockquote>
+
The decrypted container will be now available at {{ic|/dev/mapper/crypt}}.
<p><strong>Warning</strong>: the default keyboard layout is <code>us</code>. If you enter the passphrase using a different keymap, you likely won't be able to unlock your crypted volume.</p>
 
</blockquote>
 
  
<h3>Creating logical volumes</h3>
+
{{Warning|The default keyboard layout is {{ic|us}}. If you enter the passphrase using a different keymap, you likely won't be able to unlock your crypted volume.}}
  
<p>First, we will create a physical volume on top of the opened LUKS container and a volume group, named <code>void</code>. Then, we will setup the logical volumes on the volume group. The partition scheme is defined as follows:</p>
+
===Creating logical volumes===
  
<ul>
+
First, we will create a physical volume on top of the opened LUKS container and a volume group, named {{ic|void}}. Then, we will setup the logical volumes on the volume group. The partition scheme is defined as follows:
<li>
 
<code>swap</code> -- 2G (optional)</li>
 
<li>
 
<code>/</code> -- 20G</li>
 
<li>
 
<code>/home</code> -- the remaining free space</li>
 
</ul>
 
  
<blockquote>
+
<center>
<p><strong>Note</strong>: the above partitioning scheme is an example. Please, change it to suit your needs.</p>
+
{| class="wikitable"
</blockquote>
+
|-
 +
| swap
 +
| 2G (optional)
 +
|-
 +
| /
 +
| 20G
 +
|-
 +
| /home
 +
| the remaining free space
 +
|}
 +
</center>
  
<pre># pvcreate /dev/mapper/crypt
+
{{Note|The above partitioning scheme is an example. Please, change it to suit your needs.}}
# vgcreate void /dev/mapper/crypt
 
# lvcreate -C y -L 2G -n swap void (optional)
 
# lvcreate -L 20G -n root void
 
# lvcreate -l 100%FREE -n home void
 
</pre>
 
  
<h3>Creating filesystems and mounting the partitions</h3>
+
# pvcreate /dev/mapper/crypt
 +
# vgcreate void /dev/mapper/crypt
 +
# lvcreate -C y -L 2G -n swap void (optional)
 +
# lvcreate -L 20G -n root void
 +
# lvcreate -l 100%FREE -n home void
  
<p>The ESP <strong>must</strong> be formatted in <code>FAT32</code>. The root and home partition are formatted using the <code>ext4</code> filesystem.</p>
+
===Creating filesystems and mounting the partitions===
  
<p>The root partition is mounted on <code>/mnt</code>, while the ESP to <code>/mnt/boot</code>.</p>
+
The ESP '''must''' be formatted in {{ic|FAT32}}. The root and home partitions are formatted using the {{ic|ext4}} filesystem.
  
<pre># mkfs.fat -F32 /dev/sda1
+
The root partition is mounted on {{ic|/mnt}}, while the ESP is on {{ic|/mnt/boot}}.
# mkfs.ext4 /dev/mapper/void-root
 
# mkfs.ext4 /dev/mapper/void-home
 
# mount /dev/mapper/void-root /mnt
 
# mkdir /mnt/boot
 
# mount /dev/sda1 /mnt/boot
 
</pre>
 
  
<p>If you have created a swap partition, then you have to format and activate it:</p>
+
# mkfs.fat -F32 /dev/sda1
 +
# mkfs.ext4 /dev/mapper/void-root
 +
# mkfs.ext4 /dev/mapper/void-home
 +
# mount /dev/mapper/void-root /mnt
 +
# mkdir /mnt/boot
 +
# mount /dev/sda1 /mnt/boot
  
<pre># mkswap /dev/mapper/void-swap
+
If you have created a swap partition, then you have to format and activate it:
# swapon /dev/mapper/void-swap
 
</pre>
 
  
<h3>Install the base system</h3>
+
# mkswap /dev/mapper/void-swap
 +
# swapon /dev/mapper/void-swap
  
<h5>If doing this from a void live cd or any void system</h5>
+
===Install the base system===
  
<pre># xbps-install -S --repository=http://repo.voidlinux.eu/current -r /mnt base-system lvm2 cryptsetup grub-x86_64-efi
+
====If doing this from a Void live CD or any Void system====
</pre>
 
  
<h5>From any other linux</h5>
+
# xbps-install -S --repository=<nowiki>http://repo.voidlinux.eu/current</nowiki> -r /mnt base-system lvm2 cryptsetup grub-x86_64-efi
  
<pre># wget http://repo.voidlinux.eu/static/xbps-static-latest.x86_64-musl.tar.xz
+
====From any other Linux====
# tar xf xbps-static-latest.x86_64-musl.tar.xz -C /mnt
 
# /mnt/usr/bin/xbps-install -S --repository=http://repo.voidlinux.eu/current -r /mnt base-system lvm2 cryptsetup grub-x86_64-efi
 
</pre>
 
  
<h3>Chroot into Void</h3>
+
# wget <nowiki>http://repo.voidlinux.eu/static/xbps-static-latest.x86_64-musl.tar.xz</nowiki>
 +
# tar xf xbps-static-latest.x86_64-musl.tar.xz -C /mnt
 +
# /mnt/usr/bin/xbps-install -S --repository=<nowiki>http://repo.voidlinux.eu/current</nowiki> -r /mnt base-system lvm2 cryptsetup grub-x86_64-efi
  
<p>Now that the base system is installed, it's time to enter our new Void Linux environment by chrooting into it:</p>
+
===Chroot into Void===
  
<pre># mkdir /mnt/{dev,proc,sys}
+
Now that the base system is installed, it's time to enter our new Void Linux environment by chrooting into it:
# mount -t proc /proc /mnt/proc
 
# mount --rbind /dev /mnt/dev
 
# mount --rbind /sys /mnt/sys
 
# chroot /mnt /bin/bash
 
</pre>
 
  
<h3>Configure the base system</h3>
+
# mkdir /mnt/{dev,proc,sys}
 +
# mount -t proc /proc /mnt/proc
 +
# mount --rbind /dev /mnt/dev
 +
# mount --rbind /sys /mnt/sys
 +
# chroot /mnt /bin/bash
  
<p>In this step, we will set the root password, edit the mandatory configuration files and install the bootloader (GRUB).</p>
+
===Configure the base system===
  
<pre># passwd root
+
In this step, we will set the root password, edit the mandatory configuration files and install the bootloader (GRUB).
# chown root:root /
 
# chmod 755 /
 
# vi /etc/rc.conf
 
# blkid | grep void-root | cut -f2 -d\" >> /etc/fstab
 
# vi /etc/fstab
 
# echo myhostname &gt; /etc/hostname
 
# grub-mkconfig -o /boot/grub/grub.cfg
 
# grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Void Linux [GRUB]" --recheck
 
</pre>
 
  
<blockquote>
+
# passwd root
<p><strong>Warning</strong>: add <code>hostonly=yes</code> in <code>/etc/dracut.conf.d/hostonly.conf</code> and in <code>/etc/default/grub</code> add <code>rd.auto=1</code> to the line GRUB_CMDLINE_LINUX_DEFAULT="..."</p>
+
# chown root:root /
</blockquote>
+
# chmod 755 /
 +
# vi /etc/rc.conf
 +
# blkid | grep void-root | cut -f2 -d\" >> /etc/fstab
 +
# vi /etc/fstab
 +
# echo myhostname &gt; /etc/hostname
 +
# grub-mkconfig -o /boot/grub/grub.cfg
 +
# grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Void Linux [GRUB]" --recheck
  
<h2>Configure glibc locale</h2>
+
{{Warning|Add {{ic|1=hostonly=yes}} in {{path|/etc/dracut.conf.d/hostonly.conf}}. Also, in {{path|/etc/default/grub}} you must add {{ic|1=rd.auto=1}} to the line {{ic|1=GRUB_CMDLINE_LINUX_DEFAULT="..."}}.}}
  
<p>Uncomment your preferred locales in /etc/default/libc-locales </p>
+
==Configure glibc locale==
  
<pre># xbps-reconfigure -f glibc-locales
+
Uncomment your preferred locales in {{path|/etc/default/libc-locales}}.
</pre>
 
  
<h2>Configure dracut</h2>
+
# xbps-reconfigure -f glibc-locales
  
<p>Finally, force update of dracut with:</p>
+
Then, configure dracut and finally force update of dracut with:
  
<pre># xbps-reconfigure -f linux4.xx
+
# xbps-reconfigure -f linux4.xx
</pre>
 
  
<h3>Exit chroot, unmount the partitions and reboot</h3>
+
===Exit chroot, unmount the partitions and reboot===
  
<pre># exit
+
# exit
# umount -R /mnt
+
# umount -R /mnt
# reboot
+
# reboot
</pre>
 
  
<p>If this fails to boot, try the technique described here: [[A Note About GRUB And UEFI|A Note About GRUB And UEFI]]</p>
+
If this fails to boot, see [[Installation on UEFI, via chroot#If GRUB cannot be found (a note about UEFI)|this note about UEFI]].
  
<p>Note that we used /boot and not /boot/efi, so you need to drop the ../efi/.. and run</p>
+
Note that we used /boot and not /boot/efi, so you need to drop the ../efi/.. and then run:
  
<pre>mkdir /boot/EFI/BOOT
+
# mkdir /boot/EFI/BOOT
cp -p /boot/EFI/GRUB/grubx64.efi /boot/EFI/BOOT/bootx64.efi
+
# cp -p /boot/EFI/GRUB/grubx64.efi /boot/EFI/BOOT/bootx64.efi
</pre>
 
 
 
<p>Enjoy and welcome to the Void!</p>
 
  
 +
Enjoy, and welcome to the Void!
 
      
 
      
 
[[Category:Guides]]
 
[[Category:Guides]]
 
[[Category:Installation]]
 
[[Category:Installation]]

Revision as of 10:31, 20 December 2017

This guide describes how to install Void Linux on a UEFI system with root over encrypted LVM.

Introduction

Warning: If you do not boot from UEFI mode, the bootloader installation will fail!

To follow this guide, first you need to boot from a Linux live CD/USB of your choice in UEFI mode.

For UEFI boot, the disk needs to be GPT partitioned and an EFI System Partition (ESP) must be present. The size of the ESP must be at least 260M or more, type EF00, and formatted with FAT32.

This partition will serve as your /boot filesystem as well as the partition that the UEFI firmware can read to load the bootloader.

From now on, /dev/sda1 will be the ESP (/boot) and /dev/sda2 will be the encrypted partition with LVM.

Installation

Preparing the installer

Make sure the local install media is up to date before starting:

# xbps-install -Su

Preparing the disk

The first step is to use gdisk (or cgdisk) to create the GPT partitions:

# gdisk /dev/sda
Note: You can also use fdisk or cfdisk (needs util-linux 2.25 or newer)

Encrypting the partition

We will encrypt the entire /dev/sda2 partition and then unlock the container to start setting up LVM:

# cryptsetup luksFormat /dev/sda2
# cryptsetup luksOpen /dev/sda2 crypt

The decrypted container will be now available at /dev/mapper/crypt.

Warning: The default keyboard layout is us. If you enter the passphrase using a different keymap, you likely won't be able to unlock your crypted volume.

Creating logical volumes

First, we will create a physical volume on top of the opened LUKS container and a volume group, named void. Then, we will setup the logical volumes on the volume group. The partition scheme is defined as follows:

swap 2G (optional)
/ 20G
/home the remaining free space
Note: The above partitioning scheme is an example. Please, change it to suit your needs.
# pvcreate /dev/mapper/crypt
# vgcreate void /dev/mapper/crypt
# lvcreate -C y -L 2G -n swap void (optional)
# lvcreate -L 20G -n root void
# lvcreate -l 100%FREE -n home void

Creating filesystems and mounting the partitions

The ESP must be formatted in FAT32. The root and home partitions are formatted using the ext4 filesystem.

The root partition is mounted on /mnt, while the ESP is on /mnt/boot.

# mkfs.fat -F32 /dev/sda1
# mkfs.ext4 /dev/mapper/void-root
# mkfs.ext4 /dev/mapper/void-home
# mount /dev/mapper/void-root /mnt
# mkdir /mnt/boot
# mount /dev/sda1 /mnt/boot

If you have created a swap partition, then you have to format and activate it:

# mkswap /dev/mapper/void-swap
# swapon /dev/mapper/void-swap

Install the base system

If doing this from a Void live CD or any Void system

# xbps-install -S --repository=http://repo.voidlinux.eu/current -r /mnt base-system lvm2 cryptsetup grub-x86_64-efi

From any other Linux

# wget http://repo.voidlinux.eu/static/xbps-static-latest.x86_64-musl.tar.xz
# tar xf xbps-static-latest.x86_64-musl.tar.xz -C /mnt
# /mnt/usr/bin/xbps-install -S --repository=http://repo.voidlinux.eu/current -r /mnt base-system lvm2 cryptsetup grub-x86_64-efi

Chroot into Void

Now that the base system is installed, it's time to enter our new Void Linux environment by chrooting into it:

# mkdir /mnt/{dev,proc,sys}
# mount -t proc /proc /mnt/proc
# mount --rbind /dev /mnt/dev
# mount --rbind /sys /mnt/sys
# chroot /mnt /bin/bash

Configure the base system

In this step, we will set the root password, edit the mandatory configuration files and install the bootloader (GRUB).

# passwd root
# chown root:root /
# chmod 755 /
# vi /etc/rc.conf
# blkid | grep void-root | cut -f2 -d\" >> /etc/fstab
# vi /etc/fstab
# echo myhostname > /etc/hostname
# grub-mkconfig -o /boot/grub/grub.cfg
# grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Void Linux [GRUB]" --recheck
Warning: Add hostonly=yes in /etc/dracut.conf.d/hostonly.conf. Also, in /etc/default/grub you must add rd.auto=1 to the line GRUB_CMDLINE_LINUX_DEFAULT="...".

Configure glibc locale

Uncomment your preferred locales in /etc/default/libc-locales.

# xbps-reconfigure -f glibc-locales

Then, configure dracut and finally force update of dracut with:

# xbps-reconfigure -f linux4.xx

Exit chroot, unmount the partitions and reboot

# exit
# umount -R /mnt
# reboot

If this fails to boot, see this note about UEFI.

Note that we used /boot and not /boot/efi, so you need to drop the ../efi/.. and then run:

# mkdir /boot/EFI/BOOT
# cp -p /boot/EFI/GRUB/grubx64.efi /boot/EFI/BOOT/bootx64.efi

Enjoy, and welcome to the Void!