Re-indexing at each startup

[yoyomaah]

For some reason the latest version of Everything is starting to re-index all drives almost on every system startup.

Using 8.1 x64. I have 9 HDDs and 3 external HDDs. USN journal and monitoring is disabled on 2 HDDs and 1 external HDD.

Tried exiting and running Everything manually without reboot - no problem. Tried exiting manually before reboot/shutdown - doesn't seem to help. Tried delaying the launching of Everything on startup - does not help.

How can I troubleshoot this? Or at least how can I debug it to see what exactly is causing this?

[void]

Running Everything in debug mode will report why the rebuild is necessary.

Please try running Everything in debug mode

Please enable the debug mode via the Everything.ini:

• Exit Everything completely.
• Edit your Everything.ini in %APPDATA%\Everything
• Change the following line:

  Code: Select all

  debug=0

  to:

  Code: Select all

  debug=1

• Restart Everything.

What is display in the debug console after a restart and a rebuild occurs?

[yoyomaah]

Thanks.

It went fine during the previous reboot - no rebuild. Today it got rebuilt again. Debug says:
(couldn't find where it writes the log and couldn't copy the text so typed manually)

Code: Select all

...

_db_filesystem_add 0: ...
...
_db_filesystem_add 8: ...

open volume \\...
...
open volume \\...

loaded 0 of 0 changes in 0.013432 seconds
recent changes array memory usage: 0 bytes
loaded run history in 0.005381 seconds
run history data count: 992, data: 57861 bytes
run history ptr count: 726
total run history memory usage: 98901 bytes

update filesystem C:
open volume \\... (drive C:)
opened 600 0.000149
read usn journal failed
updated C: in 0.000406 seconds
failed to update drive C:
loaded db in 2.890118 seconds
_DB_WAIT: _db_load_failed_proc waiting...
_DB_WAIT: _db_load_failed_proc waited 0.000146 seconds
create db...
open volume \\... (drive C:)
opened 444 0.000125
convert parent frn to parent pointers: 0.001749 seconds
open volume \\...
opened 600 0.000175

...

At this point I see in the main windows how it rebuilds all the volumes.

C: is my primary single-volume drive, it's Samsung 840 Pro SSD 128 GB. Never had issues with it, and SMART looks fine. What could be the problem?

Also, is it possible to only rebuild a "failed" drive? Rebuilding my C: takes only a few seconds I think, while rebuilding all 9 drives takes around a minute.