input/output error

[heels]

Please help me with backup.

gives a copy error ,
ERROR: Backup of VM 107 failed - job failed with err -5 - Input/output error
INFO: Failed at 2022-10-21 13:42:14
INFO: Backup job finished with errors
TASK ERROR: job errors

I chose to create a copy on a local disk and on pbs the same error

I suppose that he first tries to create a copy in the root disk and there is 48Gb left. If so, where in the settings can I override where to make a preliminary copy? There is enough space on the other section, I did not find it in the settings.

 

[fiona]

Hi,
for VMs, no temporary copies are created. Do you see any messages in /var/log/syslog around the time the backup runs? What kind of storage is the VM's disk on? Please share the full backup log and the output of pveversion -v.

 

[heels]

Hi,
for VMs, no temporary copies are created. Do you see any messages in /var/log/syslog around the time the backup runs? What kind of storage is the VM's disk on? Please share the full backup log and the output of pveversion -v.

is on the same physical media in qcow2 format
type "Directory"

proxmox-ve: 7.0-2 (running kernel: 5.11.22-1-pve)
pve-manager: 7.0-9 (running version: 7.0-9/228c9caa)
pve-kernel-helper: 7.0-4
pve-kernel-5.11: 7.0-3
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.0.0-1+pve6
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.1.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-4
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-9
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-2
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.1-1
proxmox-backup-file-restore: 2.0.1-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.2-4
pve-cluster: 7.0-3
pve-container: 4.0-8
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-10
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.4-pve1

 

[fiona]

According to the log, the IO errors come from your sdb drive. Please check if the device is okay (e.g. using smartctl) and that it's connected properly. The errors could also come from kernel/firmware issues, but it doesn't seem like you updated recently, so those components probably didn't change recently. If the drive is dying, you might want to use a tool like ddrescue to save the data that can still be saved.

 

[heels]

According to the log, the IO errors come from your sdb drive. Please check if the device is okay (e.g. using smartctl) and that it's connected properly. The errors could also come from kernel/firmware issues, but it doesn't seem like you updated recently, so those components probably didn't change recently. If the drive is dying, you might want to use a tool like ddrescue to save the data that can still be saved.

Can you please tell me how to cure this pain? Started with the 7th version on the 6th this was not. https://drive.google.com/file/d/1dXEjZV4jzjJXuvssEZ7ZMnxh_9fTQwz2/view?usp=share_link

when a constant blinking starts on the console, and on a fresh machine and a clean installation, the same problem, if you connect from a local terminal, then there is no problem.