Used disk on new VM

[mlukasik]

Hi,

I’ve encountered a very concerning issue while creating a new VM.
It seems like a new VM is somehow "mounting" or using a disk that belongs to another, already existing VM.

I checked the hardware tab of the new VM, and the disk name usually follows the vm-ID-disk-X convention, but the content inside is definitely from another machine.

PVE: 9.1.6
Storage: LVM
Repo: Enterprise

Screen on attachment

Thanks in advance!

 

[bbgeek17]

Hi @mlukasik ,
Its possible that you are running into a situation where a VM or its disk were removed but not wiped. The data is still on the physical disk and can be read by other processes/VMs.
That said, you did not provide sufficient data about the "different VM" (is it still around, is the disk in use, etc) or the new VM (how you created it, what does it share with the last one, etc).

Cheers

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[mlukasik]

Hi @mlukasik ,
Its possible that you are running into a situation where a VM or its disk were removed but not wiped. The data is still on the physical disk and can be read by other processes/VMs.
That said, you did not provide sufficient data about the "different VM" (is it still around, is the disk in use, etc) or the new VM (how you created it, what does it share with the last one, etc).

Cheers

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

That disk from another VM are in use.
I've moved disk (from that diffrent VM) to another storage and deleted it after migration.
After a while I start to create new VM.
Before that, that disk was on the same storage as the newly created.

 

[bbgeek17]

That disk from another VM are in use.
I've moved disk (from that diffrent VM) to another storage and deleted it after migration.
After a while I start to create new VM.
Before that, that disk was on the same storage as the newly created.

The additional information you provided seems to confirm my theory that you had a disk that was was not wiped on deletion.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[mlukasik]

I know that Proxmox has a problem with disk migration on LVM storage.: https://bugzilla.proxmox.com/show_bug.cgi?id=7143

As a bypass I do:

lvdisplay | grep {VM_ID}
then
lvremove /dev/{storage}/vm-{VM_ID}-disk-0.qcow2

but it seems that is not a full solution

 

[bbgeek17]

lvremove simply deletes the metadata entry. The actual data is still on disk.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[bbgeek17]

2

Thread 'Issue with Deleting VMs in proxmox environment/ Use luns directly?'

Yesterday at 19:39

Currently running proxmox 9.1.6 on a 5 node cluster. The cluster is connect to an iscsi Dell san.
When I delete a vm (ex. vm141), I tick both boxes to purge from job configurations and destroy unreferenced disked owned by the guest. If I then create a new vm and reuse the 141 vm id and then attempt to boot into the iso, I will get the previous vms disk still. For example, I originally had a Windows vm running on vmid 141. I no longer needed that vm and deleted as mentioned above. I then needed to create a linux vm. When I clicked to create a new vm, vm id 141 was automatically populated...

• 2000gtacoma

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox