ERROR: job failed with err -61 - No data available

rodo2023

Member
Dec 14, 2022
6
0
6
Hi,

den Fehler verstehe ich nicht?!

INFO: starting new backup job: vzdump 102 --storage NasBackup2 --compress zstd --mode snapshot --notes-template '{{guestname}}' --remove 0 --node prox
INFO: Starting Backup of VM 102 (qemu)
INFO: Backup started at 2022-12-18 21:10:55
INFO: status = running
INFO: VM Name: Docker04
INFO: include disk 'scsi0' 'local-lvm:vm-102-disk-0' 64G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating vzdump archive '/mnt/pve/NasBackup2/dump/vzdump-qemu-102-2022_12_18-21_10_55.vma.zst'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task 'a687e7fe-c5d4-4daa-8f03-38d399be79b0'
INFO: resuming VM again
INFO: 0% (149.0 MiB of 64.0 GiB) in 1s, read: 149.0 MiB/s, write: 36.7 MiB/s
ERROR: job failed with err -61 - No data available
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 102 failed - job failed with err -61 - No data available
INFO: Failed at 2022-12-18 21:10:57
INFO: Backup job finished with errors
TASK ERROR: job errors
 
Hallo,

Funktioniert das gleiche Backup, aber auf einem anderen Storage?

hast du während des Backup job einen interessanten error im Syslog/journalctl gesehen?
 
Hallo Moayad,

danke für den Hinweis syslog, es gibt ein Problem mit dem Datenträger.
kernel: [52591.986036] critical medium error, dev nvme0n1, sector 209995392 op 0x0:(READ) flags 0x0 phys_seg 5 prio class 2
 
This happened for me a couple of times now on different PVE instances. The only way of getting the vm to work again was to create a new virtual disk, backing up the content of the old virtual disk with Clonezilla into the new disk and then removing the old disk.