Hello all,
This afternoon I have tried to upgrade the Proxmox Virtual Environnement from 8.14.0 to 9.0 so I launched the pve8to9 script to check the compatibility with my system. I had one failure from the script which are the following :
FAIL: systemd-boot meta-package installed. This will cause problems on upgrades of other boot-related packages. Remove 'systemd-boot' See https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#sd-boot-warning for more information.
and
WARN: The matching CPU microcode package 'amd64-microcode' could not be found! Consider installing it to receive the latest security and bug fixes for your CPU. Ensure you enable the 'non-free-firmware' component in the apt sources and run: apt install amd64-microcode
I removed systemd-boot and installed amd64-microcode as the script required. Finally I replaced bookworm by trixie in all the needed file(/etc/apt/sources.list) and launched apt update and apt dist-upgrade.
However I had the following error and tried apt upgrade :
E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (1)
E: Failure running script /usr/share/proxmox-ve/pve-apt-hook
I think this command broke my system and now I didn't have access to the GUI anymore. Thanks in advance for you help, you will find below the status from pveproxy, pvedaemon, pve-cluster.
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: enabled)
Active: active (running) since Sat 2026-01-03 19:59:50 CET; 1h 44min ago
Process: 11766 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
Main PID: 11768 (pvedaemon)
Tasks: 4 (limit: 37648)
Memory: 151.9M
CPU: 1.757s
CGroup: /system.slice/pvedaemon.service
├─11768 pvedaemon
├─11769 "pvedaemon worker"
├─11770 "pvedaemon worker"
└─11771 "pvedaemon worker"
Jan 03 19:59:49 aoostar-nas systemd[1]: Starting pvedaemon.service - PVE API Daemon...
Jan 03 19:59:50 aoostar-nas pvedaemon[11768]: starting server
Jan 03 19:59:50 aoostar-nas pvedaemon[11768]: starting 3 worker(s)
Jan 03 19:59:50 aoostar-nas pvedaemon[11768]: worker 11769 started
Jan 03 19:59:50 aoostar-nas pvedaemon[11768]: worker 11770 started
Jan 03 19:59:50 aoostar-nas pvedaemon[11768]: worker 11771 started
Jan 03 19:59:50 aoostar-nas systemd[1]: Started pvedaemon.service - PVE API Daemon.
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
Active: active (running) since Sat 2026-01-03 19:59:51 CET; 1h 44min ago
Process: 11772 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 11774 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 11792 (pveproxy)
Tasks: 4 (limit: 37648)
Memory: 197.9M
CPU: 2.891s
CGroup: /system.slice/pveproxy.service
├─11792 pveproxy
├─11793 "pveproxy worker"
├─11794 "pveproxy worker"
└─11795 "pveproxy worker"
Jan 03 19:59:50 aoostar-nas systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Jan 03 19:59:51 aoostar-nas pveproxy[11792]: starting server
Jan 03 19:59:51 aoostar-nas pveproxy[11792]: starting 3 worker(s)
Jan 03 19:59:51 aoostar-nas pveproxy[11792]: worker 11793 started
Jan 03 19:59:51 aoostar-nas pveproxy[11792]: worker 11794 started
Jan 03 19:59:51 aoostar-nas pveproxy[11792]: worker 11795 started
Jan 03 19:59:51 aoostar-nas systemd[1]: Started pveproxy.service - PVE API Proxy Server.
root@aoostar-nas:~# systemctl status pve-cluster
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; preset: enabled)
Active: active (running) since Sat 2026-01-03 19:59:59 CET; 1h 44min ago
Process: 11805 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
Main PID: 11806 (pmxcfs)
Tasks: 6 (limit: 37648)
Memory: 33.8M
CPU: 4.198s
CGroup: /system.slice/pve-cluster.service
└─11806 /usr/bin/pmxcfs
Jan 03 20:00:05 aoostar-nas pmxcfs[11806]: [status] notice: start cluster connection
Jan 03 20:00:05 aoostar-nas pmxcfs[11806]: [status] crit: cpg_initialize failed: 2
Jan 03 20:00:05 aoostar-nas pmxcfs[11806]: [status] crit: can't initialize service
Jan 03 20:00:11 aoostar-nas pmxcfs[11806]: [status] notice: update cluster info (cluster name aoostar-nas, version = 1)
Jan 03 20:00:11 aoostar-nas pmxcfs[11806]: [status] notice: node has quorum
Jan 03 20:00:11 aoostar-nas pmxcfs[11806]: [dcdb] notice: members: 1/11806
Jan 03 20:00:11 aoostar-nas pmxcfs[11806]: [dcdb] notice: all data is up to date
Jan 03 20:00:11 aoostar-nas pmxcfs[11806]: [status] notice: members: 1/11806
Jan 03 20:00:11 aoostar-nas pmxcfs[11806]: [status] notice: all data is up to date
Jan 03 20:59:58 aoostar-nas pmxcfs[11806]: [dcdb] notice: data verification successful
This afternoon I have tried to upgrade the Proxmox Virtual Environnement from 8.14.0 to 9.0 so I launched the pve8to9 script to check the compatibility with my system. I had one failure from the script which are the following :
FAIL: systemd-boot meta-package installed. This will cause problems on upgrades of other boot-related packages. Remove 'systemd-boot' See https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#sd-boot-warning for more information.
and
WARN: The matching CPU microcode package 'amd64-microcode' could not be found! Consider installing it to receive the latest security and bug fixes for your CPU. Ensure you enable the 'non-free-firmware' component in the apt sources and run: apt install amd64-microcode
I removed systemd-boot and installed amd64-microcode as the script required. Finally I replaced bookworm by trixie in all the needed file(/etc/apt/sources.list) and launched apt update and apt dist-upgrade.
However I had the following error and tried apt upgrade :
E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (1)
E: Failure running script /usr/share/proxmox-ve/pve-apt-hook
I think this command broke my system and now I didn't have access to the GUI anymore. Thanks in advance for you help, you will find below the status from pveproxy, pvedaemon, pve-cluster.
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: enabled)
Active: active (running) since Sat 2026-01-03 19:59:50 CET; 1h 44min ago
Process: 11766 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
Main PID: 11768 (pvedaemon)
Tasks: 4 (limit: 37648)
Memory: 151.9M
CPU: 1.757s
CGroup: /system.slice/pvedaemon.service
├─11768 pvedaemon
├─11769 "pvedaemon worker"
├─11770 "pvedaemon worker"
└─11771 "pvedaemon worker"
Jan 03 19:59:49 aoostar-nas systemd[1]: Starting pvedaemon.service - PVE API Daemon...
Jan 03 19:59:50 aoostar-nas pvedaemon[11768]: starting server
Jan 03 19:59:50 aoostar-nas pvedaemon[11768]: starting 3 worker(s)
Jan 03 19:59:50 aoostar-nas pvedaemon[11768]: worker 11769 started
Jan 03 19:59:50 aoostar-nas pvedaemon[11768]: worker 11770 started
Jan 03 19:59:50 aoostar-nas pvedaemon[11768]: worker 11771 started
Jan 03 19:59:50 aoostar-nas systemd[1]: Started pvedaemon.service - PVE API Daemon.
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
Active: active (running) since Sat 2026-01-03 19:59:51 CET; 1h 44min ago
Process: 11772 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 11774 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 11792 (pveproxy)
Tasks: 4 (limit: 37648)
Memory: 197.9M
CPU: 2.891s
CGroup: /system.slice/pveproxy.service
├─11792 pveproxy
├─11793 "pveproxy worker"
├─11794 "pveproxy worker"
└─11795 "pveproxy worker"
Jan 03 19:59:50 aoostar-nas systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Jan 03 19:59:51 aoostar-nas pveproxy[11792]: starting server
Jan 03 19:59:51 aoostar-nas pveproxy[11792]: starting 3 worker(s)
Jan 03 19:59:51 aoostar-nas pveproxy[11792]: worker 11793 started
Jan 03 19:59:51 aoostar-nas pveproxy[11792]: worker 11794 started
Jan 03 19:59:51 aoostar-nas pveproxy[11792]: worker 11795 started
Jan 03 19:59:51 aoostar-nas systemd[1]: Started pveproxy.service - PVE API Proxy Server.
root@aoostar-nas:~# systemctl status pve-cluster
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; preset: enabled)
Active: active (running) since Sat 2026-01-03 19:59:59 CET; 1h 44min ago
Process: 11805 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
Main PID: 11806 (pmxcfs)
Tasks: 6 (limit: 37648)
Memory: 33.8M
CPU: 4.198s
CGroup: /system.slice/pve-cluster.service
└─11806 /usr/bin/pmxcfs
Jan 03 20:00:05 aoostar-nas pmxcfs[11806]: [status] notice: start cluster connection
Jan 03 20:00:05 aoostar-nas pmxcfs[11806]: [status] crit: cpg_initialize failed: 2
Jan 03 20:00:05 aoostar-nas pmxcfs[11806]: [status] crit: can't initialize service
Jan 03 20:00:11 aoostar-nas pmxcfs[11806]: [status] notice: update cluster info (cluster name aoostar-nas, version = 1)
Jan 03 20:00:11 aoostar-nas pmxcfs[11806]: [status] notice: node has quorum
Jan 03 20:00:11 aoostar-nas pmxcfs[11806]: [dcdb] notice: members: 1/11806
Jan 03 20:00:11 aoostar-nas pmxcfs[11806]: [dcdb] notice: all data is up to date
Jan 03 20:00:11 aoostar-nas pmxcfs[11806]: [status] notice: members: 1/11806
Jan 03 20:00:11 aoostar-nas pmxcfs[11806]: [status] notice: all data is up to date
Jan 03 20:59:58 aoostar-nas pmxcfs[11806]: [dcdb] notice: data verification successful
