New node has local-lvm out of space

k5map

New Member
Jun 27, 2025
10
2
3
Cypress, TX
I built a new NUC with v8 PVE from the ISO. At the end of the build, I have a ~500GB local-lvm volume. When I join it to my cluster, it is no longer listed on the new node. So, I add it at the Datacenter level configurating it to only be accessible by the new node. When I do, it then shows 96% full (only 16GB free). Why do I lose all of the space after added it to the cluster? Are the steps I'm performing correct so I can use the local-lvm for storage of VMs?
 
Last edited:
Hi,
Please provide the output of the following cmds from the node where the LVM was created:
Bash:
~# lsblk
~# pvesm status
~# cat /etc/pve/storage.cfg
~# pvdisplay
~# vgdisplay
~# vgs
 
I'm guessing that the new node is the only one with a LVM(-Thin) storage by that name and it's therefore not in the central cluster storage configuration, which made it look like it disappeared.
I'm also guessing that it is a LVM-Thin storage and you are looking at how much of the LVM storage is used. LVM-Thin typically takes (almost) all of the underlying LVM storage. Or you added it as a LVM instead of LVM-Thin to the central cluster storage configuration.
 
@abobakr ... after not receiving a response for 3 weeks, I decided to rebuild the RPi4 cluster using PXVIRT and leave the NUC as a standalone Proxmox host. Since the NUC is not joined into a cluster, LVM-Thin storage being out of space is not an issue now.
 
  • Like
Reactions: abobakr
@leesteken ... correct, the NUC was the only node with LVM-Thin storage. The other 3 RPI4 only had LVM storage.
Proxmox VE does not run on ARM and is not supported. If you installed an unofficial fork please ask for support from the people who maintain that port. It does not surprise me that a mixed x86-64 and ARM cluster had problems. Sorry that I did not see your thread earlier.
 
  • Like
Reactions: Johannes S
At the time of the problem, I had Proxmox installed on all nodes... but this thread can be closed as I have switched to PXVIRT
Please edit the first post of the thread and select Solved from the pull-down menu, as there is no other way to close a thread.
 
Last edited: