Vm disk problem

[ferdikilic]

Hello,
During the backup, I received an error due to a network problem. The virtual machine did not respond and I stopped it with the qm stop 330 command. Then I tried to turn it on, but my virtual machine did not start. When I checked, I think the virtual disk containing the operating system is corrupted and I cannot access any data on it. Is there a way to recover it? The following command did not work
qemu-img check -r all /mnt/pve/ssd500/images/330/vm-330-disk-0.qcow2

 

[fiona]

Hi,
please share the output of pveversion -v and qm config 330.

To check for partitions/file systems on the qcow2 disk, you can use:

modprobe nbd max_part=63
qemu-nbd -n -r -c /dev/nbd0 /mnt/pve/ssd500/images/330/vm-330-disk-0.qcow2
wipefs /dev/nbd0
fdisk -l /dev/nbd0
qemu-nbd -d /dev/nbd0

If you are still on Proxmox VE 7.x and using SATA for the virtual disk, then you might've hit https://bugzilla.proxmox.com/show_bug.cgi?id=2874
You can try using a tool like https://www.cgsecurity.org/wiki/TestDisk to recover.

 

[ferdikilic]

Hello, yes I am using SATA. That's the problem. I restored the data on the virtual disk from backup. Thank you very much for your support and information.


balloon: 0
boot: order=sata0;ide2;net0
cores: 16
ide2: none,media=cdrom
machine: pc-i440fx-7.2
memory: 50000
meta: creation-qemu=7.2.0,ctime=1703068423
name: ATIKER-SRV
net0: e1000=A2:12:CF:1C2:83,bridge=vmbr0
net1: e1000=F6:26:4D:22:57:5D,bridge=vmbr0
numa: 0
ostype: win10
sata0: ssd500:330/vm-330-disk-0.qcow2,size=100G
sata1: ssd1tb:vm-330-disk-0,size=530G
sata2: nvme1tb:330/vm-330-disk-1.qcow2,size=32G
sata3: nvme1tb:330/vm-330-disk-0.qcow2,size=640G
scsihw: virtio-scsi-single
smbios1: uuid=fb905987-427b-4321-83e7-b7e3cb82392f
sockets: 1
vmgenid: 84df1fcd-380d-436a-8660-e531201ce7a5
-
root@host1:~# pveversion -v
proxmox-ve: 7.3-1 (running kernel: 5.15.85-1-pve)
pve-manager: 7.3-6 (running version: 7.3-6/723bb6ec)
pve-kernel-helper: 7.3-6
pve-kernel-5.15: 7.3-2
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.15.60-2-pve: 5.15.60-2
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.3-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-2
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-6
libpve-storage-perl: 7.3-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.3.3-1
proxmox-backup-file-restore: 2.3.3-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.1-1
proxmox-widget-toolkit: 3.5.5
pve-cluster: 7.3-2
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20221111-1
pve-firewall: 4.2-7
pve-firmware: 3.6-3
pve-ha-manager: 3.5.1
pve-i18n: 2.8-3
pve-qemu-kvm: 7.2.0-5
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1

 

[fiona]

Glad you were able to recover!

You might want to consider upgrading to Proxmox VE 8, where that bug was fixed (and Proxmox VE 7 will be end-of-life in a few months): https://pve.proxmox.com/wiki/Upgrade_from_7_to_8

 

[ferdikilic]

Thank you again for your support