You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an Arch Linux system with ZFSBootMenu running. It works perfectly fine with the prebuilt EFI release image downloadable at https://get.zfsbootmenu.org/efi. However, I can't get a generate-zbm EFI bundle to kexec into my kernel and initramfs; only the prebuilt image can do that.
When I boot into my self-compiled EFI bundle ZFSBootMenu doesn't seem to correctly hand control over to the ZFS dataset's kernel and initramfs and instead reboots the machine. With the prebuilt EFI release image no such reboot happens, that one just works perfectly.
I guess this post boils down to: what makes the prebuilt EFI release image kexec into my kernel and initramfs that I can't replicate with the self-built EFI bundle? I'm assuming kernel and initramfs files are perfectly fine since they do work when paired with the prebuilt EFI release image. Even my self-compiled image can see my kernel and initramfs, it just doesn't boot into them. Is there some debugging I can do to better understand what exactly is causing a reboot where the prebuilt EFI release image instead does a clean kexec?
I'd appreciate a second pair of eyes pointing me at what I'm missing. Thanks!
I've confirmed that this is an upstream kernel problem, and fixes are out of our hands. It will be fixed in Void (and any future ZBM build containers) once void-linux/void-packages#49529 lands.
Discussed in #598
Originally posted by Contik March 1, 2024
Hi all,
I have an Arch Linux system with ZFSBootMenu running. It works perfectly fine with the prebuilt EFI release image downloadable at https://get.zfsbootmenu.org/efi. However, I can't get a
generate-zbm
EFI bundle tokexec
into my kernel and initramfs; only the prebuilt image can do that.When I boot into my self-compiled EFI bundle ZFSBootMenu doesn't seem to correctly hand control over to the ZFS dataset's kernel and initramfs and instead reboots the machine. With the prebuilt EFI release image no such reboot happens, that one just works perfectly.
I guess this post boils down to: what makes the prebuilt EFI release image
kexec
into my kernel and initramfs that I can't replicate with the self-built EFI bundle? I'm assuming kernel and initramfs files are perfectly fine since they do work when paired with the prebuilt EFI release image. Even my self-compiled image can see my kernel and initramfs, it just doesn't boot into them. Is there some debugging I can do to better understand what exactly is causing a reboot where the prebuilt EFI release image instead does a cleankexec
?I'd appreciate a second pair of eyes pointing me at what I'm missing. Thanks!
Here's what I have:
mkinitcpio
with dependencies met per docs:/etc/zfsbootmenu/config.yaml
has:/etc/zfsbootmenu/mkinitcpio.conf
has:/efi
where/efi/EFI/ZBM/vmlinuz.EFI
sits next to Windows Boot Manager files:mkinitcpio
preset file at/etc/mkinitcpio.d/linux.preset
has:/etc/mkinitcpio.conf
has:bootfs
property set:zpool/root/archlinux-frn
is currently the only root boot environmentorg.zfsbootmenu:commandline
set like so:keylocation
in myencryptionroot
is set as:mkinitcpio -P
will embed the samezpool.key
file into initramfs via/etc/mkinitcpio.conf
linux
kernel and an initramfs live at/boot
inside the encrypted zpoollsinitcpio
confirms that the key file lands in my initramfs:The text was updated successfully, but these errors were encountered: