Image is not in qcow2 format

[Nam Trần]

After running apt-get dist-upgrade, I stopped all VMs and reboot the node. All VMs started as usual except one whose ID is 998.

qm start 998

kvm: -drive file=/mnt/pve/gold/images/998/vm-998-disk-0.qcow2,if=none,id=drive-virtio0,format=qcow2,cache=none,aio=native,detect-zeroes=on: Image is not in qcow2 format
start failed: QEMU exited with code 1

Try qemu-img check <path to image>/vm-998-disk-0.qcow2 returned error qemu-img: This image format does not support checks

In Jul 15th and 16th, my storage server was attacked by a ransomeware. It renamed vm-998-disk-0.qcow2 to vm-998-disk-0.<ransomeware signature> while the VM was running. I had shutdown the affected PC to prevent it from damaging more resources, then renamed the image back to the original one. The VM has been running well for roughly 2 months.

I do appreciate your help.

pveversion -v

proxmox-ve: 6.2-1 (running kernel: 5.4.60-1-pve)
pve-manager: 6.2-11 (running version: 6.2-11/22fb4983)
pve-kernel-5.4: 6.2-6
pve-kernel-helper: 6.2-6
pve-kernel-5.4.60-1-pve: 5.4.60-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-6
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-12
pve-cluster: 6.1-8
pve-container: 3.2-1
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-1
pve-qemu-kvm: 5.1.0-1
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-14
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve1

 

[apoc]

Hope you have a backup.
I have experienced it with other hypervisors already that systems have run fine until they got rebooted/ stopped and started.
At that point in time the storage corruption manifested itself. No way forward. The only way to get things running again: restore from backup.

 

[Nam Trần]

Hope you have a backup.
I have experienced it with other hypervisors already that systems have run fine until they got rebooted/ stopped and started.
At that point in time the storage corruption manifested itself. No way forward. The only way to get things running again: restore from backup.

I think the worst nightmare has just happened to me. The latest VM backup was since Jul 16th and data + software backup was 24 days ago. I have just tried booting from Windows Server 2016 CD/DVD and the installation wizard did recognize the disk image as a new one.

Another VM with SUSE OS on another node was not bootable after pveupdate && pveupgrade (pve-no-subscription repository). I feel scared to make any further ProxmoxVE maintenance.

 

[apoc]

Imho the problem is not PVE being upgraded.
I suspect the stop/start of the VMs (or even their reboot) triggers the issue.

Hate to say it but face it. Its likely not going to get any better.

You can try to do an in-guest (not from the hypervisor level!) backup right now but honestly, I am not sure if I would trust that data if I were you.