0 votes
30 views
in Cloud by

We have a server with the ID 112 and a snapshot named 'BeforeDiskUpgrade.' When I attempt to delete the snapshot, I encounter the error: 'rbd error: rbd: error opening image vm-112-state-BeforeDiskUpgrade: (2) No such file or directory.' I checked the pool for the snapshot, but it doesn't exist.

Command:
rbd ls -l pool-name
Error:
rbd: error opening vm-112-state-BeforeDiskUpgrade: (2) No such file or directory

However, the disk vm-112-disk-0 with 5 TiB is still present.
Can anyone advise on how to resolve this?

2 Answers

0 votes
by

Did you manually remove the snapshot? It seems there may be a leftover snapshot configuration in the VM's config file. Could you share the output of the following command:
cat /etc/pve/qemu-server/112.conf
If you confirm that there are no snapshots associated with any of the VM's disks, you may be able to resolve the issue by editing the config file to remove the snapshot entry.

by
Below is the config,

cat /etc/pve/qemu-server/112.conf
agent: 1
boot: order=sata0
ciuser: root
cores: 2
efidisk0: px-st:vm-112-disk-4,efitype=4m,pre-enrolled-keys=1,size=1M
ide0: px-st:vm-112-cloudinit,media=cdrom,size=4M
ide2: NFS:iso/CentOS-7-x86_64-Minimal-1810__2_.iso,media=cdrom,size=918M
ipconfig0: ip=IP/24,gw=gw
memory: 12288
name: disk3-new
net0: virtio=BC:24:11:DA:F0:FE,bridge=vmbr0
net1: virtio=BC:24:11:07:EA:BC,bridge=vmbr1,firewall=1,tag=501
numa: 1
ostype: l26
parent: before-password-reset
sata0: px-st:vm-112-disk-0,size=5T
scsihw: virtio-scsi-pci
smbios1: uuid=47331dc4-b36e-4189-9d6f-861690e6ebca
sockets: 3
unused0: px-st:vm-112-disk-1
unused1: px-st:vm-112-disk-3
unused2: px-st:vm-112-disk-2
vmgenid: c55ebef4-7f92-44f1-9bb3-9ef71227c0f6

[BeforeDiskUpgrade]
#Before Disk Upgrade 21/04/2024
agent: 1
boot: order=scsi0;ide2;net0
cipassword: $5$zfWUzJAH$5JRrTJpngvss2Rub2M827INK9qm5DH7iVyWIbJ7KvP7
ciuser: root
cores: 2
ide0: px-st:vm-112-cloudinit,media=cdrom,size=4M
ide2: cdrom,media=cdrom
ipconfig0: ip=ip/24,gw=gw
memory: 2048
name: test-disk3
net0: virtio=BC:24:11:DA:F0:FE,bridge=vmbr0,rate=12.5
net1: virtio=BC:24:11:07:EA:BC,bridge=vmbr1,firewall=1,tag=501
numa: 1
ostype: l26
runningcpu: kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep
runningmachine: pc-i440fx-8.1+pve0
scsi0: px-st:vm-112-disk-0,discard=on,size=5T
scsihw: virtio-scsi-pci
smbios1: uuid=47331dc4-b36e-4189-9d6f-861690e6ebca
snapstate: delete
snaptime: 1713670523
sockets: 1
vmgenid: 91ad868e-3411-4376-964b-f289c9390bba
vmstate: px-st:vm-112-state-BeforeDiskUpgrade

[before-password-reset]
agent: 1
boot: order=scsi1;scsi0
cipassword: $5$zfWUzJAH$5JRrTJpngvss2Rub2M827INK9qm5DH7iVyWIbJ7KvP7
ciuser: root
cores: 2
ide0: px-st:vm-112-cloudinit,media=cdrom,size=4M
ide2: NFS:iso/ubuntu-22.04-live-server-amd64.iso,media=cdrom,size=1432338K
ipconfig0: ip=ip/24,gw=gw
memory: 12288
name: disk3-new
net0: virtio=BC:24:11:DA:F0:FE,bridge=vmbr0
net1: virtio=BC:24:11:07:EA:BC,bridge=vmbr1,firewall=1,tag=501
numa: 1
ostype: l26
parent: disk3Issue
runningcpu: kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep
runningmachine: pc-i440fx-8.1+pve0
scsi0: px-st:vm-112-disk-0,discard=on,size=5T
scsi1: px-st:vm-112-disk-1,size=3T
scsihw: virtio-scsi-pci
smbios1: uuid=47331dc4-b36e-4189-9d6f-861690e6ebca
snaptime: 1726246676
sockets: 3
vmgenid: ed7d9953-c66a-4a0d-81e6-addb755dbb45
vmstate: px-st:vm-112-state-before-password-reset

[disk3Issue]
#This snapshot during the disk kernal issue
agent: 1
boot: order=ide2
cipassword: $5$zfWUzJAH$5JRrTJpngvss2Rub2M827INK9qm5DH7iVyWIbJ7KvP7
ciuser: root
cores: 2
ide0: px-st:vm-112-cloudinit,media=cdrom,size=4M
ide2: NFS:iso/CentOS-7-x86_64-Minimal-1810__2_.iso,media=cdrom,size=918M
ipconfig0: ip=ip/24,gw=gw
memory: 12288
name: disk3-new
net0: virtio=BC:24:11:DA:F0:FE,bridge=vmbr0
net1: virtio=BC:24:11:07:EA:BC,bridge=vmbr1,firewall=1,tag=501
numa: 1
ostype: l26
parent: BeforeDiskUpgrade
runningcpu: kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep
runningmachine: pc-i440fx-8.1+pve0
scsi0: px-st:vm-112-disk-0,discard=on,size=5T
scsihw: virtio-scsi-pci
smbios1: uuid=47331dc4-b36e-4189-9d6f-861690e6ebca
snaptime: 1726205984
sockets: 3
vmgenid: ed7d9953-c66a-4a0d-81e6-addb755dbb45
vmstate: px-st:vm-112-state-disk3Issue

Thank you
by
Backup your VM + config (just to be safe), and try removing the config section related to the missing snapshot. That leads to the snapshot not being expected to be present anymore.
0 votes
by

To be safe, back up your VM and its configuration first. Then, try removing the section in the config file related to the missing snapshot. This should prevent the system from expecting the snapshot to be present

cat /etc/pve/qemu-server/112.conf

...