Repository navigation
What to do if a check failed? #1087
|
I remember this happened occasionally and backrest's logs were showing a URL to restic docs on how to fix it, but something must have changed, as the link is no longer visible, see screenshots. Is this simply because the logs seem too long? Any way to see the full logs? Anyway, after some googling, I think this is the link I was looking for: https://restic.readthedocs.io/en/latest/077_troubleshooting.html
|
Replies: 1 comment 1 reply
|
Hmm, try clicking into the logs view to (in the ... menu in the top right) to see the full output for this command which may include more details about the error. It looks like restic was failing to get objects in many cases, this can be caused by a flaky storage backend (which is a common issue with rclone and some providers). Or could be caused by a flaky network. It looks like the check operation eventually passed which means your repo isn't corrupt, but this sort of thing popping up regularly puts you at increased risk of something going wrong when you need things to work (e.g. when running a restore operation), something to keep in mind. |


Hmm, try clicking into the logs view to (in the ... menu in the top right) to see the full output for this command which may include more details about the error.
It looks like restic was failing to get objects in many cases, this can be caused by a flaky storage backend (which is a common issue with rclone and some providers). Or could be caused by a flaky network.
It looks like the check operation eventually passed which means your repo isn't corrupt, but this sort of thing popping up regularly puts you at increased risk of something going wrong when you need things to work (e.g. when running a restore operation), something to keep in mind.