How to fix please verify the sha256 hash?

ts678 · March 17, 2024, 10:49am

You’re missing some headers that add context to the output, but it might still be confusing.

If you add –console-log-level=information, it will look a little better, maybe more like below:

Found 33 files that are missing from the remote storage, please run repair

**The operation ListBrokenFiles has started**
**No broken filesets found in database, checking for missing remote files**
**Backend event: List - Started:  ()**
**  Listing remote folder  ...**
**Backend event: List - Completed:  (105 bytes)**
**Marked 1 remote files for deletion**
4       : 02/08/2023 17:11:59   (7 match(es))
        C:\Users\gp\duplicati\Duplicati\GUI\Duplicati.GUI.TrayIcon\bin\Debug\Duplicati-server.sqlite (72,00 KB)
        C:\Users\gp\duplicati\Duplicati\GUI\Duplicati.GUI.TrayIcon\bin\Debug\Duplicati.debug.log (8,69 MB)
        C:\Users\gp\duplicati\Duplicati\GUI\Duplicati.GUI.TrayIcon\bin\Debug\QSVDHHPCMR.sqlite (14,78 MB)
        C:\Users\gp\duplicati\Duplicati\GUI\Duplicati.GUI.TrayIcon\bin\Debug\QSVDHHPCMR.sqlite-journal (2,79 MB)
**Return code: 0**

and if you follow the link, you will see the story behind how the headers are now less visible.

Beyond the above, you are maybe OK, but only you know your backup. You passed a usual tripping point by typing passphrase manually, and you didn’t trip over the need for a dbpath, suggesting that you’re trying to match a GUI job. It can be simpler to use GUI Commandline.

Using the Command line tools from within the Graphical User Interface

avoids both potential trips, but adds a few others. I don’t think this is the core problem though.

Problem is (I think – find me a developer if you want more) that you might not have an actual broken file, in the sense that missing destination dblock file has lost data from any source file.

github.com

duplicati/duplicati/blob/fc5289b1a4474ef8083698ea9d0ab2c180cfea7e/Duplicati/Library/Main/Operation/ListBrokenFilesHandler.cs#L67-L86


      
          Logging.Log.WriteInformationMessage(LOGTAG, "NoBrokenFilesetsInDatabase", "No broken filesets found in database, checking for missing remote files");

          

          using (var backend = new BackendManager(backendurl, options, result.BackendWriter, db))

          {

              var remotestate = FilelistProcessor.RemoteListAnalysis(backend, options, db, result.BackendWriter, null);

              if (!remotestate.ParsedVolumes.Any())

                  throw new UserInformationException("No remote volumes were found, refusing purge", "CannotPurgeWithNoRemoteVolumes");

          

              missing = remotestate.MissingVolumes.ToList();

              if (missing.Count == 0)

              {

                  Logging.Log.WriteInformationMessage(LOGTAG, "NoMissingFilesFound", "Skipping operation because no files were found to be missing, and no filesets were recorded as broken.");

                  return null;

              }

          

              // Mark all volumes as disposable

              foreach (var f in missing)

                  db.UpdateRemoteVolume(f.Name, RemoteVolumeState.Deleting, f.Size, f.Hash, transaction);

          

              Logging.Log.WriteInformationMessage(LOGTAG, "MarkedRemoteFilesForDeletion", "Marked {0} remote files for deletion", missing.Count);

adds context to the missing-header analysis above. Note how it named some source files that broke, whereas your run didn’t. Your message looks like a side note from RemoteListAnalysis, whose main purpose is to return some information to its caller, but which comments as it goes.

github.com

duplicati/duplicati/blob/fc5289b1a4474ef8083698ea9d0ab2c180cfea7e/Duplicati/Library/Main/Operation/FilelistProcessor.cs#L396-L397


      
          foreach(var i in missingHash)

              Logging.Log.WriteWarningMessage(LOGTAG, "MissingRemoteHash", null, "remote file {1} is listed as {0} with size {2} but should be {3}, please verify the sha256 hash \"{4}\"", i.Item2.State, i.Item2.Name, i.Item1, i.Item2.Size, i.Item2.Hash);

is at Warning level, so you see it, as that’s the default console-log-level. You miss Information.

Bottom line is that this isn’t likely going to be a one-commander. Got any other logs or history?