Stubbornly refusing to index a drive

[getho]

It's in my local volumes list. It's the most recent one I've installed, NTFS SSD.
Its not in my exclude list. I've tried rebuilding. I've tried excluding, then rebuilding, then excluding again.
I tried updating to the most recent version of everything.

Any ideas?

[void]

Please try checking your NTFS SSD drive for errors:

• Please backup anything important on your drive before checking it for errors.
• In Windows Explorer, right click your drive and click Properties.
• Click the Tools tab.
• Click Check now....
• Click Start.
• If prompted to schedule a scan on the next restart, click Yes.

Could you please send the debug log when forcing a rebuild?

• In Everything, type in the following and press ENTER:
  /debug
• This will show a debug console.
• Type in the following and press ENTER:
  /reindex d:
• where d: is your NTFS SSD drive.
• Look for the following section in the debug console:

  Code: Select all

  Indexing \\?\Volume{00000000-0000-0000-0000-000000000000}, D:,
  open volume \\?\Volume{00000000-0000-0000-0000-000000000000}
  opened 1040 0.000194
  sector size 512
  sectors_per_cluster 8
  bytes_per_cluster 4096
  mft_lcn 786432
  serial_number 00000000000000000000
  bytes_per_cluster 4096
  bytes_per_file_record 1024
  MFT 
  ...
  processed 1000000 / 1000000 file records
  ntfs index: 100000 folders, 900000 files
  

  What is shown in the debug console when indexing your NTFS SSD drive?

To close the debug console:

• In Everything, type in the following search and press ENTER:
  /debug

[getho]

thanks for getting back to me
scanned disk no probs. (it's a brand new ssd)

the console is constantly changing: I assume stuff is getting written to the C: drive then everything is keeping up with changes.
So I turned off indexing on C and the USN journal, then reindexed the ssd. After that it worked again woot.

The console had quite a few errors when C was set to monitor changes: Files not found, and repeating
usn create _
usn create close _
usn delete close _
IS that normal or is there something funky going on with my c drive?

thanks

[NotNull]

BEst way to analyze what is going on, is sending the debug log (as @void asked; see his post for details)

[void]

Thanks for the reply.

Sounds like deleting the USN journal and recreating the USN journal has fixed the issue. This may indicate the old USN journal was somehow corrupt?
I would have to see the debug log to confirm.

The "Files not found" message occurs when Everything fails to find a folder by file reference number (FRN). This means a folder's FRN could have changed without a USN journal entry or the change was not detected by Everything.
Hard to determine without the logs, it just means Everything is detecting changes, but the parent folders are missing from your index.

IS that normal or is there something funky going on with my c drive?

It's normal, please let me know if Everything stops indexing your C: drive again.

[getho]

Thanks
Hey where is the debug log? I could see the console, but couldn't grab text from it, couldn't enter any commands. The best I could've done is screenshot it. Is there a file somewhere?