TW

Not sure why you do the `cat` - your dedupper will read the whole file anyway, right? Also, it is not a very realistic scenario.

OK. Maybe we should get back to the general topic of **borgbackup**. :-) So, after all the research you did, did you find anything in borg missing or wrong (besides...

@safinaskar That post has some issues and is not true as it is now. https://borgbackup.readthedocs.io/en/stable/usage/init.html?highlight=blake2 there it talks quite a bit about speed of hash algos, so it is documented...

@safinaskar borg2 has `borg benchmark cpu`, where every user can easily find out what's fastest on a specific machine (on bare hw or in a VM). That made a lot...

That's not a `borg mount` problem, but your repo files are corrupted. First check if hardware / OS works correctly, then you can try `borg check --repair`.

Yes, running without `--repair` will mostly only show what it finds. But as I said, first fix hw/OS or it might get worse.

Maybe in this order: You can use `memtest86+` on a USB stick and check your RAM. Run at least 1 full pass. `smartctl -a /dev/sdX` and `smartctl -t long /dev/sdX`...

RAM errors can have pretty bad consequences. OTOH, the N40L supports ECC memory (and by default also came with ECC memory), so the memory system should have a decent quality....

Guess `borg mount` (like most borg command) expects a consistent/undamaged borg repo. Hopefully your hardware works ok now, otherwise that borg check run might not work well (and `--repair` could...

@noppel If you could make it a habit to always use `borg mount -f ...` in another terminal, you could maybe get a traceback some time and the issue could...