[SOLVED] PVE not reachable after upgrade to V9

marcootten

New Member
Aug 18, 2025
1
0
1
Hi everyone, i have followed the provided guide on how to upgrade my PVE server and everything went fine until the reboot. I cant reach the webinterface anymore and none of my VMs are running. I have connected a monitor to my server and can get into the command prompt but before i do there are a lot of services unable to start.

Found volume group "pve" using metadata type lvm2

logical volume(s) in volume group "pve" now active

dev/mapper/pve-root: clean, 85293/6291456 files, 3282854/25165824.blocks

Import ZFS pools by device scanning.
[FAILED] Failed to start zfs-import-scan.service

[FAILED) Failed to start pvestatd.service PVE Status Daemon.

[FAILED) Failed to start pvedaemon.service - PVE API Daemon.

[FAILED) Failed to start pve-ha-crm.service - PVE Cluster HR Resource Manager Daemon.

[FAILED) Failed to start pvedaemon.service - PVE API Daemon.

[FAILED] Failed to start pveproxy.service - PVE API Proxy Server.

[FAILED) Failed to start pve-ha-Irm.service - PVE Local HR Resource Manager Daemon.

[FAILED] Failed to start pvedaemon.service - PVE API Daemon.

[FAILED] Failed to start pveproxy.service - PVE API Proxy Server.

[FAILED] Failed to start pvedaemon.service - PVE API Daemon.

[FAILED] Falled to start pve-guests.service - PVE guests.

[FAILED] Failed to start pvedaemon.service - PVE RPI Daemon.

[FAILED] Failed to start pvedaemon.service - PVE API Daemon.

[FAILED] Failed to start pvescheduler.service - Proxmox VE scheduler.

PVE API Proxy Server failed to start pveproxy.service
I'm trying to start the services manually but they fail to start with status code 17

I have external backups of most of my VMs so could do a clean install and recover my VMs but was hoping a for a faster solution.

Anyone got any idea?
 
Last edited: