Hi, would these be the logs? The storage is local.Hi,
please check the systemd journal around the time of the backup for errors. Anything of interest logged there? Also, do check the smart values of you disks. Further, what filesystem is the VM disk located on? Is this a local storage or a shared storage?
Well, it seems you have filesystem errors. Do you have any redundancy on this storage? What kernel is in use?Nov 19 11:35:54 proxmox-server kernel: BTRFS warning (device sda3): csum failed root 5 ino 24579934 off 87854161920 csum 0x76a60e03 expected csum 0xd0336f2c mirror 1
Nov 19 11:35:54 proxmox-server kernel: BTRFS error (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 3440, gen 0
Nov 19 11:35:54 proxmox-server kernel: BTRFS warning (device sda3): direct IO failed ino 24579934 op 0x0 offset 0x1474842000 len 4096 err no 10
Nov 19 11:35:54 proxmox-server kernel: BTRFS warning (device sda3): csum failed root 5 ino 24579934 off 87854145536 csum 0x63515fd4 expected csum 0x686409d3 mirror 1
Nov 19 11:35:54 proxmox-server kernel: BTRFS error (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 3441, gen 0
Nov 19 11:35:54 proxmox-server kernel: BTRFS warning (device sda3): direct IO failed ino 24579934 op 0x0 offset 0x147483e000 len 4096 err no 10
Nov 19 11:35:55 proxmox-server pvedaemon[3984083]: ERROR: Backup of VM 102 failed - job failed with err -5 - Input/output error
I'm using kernel version 6.8.4-2-pve. I have no redundancy.Well, it seems you have filesystem errors. Do you have any redundancy on this storage? What kernel is in use?
btrfs check, see https://btrfs.readthedocs.io/en/latest/btrfs-check.html But without redundancy you will most likely have experienced some data loss.We use essential cookies to make this site work, and optional cookies to enhance your experience.