Replies: 1 comment
-
False alarm. I simply forgot to update my initramfs before I rebooted (sudo update-initramfs -c -k all). [Thank you Zdykstra for pointing me in the right direction to solve the problem.] I also forgot that /boot/efi wasn't automounted in zfsbootmenu chroot. I only had to "mount /boot/efi" to mount it. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I upgraded an Ubuntu system recently to the next distro version and was unable to boot. I could get into zfsbootmenu ok. When I tried to boot the boot environment I got the following error.
Dracut fatal don't know how to handle root=zfs:rpool/ROOT/ubuntu
I realise there have been a few breaking changes this year with a new version of ZFS and also breaking changes in zfsbootmenu so possibly I've just experienced those. I can just revert the VM to go back to before I upgraded. I was wondering if there was a way to fix the issue from chrooting into the system from zfsbootmenu? There may be some users who can't so easily revert to a previous VM state.
I tried unsuccessfully setting a zfsbootmenu root prefix property on the pool and also editing the kernel command line in the refind config. The esp wasn’t available to mount at /boot/efi either. So I couldn’t update zfsbootmenu.
Beta Was this translation helpful? Give feedback.
All reactions