Just to get the steps all in one place for anyone benefiting in the future...
Assuming booted onto system using recovery ISO.
Assuming you are logged in as root.
Assuming a boot disk of sda.
Assuming an EFI partition of sda1.
Assuming a PVE...
Thanks - looking through them (and knowing what to search for) - shows:
Replacing config file /etc/default/grub with new version
Installing for x86_64-efi platform.
grub-install.real: error: cannot find EFI directory.
Failed: grub-install...
yes - can relate to that - it bit me while testing as well ... - We do try to add checks for more common problematic configurations to the `pve8to9` script
(using proxmox-boot-tool, while having the ESP mounted on /boot/efi is nothing I've seen...
Well, a couple more minutes of research and I fixed it. Turns out you also need to mount -o bind /sys/firmware/efi/efivars <target>.
Working. Finally. Thank you! I will search for and post the requested log files shortly.
I guess you have mounted your btrfs (sda3, sdb3 at a directory - for the reminder assume /target)
* check if you have /etc/kernel/proxmox-boot-uuids (this is the check if proxmox-boot-tool is used) - and the contents match the UUIDs of sda2 sda3...
That usually is not a problem - as TLS in SMTP is opportunistic - if your downstream/backend mailserver does not advertise STATTLS PMG should simply transfer the mails without TLS.
If you run into problems - please share the logs - then we might...
hm - there were a few posts about mismatched grub stages after an upgrade ...
I'd check if you can look through the ESP (EFI service partition) and try the proxmox/shim / proxmox/grub or BOOTX64.efi entries on them - most UEFIs have an option to...
updated systemd-boot package will hit the repositories shortly on our end, so that upgrading before removing systemd-boot should avoid triggering this issue.
Thanks - will try reproducing it with the 8.0 ISO - afaics it's a single disk system?
yeah it's not the most straight-forward to read - but it does contain the most information - and in that case it points us to the issue with your system:
This...
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...