InsanePrawn
commented
4 years ago - What type of key is used for the root dataset?
- Can you narrow down which item exactly needs to be dropped from the dependency list in which unit file to make it boot?
The candidate files should be
-.mountandzfs-load-key-rootpool-ROOT.service. [hint: to override a generated unit completely, copy it from/run/systemd/generator/to/etc/systemd/systemand modify the copy. May need an initcpio rebuild?]
Arch specifics:
- Which bootloader are you using?
- Where is your /boot located?
- Can you post the
HOOKS=line from your mkinitcpio.conf?
My laptop currently boots arch configured something like this:
Let me preface this with "This feels like a terrible hack". There we go. My /boot is on a LUKS partition, the unencrypted EFI partition holds only grub.efi, the rest is on encrypted ZFS. Don't ask. :) I've had to drop the stock arch zfs[-sd] hooks as they wouln't successfully load the keys or sometimes not even import the pool. Instead I chose to use the `systemd` hook itself. So now we get this mess in mkinitcpio.conf. Sigh. ``` FILES=(/etc/keys/*.key /etc/zfs/zpool.cache /usr/lib/systemd/system/systemd-udev-settle.service /etc/udev/rules.d/* /etc/systemd/system/{zfs-load-key-zroot.service,sysroot.mount,initrd-switch-root.service.requires/*}) [...] HOOKS=(base keyboard systemd sd-vconsole autodetect modconf block encrypt filesystems usr fsck) ``` and a manually created `sysroot.mount` (slightly modified `-.mount`) ``` systemctl cat sysroot.mount # /etc/systemd/system/sysroot.mount # Automatically generated by zfs-mount-generator [Unit] SourcePath=/etc/zfs/zfs-list.cache/zroot Documentation=man:zfs-mount-generator(8) Before=zfs-mount.service initrd-switch-root.service After=zfs-import.target zfs-load-key-zroot.service Wants=zfs-import.target zfs-load-key-zroot.service [Mount] Where=/sysroot What=zroot/os/ROOT/default Type=zfs Options=defaults,noatime,dev,exec,rw,suid,nomand,zfsutil ``` aaaand a modified keyload service. The `RequiresMountsFor` the key file caused dependency cycles for me too IIRC. ``` systemctl cat zfs-load-key-zroot.service # /etc/systemd/system/zfs-load-key-zroot.service [Unit] Description=Load ZFS key for zroot #SourcePath=/etc/zfs/zfs-list.cache/zroot Documentation=man:zfs-mount-generator(8) DefaultDependencies=no Wants=systemd-udev-settle.service After=systemd-udev-settle.service systemd-udev-trigger.service cryptsetup.target Before=zfs-mount.service initrd-switch-root.service #RequiresMountsFor='/etc/keys/zroot.key' #RequiresMountsFor= [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/sh -c '/usr/bin/udevadm settle; /usr/bin/zpool import -N zroot; set -eu;keystatus="$$(/usr/bin/zfs get -H -o value keystatus "zroot")";[ "$$keystatus" = "unavailable" ] || exit 0;/usr/bin/zfs load-key "zroot"' ``` This is probably not everything someone would need to replicate my setup, but it might help you get on the right way. I'm not sure myself if all of these modifications are necessary or the best way to do things, the udev stuff is definitely a big question mark to me right now, but at this point I'm just glad I got a booting laptop and will leave testing the finer details to the brave and/or people with VMs. :) Seeing how I'm not willing to touch this often, this might have gotten easier to do. Note that my setup will ignore the `root=` kernel cmdline.
deadbeef2000
rlaager
mtippmann
System information
Describe the problem you're observing
I have recently updated from ZFS 0.8.3 to ZFS 0.8.4. I am using the zfs-mount-generator and I used the instructions from the arch wiki. I've got one ZPOOL (rootpool), with 3 datasets, ROOT, ROOT/HOME, ROOT/SWAP. rootpool/ROOT is encrypted with a passphrase. After the upgrade, systemd complained about ordering cycles on bootup
Describe how to reproduce the problem
Use systemd-mount-generator with an encryted dataset for the root filesystem.
Include any warning/errors/backtraces from the system logs
With zfs-import-scan.service:
With zfs-import-cache.service:
How to get it fixed (not properly!)
Edit /usr/lib/systemd/system-generators/zfs-mount-generator Remove the content of after and before on lines 113 and 114 Comment out line 207 (after="${after} ${keyloadunit}")
It removes the (actually rather useful) dependencies to avoid the ordering cycle with systemd-journald.socket.