Add Makefile, update documentation, clean up VERSION
* Add a basic Makefile, that copies files to to the system. Limited test on a Void linux system only. * Clean up the README.md to include more detailed documentation on integration with rEFInd and efibootmgr, how to use generate-zbm, and other tidbits. * Remove the VERSION file loading from generate-zbm, prefer the internal version string now. This simplifies deployment greatly.
This commit is contained in:
Zach Dykstra
parent
e8d2ba43f0
commit
7f09058c2c
|
|
@ -0,0 +1,7 @@
|
|||
.PHONY: install zfsbootmenu
|
||||
|
||||
install: zfsbootmenu
|
||||
install -t $(DESTDIR)$(PREFIX)/etc/zfsbootmenu/ -D etc/zfsbootmenu/config.ini
|
||||
install -t $(DESTDIR)$(PREFIX)/etc/zfsbootmenu/dracut.conf.d/ -D etc/zfsbootmenu/dracut.conf.d/*
|
||||
install -m 0755 -t $(DESTDIR)$(PREFIX)/usr/lib/dracut/modules.d/90zfsbootmenu -D 90zfsbootmenu/*
|
||||
install -m 0755 bin/generate-zbm $(DESTDIR)$(PREFIX)/bin/generate-zbm
|
||||
169
README.md
169
README.md
|
|
@ -25,8 +25,8 @@ At this point, you'll be booting into your OS-managed kernel and initramfs, alon
|
|||
This tool makes uses of the following additional software:
|
||||
* [fzf](https://github.com/junegunn/fzf)
|
||||
* [kexec-tools](https://github.com/horms/kexec-tools)
|
||||
* Linux (currently 5.3.10)
|
||||
* ZFS (currently 0.8.2 for Void Linux).
|
||||
* Linux Kernel
|
||||
* ZFS on Linux (currently 0.8.2 built on Void Linux).
|
||||
|
||||
Binary releases for x86_64 and ppc64le are built on Void Linux hosts.
|
||||
|
||||
|
|
@ -38,13 +38,12 @@ To ensure the boot menu can find your kernels, you'll need to ensure `/boot` res
|
|||
NAME USED AVAIL REFER MOUNTPOINT
|
||||
zroot 278G 582G 96K none
|
||||
zroot/ROOT 10.9G 582G 96K none
|
||||
zroot/ROOT/void.2019.08.20 6.20M 582G 6.13G /
|
||||
zroot/ROOT/void.2019.10.04 1.20M 582G 7.17G /
|
||||
zroot/ROOT/void.2019.11.01 10.9G 582G 7.17G /
|
||||
zroot/home 120G 582G 11.8G /home
|
||||
```
|
||||
|
||||
There are three boot environments created, identified by mounting to /. The environment that this system will boot into is defined by the `bootfs` value set on the `zroot` zpool.
|
||||
There are two boot environments created, identified by mounting to /. The environment that this system will boot into is defined by the `bootfs` value set on the `zroot` zpool.
|
||||
|
||||
```
|
||||
NAME PROPERTY VALUE SOURCE
|
||||
|
|
@ -55,46 +54,170 @@ On start, ZFS Boot Menu will find the highest versioned kernel in `zroot/ROOT/vo
|
|||
|
||||
# Installation
|
||||
|
||||
If you're coming from a legacy installation with `/boot` on EFI, EXT4, etc, you'll need to create `/boot` on the ZFS filesystem and then copy the contents from the old `/boot` into it.
|
||||
In the boot environment, the file `/etc/default/grub` will need to be created with the variable `GRUB_CMDLINE_LINUX_DEFAULT` defined. These are the kernel arguments passed to the kernel in your boot environment. Do not set any `root=` or any other pool-related options here. This value will be filled in when a boot environment is selected.
|
||||
|
||||
The file `/etc/default/grub` will need to be created with the variable `GRUB_CMDLINE_LINUX_DEFAULT` defined. These are the kernel arguments passed to the kernel in your boot environment. For example, I have the following set:
|
||||
For example, I have the following set:
|
||||
|
||||
```
|
||||
GRUB_CMDLINE_LINUX_DEFAULT="zfs.zfs_arc_max=8589934592 elevator=noop modprobe.blacklist=ast video=offb:off amdgpu.dc=1 radeon.cik_support=0 amdgpu.cik_support=1 amdgpu.dpm=1"
|
||||
GRUB_CMDLINE_LINUX_DEFAULT="zfs.zfs_arc_max=8589934592 elevator=noop"
|
||||
```
|
||||
|
||||
Finally, you'll need to now put the ZFS Boot Menu kernel and initramfs somewhere where a low-level bootloader (Grub, a UEFI implementation, etc) can read them. I have a simple 512M partition on my boot drive that is mounted to `/efi`.
|
||||
|
||||
## EFI
|
||||
|
||||
ZFS Boot Menu integrates nicely with an EFI system. There will be two key things to configure here.
|
||||
|
||||
* The mountpoint of the EFI partition and it's contents
|
||||
* The mountpoint of the boot environment `/boot` and it's contents
|
||||
|
||||
Each boot environment should have `/boot` live on the ZFS filesystem. Using the above example, `zroot/ROOT/void.2019.11.01` would contain `/boot` with any kernel/initramfs pairs.
|
||||
|
||||
```
|
||||
# ls /efi | more
|
||||
vmlinuz-bootmenu
|
||||
initramfs-bootmenu.img
|
||||
# ls /boot
|
||||
config-5.3.18_1
|
||||
config-5.4.6_1
|
||||
efi
|
||||
initramfs-5.3.18_1.img
|
||||
initramfs-5.4.6_1.img
|
||||
System.map-5.3.18_1
|
||||
System.map-5.4.6_1
|
||||
vmlinuz-5.3.18_1
|
||||
vmlinuz-5.4.6_1
|
||||
```
|
||||
|
||||
The easiest way now is to add an option to boot into this kernel. You'll need to know the following:
|
||||
* Your hostid, determined by simply running `hostid`
|
||||
* Your preferred pool name if you have multiple
|
||||
|
||||
From here, you can add an entry via `efibootmgr`:
|
||||
Once `/boot` is backed by ZFS in a boot environment, you'll need to install the boot menu files. Typically, EFI partitions are mounted to `/boot/efi`, and contain a number of sub-directories. In this example, `/boot/efi/EFI/void` holds the ZFS Boot Menu kernel and initramfs.
|
||||
|
||||
```
|
||||
# lsblk -f /dev/sda
|
||||
NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
|
||||
sdg
|
||||
├─sda1 vfat AFC2-35EE 7.9G 1% /boot/efi
|
||||
└─sda2 swap 412401b6-4aec-4452-a6bd-6fc20fbdc2a5 [SWAP]
|
||||
|
||||
# ls /boot/efi/EFI/void/
|
||||
initramfs-0.7.4.img
|
||||
initramfs-0.7.5.img
|
||||
vmlinuz-0.7.4
|
||||
vmlinuz-0.7.5
|
||||
```
|
||||
|
||||
|
||||
With this layout, you'll now need a way to boot the kernel and initramfs via EFI. This can be done via a manual entry set via efibootmgr, or it can be done with rEFInd.
|
||||
|
||||
If you are using a pre-built kernel and initramfs downloaded from the releases page, you'll need to identify the following additional details:
|
||||
|
||||
* Your system's hostid (`hostid`). It's important that this command is executed as root, to ensure that it returns the correct value.
|
||||
* Your boot pool name, if you have multiple.
|
||||
* The disk path and partition index of your EFI partition. (/dev/sda, part 1)
|
||||
|
||||
### efibootmgr
|
||||
|
||||
|
||||
```
|
||||
efibootmgr --disk /dev/sda \
|
||||
--part 1 \
|
||||
--create \
|
||||
--label "ZFS Boot Menu" \
|
||||
--loader /vmlinuz-bootmenu \
|
||||
--unicode 'root=zfsbootmenu:POOL=zroot ro initrd=\initramfs-bootmenu.img quiet spl_hostid=`hostid`' \
|
||||
--loader /vmlinuz-0.7.5 \
|
||||
--unicode 'root=zfsbootmenu:POOL=zroot ro initrd=\EFI\void\initramfs-0.7.5.img quiet spl_hostid=a8c0a2a8' \
|
||||
--verbose
|
||||
```
|
||||
|
||||
This command assumes that both the kernel and the initramfs are in the top level directory of your EFI partition. From here, you will be able to reboot and pick `ZFS Boot Menu` from your UEFI boot menu, and then from there boot into your ZFS boot environment.
|
||||
Take note to adjust `zfsbootmenu:POOL=`, `spl_hostid=`, `--disk` and `--part` to match your system configuration.
|
||||
|
||||
Each time the bootmenu is updated, a new EFI entry will need to be manually added.
|
||||
|
||||
### rEFInd
|
||||
|
||||
`rEFInd` is considerably easier to install and manage. Refer to your distributions packages for installation. Once rEFInd` has been installed, you can create `refind_linux.conf` in the directory holding the ZFS Boot Menu files (`/boot/efi/EFI/void` in our example):
|
||||
|
||||
```
|
||||
"Boot Default BE" "ro quiet loglevel=0 timeout=0 zfsbootmenu:POOL= spl_hostid="
|
||||
"Select BE" "ro quiet loglevel=0 timeout=-1 zfsbootmenu:POOL= spl_hostid="
|
||||
```
|
||||
|
||||
|
||||
As with the efibootmgr section, the `zfsbootmenu:POOL=` and `spl_hostid=` options need to be configured to match your environment.
|
||||
|
||||
This file will configure `rEFInd` to create two entries for each kernel and initrams pair it finds. The first will directly boot into the environment set via the `bootfs` pool property. The second will force ZFS Boot Menu to display an environment / kernel / snapshot selection menu, allowing you to boot alternate environments, kernels and snapshots.
|
||||
|
||||
# Command line options
|
||||
|
||||
ZFS Boot Menu currently understands the following options:
|
||||
|
||||
* `spl_hostid=` used to set the system hostid if you are using a pre-built initramfs from the release page.
|
||||
* `force_import=0|1` set to `1` to attempt to force import all pools on the system. Use with caution!
|
||||
* `read_write=0|1` set to `1` to enable writes to pools when importing. Pools are imported read-only by default as a safety precaution.
|
||||
* `timeout=`
|
||||
* A value of `0` will result in the system immediately booting from the pool configured in the `bootfs` pool property
|
||||
* A value of `-1` will result in the system displaying a boot menu.
|
||||
* Any other positive value will show a countdown timer to boot the environment configured under `bootfs`, otherwise it will default to a boot menu.
|
||||
* `""|zfsbootmenu|zfsbootmenu:|zfsbootmenu:POOL=zroot` The first three values are functionally identical. The fourth can be used to prefer a pool if multiple are present in the system.
|
||||
|
||||
|
||||
# initramfs creation
|
||||
|
||||
`bin/generate-zbm` can be used to create an initramfs on your system. It ships with void-specific defaults in `etc/config.ini`. To create an initramfs, the following additional tools/libraries will need to be available on your system:
|
||||
|
||||
* [fzf](https://github.com/junegunn/fzf)
|
||||
* [kexec-tools](https://github.com/horms/kexec-tools)
|
||||
* [perl Config::IniFiles](https://metacpan.org/pod/Config::IniFiles)
|
||||
|
||||
If you want to create an unified EFI file (kernel, initramfs, command line), the following additional tools will be needed:
|
||||
|
||||
* gnu objcopy (typically packaged as binutils)
|
||||
* linuxx64.efi.stub (typically packaged as gummiboot)
|
||||
|
||||
Your distribution should have packages for these already.
|
||||
|
||||
## config.ini
|
||||
|
||||
`/etc/zfsbootmenu/config.ini` is used to control the behavior of generate-zbm. An example is documented below.
|
||||
|
||||
```
|
||||
[Global]
|
||||
ManageImages=0
|
||||
DracutConfDir=/etc/zfsbootmenu/dracut.conf.d
|
||||
|
||||
[Kernel]
|
||||
CommandLine="ro quiet loglevel=0"
|
||||
|
||||
[Components]
|
||||
ImageDir=/boot/efi/EFI/void
|
||||
Versioned=1
|
||||
Copies=3
|
||||
|
||||
[EFI]
|
||||
ImageDir=/boot/efi/EFI/void
|
||||
Versioned=1
|
||||
Copies=0
|
||||
```
|
||||
|
||||
### Global
|
||||
* `ManageImages` Set this to 1 to allow generate-zbm to perform any actions (creation, removal of old files, etc)
|
||||
* `DracutConfDir` Set this to the location of the dracut configuration director for ZFS Boot Menu. This *CAN NOT* be the same location as the system `dracut.conf.d`, as the configuration files there directly conflict with the creation of the bootmenu initramfs.
|
||||
|
||||
### Kernel
|
||||
* `CommandLine` If you're making a unified EFI file, this is the command line passed to the module. Refer to [Command line options](README.md#command-line-options).
|
||||
|
||||
### Components
|
||||
* `ImageDir` This is the destination directory for the initramfs and kernel.
|
||||
* `Versioned` Set to 1 to create versioned files. Set to 0 to disable a version suffix, which is useful if you have static bootloader entries pointing to ZFS Boot Menu.
|
||||
* `Copies` This controls the number of copies to keep, in addition to the file that is currently being created.
|
||||
|
||||
### EFI
|
||||
* `ImageDir` This is the destination directory for the unified EFI file.
|
||||
* `Versioned` Set to 1 to create versioned files. Set to 0 to disable a version suffix, which is useful if you have static bootloader entries pointing to ZFS Boot Menu.
|
||||
* `Copies` This controls the number of copies to keep, in addition to the file that is currently being created.
|
||||
|
||||
|
||||
# Native encryption
|
||||
|
||||
ZFS Boot Menu can import pools or filesystems with native encryption enabled. If your boot environments are not encrypted but say /home is, you will not receive a decryption prompt. To ensure that you can decrypt your pool to load the kernel and initramfs, you'll need to ensure that you have the the filesystem parameters configured correctly.
|
||||
ZFS Boot Menu can import pools or filesystems with native encryption enabled. If your boot environments are not encrypted but say /home is, you will not receive a decryption prompt. To ensure that you can decrypt your pool to load the kernel and initramfs, you'll need to you have the filesystem parameters configured correctly.
|
||||
|
||||
```
|
||||
zfs get all zroot | egrep '(encryption|keylocation|keyformat)'
|
||||
Password:
|
||||
zfs get all zroot | egrep '(encryption|keylocation|keyformat)'
|
||||
zroot encryption aes-256-gcm -
|
||||
zroot keylocation file:///etc/zfs/zroot.key local
|
||||
zroot keyformat passphrase -
|
||||
|
|
@ -110,6 +233,8 @@ install_items+=" /etc/zfs/zroot.key "
|
|||
|
||||
It's critical that you do not put this key file into the ZFS Boot Menu initramfs, since that file exists on an unencrypted volume - leaving your pool essentially wide-open.
|
||||
|
||||
|
||||
|
||||
# Limitations
|
||||
|
||||
Currently, the kernel command line for the boot environment is read from `/etc/default/grub`. I'd like to support multiple locations determined by probing the OS installed in the boot environment.
|
||||
|
|
@ -117,5 +242,3 @@ Currently, the kernel command line for the boot environment is read from `/etc/d
|
|||
When building a kernel command line to pass to the kexec'd kernel, the command line generated is always created for Dracut's ZFS module. Again, this will need to be modified based on the detected OS in the boot environment.
|
||||
|
||||
Both of the above issues are readily resolved by hopefully reading /etc/os-release from the boot environment and acting based on that.
|
||||
|
||||
Because this is implemented as a full kernel and initramfs, it doesn't really fit into the way your distribution ships/installs packages. It doesn't make any sense for your OS to install these two files into `/boot`. They need to be placed in an implementation-dependent location so that GRUB, EFI, etc can read them. This makes updating the boot menu on an installed system slightly more burdensome, since your normal package update process won't see updates.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,8 @@
|
|||
use strict;
|
||||
use warnings;
|
||||
|
||||
our $VERSION = '0.7.5';
|
||||
|
||||
use Getopt::Long qw(:config no_ignore_case auto_version);
|
||||
use Pod::Usage qw(pod2usage);
|
||||
use File::Basename;
|
||||
|
|
@ -26,10 +28,10 @@ sub safeCopy;
|
|||
my ( %runConf, %config, %components );
|
||||
|
||||
my $configfile = "/etc/zfsbootmenu/config.ini";
|
||||
my $version_file = "/usr/share/zfsbootmenu/VERSION";
|
||||
|
||||
$runConf{bootdir} = "/boot";
|
||||
$runConf{confd} = "/usr/share/zfsbootmenu/dracut.conf.d";
|
||||
$runConf{version} = $VERSION;
|
||||
|
||||
GetOptions(
|
||||
"version|v=s" => \$runConf{version},
|
||||
|
|
@ -61,19 +63,6 @@ if ( defined $config{Global}{DracutConfDir} ) {
|
|||
$runConf{confd} = $config{Global}{DracutConfDir};
|
||||
}
|
||||
|
||||
# Sanity check that we can determine the version of zfsbootmenu
|
||||
unless ( defined $runConf{version} ) {
|
||||
if ( -f $version_file ) {
|
||||
open( my $fh, '<', $version_file );
|
||||
read $fh, $runConf{version}, -s $fh;
|
||||
close($fh);
|
||||
chomp( $runConf{version} );
|
||||
} else {
|
||||
print "Unable to determine version\n";
|
||||
exit;
|
||||
}
|
||||
}
|
||||
|
||||
# Create a temp directory
|
||||
# It is automatically purged on program exit
|
||||
my $dir = File::Temp->newdir();
|
||||
|
|
|
|||
Loading…
Reference in New Issue