UnclePa
I tried to carefully follow the directions for updating the boot tree but now it won't boot at all. Any ideas on what I did wrong and how to fix it?
banned_9-26-2021
Most likely you enabled something through 66-env in the boot module that either has a missing dependency or something not set right.
Like if you don't define swap in /etc/fstab and say use swap=yes it will fail. If you enable zfs, btrfs, and don''t have the right sw it fails.
It is best to remove the existing module 66-disable -t boot boot@ system (if that is the name you used) and enable a new module named something else. 66-enable -t boot boot@ newname ... The default boot module should boot at any system and give you tty1 tty2 and tty12.
If you boot another linux and chroot into it or boot obarun-live you can fix it:
UnclePa
Thanks! I didn't notice that for some reason refind was trying to run the wrong vmlinuz-linux. Normally it defaults to the correct one. Maybe I can blame it on my coffee not being ready when I got up. Sorry for the false alarm.
banned_9-26-2021
Great that it was fixed but how did updating the boot tree effect efi boot? That appears unrelated.
UnclePa
I have no idea. I walked away after entering "reboot", otherwise I would have thought I might have pressed an arrow key or something by mistake. C-A-Delete and it crashed as above and I panicked. After your message I couldn't find my Obarun USB and thought I'd try booting on an old kernel. That's when I noticed refind was defaulting to the wrong one.
banned_9-26-2021
Interesting. Check on /boot/grub/ if you have a file named custom.cfg, if it was left from the past this can only be manually written, a grub update or kernel installation would not affect it.