So the nesting level is 1 and this is not the issue.
I do notice that you ran CLI without the -a option (duplicacy -log check), which means it only checks snapshots with the id kevin_salvage1. So there must be another snapshot id that has missing chunks.
Two questions:
snapshots besides kevin_salvage1?Regarding other directories under snapshots: - it looks like no.
I do not see that chunk anywhere in the storage
???
I thought I was on to something but I was wrong… so … the question still is here… why does the CLI say no missing chunks and the gui says missing chunks?
Can I pay for some on-site support from someone? I need to get this resolved asap- seriously. Thanks!!
I also note that this is happening on two completely separate storages I think.
Should I somehow totally uninstall Duplicacy and start over? Maybe there is something messed up from the old gui days??
This chunk should be found under the subdirectory db with the name 537514f0d6d66e4662622438b843cbab8f042f7a4ecaef0e6de78f3d7628cd.
I would suggest running the CLI from the directory ~/.duplicacy-web/bin and checking with the -a option (check -a). Also make sure that the CLI is working with the same storage as the web GUI (in your post it looks like they are not the same (sftp://backups@kv.dns.org:2222//share/hoxdrmes/dataps/KevinV vs sftp://backups@kv.ds.org:2222//share/hXXXXX/ups/KevinV even though I understand the latter is redacted)
This chunk does not exist in the db directory or any directory that I can find…
Will try your next suggestion next.
OK- in the webgui / bin directory there are three execuatables. I ran the latest one with check -a and see this: (No missing chunks)
Salvage1:bin kevinvannorsdel$ ./duplicacy_osx_x64_2.4.1 check -a
Storage set to sftp://backups@kv.redact.org:2222//share/homes/backups/KevinV
Listing all chunks
1 snapshots and 17 revisions
Total chunk size is 328,017M in 85224 chunks
All chunks referenced by snapshot kevin_salvage1 at revision 1 exist
All chunks referenced by snapshot kevin_salvage1 at revision 2 exist
All chunks referenced by snapshot kevin_salvage1 at revision 3 exist
All chunks referenced by snapshot kevin_salvage1 at revision 4 exist
All chunks referenced by snapshot kevin_salvage1 at revision 5 exist
All chunks referenced by snapshot kevin_salvage1 at revision 6 exist
All chunks referenced by snapshot kevin_salvage1 at revision 7 exist
All chunks referenced by snapshot kevin_salvage1 at revision 8 exist
All chunks referenced by snapshot kevin_salvage1 at revision 9 exist
All chunks referenced by snapshot kevin_salvage1 at revision 10 exist
All chunks referenced by snapshot kevin_salvage1 at revision 11 exist
All chunks referenced by snapshot kevin_salvage1 at revision 12 exist
All chunks referenced by snapshot kevin_salvage1 at revision 13 exist
All chunks referenced by snapshot kevin_salvage1 at revision 14 exist
All chunks referenced by snapshot kevin_salvage1 at revision 15 exist
All chunks referenced by snapshot kevin_salvage1 at revision 16 exist
All chunks referenced by snapshot kevin_salvage1 at revision 17 exist
but the GUI check still shows missing…
Can I somehow see the exact command line that the GUI is running?
The server here (kv.redact.org) is different from what you showed earlier (kv.ds.org):
The log you posted already above tells you the directory the check command ran from and the arguments:
So this is what you need to do to replicate the check run:
cd /Users/kevinvsdel/.duplicacy-web/repositories/localhost/all
/Users/kevinvsdel/.duplicacy-web/bin/duplicacy_osx_x64_2.4.1 check -storage storage_timberwolf -a -tabular
Well I guess I am too stupid to figure out what is wrong with this.
I think I am going to try to uninstall everything and start over. I can’t make sense of what is wrong.
I’ll see if I can find a forum entry about how to wipe everything and start over.
So I didn’t find an entry for how best to “start over” with a Mac.
Do I just delete all the .duplicacy* directories, delete the duplicacy app and then re-download and set up again?
Perhaps there is some keychain stuff I should clear out too?
It is not the installation that caused the issue, I think. You’ll just need to initialize a new storage and start backups there.
I have cleared out everything both on the storage server as well as the client - and re-instaled duplicacy and re-set up everything and so far so good. Thanks!