Will not index d:

If you are experiencing problems with "Everything", post here for assistance.
Post Reply
rightnyer
Posts: 3
Joined: Thu May 26, 2011 1:32 pm

Will not index d:

Post by rightnyer »

I have two hard drives, a Raid 0 array as c: and a 2 TB data drive as d:. No matter what I do, it simply will not search d:. When I delete the database file and close Everything, and then restart it, it says "Indexing d:" but then once the software loads, only files from c: are in it. I am running 1.2.1.451a. Anyone have any ideas?
therube
Posts: 4955
Joined: Thu Sep 03, 2009 6:48 pm

Re: Will not index d:

Post by therube »

D: formatted NTFS?
You haven't excluded D: in options?
BillCh
Posts: 7
Joined: Thu Oct 15, 2009 9:23 am

Re: Will not index d:

Post by BillCh »

Also do not get anything from D:\ to show up. C:\ is fine, E:\, G:\, ... but not E:\?!?

Deleted .db as well. Did work well before. Now installed SSD as C:\ and D:\ is a RAID-1 thing but E:\ is RAID-1 too and it works there. Also did error checking on D:\ (no errors found).

Of course it is not included in exclude list. And it shows up in local drives to index.

Any advice what can cause this? Ideas to get it to work (again)?

Thanks!
BillCh
Posts: 7
Joined: Thu Oct 15, 2009 9:23 am

Re: Will not index d:

Post by BillCh »

bump
void
Developer
Posts: 16690
Joined: Fri Oct 16, 2009 11:31 pm

Re: Will not index d:

Post by void »

From a command prompt, please run:

Code: Select all

fsutil fsinfo volumeinfo D:

Code: Select all

fsutil fsinfo ntfsinfo D:
What is the output from both these commands?
BillCh
Posts: 7
Joined: Thu Oct 15, 2009 9:23 am

Re: Will not index d:

Post by BillCh »

fsutil fsinfo volumeinfo D:

Volume Name : HLH-D_1TB
Volume Serial Number : 0x64525ea6
Max Component Length : 255
File System Name : NTFS
Supports Case-sensitive filenames
Preserves Case of filenames
Supports Unicode in filenames
Preserves & Enforces ACL's
Supports file-based Compression
Supports Disk Quotas
Supports Sparse files
Supports Reparse Points
Supports Object Identifiers
Supports Encrypted File System
Supports Named Streams
Supports Transactions
Supports Hard Links
Supports Extended Attributes
Supports Open By FileID
Supports USN Journal

fsutil fsinfo ntfsinfo D:

NTFS Volume Serial Number : 123456789012345678
Version : 3.1
Number Sectors : 0x00000000747018c0
Total Clusters : 0x000000000e8e0318
Free Clusters : 0x0000000000009201
Total Reserved : 0x0000000000000480
Bytes Per Sector : 512
Bytes Per Physical Sector : <Not Supported>
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x000000001c4c0000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x000000000a2e7b20
Mft Zone End : 0x000000000a2ed660
RM Identifier: 12345678-9012-3456-7890-123456789012
BillCh
Posts: 7
Joined: Thu Oct 15, 2009 9:23 am

Re: Will not index d:

Post by BillCh »

Also strange is that I autostart Everything.exe (and I see it in the tray) but I also have a shortcut to launch Everything.exe. When I do this on the PC I am having troubles with D:\ it always starts to buid the index new - which it does not on the other PCs I have Everything installed.

Why is this, how to avoid, and has this something to do with my D:\ problem?

I know my problems on this PC must have something to do with that machine (although it is a clean W7 64bit installation like on the others) as Everything runs just fine on the other ones.

So I appreciate your support from your side even more, thanks a lot!
void
Developer
Posts: 16690
Joined: Fri Oct 16, 2009 11:31 pm

Re: Will not index d:

Post by void »

The output looks normal, is there any errors reported in your Errorlog.txt file in your "Everything" installation folder?
Also strange is that I autostart Everything.exe (and I see it in the tray) but I also have a shortcut to launch Everything.exe. When I do this on the PC I am having troubles with D:\ it always starts to buid the index new - which it does not on the other PCs I have Everything installed.

Why is this, how to avoid, and has this something to do with my D:\ problem?
Try rebuilding the USN Journal for the D: drive..
To rebuild the USN Journal:
  • In "Everything", from the Tools menu, click Options.
  • Click the Volumes tab.
  • Select the D: volume.
  • Uncheck Enable USN Journal.
  • Click OK.
  • Restart your computer.
  • In "Everything", from the Tools menu, click Options.
  • Click the Volumes tab.
  • Select the D: volume.
  • Check Enable USN Journal.
  • Set the Maximum Allocation size to 32768 KB.
  • Set the Allocation Delta size to 8192 KB.
  • Click OK.
BillCh
Posts: 7
Joined: Thu Oct 15, 2009 9:23 am

Re: Will not index d:

Post by BillCh »

Index on D:\ seems to work again after following your advice. Thank you!
1Delu
Posts: 1
Joined: Mon Jun 15, 2009 11:38 am

Re: Will not index d:

Post by 1Delu »

void wrote:The output looks normal, is there any errors reported in your Errorlog.txt file in your "Everything" installation folder?
Also strange is that I autostart Everything.exe (and I see it in the tray) but I also have a shortcut to launch Everything.exe. When I do this on the PC I am having troubles with D:\ it always starts to buid the index new - which it does not on the other PCs I have Everything installed.

Why is this, how to avoid, and has this something to do with my D:\ problem?
Try rebuilding the USN Journal for the D: drive..
To rebuild the USN Journal:
  • In "Everything", from the Tools menu, click Options.
  • Click the Volumes tab.
  • Select the D: volume.
  • Uncheck Enable USN Journal.
  • Click OK.
  • Restart your computer.
  • In "Everything", from the Tools menu, click Options.
  • Click the Volumes tab.
  • Select the D: volume.
  • Check Enable USN Journal.
  • Set the Maximum Allocation size to 32768 KB.
  • Set the Allocation Delta size to 8192 KB.
  • Click OK.
I am also having the same issue. Whatever I do,it couldn't not searching my 1TB disk, F:
Removing the installed "Everything" and downloading the portable version is the only solution I get so far.
Post Reply