Hey, welcome to the forum!
I’m sorry that restic does not work for you, but it looks like there’s a hardware fault. What restic tells you is that the data written to the external hard drive was modified, so the signature does not match. Restic encrypts and signs all data it writes, and the signature is checked before it uses any data read from the repository.
You can try to find out what’s going on by running
restic check --read-data, which will read and verify all the data stored on the external hard drive. I suspect you will see the same (or similar) errors, but it may help us to pin down the issue.
The issue could have happened on different levels:
- The data was modified in memory while restic was running during backup
- The data was modified in memory before writing it to the disk by the file system
- The harddrive is faulty, the data read back is not the same as the data written to it
- The data was modified in memory after reading it from the hard disk
I think it’s likely that either the memory in your machine or the harddrive used to store the data is faulty. I’m sorry if that’s not what you wanted to hear, but these kinds of problems were detected by restic several times in the past already.
I’d do two things:
memtest on the machine for several hours
sha256sum on the files in the restic repo, the file name for the files must match the output of
sha256sum. If it does not match, it’s likely an issue with the hard disk
restic check --read-data so we can get an idea on which layer the corruption has happened.
Good luck! And please report back if you have any results