TW
Yes, maybe use `rsync -avH --delete` (be careful) so you can restart in case it gets interrupted. After all is synced, you could do another rsync run using their "checksums...
Suspect is all hw between the cpu/ram running "borg serve" and the disk where the repo data is stored on. Better run the check --repair AFTER it is on the...
If you only run borg create, segments should not change, just new segments will be created (with higher numbers). If you run borg compact though, it will compact from old...
That would rather indicate that your hw works in a non-reproducable / unstable way.
Yes. It is also odd that one does not see exactly where it fails. Can you use a completely different machine, make a new copy of the repo and try...
Added the hardware issue label. Not 100% sure yet, but that's my best guess.
The repository part of `borg check` reads all data in the segment files and does a crc32 check for each entry.
Looks like your RAMs have an identity crisis and rather feel like a RNG. :-)
The warning about missing hardlink capability is harmless, borg should also work without that (just a bit less secure in some situations). The traceback below is strange. Likely we have...
Please add the output of `mount` to the top post, so we can see the smbfs/cifs mount options.