Hello,
I’m getting a “FATAL Chunk d6628df5ad05f46e3f80e478d634c376a1bf9b2c9c3445336ae6ecb55f496c05 can’t be found” error.
I went through Prune operation returned an error, FATAL: chunk xxxx can't be found and Fix missing chunks. I couldn’t find the chunk being deleted in the prune logs, and the chunk doesn’t exist on the storage (GDrive). I tried prune -exhaustive -exclusive, but same error. I also went through and deleted every snapshot in the snapshot folder, and that didn’t fix the issue either. I also tried changing the id in the preferences to something new and running a backup/prune, and still received the error.
So after you empty the snapshots folder on GDrive and run a backup and it still gives you the error?
Correct. Emptied the snapshots folder. Re-ran the backup:
2019-03-15 11:41:26.874 INFO BACKUP_END Backup for P:\ at revision 1 completed
2019-03-15 11:41:26.877 INFO BACKUP_STATS Files: 55799 total, 353,043M bytes; 55799 new, 353,043M bytes
2019-03-15 11:41:26.877 INFO BACKUP_STATS File chunks: 71766 total, 353,043M bytes; 0 new, 0 bytes, 0 bytes uploaded
2019-03-15 11:41:26.877 INFO BACKUP_STATS Metadata chunks: 6 total, 18,762K bytes; 0 new, 0 bytes, 0 bytes uploaded
2019-03-15 11:41:26.877 INFO BACKUP_STATS All chunks: 71772 total, 353,061M bytes; 0 new, 0 bytes, 0 bytes uploaded
2019-03-15 11:41:26.877 INFO BACKUP_STATS Total running time: 01:25:16
2019-03-15 11:41:27.961 INFO STORAGE_SET Storage set to gcd://Backups
2019-03-15 11:41:30.590 INFO SNAPSHOT_CHECK Listing all chunks
2019-03-15 11:45:47.098 INFO SNAPSHOT_CHECK 1 snapshots and 1 revisions
2019-03-15 11:45:47.102 INFO SNAPSHOT_CHECK Total chunk size is 350,379M in 73422 chunks
2019-03-15 11:45:47.780 INFO SNAPSHOT_CHECK All chunks referenced by snapshot MediaServer-Pool at revision 1 exist
2019-03-15 11:45:48.331 INFO STORAGE_SET Storage set to gcd://Backups
2019-03-15 11:45:52.229 INFO RETENTION_POLICY Keep no snapshots older than 9999999 days
2019-03-15 11:45:52.229 INFO RETENTION_POLICY Keep 1 snapshot every 7 day(s) if older than 30 day(s)
2019-03-15 11:46:02.737 INFO SNAPSHOT_NONE No snapshot to delete
Snapshot 1 was created in GDrive. Ran prune and got the same error:
PS P:> .\duplicacy_win_x64_2.1.2.exe prune -exhaustive -exclusive -a -keep 0:9999999 -keep 7:30 -keep 30:30
Storage set to gcd://Backups
Keep no snapshots older than 9999999 days
Keep 1 snapshot every 7 day(s) if older than 30 day(s)
Chunk 955540093891f41ce1d6384dd5b77143318b5907a1d3c4cd2253d59e70364ce5 can’t be found
A check:
PS P:> .\duplicacy_win_x64_2.1.2.exe check -a
Storage set to gcd://Backups
Listing all chunks
2 snapshots and 35 revisions
Total chunk size is 350,379M in 73422 chunks
All chunks referenced by snapshot MediaServer-Pool at revision 1 exist
Chunk 955540093891f41ce1d6384dd5b77143318b5907a1d3c4cd2253d59e70364ce5 can’t be found
What’s odd is when I run check -a from the other repo (C drive vs P drive) on the same machine I don’t get the same error:
PS C:> .\duplicacy_win_x64_2.1.2.exe check -a
Storage set to gcd://Backups
Listing all chunks
2 snapshots and 35 revisions
Total chunk size is 350,379M in 73422 chunks
All chunks referenced by snapshot MediaServer-Pool at revision 1 exist
All chunks referenced by snapshot MediaServer - C at revision 1 exist
All chunks referenced by snapshot MediaServer - C at revision 3 exist
All chunks referenced by snapshot MediaServer - C at revision 10 exist
This is likely caused by a discrepancy between the local cache and the storage. For instance, if you create the first backup at revision 1 from repository A, delete the snapshot file (revision 1) from the storage, and then run the backup again from repository B (with the same repository id), then the snapshot file in the cache under repository A would be different from the one in the storage.
To fix it, remove everything in the local cache (i.e., the .duplicacy/cache directory under the repository A).
1 Like
Sure enough; fixed. Thank you. Appreciate it.
1 Like