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!)
8 Months ago should have been bookworm - thanks for the info!
Could you (and others affected by grub not booting after upgrade) - also share:
grep grub /var/log/apt/term.log
(unless your term.log has been rotated after the upgrade in which...
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.
good find regarding the mismatch of grubx64.efi - how was this system setup?
* proxmox VE ISO or on top of debian?
* when was it setup ? (debian version PVE version)?
This should help us in reproducing the issue.
Thanks!
Yes
Yes - because you're still on PVE-8 (bookworm) - I thought that the following part should explain that:
which is also why the pve8to9 script does not warn you before upgrading to pve-9 (trixie):
I will warn you after upgrading to 9 (at...
Yes your assumption is correct - removing the sytemd-boot meta-package is what we recommend - the patch for pbs3to4 was just a tad to late for the ISO today:
https://lore.proxmox.com/pbs-devel/20250806114909.2143258-1-s.ivanov@proxmox.com/T/#u...
Just a heads up, there are some references to pve filenames rather than pbs filenames in the repository sections - under both codeblock sections, listing: /etc/apt/sources.list.d/pve-enterprise.list & /etc/apt/sources-list.d/pve-install-repo.list
Hi,
if you are on Proxmox VE 9 (based on Debian 13), you should not run the kernel for Proxmox VE 8 (based on Debian 12, the bpo12 means the package was backported for Debian 12). Also make sure the proxmox-default-headers package is installed.
One nitpick: the upgrade guide points people to the pbs-test repository. Maybe show the enterprise and no-subscription repository sources instead (as you did for PVE 9.0), now that it is released? Great work nonetheless!
EDIT: Minor observation...
could you please share the complete logs of the mail - usually there should be logs from pmg-smtp-filter present as well.
without further information I would guess that something caused the mailprocessing to take too long and thus it was not...
Thanks for the report! good catch - https://lore.proxmox.com/pve-devel/20250806110251.2117322-1-s.ivanov@proxmox.com/T/#u
(found that just a short bit before)
In legacy boot there is a little typo in the pve8to9 script.
INFO: Checking bootloader configuration...
INFO: systemd-boot package installed on legacy-boot system is not necessary, consider remoing it
Just for information.
We are pleased to announce the first stable release of Proxmox Backup Server 4.0 - immediately available for download!
The new version is based on the great Debian 13 "Trixie" but we're using a newer Linux kernel 6.14.8-2 as stable default in...
We are pleased to announce the first stable release of Proxmox Backup Server 4.0 - immediately available for download!
The new version is based on the great Debian 13 "Trixie" but we're using a newer Linux kernel 6.14.8-2 as stable default in...
this means you are not using `proxmox-boot-tool` at the moment. please check the output of `pve8to9`, it should tell you if you need to remove or install packages as part of the upgrade.
We tried to make those checks as safe as possible so this should not cause issues.
A bit of background - currently systems:
* having root on ZFS or BTRFS
* booting using UEFI (not legacy bios boot)
* not having secure-boot enabled
use...