Dominik,
Your command worked like a charm. Solved!
root@nofdcbprox00:~# pvesm list storage_nvme
storage_nvme:vm-122-disk-1 raw 408021893120 122
storage_nvme:vm-135-disk-0 raw 214748364800 135
Stoiko,
root@nofdcbprox00:~# pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.18-9-pve)...
Hi Dominik,
root@nofdcbprox02:~# qm rescan
rescan volumes...
VM 133: add unreferenced volume 'storage01_vm:vm-133-disk-0' as 'unused0' to config.
It corrected another VM (lol), but not for VM 122.
root@nofdcbprox02:~# qm config 122
agent: 1
bootdisk: scsi0
cores: 3
ide2: none,media=cdrom...
Hi Dominik,
Thanks for the prompt answer, but it didn't work.
I tried with the VM operational and shutdown, but no difference whatsoever. :(
No snapshots attached either:
# qm listsnapshot 122
current no-parent You are here!
Any other ideas?
Dear sirs,
A moved vm disk (vm-122-disk-0) that is no longer in use is still present in one of my storage pools and I can't delete it. It's not in the VM configuration file:
# cat /etc/pve/qemu-server/122.conf
agent: 1
bootdisk: scsi0
cores: 3
ide2: none,media=cdrom
memory: 16384
name...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.