The post on “fixing missing chunks” says:
If you are uninterested in figuring out why the chunk went missing and just want to fix the issue, you can keep removing by hand the affected snapshot files under the snapshots folder in the storage, until the check -a command passes without reporting missing chunks.
So I will try to delete snapshot files in my B2 storage to fix the problem.
The error is:
2020-06-29 12:23:01.113 INFO SNAPSHOT_CHECK All chunks referenced by snapshot DESKTOP-R63ACG7-FC-E at revision 1 exist
2020-06-29 12:23:01.324 FATAL DOWNLOAD_CHUNK Chunk e7b87a8f4d40305923508bf6b2e8e3ab9425f1de9f8cced85bf89e69a3c0dd11 can’t be found
Chunk e7b87a8f4d40305923508bf6b2e8e3ab9425f1de9f8cced85bf89e69a3c0dd11 can’t be found
Question 1: Does this mean that the missing chunk is part of the snapshot “DESKTOP-R63ACG7-FC-E”? Is this the snapshot I should delete? The error message about the missing chunk is on a separate line in the log and doesn’t specifically indicate which snapshot it is related to.
Question 2: In the “(B2 cloud storage)/snapshots/DESKTOP-R63ACG7-FC-E”, all the files have names that are one or two-digit numbers, but file "8 "looks different. It shows a 2 in parenthesis and when clicked, it shows two versions of the file
8 (2) 8K 05/17/2018 00:01
8 4K 05/17/2018 00:01
8 4K 05/17/2018 00:01
Why is this? Is the missing chunk problem related, or is this normal?
Question 3: When I search all the files in my local snapshots cache, the chunk hash is not found inside any of those snapshot files. If the chunk does not show up in any of the snapshots files, then how would deleting snapshot files in the cloud resolve the problem?