Error during backup ( err -5 - Input/output error)

[ButelkaWody]

Hello,
When I'm wanna do a copy of my vm after 3% of progress i have error.
I tried change storage but it doesn't help. I checked my disk using smartctl but everything is ok..

I put the log below:

root@proxmox:/var/log/vzdump# cat qemu-108.log
2023-03-22 23:03:53 INFO: Starting Backup of VM 108 (qemu)
2023-03-22 23:03:53 INFO: status = stopped
2023-03-22 23:03:53 INFO: backup mode: stop
2023-03-22 23:03:53 INFO: ionice priority: 7
2023-03-22 23:03:53 INFO: VM Name: UbuntusrvGNS3
2023-03-22 23:03:53 INFO: include disk 'virtio0' 'local-lvm:vm-108-disk-0' 200G
2023-03-22 23:03:53 INFO: snapshots found (not included into backup)
2023-03-22 23:03:53 INFO: creating vzdump archive '/var/lib/vz/dump/vzdump-qemu-108-2023_03_22-23_03_53.vma.zst'
2023-03-22 23:03:53 INFO: starting kvm to execute backup task
2023-03-22 23:03:54 INFO: started backup task '1c5199a7-df7d-492b-b2f6-c2a409314827'
2023-03-22 23:03:57 INFO:   0% (149.0 MiB of 200.0 GiB) in 3s, read: 49.7 MiB/s, write: 22.4 MiB/s
2023-03-22 23:04:08 INFO:   1% (2.0 GiB of 200.0 GiB) in 14s, read: 172.8 MiB/s, write: 48.4 MiB/s
2023-03-22 23:04:11 INFO:   2% (5.1 GiB of 200.0 GiB) in 17s, read: 1.0 GiB/s, write: 22.8 MiB/s
2023-03-22 23:04:26 INFO:   3% (6.1 GiB of 200.0 GiB) in 32s, read: 72.6 MiB/s, write: 48.5 MiB/s
2023-03-22 23:05:01 INFO:   3% (6.6 GiB of 200.0 GiB) in 1m 7s, read: 12.6 MiB/s, write: 8.1 MiB/s
2023-03-22 23:05:01 ERROR: job failed with err -5 - Input/output error
2023-03-22 23:05:01 INFO: aborting backup job
2023-03-22 23:05:01 INFO: stopping kvm after backup task
2023-03-22 23:05:03 ERROR: Backup of VM 108 failed - job failed with err -5 - Input/output error

Proxmox version:

root@proxmox:/var/log/vzdump# pveversion
pve-manager/7.2-3/c743d6c1 (running kernel: 5.15.30-2-pve)

Maybe someone had this error, any suggestions are welcome.
Thanks

 

[Chris]

Hi,
some users reported this to correlate with bad memory, see https://forum.proxmox.com/threads/p...days-external-internal-backup-targets.123427/

Try running a memtest and check the journal from around the time of the backup journalctl --since <date> --until <date>