Fatal error: Detected non-empty blocksets with no associated blocks

Support
36

I’m basically going to say the same thing that gabor just did, but just reporting another case, and how I fixed it. I had this same issue happening on my macOS machine.

(And the obvious warnings here before anyone proceeds. I’m not a SQL expert. I’m not a Duplicati expert. Make sure you make a backup of your database before doing anything.)

  1. On a mac, the database file is in: ~/.config/Duplicati/
    It’s the long string of numbers ending in “.sqlite”. It will probably be a pretty big file.

  2. I made a copy of the sqlite file as backup.

  3. I then opened the sqlite file using https://sqlitebrowser.org/. (Or really whatever sql program you want.)

  4. I ran the query as suggested by johnvk:

SELECT * FROM Blockset WHERE Length > 0 AND ID NOT IN (SELECT BlocksetId FROM BlocksetEntry)

  1. That found exactly one entry in my database in the Blockset table. I deleted that entry.

  2. In duplicati, I then repaired the database (don’t know if this was necessary or not).

  3. Then the backup worked! Huzzah.

3 Likes