Search results

Okay, I solved it in the most unusual way. I physically swapped the 2 hard disks and everything greened up.

I upgraded from v4 to v5.3-5 this morning. At first proxmox would not come up. I edited /etc/lvm/lvm.conf, setting allow_changes_with_duplicate_pvs = 1. This allowed proxmox to boot. However some of my VMs won't come up. I tried installing multipath-tools and rebooting, but that solved...

Awesome. I had a similar workaround. But maybe this is something that should be exposed in a command in a later version of PVE. A very minor problem, just wishful thinking.

I know that the cluster name is hidden in corosync, but is there any pvecm-esque command that tells you the cluster name? If not, I feel like it should be displayed in the "pvecm status". There are a few times where I've needed the cluster name and had to go digging to find it again.