Do you remember when the breaking systems were initially setup? - there were changes to how booting is handled for btrfs installs during PVE 8.0 - so it would help to know which ones make problems for you.
* Are those UEFI or legacy BIOS setups...
Do the guests in question have a RNG device configured?
(see the changelog for PVE 8.4 - UEFI PXE boot needs on in recent versions : https://pve.proxmox.com/wiki/Roadmap#8.4-known-issues)
Thanks for the reminder about this thread!
both the pve8to9 check and our recommendation have changed (since I suggested to keep systemd-boot installed).
Currently you should uninstall the package if you don't need it (no root on ZFS with uefi) -...
The check was adapted in the mean time to deal with that situation:
https://lore.proxmox.com/all/175466070754.625540.12444949078147201723.b4-ty@proxmox.com/T/#u
(the current recommendation is to remove the systemd-boot meta-package after...
that usually doesn't mean that it hangs at that point, but that you don't get any of the rest of the output. you could try booting with "quiet" removed from the kernel cmdline (you can edit it for one boot in the Grub menu by hitting 'e'), that...
Thanks that does sound quite sensible indeed! - I tried adapting the docs accordingly:
https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Systemd-boot_meta-package_changes_the_bootloader_configuration_automatically_and_should_be_uninstalled
@Stoiko Ivanov ,
Yes. That part was clear. I understood the problem--I just wasn't quite clear on how to deal with it. :)
This is the part that confused me a bit.
Looking at the wiki:
It was not clear to me just from reading this when the...
in this case it's not mounted, because you have ZFS on `/` and use proxmox-boot-tool for managing the boot-loader :) (similarly for pve-root and swap(on ZFS no swap is created)
on systems installed on ext4+lvm-thin it needs to be mounted.
I...
just to be on the safe side - you mean /etc/sysctl.conf?
theoretically yes - but see the man page sysctl.d(5):
`It is recommended to prefix all filenames with a two-digit number and a dash, to simplify the ordering of the files` - so maybe...
Thanks!
hm - not sure how grub deals with /boot/efi being a mdraid - I'd suggest:
* checking `efibootmgr -v`
* ensureing that bootx64.efi (a.k.a removable grub entry) gets updated as well:
echo 'grub-efi-amd64 grub2/force_efi_extra_removable...
see https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Prerequisites:
(that is before changing the sources to trixie - you should install all pending updates)
I hope this helps!
For anyone still looking for a solution, my /boot/EFI partition had some corruption. Running an fsck and fixing the errors on the partition resolved this for me.
not necessarily - the only thing that is odd about it as far as I can see is that you have both:
* using proxmox-boot-tool for booting (ZFS system on legacy boot)
* one of the ESPs mounted at /boot/efi (on a legacy boot system!)
I'd recomment...
it looks like I could eventually fix it as I force-reinstalled grub-efi-amd64 which was broken during upgrade process.
Phew ! Thanks for your assistance !
it sounds like you are booting from the removable boot loader entry, and did not update that one, so now there is a mismatch between the first part of grub and the rest of grub on the ESP..
could you post the output of "efibootmgr -v" (from a...