Intermittent "Connection error" when trying to do file level restore

Oct 9, 2025
3
0
1
New installation of PBS 4.0.14 connected to PX 8.4.14, backups run and complete successfully, but when I try to do 'File Level Restore' about 75% of the time I can't drill down into an actual partition without getting a pop up that just says 'Connection error'. Not sure what to do about it, anyone experienced this?

1760025568216.png

Thanks,
Matt H
 
Hi,
please post the output of /var/log/proxmox-backup/file-restore/qemu.log after a failed file restore and the systemd journal from around that time journalctl --since <DATETIME> --until <DATETIME> > journal.log, both gathered from the PVE host.
 
Hi,
please post the output of /var/log/proxmox-backup/file-restore/qemu.log after a failed file restore and the systemd journal from around that time journalctl --since <DATETIME> --until <DATETIME> > journal.log, both gathered from the PVE host.
Thanks Chris, I've attached them both here. FWIW, the journalctl output references a missing chunk (/mnt/dd04/.chunks/0c94/0c941ae1160a30872af57ac18dbae2a5b413c9450f8f50f6a87dee22abf3cf6d), I checked on the PBS and the /mnt/dd04/.chunks/0c94/ folder is empty.

Let me know what you think I should do, thanks!
 

Attachments

Verify your snapshots, seems like you have at least 3 missing/corrupt chunks!
 
If you still have the VM, you can try to back the VM up again (after making sure the last backup snapshot in the group failed verification, so the dirty bitmap is cleared). In case the original data is still there, the chunks will be uploaded again, which can "heal" snapshots which reference the same previously corrupt chunks.
If that does not work, then your snapshots are corrupt and you will have some data loss. You can nevertheless try to recover the raw image by running proxmox-backup-debug recover index <file> <chunks> --ignore-corrupt-chunks=true --ignore-missing-chunks=true --output-path=<path-to-target-image-file> on the PBS, <file> being the path to the index file (ending in .fidx in the respective snapshot folder) and <chunks> is the path to the chunk store base directory, so <datastore>/.chunks.

Above steps assume you are using a regular datastore, these will not work on an S3 backed datastore, there you will have to fetch the whole datastore contents from S3 by some external tooling first.