No Disk Storage Options Available for VM's Following Upgrade to VE7.2-7 - Communication Failure (0)

[wits-zach]

I have an issue where I cannot create new VM's following what appears to be an otherwise successful upgrade to VE7.2-7.

Looking at another thread on what seems to be a related issue, I ran the pvesm status command, which succeeded with the following output:

admin@pxmx:/Data1A# pvesm status
WARNING: VG name ubuntu-vg is used by VGs WOUGKF-e2na-vRJo-24ST-NDUf-i7JX-Wc5sbS and qyAZav-tPd3-OEXp-mdVb-dcu7-1SYo-e7e52v.
Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
WARNING: VG name centos is used by VGs 4XYe9S-Z217-chAs-CBzT-NgZz-rmOD-7htVQe and HTXgAW-3Uei-XDHQ-2no8-azBs-mxjs-rw0jYg.
Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
WARNING: VG name centos is used by VGs emTCy6-o06i-xED3-cpVu-L9oM-xXhF-wFGpvn and HTXgAW-3Uei-XDHQ-2no8-azBs-mxjs-rw0jYg.
Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
WARNING: Not using device /dev/sdac2 for PV JxrA15-BcVE-c4T0-44tM-zE8A-GMII-csm3ms.
WARNING: PV JxrA15-BcVE-c4T0-44tM-zE8A-GMII-csm3ms prefers device /dev/sdaj2 because device was seen first.
WARNING: VG name ubuntu-vg is used by VGs WOUGKF-e2na-vRJo-24ST-NDUf-i7JX-Wc5sbS and qyAZav-tPd3-OEXp-mdVb-dcu7-1SYo-e7e52v.
Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
WARNING: VG name centos is used by VGs 4XYe9S-Z217-chAs-CBzT-NgZz-rmOD-7htVQe and HTXgAW-3Uei-XDHQ-2no8-azBs-mxjs-rw0jYg.
Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
WARNING: VG name centos is used by VGs emTCy6-o06i-xED3-cpVu-L9oM-xXhF-wFGpvn and HTXgAW-3Uei-XDHQ-2no8-azBs-mxjs-rw0jYg.
Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
WARNING: Not using device /dev/sdac2 for PV JxrA15-BcVE-c4T0-44tM-zE8A-GMII-csm3ms.
WARNING: PV JxrA15-BcVE-c4T0-44tM-zE8A-GMII-csm3ms prefers device /dev/sdaj2 because device was seen first.
Name Type Status Total Used Available %
Data1 nfs active 38144000 0 36173824 0.00%
Data1A nfs active 959775744 609614848 301333504 63.52%
Data2 nfs active 38144000 0 36173824 0.00%
Data2A nfs active 2882594816 605605888 2130486272 21.01%
Data3A nfs active 1921192960 0 1823527936 0.00%
Training zfs active 10690231378 3190216730 7500014648 29.84%
local dir active 28465204 9037336 17956588 31.75%
local-lvm lvmthin active 62562304 0 62562304 0.00%

I am able to select an ISO from the ISO storage in the GUI, but where it fails is on the "Disks" menu as shown below:



I already ran pvecm updatecerts --force and systemctl restart pveproxy.service pvedaemon.service with no resolution. Given that the storage looks like it is working, this appears to be a problem in this specific part of the VM creation GUI.

Does anyone have any suggestions on what to do to remedy this? Thank you!

 

[mira]

Do you see anything in the syslog/journal hinting at an issue?

 

[wits-zach]

As embarrassed as I am to admit it, I actually had this same problem last year and solved it by freeing up inodes due to excessive .vg file creations:

https://forum.proxmox.com/threads/excessive-inode-consumption-and-etc-lvm-archive.91868/

What happened is that when I upgraded to Proxmox 7, it change my /etc/lvm/lvm.conf file reset back to 30 days retaining rather than 2. So, I ran out of inodes again, which then caused a series of other errors resulting in me needing to reinstall Grub2...

The real question at this point is why my system keeps creating so many .vg files. I will need to look into that. Thank you though for responding!

 

[mira]

Do you change things that often? Create new LVs, remove LVs, resize LVs or similar?