Skip to content
Discussion options

You must be logged in to vote

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.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@ovizii
Comment options

Answer selected by ovizii
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants