Backup of VM Fails With err -6

lucacraft89

New Member
Mar 10, 2024
8
1
3
When i go to backup VM with id 219 and only this one the backup fails even on local or empty 480GB disk, i suspect corrupt files because when i try to copy with cp -v disk.qcow2 it gives "IO error" at some point.

backuo log
Rich (BB code):
INFO: starting new backup job: vzdump 219 --notification-mode auto --node pve --mode snapshot --compress zstd --remove 0 --notes-template '{{guestname}}' --storage crucial-backup
INFO: Starting Backup of VM 219 (qemu)
INFO: Backup started at 2024-10-30 11:52:05
INFO: status = running
INFO: VM Name: linux19
INFO: include disk 'scsi0' 'local-crucial:219/vm-219-disk-1.qcow2' 150G
INFO: include disk 'efidisk0' 'local-crucial:219/vm-219-disk-0.qcow2' 528K
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: snapshots found (not included into backup)
INFO: creating vzdump archive '/mnt/pve/crucial-backup/dump/vzdump-qemu-219-2024_10_30-11_52_05.vma.zst'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task 'af01197b-ad36-41f7-8400-bda88d7e2677'
INFO: resuming VM again
INFO:   2% (3.1 GiB of 150.0 GiB) in 3s, read: 1.0 GiB/s, write: 194.0 MiB/s
INFO:   3% (4.5 GiB of 150.0 GiB) in 13s, read: 144.1 MiB/s, write: 127.4 MiB/s
INFO:   4% (6.1 GiB of 150.0 GiB) in 21s, read: 200.3 MiB/s, write: 137.5 MiB/s
INFO:   6% (10.3 GiB of 150.0 GiB) in 24s, read: 1.4 GiB/s, write: 46.4 MiB/s
INFO:   7% (10.5 GiB of 150.0 GiB) in 27s, read: 83.1 MiB/s, write: 82.6 MiB/s
INFO:   8% (12.1 GiB of 150.0 GiB) in 39s, read: 137.7 MiB/s, write: 125.3 MiB/s
INFO:   9% (13.7 GiB of 150.0 GiB) in 48s, read: 183.9 MiB/s, write: 170.2 MiB/s
INFO:  10% (15.3 GiB of 150.0 GiB) in 57s, read: 182.0 MiB/s, write: 168.7 MiB/s
INFO:  10% (15.4 GiB of 150.0 GiB) in 58s, read: 118.6 MiB/s, write: 118.5 MiB/s
ERROR: job failed with err -61 - No data available
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 219 failed - job failed with err -61 - No data available
INFO: Failed at 2024-10-30 11:53:04
INFO: Backup job finished with errors
INFO: notified via target `mail-to-root`
TASK ERROR: job errors
 
if reading the volume doesn't work, then yes, likely the file is corrupt and/or the underlying storage is defective.
 
fsck is not for checking disk health, just filesystem metadata. A commonly used tool for checking disk health is smartctl. You can also try to copy the image to a different storage (e.g. via Disk Action > Move storage to see if you get the same error). And if yes, please see my link again.
 

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!