I am hoping this helps others as I ran into an issue upgrading my OVH bare metal installs of PVE 8 to 9. OVH Bare metal supplies the templates and I opened a case with them and asked them to test the upgrade because it failed for me as documented by Proxmox. I have yet to fully test this but here is their response that may at least initially help others...
Not sure if anyone at Proxmox has access to an OVH account for bare metal to further test this or others can add additional context so those of us using the OVH templates have a working in place upgrade
Keenan (OVHcloud US) Aug 18, 2025, 5:32 PM EDT Alright, I was able to upgrade successfully from PVE8 --> PVE9 with two deviations from the standard upgrade guide here:
***Please make sure your data is backed up before attempting this, as I was able to do upgrades on a clean box with no production data.***
The only changes I had to make were for the section Update the configured APT repositories --> Update Debian Base Repositories to Trixie
Instead of doing sed -i 's/bookworm/trixie/g' /etc/apt/sources.list
I had to do this: sed -i 's/bookworm/trixie/g' /etc/apt/sources.list.d/debian.sources
I also had to make an undocumented change: sed -i 's/bookworm/trixie/g' /etc/apt/sources.list.d/pve-install-repo.list
Afterwords, following the rest of the guide exactly, I was able to jump up to PVE9.
I believe this is because the default installation calls for editing the sources file at /etc/apt/sources.list, but our template uses this file to reference another file for some reason. There's an additional source that I also updated.
Please note the upgrade process will ask you if you want to replace certain config files during the upgrade process with the newest versions. You'll need to use your discretion on whether or not you should do that, as I don't have any way of knowing what changes you've made to your environment.
For PBS, please check your apt sources list in a similar fashion to make sure the sed command is actually replacing the proper strings. An alternative approach could be using something like nano to go through each file in your apt sources and manually replacing any instance of bookworm with trixie
Hi. After struggling a little to upgrade from Proxmox 8 to 9 on bare metal servers hosted by OVH, I thought I'd explain how I succeeded.
First of all, this is not a generic tutorial, this is just how I could solve my problem on my 2 servers (one "So-yo-start SYS-LE-2" and one "ADVANCE-1 | AMD EPYC 4244P"). It might be different depending on your config, your server model, your partition table, raid etc... So use wisely. Backup first and don't do that in production...
Servers have 2 1TB SSD, they use soft raid, and have an LVM partition for /var/lib/vz. No ZFS.
Hi. After struggling a little to upgrade from Proxmox 8 to 9 on bare metal servers hosted by OVH, I thought I'd explain how I succeeded.
First of all, this is not a generic tutorial, this is just how I could solve my problem on my 2 servers (one "So-yo-start SYS-LE-2" and one "ADVANCE-1 | AMD EPYC 4244P"). It might be different depending on your config, your server model, your partition table, raid etc... So use wisely. Backup first and don't do that in production...
Servers have 2 1TB SSD, they use soft raid, and have an LVM partition for /var/lib/vz. No ZFS.
