job failed with err -61 - No data available

[sebastiano]

Hi every one, i have a machine every day backup failed at 32% with the same error........ i don't understand if there is a problem with the disk or other... can anyone help me? The machine work good

INFO: Starting Backup of VM 301 (qemu)
INFO: Backup started at 2023-01-18 20:01:32
INFO: status = running
INFO: VM Name: SERVEREXT
INFO: include disk 'sata0' 'local-lvm:vm-301-disk-0' 200G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating vzdump archive '/mnt/pve/NAS2/dump/vzdump-qemu-301-2023_01_18-20_01_32.vma.zst'
INFO: started backup task 'f229342d-ca16-4810-8256-4dd37d95c47e'
INFO: resuming VM again
INFO: 0% (1.6 GiB of 200.0 GiB) in 3s, read: 554.6 MiB/s, write: 233.0 MiB/s
INFO: 1% (2.3 GiB of 200.0 GiB) in 6s, read: 224.8 MiB/s, write: 223.2 MiB/s
INFO: 2% (4.1 GiB of 200.0 GiB) in 15s, read: 202.2 MiB/s, write: 197.8 MiB/s
INFO: 3% (6.0 GiB of 200.0 GiB) in 23s, read: 252.8 MiB/s, write: 251.1 MiB/s
INFO: 4% (8.2 GiB of 200.0 GiB) in 36s, read: 168.7 MiB/s, write: 167.9 MiB/s
INFO: 5% (10.1 GiB of 200.0 GiB) in 50s, read: 142.2 MiB/s, write: 139.6 MiB/s
INFO: 6% (12.2 GiB of 200.0 GiB) in 1m 7s, read: 127.7 MiB/s, write: 127.2 MiB/s
INFO: 7% (14.0 GiB of 200.0 GiB) in 1m 15s, read: 230.2 MiB/s, write: 228.0 MiB/s
INFO: 8% (16.0 GiB of 200.0 GiB) in 1m 24s, read: 225.2 MiB/s, write: 223.2 MiB/s
INFO: 9% (18.2 GiB of 200.0 GiB) in 1m 33s, read: 242.9 MiB/s, write: 241.8 MiB/s
INFO: 10% (20.1 GiB of 200.0 GiB) in 1m 46s, read: 153.6 MiB/s, write: 150.7 MiB/s
INFO: 11% (22.1 GiB of 200.0 GiB) in 1m 55s, read: 228.0 MiB/s, write: 224.3 MiB/s
INFO: 12% (24.0 GiB of 200.0 GiB) in 2m 1s, read: 330.5 MiB/s, write: 264.1 MiB/s
INFO: 13% (26.1 GiB of 200.0 GiB) in 2m 9s, read: 269.2 MiB/s, write: 266.9 MiB/s
INFO: 14% (28.1 GiB of 200.0 GiB) in 2m 22s, read: 153.9 MiB/s, write: 153.5 MiB/s
INFO: 15% (30.1 GiB of 200.0 GiB) in 2m 36s, read: 144.2 MiB/s, write: 143.8 MiB/s
INFO: 16% (32.1 GiB of 200.0 GiB) in 2m 52s, read: 131.2 MiB/s, write: 130.5 MiB/s
INFO: 17% (34.2 GiB of 200.0 GiB) in 3m 7s, read: 139.0 MiB/s, write: 138.3 MiB/s
INFO: 18% (36.1 GiB of 200.0 GiB) in 3m 15s, read: 245.1 MiB/s, write: 243.5 MiB/s
INFO: 19% (38.1 GiB of 200.0 GiB) in 3m 33s, read: 113.0 MiB/s, write: 112.8 MiB/s
INFO: 20% (40.2 GiB of 200.0 GiB) in 3m 49s, read: 135.9 MiB/s, write: 135.7 MiB/s
INFO: 21% (42.0 GiB of 200.0 GiB) in 4m 9s, read: 94.8 MiB/s, write: 94.8 MiB/s
INFO: 22% (44.0 GiB of 200.0 GiB) in 4m 29s, read: 102.0 MiB/s, write: 102.0 MiB/s
INFO: 23% (46.0 GiB of 200.0 GiB) in 4m 54s, read: 82.5 MiB/s, write: 82.5 MiB/s
INFO: 24% (48.1 GiB of 200.0 GiB) in 5m 9s, read: 139.9 MiB/s, write: 139.9 MiB/s
INFO: 25% (50.0 GiB of 200.0 GiB) in 5m 28s, read: 104.0 MiB/s, write: 104.0 MiB/s
INFO: 26% (52.0 GiB of 200.0 GiB) in 5m 45s, read: 120.3 MiB/s, write: 120.3 MiB/s
INFO: 27% (54.0 GiB of 200.0 GiB) in 6m 1s, read: 128.2 MiB/s, write: 128.2 MiB/s
INFO: 28% (56.0 GiB of 200.0 GiB) in 6m 15s, read: 146.0 MiB/s, write: 146.0 MiB/s
INFO: 29% (58.1 GiB of 200.0 GiB) in 6m 27s, read: 180.6 MiB/s, write: 174.1 MiB/s
INFO: 30% (60.2 GiB of 200.0 GiB) in 6m 34s, read: 301.4 MiB/s, write: 268.7 MiB/s
INFO: 31% (62.2 GiB of 200.0 GiB) in 6m 44s, read: 200.5 MiB/s, write: 200.3 MiB/s
INFO: 32% (64.1 GiB of 200.0 GiB) in 6m 53s, read: 219.9 MiB/s, write: 204.1 MiB/s
INFO: 32% (64.9 GiB of 200.0 GiB) in 6m 57s, read: 198.1 MiB/s, write: 197.6 MiB/s
ERROR: job failed with err -61 - No data available
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 301 failed - job failed with err -61 - No data available
INFO: Failed at 2023-01-18 20:08:41
INFO: Backup job finished with errors

TASK ERROR: job errors

 

[mattlehrer]

Getting the same on one of my nodes. 4 nodes, 3 backed up fine, 1 failed to same NAS.
Running latest pve with all patches.

 

[Choppel]

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.

 

[Choppel]

PS: There is most likely a problem with the physical disk. Have a look at the syslog during backup.