Fehler beim erstellen von Backups / 400 Bad Request: detected chunk with wrong digest.

LevantinLynx

New Member
Jun 1, 2024
9
4
3
Germany
Hallo zusammen,

ich verzweifle seit zei Tagen daran, dass meine Media LXC beim Backup random Fehler werfen. Es ist immer ein chunk with wrong digest Error.
Zuvor lief dasselbe System gute 9 Monate ohne Probleme. (Keine Hardware Änderungen vorgenommen)

Im Forum habe ich ein paar andere Beiträge gefunden, deren Vorschläge leider nicht zu einer Lösung führten...

Bereits getestet:
  • Memtest86+ laufen lassen (Alle Tests auf den vollen Speicherbereich): 10h > 7 Pass 0 Error
  • Da es DDR5 ist, 1x Memory retraining > keine Veränderung
  • Alle Disks gescheckt
    - 4x 1TB WD RED NAS SSD (2.5") > keine Fehler im SMART Bereich (Media Storage)
    - 2x 4TB WD RED NAS HDD (3.5") > keine Fehler im SMART Bereich (Backup Storage)
    - Prüfung aller ZFS Pools mit scrubs 0 Fehler
    - SATA Kabel geprüft und neu gesteckt
  • "apt install --reinstall locales" keine Veränderung

Logs im ProxMox Host
Code:
Aug 22 13:41:16 prox2 pvedaemon[1832]: <root@pam> end task UPID:prox2:00005862:0003AB9F:66C721BC:vzdump::root@pam: job errors
Aug 22 13:41:16 prox2 pvedaemon[22626]: job errors
Aug 22 13:41:15 prox2 pvedaemon[22626]: INFO: Backup job finished with errors
Aug 22 13:41:15 prox2 pvedaemon[22626]: ERROR: Backup of VM 233 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/vzdumptmp22626_233/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' --backup-type ct --backup-id 233 --backup-time 1724326854 --entries-max 1048576 --repository root@pam@pbs.REDACTED:backup_hdd_striped --ns MiniProx' failed: exit code 255
Aug 22 13:40:54 prox2 pvedaemon[22626]: INFO: Starting Backup of VM 233 (lxc)
Aug 22 13:40:54 prox2 pvedaemon[22626]: ERROR: Backup of VM 232 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/vzdumptmp22626_232/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' --backup-type ct --backup-id 232 --backup-time 1724326573 --entries-max 1048576 --repository root@pam@pbs.REDACTED:backup_hdd_striped --ns MiniProx' failed: exit code 255
Aug 22 13:38:22 prox2 kernel: perf: interrupt took too long (3168 > 3147), lowering kernel.perf_event_max_sample_rate to 63000
Aug 22 13:36:13 prox2 pvedaemon[22626]: INFO: Starting Backup of VM 232 (lxc)
Aug 22 13:36:13 prox2 pvedaemon[22626]: ERROR: Backup of VM 231 failed - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:999 -m g:1000:104:1 -m g:1001:101001:64535 -- /usr/bin/proxmox-backup-client backup '--crypt-mode=none' pct.conf:/var/tmp/vzdumptmp22626_231/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' --backup-type ct --backup-id 231 --backup-time 1724326332 --entries-max 1048576 --repository root@pam@pbs.REDACTED:backup_hdd_striped --ns MiniProx' failed: exit code 255
Aug 22 13:32:49 prox2 pvedaemon[1831]: <root@pam> successful auth for user 'root@pam'
Aug 22 13:32:12 prox2 pvedaemon[22626]: INFO: Starting Backup of VM 231 (lxc)
Aug 22 13:32:12 prox2 pvedaemon[22626]: INFO: starting new backup job: vzdump 232 233 231 --all 0 --notes-template '{{guestname}}_{{vmid}}_{{node}}' --notification-mode notification-system --fleecing 0 --mode snapshot --node prox2 --storage zz_backup_pool
Aug 22 13:32:12 prox2 pvedaemon[1832]: <root@pam> starting task UPID:prox2:00005862:0003AB9F:66C721BC:vzdump::root@pam:

Falls jemand ncoh Ideen hat, was ich noch testen kann, bin für jeden Vorschlag dankbar.

Logs im PBS
Code:
Aug 22 13:41:15 pbs proxmox-backup-proxy[1172]: removing unfinished backup
Aug 22 13:41:15 pbs proxmox-backup-proxy[1172]: backup ended and finish failed: backup ended but finished flag is not set.
Aug 22 13:41:15 pbs proxmox-backup-proxy[1172]: POST /dynamic_chunk: 400 Bad Request: detected chunk with wrong digest.
Aug 22 13:41:15 pbs proxmox-backup-proxy[1172]: POST /dynamic_chunk
Aug 22 13:41:15 pbs proxmox-backup-proxy[1172]: upload_chunk done: 1651393 bytes, 151f0b27abbfe4c08939fd6aa1643017e7fbcda19e91685e7287bca682b9b572
Aug 22 13:41:15 pbs proxmox-backup-proxy[1172]: POST /dynamic_chunk
 
Ja, schedule ist auf jeden Sonntag mit 30 Tage reverify eingestellt. Lasse es gerade auch laufen, kurz nach dem Post kam mir die Idee das mal manuell zu starten, da diesen Sonntag nichts lief. (Server war wegen bauarbeiten der Stadt am Stromnetz aus)
 
  • Like
Reactions: fireon
Ja, schedule ist auf jeden Sonntag mit 30 Tage reverify eingestellt. Lasse es gerade auch laufen, kurz nach dem Post kam mir die Idee das mal manuell zu starten, da diesen Sonntag nichts lief. (Server war wegen bauarbeiten der Stadt am Stromnetz aus)
Manueller verify lief durch ohne Fehler.

Bin nicht sicher, was active full backup ist? Habe nicht genug Platz um das in einem eigenen Namespace nochmal abzulegen. Müsste die original Backups löschen.
 
Last edited:
Wenn du einen neuen Namespace anlegst, werden die Daten trotzdem gededupt gespeichert. AAuch wenn er eine neue Backupkette anlegt.
 
Wenn du einen neuen Namespace anlegst, werden die Daten trotzdem gededupt gespeichert. AAuch wenn er eine neue Backupkette anlegt.

Guter Hinweis, so genau hatte ich mir die Docu des PBS in dem Bezug noch nicht angeschaut :P

Dann lösche ich mal alle Backups und versuche es einmal manuell.
 
So, alles gelöscht, Backup neu gemacht. Selber Fehler...
Habe den PBS komplett neu aufgesetzt. Fehler bleibt unverändert.

1724628293604.png
 
Last edited:
Bekommst du überhaupt ein Backup hin mit einem defekten Block oder bricht er komplett ab?
Ich befürchte deine Quelldisk hat da einen fehler. In der Regel wird empfohlen die Daten in der VM zu sichern und einmal Restore der VM durchführen.
 
Hmmm... Quelldisk sind 4x 1TB WD Red SDD 2.5" im raidz1.
Alle disks haben keine Fehler im SMART report und Scrubs sagen auch, dass alles ok ist.

Werde mal eine Disk organisieren und per USB anstecken und ein backup ohne PBS durchführen.

Zu deiner Frage: Backups berechen sofort ab. Nach dem Bad Chunk digest Error ist ende. Zumindest für die VM/LXC, er wird dann mit der nächsten weiter gemacht.
Mich wundert halt, dass alle anderen Backups kein Problem geben, nur die 3 Container. In allen VM und LXC läuft ausschließlich Debian 12. Auf 231 läuft Jellyfin, 232 Audiobookshelf und 233 Navidrome. Bei den Medien Daten gibt es keine Überschneidung.
 
Last edited:
So nach einem Bios reset auf defult values und installation von intel-microcode erhalte ich nun auch im syslog schöne Fehler.
Es wird ein exploit vemutet und dann crashed was. Der Host ist dann auch nach kurzer Zeit komplett unresponsive und ein hard reset ist nötig.


Code:
2024-08-26T07:00:36.297936+02:00 prox2 pvedaemon[10095]: INFO: starting new backup job: vzdump 232 233 231 --node prox2 --storage z_backup_default --fleecing 0 --notes-template '{{guestname}}_{{vmid}}_{{node}}' --notification-mode notification-system --mode snapshot --all 0
2024-08-26T07:00:36.298905+02:00 prox2 pvedaemon[10095]: INFO: Starting Backup of VM 231 (lxc)
2024-08-26T07:04:02.059143+02:00 prox2 kernel: [ 1144.128833] kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
2024-08-26T07:04:02.059157+02:00 prox2 kernel: [ 1144.130160] BUG: unable to handle page fault for address: ffffa74400173e60
2024-08-26T07:04:02.059158+02:00 prox2 kernel: [ 1144.131588] #PF: supervisor instruction fetch in kernel mode
2024-08-26T07:04:02.059158+02:00 prox2 kernel: [ 1144.132857] #PF: error_code(0x0011) - permissions violation
2024-08-26T07:04:02.059160+02:00 prox2 kernel: [ 1144.134091] PGD 100000067 P4D 100000067 PUD 10027f067 PMD 100288067 PTE 8000000100d74163
2024-08-26T07:04:02.059161+02:00 prox2 kernel: [ 1144.135261] Oops: 0011 [#1] PREEMPT SMP NOPTI
2024-08-26T07:04:02.059161+02:00 prox2 kernel: [ 1144.136293] CPU: 3 PID: 17 Comm: rcu_preempt Tainted: P        W  O       6.8.12-1-pve #1
2024-08-26T07:04:02.059161+02:00 prox2 kernel: [ 1144.137307] Hardware name: Default string Default string/Default string, BIOS 5.27 03/04/2024
2024-08-26T07:04:02.059161+02:00 prox2 kernel: [ 1144.138482] RIP: 0010:0xffffa74400173e60
2024-08-26T07:04:02.059162+02:00 prox2 kernel: [ 1144.139685] Code: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff 60 3e 17 00 44 a7 ff ff 10 00 00 00 00 00 00 00 46 02 01 00 00 00 00 00 <70> 3e 17 00 44 a7 ff ff 18 00 00 00 00 00 00 00 00 3b be dd 5a 98
2024-08-26T07:04:02.059163+02:00 prox2 kernel: [ 1144.140907] RSP: 0018:ffffa74400173e70 EFLAGS: 00010246
2024-08-26T07:04:02.059164+02:00 prox2 kernel: [ 1144.142060] RAX: 0000000000000000 RBX: ffffa74400173ea0 RCX: 0000000000000000
2024-08-26T07:04:02.059164+02:00 prox2 kernel: [ 1144.143224] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
2024-08-26T07:04:02.059165+02:00 prox2 kernel: [ 1144.144301] RBP: ffffa74400173e60 R08: 0000000000000000 R09: 0000000000000000
2024-08-26T07:04:02.059165+02:00 prox2 kernel: [ 1144.145355] R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff971b2a4a
2024-08-26T07:04:02.059166+02:00 prox2 kernel: [ 1144.146634] R13: 0000000000000000 R14: ffff8b3500d42900 R15: ffff8b3500d42900
2024-08-26T07:04:02.059166+02:00 prox2 kernel: [ 1144.147875] FS:  0000000000000000(0000) GS:ffff8b3c5f980000(0000) knlGS:0000000000000000
2024-08-26T07:04:02.059166+02:00 prox2 kernel: [ 1144.149064] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
2024-08-26T07:04:02.059167+02:00 prox2 kernel: [ 1144.150203] CR2: ffffa74400173e60 CR3: 0000000770234005 CR4: 0000000000f72ef0
2024-08-26T07:04:02.059167+02:00 prox2 kernel: [ 1144.151317] PKRU: 55555554
2024-08-26T07:04:02.059168+02:00 prox2 kernel: [ 1144.152362] Call Trace:
2024-08-26T07:04:02.059168+02:00 prox2 kernel: [ 1144.153650]  <TASK>
2024-08-26T07:04:02.059169+02:00 prox2 kernel: [ 1144.154899]  ? show_regs+0x6d/0x80
2024-08-26T07:04:02.059169+02:00 prox2 kernel: [ 1144.156093]  ? __die+0x24/0x80
2024-08-26T07:04:02.059170+02:00 prox2 kernel: [ 1144.157228]  ? page_fault_oops+0x176/0x4f0
2024-08-26T07:04:02.059170+02:00 prox2 kernel: [ 1144.158321]  ? search_bpf_extables+0x60/0x90
2024-08-26T07:04:02.059170+02:00 prox2 kernel: [ 1144.159337]  ? kernelmode_fixup_or_oops.constprop.0+0x69/0x90
2024-08-26T07:04:02.059171+02:00 prox2 kernel: [ 1144.160466]  ? __bad_area_nosemaphore+0x19d/0x270
2024-08-26T07:04:02.059171+02:00 prox2 kernel: [ 1144.161682]  ? bad_area_nosemaphore+0x16/0x30
2024-08-26T07:04:02.059171+02:00 prox2 kernel: [ 1144.162928]  ? do_kern_addr_fault+0x7b/0xa0
2024-08-26T07:04:02.059172+02:00 prox2 kernel: [ 1144.164086]  ? exc_page_fault+0x10d/0x1b0
2024-08-26T07:04:02.059172+02:00 prox2 kernel: [ 1144.165170]  ? asm_exc_page_fault+0x27/0x30
2024-08-26T07:04:02.059172+02:00 prox2 kernel: [ 1144.166214]  ? rcu_gp_fqs_loop+0x37a/0x550
2024-08-26T07:04:02.059173+02:00 prox2 kernel: [ 1144.167197]  ? __pfx_rcu_gp_kthread+0x10/0x10
2024-08-26T07:04:02.059173+02:00 prox2 kernel: [ 1144.168444]  ? rcu_gp_kthread+0xe8/0x190
2024-08-26T07:04:02.059173+02:00 prox2 kernel: [ 1144.169659]  ? kthread+0xef/0x120
2024-08-26T07:04:02.059174+02:00 prox2 kernel: [ 1144.170885]  ? __pfx_kthread+0x10/0x10
2024-08-26T07:04:02.059174+02:00 prox2 kernel: [ 1144.171986]  ? ret_from_fork+0x44/0x70
2024-08-26T07:04:02.059174+02:00 prox2 kernel: [ 1144.173060]  ? __pfx_kthread+0x10/0x10
2024-08-26T07:04:02.059175+02:00 prox2 kernel: [ 1144.174094]  ? ret_from_fork_asm+0x1b/0x30
2024-08-26T07:04:02.059175+02:00 prox2 kernel: [ 1144.175073]  </TASK>
2024-08-26T07:04:02.059176+02:00 prox2 kernel: [ 1144.176329] Modules linked in: cfg80211 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat veth ebtable_filter ebtables ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter input_leds nf_tables sunrpc binfmt_misc bonding tls nfnetlink_log nfnetlink snd_sof_pci_intel_tgl snd_sof_intel_hda_common intel_rapl_msr intel_rapl_common xe snd_hda_codec_hdmi soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci drm_gpuvm snd_sof_xtensa_dsp drm_exec gpu_sched snd_sof drm_suballoc_helper x86_pkg_temp_thermal snd_hda_codec_realtek drm_ttm_helper intel_powerclamp snd_sof_utils snd_hda_codec_generic snd_soc_hdac_hda snd_hda_ext_core kvm_intel snd_soc_acpi_intel_match snd_soc_acpi soundwire_generic_allocation soundwire_bus kvm snd_soc_core snd_compress ac97_bus irqbypass snd_pcm_dmaengine crct10dif_pclmul polyval_clmulni polyval_generic
2024-08-26T07:04:02.059180+02:00 prox2 kernel: [ 1144.176391]  ghash_clmulni_intel snd_hda_intel sha256_ssse3 snd_intel_dspcfg sha1_ssse3 snd_intel_sdw_acpi mei_hdcp mei_pxp aesni_intel snd_hda_codec crypto_simd cryptd snd_hda_core i915 snd_hwdep cmdlinepart snd_pcm snd_timer rapl spi_nor drm_buddy wmi_bmof snd ttm intel_cstate pcspkr mtd soundcore drm_display_helper intel_pmc_core cec mei_me intel_vsec rc_core mei i2c_algo_bit pmt_telemetry igen6_edac pmt_class acpi_pad acpi_tad mac_hid vhost_net vhost vhost_iotlb tap coretemp efi_pstore dmi_sysfs ip_tables x_tables autofs4 zfs(PO) spl(O) hid_generic usbkbd btrfs usbhid hid blake2b_generic xor raid6_pq libcrc32c xhci_pci crc32_pclmul nvme xhci_pci_renesas spi_intel_pci spi_intel nvme_core ahci i2c_i801 xhci_hcd igc nvme_auth i2c_smbus libahci video wmi
2024-08-26T07:04:02.059180+02:00 prox2 kernel: [ 1144.187297] CR2: ffffa74400173e60
2024-08-26T07:04:02.059181+02:00 prox2 kernel: [ 1144.188502] ---[ end trace 0000000000000000 ]---
2024-08-26T07:04:02.059181+02:00 prox2 kernel: [ 1144.294833] RIP: 0010:0xffffa74400173e60
2024-08-26T07:04:02.059181+02:00 prox2 kernel: [ 1144.296371] Code: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff 60 3e 17 00 44 a7 ff ff 10 00 00 00 00 00 00 00 46 02 01 00 00 00 00 00 <70> 3e 17 00 44 a7 ff ff 18 00 00 00 00 00 00 00 00 3b be dd 5a 98
2024-08-26T07:04:02.059182+02:00 prox2 kernel: [ 1144.297883] RSP: 0018:ffffa74400173e70 EFLAGS: 00010246
2024-08-26T07:04:02.059182+02:00 prox2 kernel: [ 1144.299256] RAX: 0000000000000000 RBX: ffffa74400173ea0 RCX: 0000000000000000
2024-08-26T07:04:02.059182+02:00 prox2 kernel: [ 1144.300524] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
2024-08-26T07:04:02.059183+02:00 prox2 kernel: [ 1144.301654] RBP: ffffa74400173e60 R08: 0000000000000000 R09: 0000000000000000
2024-08-26T07:04:02.059183+02:00 prox2 kernel: [ 1144.302766] R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff971b2a4a
2024-08-26T07:04:02.059184+02:00 prox2 kernel: [ 1144.303870] R13: 0000000000000000 R14: ffff8b3500d42900 R15: ffff8b3500d42900
2024-08-26T07:04:02.059184+02:00 prox2 kernel: [ 1144.305023] FS:  0000000000000000(0000) GS:ffff8b3c5f980000(0000) knlGS:0000000000000000
2024-08-26T07:04:02.059184+02:00 prox2 kernel: [ 1144.306370] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
2024-08-26T07:04:02.059185+02:00 prox2 kernel: [ 1144.307671] CR2: ffffa74400173e60 CR3: 00000001a37fe004 CR4: 0000000000f72ef0
2024-08-26T07:04:02.059185+02:00 prox2 kernel: [ 1144.308837] PKRU: 55555554
2024-08-26T07:04:02.059185+02:00 prox2 kernel: [ 1144.310025] note: rcu_preempt[17] exited with irqs disabled
2024-08-26T07:06:34.123931+02:00 prox2 pvedaemon[10095]: ERROR: Backup of VM 231 failed - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:999 -m g:1000:104:1 -m g:1001:101001:64535 -- /usr/bin/proxmox-backup-client backup '--crypt-mode=none' pct.conf:/var/tmp/vzdumptmp10095_231/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' --backup-type ct --backup-id 231 --backup-time 1724648436 --entries-max 1048576 --repository root@pam@pbs.REDACTED:backup_hdd_striped --ns default' failed: exit code 255
2024-08-26T07:06:34.124373+02:00 prox2 pvedaemon[10095]: INFO: Starting Backup of VM 232 (lxc)
2024-08-26T07:06:41.722630+02:00 prox2 pvedaemon[1839]: <root@pam> successful auth for user 'root@pam'
2024-08-26T07:07:19.545168+02:00 prox2 pvedaemon[10095]: ERROR: Backup of VM 232 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/vzdumptmp10095_232/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' --backup-type ct --backup-id 232 --backup-time 1724648794 --entries-max 1048576 --repository root@pam@pbs.REDACTED:backup_hdd_striped --ns default' failed: exit code 255
2024-08-26T07:07:19.545513+02:00 prox2 pvedaemon[10095]: INFO: Starting Backup of VM 233 (lxc)
2024-08-26T07:07:32.961919+02:00 prox2 pvedaemon[1838]: <root@pam> starting task UPID:prox2:000036EB:0002114D:66CC0D94:vncproxy:10012:root@pam:
2024-08-26T07:07:32.962245+02:00 prox2 pvedaemon[14059]: starting vnc proxy UPID:prox2:000036EB:0002114D:66CC0D94:vncproxy:10012:root@pam:
2024-08-26T07:07:36.514034+02:00 prox2 pvedaemon[1838]: <root@pam> end task UPID:prox2:000036EB:0002114D:66CC0D94:vncproxy:10012:root@pam: OK
2024-08-26T07:07:57.639303+02:00 prox2 pvedaemon[10095]: ERROR: Backup of VM 233 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/vzdumptmp10095_233/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' --backup-type ct --backup-id 233 --backup-time 1724648839 --entries-max 1048576 --repository root@pam@pbs.REDACTED:backup_hdd_striped --ns default' failed: exit code 255
2024-08-26T07:07:57.639408+02:00 prox2 pvedaemon[10095]: INFO: Backup job finished with errors
2024-08-26T07:07:57.836999+02:00 prox2 pvedaemon[10095]: job errors
2024-08-26T07:07:57.848829+02:00 prox2 pvedaemon[1838]: <root@pam> end task UPID:prox2:0000276F:00016E7E:66CC0BF4:vzdump::root@pam: job errors
 
Fehler ist aber nicht reproduzierbar... im zwieten Anlauf kommt wieder nur dasselbe wie im ursprünglichen Fehler Post.

Code:
2024-08-26T07:29:34.148159+02:00 prox2 pvedaemon[1835]: <root@pam> starting task UPID:prox2:00002183:0001819F:66CC12BE:vzdump::root@pam:
2024-08-26T07:29:34.260774+02:00 prox2 pvedaemon[8579]: INFO: starting new backup job: vzdump 232 233 231 --node prox2 --notes-template '{{guestname}}_{{vmid}}_{{node}}' --storage z_backup_default --mode snapshot --fleecing 0 --notification-mode notification-system --all 0
2024-08-26T07:29:34.261691+02:00 prox2 pvedaemon[8579]: INFO: Starting Backup of VM 231 (lxc)
2024-08-26T07:34:08.655415+02:00 prox2 pvedaemon[8579]: ERROR: Backup of VM 231 failed - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:999 -m g:1000:104:1 -m g:1001:101001:64535 -- /usr/bin/proxmox-backup-client backup '--crypt-mode=none' pct.conf:/var/tmp/vzdumptmp8579_231/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' --backup-type ct --backup-id 231 --backup-time 1724650174 --entries-max 1048576 --repository root@pam@pbs.REDACTED:backup_hdd_striped --ns default' failed: exit code 255
2024-08-26T07:34:08.655955+02:00 prox2 pvedaemon[8579]: INFO: Starting Backup of VM 232 (lxc)
2024-08-26T07:36:36.177670+02:00 prox2 pvedaemon[8579]: ERROR: Backup of VM 232 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/vzdumptmp8579_232/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' --backup-type ct --backup-id 232 --backup-time 1724650448 --entries-max 1048576 --repository root@pam@pbs.REDACTED:backup_hdd_striped --ns default' failed: exit code 255
2024-08-26T07:36:36.177995+02:00 prox2 pvedaemon[8579]: INFO: Starting Backup of VM 233 (lxc)
2024-08-26T07:37:01.606515+02:00 prox2 pvedaemon[8579]: ERROR: Backup of VM 233 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/vzdumptmp8579_233/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' --backup-type ct --backup-id 233 --backup-time 1724650596 --entries-max 1048576 --repository root@pam@pbs.REDACTED:backup_hdd_striped --ns default' failed: exit code 255
2024-08-26T07:37:01.606634+02:00 prox2 pvedaemon[8579]: INFO: Backup job finished with errors
2024-08-26T07:37:01.729011+02:00 prox2 pvedaemon[8579]: job errors
2024-08-26T07:37:01.740980+02:00 prox2 pvedaemon[1835]: <root@pam> end task UPID:prox2:00002183:0001819F:66CC12BE:vzdump::root@pam: job errors
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!