Hello all,
I'm running a PVE cluster consisting of three HP DL380 Gen 10 hosts. All updates from PVE 6 through 9 always ran flawless, until I updated from 9.0.5 to 9.1.6 via
Numerous attempts of restarting
I found no way to get rid of the storage question marks.
Trying to show the status of any container or VM runs into a
Trying to show the status of storage results in a
Measures I tried to solve the problem include:
a) removing those IP addresses from
b) pinning the kernel to 6.14.11-5-pve
None of these steps did help.
Storage (e.g. that holding our VM disk images) is bound mostly via NFS and seems to work fine. Even migration of a VM's computing resources works.
I should also mention that running
Please find the output of
I'm running a PVE cluster consisting of three HP DL380 Gen 10 hosts. All updates from PVE 6 through 9 always ran flawless, until I updated from 9.0.5 to 9.1.6 via
apt update && apt upgrade which made the names of LXC containers and VMs in the web GUI vanish. They as well as hosts and storages show a grey question mark instead.Numerous attempts of restarting
pveproxy, corosync and pve-cluster on all the nodes didn't help. Restarting pvestatd makes the hosts, LXC and VM question marks go away, but only to return after 3 minutes or so.I found no way to get rid of the storage question marks.
Trying to show the status of any container or VM runs into a
connection timed out (596) error. Trying to show the status of storage results in a
communication failure (0) or connection timed out (596) even when it's about local storage. Measures I tried to solve the problem include:
a) removing those IP addresses from
/etc/corosync/corosync.conf which do not listen at UDP port 5405 (there were some configured as ring1_addr)b) pinning the kernel to 6.14.11-5-pve
None of these steps did help.
Storage (e.g. that holding our VM disk images) is bound mostly via NFS and seems to work fine. Even migration of a VM's computing resources works.
I should also mention that running
pvesm status on any node never returns a result but must be interrupted to regain the prompt.Please find the output of
pveversion -v below. Please let me know which additional information is needed. Any help will be appreciated.
Code:
proxmox-ve: 9.1.0 (running kernel: 6.14.11-5-pve)
pve-manager: 9.1.6 (running version: 9.1.6/71482d1833ded40a)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.17: 6.17.13-1
proxmox-kernel-6.17.13-1-pve-signed: 6.17.13-1
proxmox-kernel-6.17.9-1-pve-signed: 6.17.9-1
proxmox-kernel-6.14.11-5-pve-signed: 6.14.11-5
proxmox-kernel-6.14: 6.14.11-5
ceph-fuse: 19.2.3-pve1
corosync: 3.1.10-pve1
criu: 4.1.1-1
frr-pythontools: 10.4.1-1+pve1
ifupdown2: 3.3.0-1+pmx12
intel-microcode: 3.20251111.1~deb13u1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.2
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.5
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.0.7
libpve-cluster-perl: 9.0.7
libpve-common-perl: 9.1.7
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.2.5
libpve-rs-perl: 0.11.4
libpve-storage-perl: 9.1.0
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-4
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.1.4-1
proxmox-backup-file-restore: 4.1.4-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.1
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.3
proxmox-widget-toolkit: 5.1.8
pve-cluster: 9.0.7
pve-container: 6.1.2
pve-docs: 9.1.2
pve-edk2-firmware: not correctly installed
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.18-1
pve-ha-manager: 5.1.1
pve-i18n: 3.6.6
pve-qemu-kvm: 10.1.2-7
pve-xtermjs: 5.5.0-3
qemu-server: 9.1.4
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve3
vncterm: 1.9.1
zfsutils-linux: 2.4.0-pve1
