Backup Error - job failed with err -5 - Input/output error

[sashxp]

Hi Guys,

since 6 Days i get the following error with backupping my Win10 QEMO machine.
I don't have any idea how to fix it, because of the small error message.

INFO: starting new backup job: vzdump 105 --storage Data1_Backup1 --remove 0 --mode snapshot --compress zstd --node pve
INFO: Starting Backup of VM 105 (qemu)
INFO: Backup started at 2020-06-06 12:20:52
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: Windows10
INFO: include disk 'virtio0' 'SSD_VM2:105/vm-105-disk-0.qcow2' 64G
INFO: creating archive '/mnt/hdd_r1_data1/backup1/proxmox/dump/vzdump-qemu-105-2020_06_06-12_20_52.vma.zst'
INFO: starting kvm to execute backup task
INFO: started backup task 'b96128b6-b14c-4e47-a033-f4345db6a2e9'
INFO: status: 0% (201457664/68719476736), sparse 0% (50847744), duration 3, read/write 67/50 MB/s
INFO: status: 0% (310181888/68719476736), sparse 0% (57696256), duration 7, read/write 27/25 MB/s
ERROR: job failed with err -5 - Input/output error
INFO: aborting backup job
INFO: stopping kvm after backup task
trying to acquire lock...
 OK
ERROR: Backup of VM 105 failed - job failed with err -5 - Input/output error
INFO: Failed at 2020-06-06 12:21:01
INFO: Backup job finished with errors
TASK ERROR: job errors

What could i check or do to solve this problem?

thx

 

[fireon]

ERROR: job failed with err -5 - Input/output error

That means a Problem with the VM Image or with the target storage. All other VM's running fine in backup? Your traget is writeable? Your local storage, or the storage where your Windows10 is running, is also ok?

 

[sashxp]

All other VM's running fine in backup? Your traget is writeable? Your local storage, or the storage where your Windows10 is running, is also ok?

Yes, other VM on the same Storage works as expected an all other backups to the Target also just works... Anyone knows where i could find more Information about the Problem?

 

[fireon]

Could you backup the VM if you stop it? Is the qemu Agent enabled? Post your VM Config.

 

[sashxp]

The VM is stopped - you can see it at line 4

 

[fireon]

The VM is stopped - you can see it at line 4

Yes, thanks. Right So please post your VMconfig.

qm config 105

For test please change your backupcomrpession to LZO, or "no compression".

 

[sashxp]

Yes, thanks. Right So please post your VMconfig.

no Problem - nothing special in vm config:

bootdisk: virtio0
cores: 2
cpu: host
ide2: none,media=cdrom
memory: 6144
name: Windows10
net0: virtio=7A:8A:AF2:B7:CA,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=cc592130-755a-495f-9615-74b8ccc2293d
sockets: 1
virtio0: SSD_VM2:105/vm-105-disk-0.qcow2,size=64G
vmgenid: a029f134-73bf-451c-b7b6-91f69d68cca9[/CODE]

For test please change your backupcomrpession to LZO, or "no compression".

same Problem - the compression doesn't change anything - and i've also changed the backup target, no success:

INFO: starting new backup job: vzdump 105 --storage Data2_backup2 --node pve --compress gzip --remove 0 --mode stop
INFO: Starting Backup of VM 105 (qemu)
INFO: Backup started at 2020-06-07 15:55:13
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: Windows10
INFO: include disk 'virtio0' 'SSD_VM2:105/vm-105-disk-0.qcow2' 64G
INFO: creating archive '/mnt/data2/backup2/proxmox/dump/vzdump-qemu-105-2020_06_07-15_55_13.vma.gz'
INFO: starting kvm to execute backup task
INFO: started backup task '4b3ab634-4cad-4547-8a33-23c206fdfdbd'
INFO: status: 0% (171048960/68719476736), sparse 0% (48922624), duration 3, read/write 57/40 MB/s
INFO: status: 0% (310181888/68719476736), sparse 0% (57491456), duration 9, read/write 23/21 MB/s
ERROR: job failed with err -5 - Input/output error
INFO: aborting backup job
INFO: stopping kvm after backup task
trying to acquire lock...
 OK
ERROR: Backup of VM 105 failed - job failed with err -5 - Input/output error
INFO: Failed at 2020-06-07 15:55:24
INFO: Backup job finished with errors
TASK ERROR: job errors

thats why i think it has to do with the source? how does source gets corrupted, than it cant be read?

 

[fireon]

Test if your sourceimage has errors:

qemu-img check -r all yourHDD.qcow2

https://www.geekpills.com/virtulization/repair-qcow2-disk

 

[sashxp]

no Errors - nothin to repair...

qemu-img check -r all /mnt/vm02/vm/images/105/vm-105-disk-0.qcow2
No errors were found on the image.
1048576/1048576 = 100.00% allocated, 0.00% fragmented, 0.00% compressed clusters
Image end offset: 68730224640

 

[sashxp]

i have a working backup from 28.05.2020 - will try to restore this and do a backup.

EDIT: this works ootb

()
INFO: starting new backup job: vzdump 105 --mode snapshot --remove 0 --compress zstd --node pve --storage Data1_Backup1
INFO: Starting Backup of VM 105 (qemu)
INFO: Backup started at 2020-06-07 21:37:18
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: Windows10
INFO: include disk 'virtio0' 'SSD_VM2:105/vm-105-disk-0.qcow2' 64G
INFO: creating archive '/mnt/hdd_r1_data1/backup1/proxmox/dump/vzdump-qemu-105-2020_06_07-21_37_18.vma.zst'
INFO: starting kvm to execute backup task
INFO: started backup task '4f8632b6-fe04-4ddc-8423-fc72b4ba100c'
INFO: status: 0% (93454336/68719476736), sparse 0% (42168320), duration 3, read/write 31/17 MB/s
INFO: status: 1% (702218240/68719476736), sparse 0% (61784064), duration 31, read/write 21/21 MB/s
INFO: status: 2% (1377042432/68719476736), sparse 0% (76562432), duration 63, read/write 21/20 MB/s
INFO: status: 3% (2065104896/68719476736), sparse 0% (80158720), duration 95, read/write 21/21 MB/s
INFO: status: 4% (2750218240/68719476736), sparse 0% (89841664), duration 127, read/write 21/21 MB/s
INFO: status: 5% (3457548288/68719476736), sparse 0% (158810112), duration 159, read/write 22/19 MB/s
INFO: status: 6% (4131782656/68719476736), sparse 0% (186687488), duration 190, read/write 21/20 MB/s
INFO: status: 7% (4827709440/68719476736), sparse 0% (197627904), duration 223, read/write 21/20 MB/s
INFO: status: 8% (5520359424/68719476736), sparse 0% (208310272), duration 257, read/write 20/20 MB/s
INFO: status: 9% (6192168960/68719476736), sparse 0% (218521600), duration 287, read/write 22/22 MB/s
INFO: status: 10% (6875512832/68719476736), sparse 0% (222470144), duration 316, read/write 23/23 MB/s
INFO: status: 11% (7568883712/68719476736), sparse 0% (233181184), duration 342, read/write 26/26 MB/s
INFO: status: 12% (8259764224/68719476736), sparse 0% (236355584), duration 368, read/write 26/26 MB/s
INFO: status: 13% (8940355584/68719476736), sparse 0% (241311744), duration 392, read/write 28/28 MB/s
INFO: status: 14% (9637134336/68719476736), sparse 0% (244166656), duration 415, read/write 30/30 MB/s
INFO: status: 15% (10308354048/68719476736), sparse 0% (246657024), duration 437, read/write 30/30 MB/s
INFO: status: 16% (11059724288/68719476736), sparse 1% (805093376), duration 449, read/write 62/16 MB/s
INFO: status: 17% (11784617984/68719476736), sparse 2% (1529925632), duration 456, read/write 103/0 MB/s
INFO: status: 18% (12380930048/68719476736), sparse 3% (2125946880), duration 461, read/write 119/0 MB/s
INFO: status: 19% (13089505280/68719476736), sparse 3% (2202509312), duration 479, read/write 39/35 MB/s
INFO: status: 20% (13854244864/68719476736), sparse 3% (2660618240), duration 492, read/write 58/23 MB/s
INFO: status: 21% (14493089792/68719476736), sparse 4% (3299463168), duration 497, read/write 127/0 MB/s
INFO: status: 22% (15132131328/68719476736), sparse 5% (3938504704), duration 502, read/write 127/0 MB/s
INFO: status: 23% (15823273984/68719476736), sparse 5% (4050444288), duration 519, read/write 40/34 MB/s
INFO: status: 24% (16536305664/68719476736), sparse 5% (4055298048), duration 538, read/write 37/37 MB/s
INFO: status: 25% (17196384256/68719476736), sparse 5% (4075921408), duration 553, read/write 44/42 MB/s
INFO: status: 26% (17905680384/68719476736), sparse 5% (4078280704), duration 568, read/write 47/47 MB/s
INFO: status: 27% (18559401984/68719476736), sparse 5% (4087930880), duration 580, read/write 54/53 MB/s
INFO: status: 28% (19253493760/68719476736), sparse 5% (4113321984), duration 591, read/write 63/60 MB/s
INFO: status: 29% (19954466816/68719476736), sparse 6% (4126638080), duration 601, read/write 70/68 MB/s
INFO: status: 30% (20669726720/68719476736), sparse 6% (4543725568), duration 605, read/write 178/74 MB/s
INFO: status: 37% (25614024704/68719476736), sparse 13% (9488023552), duration 608, read/write 1648/0 MB/s
INFO: status: 45% (30984699904/68719476736), sparse 21% (14858698752), duration 611, read/write 1790/0 MB/s
INFO: status: 53% (36998479872/68719476736), sparse 30% (20872478720), duration 614, read/write 2004/0 MB/s
INFO: status: 63% (43926355968/68719476736), sparse 40% (27800354816), duration 617, read/write 2309/0 MB/s
INFO: status: 76% (52254474240/68719476736), sparse 52% (36128473088), duration 620, read/write 2776/0 MB/s
INFO: status: 92% (63394152448/68719476736), sparse 68% (47268151296), duration 623, read/write 3713/0 MB/s
INFO: status: 99% (68440621056/68719476736), sparse 75% (52105850880), duration 626, read/write 1682/69 MB/s
INFO: status: 100% (68719476736/68719476736), sparse 75% (52107943936), duration 629, read/write 92/92 MB/s
INFO: transferred 68719 MB in 629 seconds (109 MB/s)
INFO: stopping kvm after backup task
INFO: archive file size: 7.52GB
trying to acquire lock...
 OK
INFO: Finished Backup of VM 105 (00:10:31)
INFO: Backup finished at 2020-06-07 21:47:49
INFO: Backup job finished successfully
TASK OK

 

[sashxp]

I've using just "normal" storage - no ceph - but could it possible, that i run into: https://bugzilla.proxmox.com/show_bug.cgi?id=2311

 

[fireon]

Yes, and maybe an Stuff could bring more light in this issue.

 

[sashxp]

Stuff? I don't understand what you mean

 

[fireon]

Stuff? I don't understand what you mean

Proxmox Support: https://forum.proxmox.com/members/?key=staff_members
Wrong spelling... i've corrected my post.