Proxmox cluster, cannot start vm due to quorum

E

ecyoong

New Member
Apr 21, 2025
7
0
1
Hi

I have a proxmox cluster configured
PV1
PV2
qDevice

there is a issue on network where, pv1 been not able to connect to network where same network with PV2 and qDevice.

i not sure what issue with the pv1 network where which is locally connected with same router with PV2 & qdevice. pv1 cannot ping pv2 & qdevice.
due to this, the vm inside pv1 not not able to start automatically, i try to start the VM (pv1) manually, it said "error 500, cluster not ready and no quorum?"
i try to pvecm delnode pv2 ---> cluster not ready - no quorum
and pvevm remove qdevice --> all nodes must be online, nodepv2 is olline, aborting

anyway i can remove node pv2 and qdevice to make my pv1 to able to start vm to copy data out 1st?
 
Hello,

Would it be possible to share your network connection settings for your nodes here, and if you could, please share the output of the ping from pv1 > pv2 and vice versa?

Thanks!
 
Last edited:
You could try "pvecm expected 1" on PV1 and see if it is happy and can start VMs.

In the end this looks like you have to reinstall both nodes and build cluster again after fixing your network issues.
If you have/make backups of all VMs on external storage (PBS, NAS, usb disk etc.) you won't lose data.
Add storage and restore VMs on new cluster (or first freshly installed node if you are in a hurry) and fire them up.
 
hi

from PVE1
*************************
root@pve01:~# ping -c 4 192.168.1.1 ----> router
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.01 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.14 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.01 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.48 ms

--- 192.168.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 1.005/1.159/1.480/0.192 ms
root@pve01:~# ping -c 4 192.168.1.220 ----> pve1
PING 192.168.1.220 (192.168.1.220) 56(84) bytes of data.
64 bytes from 192.168.1.220: icmp_seq=1 ttl=64 time=0.009 ms
64 bytes from 192.168.1.220: icmp_seq=2 ttl=64 time=0.023 ms
64 bytes from 192.168.1.220: icmp_seq=3 ttl=64 time=0.074 ms
64 bytes from 192.168.1.220: icmp_seq=4 ttl=64 time=0.013 ms

--- 192.168.1.220 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3081ms
rtt min/avg/max/mdev = 0.009/0.029/0.074/0.026 ms
root@pve01:~# ping -c 4 192.168.1.221 ----> pve2
PING 192.168.1.221 (192.168.1.221) 56(84) bytes of data.
From 192.168.1.220 icmp_seq=1 Destination Host Unreachable
From 192.168.1.220 icmp_seq=2 Destination Host Unreachable
From 192.168.1.220 icmp_seq=3 Destination Host Unreachable
From 192.168.1.220 icmp_seq=4 Destination Host Unreachable

--- 192.168.1.221 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3076ms
pipe 2
root@pve01:~# ping -c 4 192.168.1.222 ------> qdevice
PING 192.168.1.222 (192.168.1.222) 56(84) bytes of data.
From 192.168.1.220 icmp_seq=1 Destination Host Unreachable
From 192.168.1.220 icmp_seq=2 Destination Host Unreachable
From 192.168.1.220 icmp_seq=3 Destination Host Unreachable
From 192.168.1.220 icmp_seq=4 Destination Host Unreachable

--- 192.168.1.222 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3031ms
pipe 3
root@pve01:~#
*****************************************



FROM PVE 2
********************************
root@pve02:~# ping -c 4 192.168.1.1 ----> router
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.19 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.58 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.13 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.04 ms

--- 192.168.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 1.035/1.234/1.579/0.207 ms
root@pve02:~# ping -c 4 192.168.1.220 ----> PVE1
PING 192.168.1.220 (192.168.1.220) 56(84) bytes of data.
From 192.168.1.221 icmp_seq=1 Destination Host Unreachable
From 192.168.1.221 icmp_seq=2 Destination Host Unreachable
From 192.168.1.221 icmp_seq=3 Destination Host Unreachable
From 192.168.1.221 icmp_seq=4 Destination Host Unreachable

--- 192.168.1.220 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3068ms
pipe 3
root@pve02:~# ping -c 4 192.168.1.221 ----> PVE2
PING 192.168.1.221 (192.168.1.221) 56(84) bytes of data.
64 bytes from 192.168.1.221: icmp_seq=1 ttl=64 time=0.044 ms
64 bytes from 192.168.1.221: icmp_seq=2 ttl=64 time=0.027 ms
64 bytes from 192.168.1.221: icmp_seq=3 ttl=64 time=0.029 ms
64 bytes from 192.168.1.221: icmp_seq=4 ttl=64 time=0.038 ms

--- 192.168.1.221 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3053ms
rtt min/avg/max/mdev = 0.027/0.034/0.044/0.006 ms
root@pve02:~# ping -c 4 192.168.1.222 ----> qdevice
PING 192.168.1.222 (192.168.1.222) 56(84) bytes of data.
64 bytes from 192.168.1.222: icmp_seq=1 ttl=64 time=0.201 ms
64 bytes from 192.168.1.222: icmp_seq=2 ttl=64 time=0.190 ms
64 bytes from 192.168.1.222: icmp_seq=3 ttl=64 time=0.238 ms
64 bytes from 192.168.1.222: icmp_seq=4 ttl=64 time=0.226 ms

--- 192.168.1.222 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3087ms
rtt min/avg/max/mdev = 0.190/0.213/0.238/0.019 ms
root@pve02:~#
 
PVE 1
*******************
root@pve01:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.

auto lo
iface lo inet loopback

auto enp2s0
iface enp2s0 inet manual

auto enp0s31f6
iface enp0s31f6 inet manual

auto bond0
iface bond0 inet manual
bond-slaves enp2s0 enp0s31f6
bond-miimon 100
bond-mode balance-alb

auto vmbr0
iface vmbr0 inet static
address 192.168.1.220/24
gateway 192.168.1.1
bridge-ports bond0
bridge-stp off
bridge-fd 0


source /etc/network/interfaces.d/*
root@pve01:~#
**************************************

PVE2
***********************************
root@pve02:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

auto enp1s0
iface enp1s0 inet manual

auto bond0
iface bond0 inet manual
bond-slaves eno1 enp1s0
bond-miimon 100
bond-mode balance-alb

auto vmbr0
iface vmbr0 inet static
address 192.168.1.221/24
gateway 192.168.1.1
bridge-ports bond0
bridge-stp off
bridge-fd 0

source /etc/network/interfaces.d/*
root@pve02:~#
 
the PVE2 able to ping other local network device...... not the PVE1 where it can ping certain device only like router and my laptop ip. other than that, other will return Destination Host Unreachable
 
You must log in or register to reply here.
Top Bottom
Back