Open benjamin051000 opened 1 year ago
Please let me know if I need to transfer this issue to restic, too. I really want to get to the bottom of this.
I don't know what changed, but I deleted everything, started over, and now I'm able to open the repo downloaded from backblaze. I wonder what the issue may have been...
Just updating: I still get this issue spontaneously :(
Hi, in a previous versions there was a bug when starting more then one service in a compose file. Both services tried to init the repo. Maybe this could be the reason for the first issue. Since there is no start time in the log it's a little bit complicated to debug.
Regarding your second issue with the B2 bucket.... I'm not an B2 expert. But why do you download a snapshot? Are you sure you downloading the complete repo? Since restic uses incremental backup you need to download all files in the bucket. Could you create a extra "restore" container and mount this to your B2 bucket on the source side and to a restore volume on the other side. And try to restore some files?
Here's my setup:
Backup task logs:
Check logs:
I see the restic repo folder in my Backblaze bucket.
So, I created a snapshot (which is how you download files from backblaze), and downloaded/extracted it. Here's what I see:
I am not sure what to do. I have already tried deleting the repo from the cloud and restarting the resticker containers to rebuild the repo from scratch. Both times I get this exact error and am unable to open the vault. I know the password I'm entering is correct because the error changes when I enter something wrong.
I also am not sure this is a drive issue since the check job states no errors. Does the check job run locally, though? Or does it run on the files in the cloud? That may affect my opinion about it being a drive issue.
Any help would be greatly appreciated, thanks!