Backup interrupts after some time

Feb 3, 2026
5
0
1
lithilion.at
Greetings!

I have a PVE and PBS setup (both on latest versions). The PBS is configured as backup for the PVE, no network intermediate in between (PVE and PBS are in the same /24 network). Both have zfs as file system. I have a recurring backup scheduled for most of my VMs and LXCs which is working fine (around 12 pieces with each about 1-8 GB disk space).
One LXCs gets interupted always and never finishes. The error message is the following:

Code:
...
INFO: processed 89.677 GiB in 54m, uploaded 88.117 GiB
INFO: HTTP/2.0 connection failed
INFO: unclosed encoder dropped
INFO: closed encoder dropped with state
INFO: unfinished encoder state dropped
INFO: finished encoder state with errors
INFO: catalog upload error - channel closed 
INFO: Error: error:0A0003FC:SSL routines:ssl3_read_bytes:ssl/tls alert bad record mac:../ssl/record/rec_layer_s3.c:916:SSL alert number 20
INFO: cleanup temporary 'vzdump' snapshot
ERROR: Backup of VM 111 failed - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client backup '--crypt-mode=none' pct.conf:/var/tmp/vzdumptmp3550466_111/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --include-dev /mnt/vzsnap0/./opt/nextcloud/data --skip-lost-and-found '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' --backup-type ct --backup-id 111 --backup-time 1770066685 --entries-max 1048576 --repository svc-backup@pbs@192.168.178.9:dsn-computing-infra' failed: exit code 255
...
I tried multiple traffic ratelimiting options (PBS incoming) which do not seam to work. Also, it gets interrupted at various times. Sometimes it stops at around an hour, sometimes at two or three hours. Sometimes after 50GB, sometimes after 100 or 300 GB.
The LXC has around 650GB in total.

Also, sometimes - not always, I have no idea when or why this occurs - the PBS dies during this specific backup and I need to reboot via hardware power off and on.

Could somebody give me a hint, where to look at this?
 
Last edited:
Thanks for the hints.
  • Is there a proxmox tool for memory testing? Or just take a debian tool?
  • I will take a look for the firmware bug (unlikely, I don't think that this is a e1000 card. - I will take a look)
  • A fritzbox is in between. Both hosts have the standard MTU of 1500 configured
 
  • The PVE installer ISO has one included
  • ls -l /sys/class/net/*/device/driver will show the driver(s)
 
@Lithilion

I haven't used it myself, but there is a way to blacklist (mask) bad memory ranges:

https://www.memtest86.com/blacklist-ram-badram-badmemorylist.html

In Linux:

" Linux BadRAM

Most newer Linux kernels (eg. Ubuntu 12.04 or newer) support BadRAM, which allow a blacklist of memory address & mask patterns to be passed in as a GRUB2 boot-time parameter. This work-around makes it possible for Linux to reliably run with defective RAM. For history and background information on the original BadRAM project by Rick van Rein, see the following page: http://rick.vanrein.org/linux/badram/


How to blacklist RAM regions​


MemTest86 Pro (v9 or later) supports automatic generation of BadRAM string patterns from detected errors in the HTML report, that can be used directly in the GRUB2 configuration without needing to manually calculate address/mask values by hand.


To enter the address ranges to blacklist manually, do the following:


  1. Edit /etc/default/grub and add the following line:

    GRUB_BADRAM=addr,mask[,addr,mask...]
    where the list of addr,mask pairs specify the memory range to block using address bit matching
    Eg. GRUB_BADRAM=0x7ddf0000,0xffffc000 shall exclude the memory range 0x7DDF0000-0x7DDF4000
  2. Open and terminal and run the following command
    sudo update-grub
  3. Reboot the system

How to view blacklisted RAM regions​


To view the memory regions that have been blacklisted, do the following:


  1. Open and terminal and run the following command
    sudo cat /proc/iomem


    ...<br> 7ddf0000-7ddf3fff : RAM buffer<br> ...<br>


    Memory ranges blacklisted by BadRAM are marked as RAM buffer"
 
  • Like
Reactions: Johannes S