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
See openzfs/zfs#10355 . REMAKE_INITRD='yes' needs to be added to /etc/dkms/zfs.conf to prevent breakage upon kernel updates, making it impossible to boot.
Took a lot of time to debug and fix, annoying.
Also, the grub changes make it impossible to boot into hetzner's rescue mode, requiring a support ticket to change boot order and make it working again. Please fix this.
Unrelated, but there's a stray 18.04 variable in the script:
Also, the grub changes make it impossible to boot into hetzner's rescue mode, requiring a support ticket to change boot order and make it working again. Please fix this.
can you elaborate this point? on which OS have you experienced it?
crpb
added a commit
to crpb/zfs-hetzner-vm
that referenced
this issue
Jun 13, 2022
I also just ran into the issue of a non-booting system (Debian Bullseye) after an upgrade of linux-image-amd64. Maybe this will keep the doctor(rescue-shell) away in the future.
See openzfs/zfs#10355 .
REMAKE_INITRD='yes'
needs to be added to/etc/dkms/zfs.conf
to prevent breakage upon kernel updates, making it impossible to boot.Took a lot of time to debug and fix, annoying.
Also, the grub changes make it impossible to boot into hetzner's rescue mode, requiring a support ticket to change boot order and make it working again. Please fix this.
Unrelated, but there's a stray 18.04 variable in the script:
zfs-hetzner-vm/hetzner-ubuntu20-zfs-setup.sh
Line 682 in c2bd033
The text was updated successfully, but these errors were encountered: