Can't remove orphaned Snapshot Named in List - Disk Gone

JakeBikeIT

Member
Jul 25, 2023
58
2
8
Hi All,

I have management DC- that I snapshot accidentally.

Foolishly I halted the snapshot ., I unlocked the DC and all is running fine - there is no snapshot disk - but I cannot remove the name "BeforeUpdate" of the snapshot.

I never snap DC's - I was meaning to snap a Linux machine running underneath it.

How can I remove the Orphaned name please
 
A management domain controller - creates centralised authentication in a part of the network that manages everything from switch config, storage config, hypervisor management, cluster management, PVE and hyperV etc..

I've got a snapshot that I took accidentally I can see the name of snapshot - the disk is gone - I want to delete the name - do you know how?
 
1703152971680.png

bios: ovmf
boot: order=ide0;ide2
cores: 2
efidisk0: local-lvm:vm-104-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
ide0: local-lvm:vm-104-disk-1,size=120G
ide2: local:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K
machine: pc-q35-7.2
memory: 8192
meta: creation-qemu=7.2.0,ctime=1700222103
name: Guralpman-DC1
net0: vmxnet3=6E:1F:65:2F:C2:BF,bridge=vmbr6,firewall=1
numa: 0
onboot: 1
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=b700fdc1-41db-4f10-999d-e1ee3559efc1
sockets: 2
tpmstate0: local-lvm:vm-104-disk-2,size=4M,version=v2.0
vga: virtio
vmgenid: 5b8b46c9-636e-40a7-a4b4-0c77834badde

1703153022819.png

It doesn't appear to be of any consequence - aside from causing unwanted locks when you go to remove it.

The drive is not running on the snap.

And - Thanks for your reply!

it does have an Ent License
 
Thank you for the VM config.

Could you please also provide us with the `cat /etc/pve/qemu-server/104.conf` command?
 
bios: ovmf
boot: order=ide0;ide2
cores: 2
efidisk0: local-lvm:vm-104-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
ide0: local-lvm:vm-104-disk-1,size=120G
ide2: local:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K
machine: pc-q35-7.2
memory: 8192
meta: creation-qemu=7.2.0,ctime=1700222103
name: Guralpman-DC1
net0: vmxnet3=6E:1F:65:2F:C2:BF,bridge=vmbr6,firewall=1
numa: 0
onboot: 1
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=b700fdc1-41db-4f10-999d-e1ee3559efc1
sockets: 2
tpmstate0: local-lvm:vm-104-disk-2,size=4M,version=v2.0
vga: virtio
vmgenid: 5b8b46c9-636e-40a7-a4b4-0c77834badde

[BeforeUpdate]
bios: ovmf
boot: order=ide0;ide2
cores: 2
efidisk0: local-lvm:vm-104-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
ide0: local-lvm:vm-104-disk-1,size=120G
ide2: local:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K
machine: pc-q35-7.2
memory: 8192
meta: creation-qemu=7.2.0,ctime=1700222103
name: Guralpman-DC1
net0: vmxnet3=6E:1F:65:2F:C2:BF,bridge=vmbr6,firewall=1
numa: 0
onboot: 1
ostype: win11
runningcpu: kvm64,enforce,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vpindex,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep
runningmachine: pc-q35-7.2+pve0
scsihw: virtio-scsi-single
smbios1: uuid=b700fdc1-41db-4f10-999d-e1ee3559efc1
snapstate: delete
snaptime: 1702916886
sockets: 2
tpmstate0: local-lvm:vm-104-disk-2,size=4M,version=v2.0
vga: virtio
vmgenid: 5b8b46c9-636e-40a7-a4b4-0c77834badde
 
Hi,

If the snapshot is already removed from your storage `pve/snap-VM-104-disk-1_BeforeUpdate` you can safely remove the [BeforeUpdate] section from the `/etc/pve/qemu-server/104.conf`.
 
Just to be clear Moayad and thandyou again -

Just use Nano and remove the [BeforeUpdate] line and everything below and re-save?
 
You have to get rid of the all the `BeforeUpdate` section i.e., remove all the following section from the VM config:
Code:
[BeforeUpdate]
bios: ovmf
boot: order=ide0;ide2
cores: 2
efidisk0: local-lvm:vm-104-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
ide0: local-lvm:vm-104-disk-1,size=120G
ide2: local:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K
machine: pc-q35-7.2
memory: 8192
meta: creation-qemu=7.2.0,ctime=1700222103
name: Guralpman-DC1
net0: vmxnet3=6E:1F:65:2F:C2:BF,bridge=vmbr6,firewall=1
numa: 0
onboot: 1
ostype: win11
runningcpu: kvm64,enforce,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vpindex,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep
runningmachine: pc-q35-7.2+pve0
scsihw: virtio-scsi-single
smbios1: uuid=b700fdc1-41db-4f10-999d-e1ee3559efc1
snapstate: delete
snaptime: 1702916886
sockets: 2
tpmstate0: local-lvm:vm-104-disk-2,size=4M,version=v2.0
vga: virtio
vmgenid: 5b8b46c9-636e-40a7-a4b4-0c77834badde

I would have a copy of the VM config just in case you did something not correct.
 

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!