Full Snapshot restore fails, Repo Check is OK

[Tumtum2814]

using backrest in docker on unraid. Trying to setup backup. Backup runs ok but testing restore before i fully dive in to keeping restic.

-Testing local first before i setup B2.
-Have run the commands straight from command line as well.

2 common issues pop up, one is a broken pipe. I have tried mounting a blank partition and letting it restore to there, and wiping the files if a restore fails, sometimes fixes the broken pipe problem. but frequently when trying with verbose i get broken pipe

Other main issue is random restore failure code 1 and it will just be a generic, 45 , or 57 errors found.
-I have checked, pruned the repo, no issues.

• Tried using backrest and just a basic restore command from the CLI
• ran restore as dry run (broken pipe)
  Would love any help. Really like backrest, just wanna get it working haha

[ismaildasci]

broken pipe during restore usually means connection dropped or disk IO issue.

few things to check:

1. check disk space:
   make sure destination has enough space for full restore

2. try with smaller subset first:

restic restore latest --target /mnt/restore --include /path/to/small/folder

3. increase timeouts:
   if using backrest UI, check if theres timeout setting. for CLI:

restic restore latest --target /mnt/restore -o timeout=0

4. check restic cache:

restic cache --cleanup
restic cache --max-age 0

5. run check with read-data:

restic check --read-data

this verifies actual data integrity, not just metadata

6. try with verbose to see which file fails:

restic restore latest --target /mnt/restore --verbose=2 2>&1 | tee restore.log

7. docker memory limit:
   if running in docker, increase memory limit. restic can be memory hungry during restore

8. unraid specific:
   check if destination is on array or cache drive. array can be slow and cause timeouts

what size is the backup repo? and how many files roughly?