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

**URL:** https://forum.duplicati.com/t/fatal-error-detected-non-empty-blocksets-with-no-associated-blocks/5938
**Category:** Support
**Created:** [January 9, 2019, 5:30am UTC](https://forum.duplicati.com/t/fatal-error-detected-non-empty-blocksets-with-no-associated-blocks/5938 "2019-01-09T05:30:34Z")
**Posts on this page:** 1
**Showing post:** 21

<div class="post-metadata">

### Author: ![johnvk](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/j/f17d59/32.png) [@johnvk](https://forum.duplicati.com/u/johnvk)
#### Post date: [January 28, 2019, 11:42pm UTC](https://forum.duplicati.com/t/fatal-error-detected-non-empty-blocksets-with-no-associated-blocks/5938/21 "2019-01-28T23:42:14Z")

</div>

What `--log-file-log-level` did you use? [I suggest verbose](https://forum.duplicati.com/t/log-file-log-level-vs-log-level-and-log-file-log-filter-and-how-many-log-files-are-there-and-what-are-the-different-logs-and-what-is-the-meaning-of-the-levels/6084).

If verbose is too much, try `Information`

What would be helpful (but it’s a lot of steps) is

1. Starting with a working backup job
2. Turn on `--log-file-log-level` (as you have)
3. experience non-empty blocksets error (well, I hope you _don’t_, I hope no one does, but _if_ you do)
4. perform [sql query in database browser](https://forum.duplicati.com/t/fatal-error-detected-non-empty-blocksets-with-no-associated-blocks/5938/6)
5. Find 5 of 10 files “around” where the failing file was
6. go _back_ to logfile and search for those files. This is likely from previous runs, not the current that received the error.
7. hopefully something in the logfile will be revealing

---

_[View the full topic](https://forum.duplicati.com/t/fatal-error-detected-non-empty-blocksets-with-no-associated-blocks/5938)._
