Can't delete unused disks

muzicman0

New Member
Oct 16, 2024
13
1
3
I have 2 disks that are attached to a VM, but are unused. I can't delete them, as the system says they are in use. They are assigned to VM201, but originally I didn't have a VM201. Once I created the 201 VM, I ran a rescan to attach them so I could delete them, but they still won't delete.

What can I do?
 
Here is the msg. I have backups on a PBS server, but no snapshots locally that I am aware of. How would I check? Thanks for the response!

Screenshot 2024-11-20 082752.png

[EDIT]I have 2 disks. the other one is .....-disk-1.
 
As requested. Again, thanks!

Code:
root@hw-vhost02-srv:~# qm config 201
agent: 1
balloon: 1024
boot: order=scsi0;net0
cores: 2
cpu: x86-64-v2-AES
memory: 2048
meta: creation-qemu=9.0.2,ctime=1732060924
name: hw-tailscale02-vm
net0: virtio=BC:24:11:7C:77:59,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
scsi0: data_2tb_1:vm-201-disk-2,iothread=1,size=32G
scsihw: virtio-scsi-single
smbios1: uuid=c393c0c7-e7f5-43e0-8f86-68a93fd29918
sockets: 1
unused0: data_2tb_1:vm-201-disk-0
unused1: data_2tb_1:vm-201-disk-1
vmgenid: 4f14d0cc-3851-4228-b407-1a7193f18954
root@hw-vhost02-srv:~#

Code:
root@hw-vhost02-srv:~# pvesm list data_2tb_1
Volid                    Format  Type              Size VMID
data_2tb_1:vm-201-disk-0 raw     images         4194304 201
data_2tb_1:vm-201-disk-1 raw     images     53687091200 201
data_2tb_1:vm-201-disk-2 raw     images     34359738368 201
data_2tb_1:vm-202-disk-0 raw     images         4194304 202
data_2tb_1:vm-202-disk-1 raw     images    322122547200 202
data_2tb_1:vm-203-disk-0 raw     images         4194304 203
data_2tb_1:vm-203-disk-1 raw     images     64424509440 203
data_2tb_1:vm-204-disk-0 raw     images    107374182400 204
data_2tb_1:vm-205-disk-0 raw     images         4194304 205
data_2tb_1:vm-205-disk-1 raw     images     26843545600 205
data_2tb_1:vm-206-disk-0 raw     images         4194304 206
data_2tb_1:vm-206-disk-1 raw     images     41875931136 206
data_2tb_1:vm-206-disk-2 raw     images         4194304 206
root@hw-vhost02-srv:~#
 
The error you are getting is directly from lvremove, i.e. on OS level.
It implies that the OS/Kernel has a lock/hold on the disk. Possibly outside of Proxmox.

First ensure that this disk is not used by any active VM, check other VM configurations.
The search your favorite engine for tips on determining why an LVM slice could be busy. There are multiple articles that list various steps.
A sure way to get this resolved is to reboot your node.

Good luck



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

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!