Backup failed, 'guest-fsfreeze-thaw' failed - got timeout| job errors

[sarw]

Good time, I ran into a problem that backup does not work on one of the 3 machines, after searching for information on the forums I tried to disable quemu agent - the problem persists.
Attaching the system versions:

pve-qemu-kvm: 8.1.5-6
qemu-server: 8.2.1
pve-manager/8.2.4/running kernel: 6.5.13-5-pve
problem VM100

Details​

VMID	Name	Status	Time	Size	Filename
100	addc	err	14min 17s	0 B	null
102	asterisk	ok	8min 48s	16.236 GiB	/media/backup/dump/vzdump-qemu-102-2024_09_08-01_14_22.vma.zst
103	mailbox	ok	55min 52s	88.812 GiB	/media/backup/dump/vzdump-qemu-103-2024_09_08-01_23_10.vma.zst

Total running time: 1h 18min 57s
Total size: 105.048 GiB

Logs​

vzdump 102 103 100


100: 2024-09-08 01:00:05 INFO: Starting Backup of VM 100 (qemu)
100: 2024-09-08 01:00:05 INFO: status = running
100: 2024-09-08 01:00:05 INFO: VM Name: addc
100: 2024-09-08 01:00:05 INFO: include disk 'scsi0' 'SSDSams1:100/vm-100-disk-0.raw' 100G
100: 2024-09-08 01:00:05 INFO: include disk 'scsi1' 'pveolddirectory:100/vm-100-disk-3.raw'
100: 2024-09-08 01:00:05 INFO: backup mode: snapshot
100: 2024-09-08 01:00:05 INFO: ionice priority: 7
100: 2024-09-08 01:00:05 INFO: creating vzdump archive '/media/backup/dump/vzdump-qemu-100-2024_09_08-01_00_05.vma.zst'
100: 2024-09-08 01:00:05 INFO: issuing guest-agent 'fs-freeze' command
100: 2024-09-08 01:00:37 INFO: issuing guest-agent 'fs-thaw' command
100: 2024-09-08 01:03:37 ERROR: VM 100 qmp command 'guest-fsfreeze-thaw' failed - got timeout
100: 2024-09-08 01:03:37 ERROR: got timeout
100: 2024-09-08 01:03:37 INFO: aborting backup job
100: 2024-09-08 01:13:37 ERROR: VM 100 qmp command 'backup-cancel' failed - unable to connect to VM 100 qmp socket - timeout after 5987 retries
100: 2024-09-08 01:13:37 INFO: resuming VM again
100: 2024-09-08 01:14:22 ERROR: Backup of VM 100 failed - VM 100 qmp command 'cont' failed - unable to connect to VM 100 qmp socket - timeout after 450 retries

 

[fiona]

Hi,
please try to upgrade to current versions and see if the issue persists:
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#system_software_updates
https://pve.proxmox.com/wiki/Package_Repositories

If it does persist, please share the output of pveversion -v and qm config 100 as well as the system log/journal from around the time the issue happens. Is the VM still responsive after the issue happens or is it stuck?

 

[sarw]

We have already tried, it did not work, we cannot update the versions, because our raid controller does not support, we cannot update the raid controller because the disks are formatted,
backup does not work after changing server components, however, it does not work only on VM100 (windows8.x/2012/2012r2)but on VM102 VM103 everything works (6.x - 2.6 Kernel)

 

[fiona]

You could still try to upgrade to pve-qemu-kvm >=9 and the latest version of qemu-server, those are not related to the RAID controller.

If it does persist, please share the output of pveversion -v and qm config 100 as well as the system log/journal from around the time the issue happens. Is the VM still responsive after the issue happens or is it stuck?

 

[sarw]

When updating them, a new version of the kernel is required, therefore we cannot do this.

 

[fiona]

You can simply pin the older kernel even after installing a newer kernel and continue booting into the older kernel, see: https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_kernel_pin
Or you could hold back the kernel package if you really wanted to, but I'd not recommend it.