Can't change/remove or start vm. Proxmox 1.9

[techguys]

Had some issues on a VM being extremely slow so we removed it and created a new one using the same vmid (101). And it won't start, so I tried to remove it and it won't remove... tried to make changes to it and can't make any changes:
Oct 8 09:38:25 atom1 pvedaemon[3213]: destroying VM 101 on node 0 (localhost)
Oct 8 09:38:25 atom1 pvedaemon[3213]: VM 101 destroy failed -
Oct 8 09:38:35 atom1 pvedaemon[3225]: starting VM 101 on node 0 (localhost)
Oct 8 09:38:35 atom1 pvedaemon[3225]: VM 101 start failed -
Oct 8 09:38:47 atom1 pvedaemon[2862]: apply settings to VM 101 on node 0 (localhost)
Oct 8 09:38:48 atom1 pvedaemon[2862]: unable to apply VM settings, command failed: /usr/sbin/qm set 101 --name Database01 --description --cores 2 --ostype w2k8 --memory 8192 --onboot 1 --sockets 2

Rebooted the hypervisor jic that would magically fix it (too much of a Windows background I guess ) and didn't do anything.

Version:
atom1:~# pveversion -v
pve-manager: 1.9-24 (pve-manager/1.9/6542)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-43
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.32-6-pve: 2.6.32-43
qemu-server: 1.1-32
pve-firmware: 1.0-13
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.28-1pve5
vzdump: 1.2-15
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6

We do have another vm (w2k8) running on this machine fine. Only differences are the disk that the VM is on, and then amount of memory and cores given to the VM.

 

[dietmar]

What output do you get when you start manually?

# qm start 101

 

[techguys]

Hey that's useful info

atom1:~# qm start 101
VM is locked (backup)

Of course I don't know how to unlock it?

 

[techguys]

Hmm, so I still can't remove it:
Oct 8 10:15:14 atom1 pvedaemon[3678]: VM 101 stopped
Oct 8 10:15:26 atom1 pvedaemon[3690]: destroying VM 101 on node 0 (localhost)
Oct 8 10:15:26 atom1 qm[3691]: VM 101 destroy called (removing all data)
Oct 8 10:15:27 atom1 qm[3691]: VM 101 destroy failed - command '/sbin/lvremove -f atom1-disk3/vm-101-disk-1' failed with exit code 5
Oct 8 10:15:27 atom1 pvedaemon[3690]: VM 101 destroy failed -

Tried from the command line:
atom1:~# qm destroy 101
Can't remove logical volume "vm-101-disk-1" under snapshot
command '/sbin/lvremove -f atom1-disk3/vm-101-disk-1' failed with exit code 5

 

[dietmar]

Of course I don't know how to unlock it?

qm unlock 101

(see 'man qm')

 

[dietmar]

atom1:~# qm destroy 101
Can't remove logical volume "vm-101-disk-1" under snapshot
command '/sbin/lvremove -f atom1-disk3/vm-101-disk-1' failed with exit code 5

Does 'vgs' shows an active snapshot? if so, remove that with 'lvremove'.

 

[techguys]

Thanks again for responding.
Doesn't look like it:
atom1:~# vgs
VG #PV #LV #SN Attr VSize VFree
atom1-disk2 1 1 0 wz--n- 418.62G 338.62G
atom1-disk3 1 2 1 wz--n- 418.62G 317.62G
pve 1 3 0 wz--n- 418.12G 4.00G

 

[udo]

Hi,
and what shows "lvs"?

 

[techguys]

Ah ha...:
atom1:~# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
vm-100-disk-1 atom1-disk2 -wi-ao 80.00G
vm-101-disk-1 atom1-disk3 owi-a- 100.00G
vzsnap-atom1-0 atom1-disk3 swi-a- 1.00G vm-101-disk-1 9.64
data pve -wi-ao 303.12G
root pve -wi-ao 96.00G
swap pve -wi-ao 15.00G

Looks like there is a failed snapshot going. This is the first installation I've used LVM style disks with... Starting to wish I hadn't. There are obviously some things proxmox is doing inherently with LV's that I'm not aware.

 

[udo]

... This is the first installation I've used LVM style disks with... Starting to wish I hadn't. There are obviously some things proxmox is doing inherently with LV's that I'm not aware.

Hi,
lvm is very nice - especially with pve (resizing VM-disks and so on). Play a little bit with this stuff to be familiar with lvm... and remove the snapshot, than you can remove the VM.

Udo

 

[dietmar]

vzsnap-atom1-0 atom1-disk3 swi-a- 1.00G vm-101-disk-1 9.64
There are obviously some things proxmox is doing inherently with LV's that I'm not aware.

That is from 'vzdump' backup using snapshot mode.

 

[techguys]

Thanks for all the info. I did an lvdisplay to determine what LVM's were there and then did an lvremove of the snapshot and then was able to remove the VM.

Thanks!