thanks - which version did you start with? any other specifics how this was setup?
this would also help narrowing this down - s a stock debian bookworm system here has shimx64.efi as configured boot-entry and not grubx64.efi as in your case.
Upgrading from Proxmox 8 to 9 issues; Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.
- Thread starter tessierp
- Start date
this would also help narrowing this down - s a stock debian bookworm system here has shimx64.efi as configured boot-entry and not grubx64.efi as in your case.
Server boots on grub which briefly displays GRUB START then reboot instantly.
I guess EFI boot is wrongly configured as I could manually boots on Legacy BIOS, but couldn't make system boots automatically like before on PVE8.
pve8to9 script didn't raise any warning before.
I Setup it At December 7 2024 (actual stable versions of Debian (this was bookworm or bulseye) and actual Proxmox 7 or 8).
Last edited:
Symptoms for me:
- Protectli VP2420 -- booted straight into BIOS settings. This means it didn't find a bootable operating system.
- HP SFF PC -- booted to a screen literally saying no operating system found.
8 Months ago should have been bookworm - thanks for the info!
Could you (and others affected by grub not booting after upgrade) - also share:
Code:
grep grub /var/log/apt/term.logmaybe my configuration could also help you, I could eventually pinpoint an error in the log which wasn't picked by pve8to9 script (underlined in bold below):
that sounds odd (should not happen with our usual setups) - please share:
* `proxmox-boot-tool status`
* `mount |grep efi`
(thanks for sharing the term.log!)
I most likely have odd setup as motherboard is quite old now, but it used to boot correctly until upgrade to pve9:
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 !
Phew ! Thanks for your assistance !
The info:
Bash:
root@pve33:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
E: /etc/kernel/proxmox-boot-uuids does not exist.
Bash:
root@pve33:~# mount |grep efi
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
/dev/md126 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
Bash:
root@pve33:~# ls -la /var/log/apt/term.log*
-rw-r----- 1 root adm 902118 aug 7 11:34 /var/log/apt/term.log
-rw-r----- 1 root adm 5303 jul 31 06:25 /var/log/apt/term.log.1.gz
-rw-r----- 1 root adm 9978 jun 25 16:08 /var/log/apt/term.log.2.gzOutput of
grep grub /var/log/apt/term.log > pve.txt:Cluster, term.log files are very similar:
pve33.txt (7.26 KB): https://upload.disroot.org/r/LZPfy_1D#+SsBo7abqBuFADsjUOiUeddNr84MNeZSl44isUUJ3h0=
pve22.txt (7.26 KB): https://upload.disroot.org/r/j6VseCGz#Mhy3fcCp+rZBi/NqmfxJ5OGBUTTeOaBDqKKr5Ok8b3I=
pve11.txt (16.23 KB): https://upload.disroot.org/r/Jo0VRTez#PPV9zRSwcw3n2mjObZ/yQH7AfVgLno+KaC2oGJy63vA=
(Links expiration: Saturday, September 6, 2025)
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 removing the fstab entry of /boot/efi - as proxmox-boot-tool does not need it and most boot-loader packages on Debian do something there during upgrades - it's a setup we don't test/support
after removing that and unmounting it once - I'd run a `proxmox-boot-tool reinit` to ensure the upgrade goes through without any warning/error
(of course changing boot-loader configs always has a small potential for problems - so make sure you have a backup and a live-cd to get the system in a bootable state)
I hope this helps!
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:
Code:
echo 'grub-efi-amd64 grub2/force_efi_extra_removable boolean true' | debconf-set-selections -v -u* checking `efibootmgr -v` again to make sure that the proxmox entries are listed as selected
I hope this helps!
I am scared to reboot, cause my efi partition is not in my fstab:
EDIT: Neither is pve root and swap.
Code:
root@pve4:~# cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
root@pve4:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
6BD0-2C08 is configured with: uefi (versions: 6.14.8-2-pve, 6.8.12-13-pve)
root@pve4:~#EDIT: Neither is pve root and swap.
Last edited:
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 hope this helps!
Good to know.in this case it's not mounted, because you have ZFS on `/` and use proxmox-boot-tool for managing the boot-loader
on systems installed on ext4+lvm-thin it needs to be mounted.
I hope this helps!
Thanks!
Just wanted to let someone else know that I was unsuccessful in getting PBS 8 to got 9. Same error as everyone else here, would not reboot, GRUB gave me an error message and that was it. Booting from recovery ISO didn't work either. Ended up re-installing from scratch and re-building. I orignally installed from the PBS 8 iso image & running UEFI on the server, all I did was change the repositires to trixie, and do a apt dist-upgrade like I've done with the PVE 8 to 9 systems.
[deleted]
What an adventure indeed! Just wanted to say thank you for saving me from a reinstall (although I was able to reboot using the Rescue Boot and had backups so it wouldn't have been a huge deal). I also didn't see any warnings of note during pve8to9 -full, and yet this caused a fatal flaw in the upgrade. My previous install was a vanilla PVE 8.4 install from ISO, so I'm not quite sure what went awry.
Ah well, all good now!