Change in handling of Sleeping drives

[therube]

Has there been a Change in the handling of Sleeping drives?

A few times now, I've had a drive awaken (after "sleeping", parking heads... after x-minute no activity kind of thing) & at that time, I'll catch Everything doing a very quick (Index) "refresh" (rather then a Rebuild, or so it seems)?

[void]

Has there been a Change in the handling of Sleeping drives?

Everything is not aware of a sleeping state for drives.
Everything sees drives as online or offline.
Maybe Everything is seeing sleeping drives as offline?

Is it possible to get the debug output of the issue occuring?

[therube]

If there's been no change, I'm just going to have to keep a better eye out for just what is happening, & hopefully I can catch it at a time to get some decent information back.

[therube]

I heard a drive spin up, so I captured at that point, but I didn't catch whether Everything was doing (what I'll call) a "refresh"?

Code: Select all

QueryDosDevice X: \Device\HarddiskVolume66
X:\ GetVolumeNameForVolumeMountPoint FAILED
add found volume: \\.\X: | X: |  | 00000000
add volume: \\.\X: | X: |
volume: \\?\Volume{80b65e57-1ead-11dd-a4f0-806d6172696f} | C: |  found 1
volume: \\?\Volume{e2c2021e-4d0e-11e6-a24d-0050ba8bed58} | D: |  found 0
volume: \\?\Volume{80b65e61-1ead-11dd-a4f0-806d6172696f} | E: |  found 1
volume: \\?\Volume{80b65e59-1ead-11dd-a4f0-806d6172696f} | L: |  found 1
volume: \\?\Volume{80b65e5a-1ead-11dd-a4f0-806d6172696f} | M: |  found 1
volume: \\?\Volume{80b65e5b-1ead-11dd-a4f0-806d6172696f} | O: |  found 1
volume: \\?\Volume{80b65e5c-1ead-11dd-a4f0-806d6172696f} | W: |  found 1
volume: \\.\X: | X: |  found 1
volume: \\?\Volume{80b65e5d-1ead-11dd-a4f0-806d6172696f} | X: |  found 0
ntfs volume create list 0.008762 seconds
rebuild: guid changed
create db...

[therube]

I'm now thinking that that is going to turn out to be worthless.
Had another "wake" occasion, but it did not cause a "refresh".
I'll keep looking...

[void]

Thanks for the debug output.

As suspected, the volume guid is unavailable and Everything is using the fall back \\.\X: for the volume guid.

I've changed Everything to not allow \\.\X: for physical hard drives for the next beta update. This will allow Everything to continue to index NTFS images, and only index physical hard drives when a volume guid is available.

The indexing of \\.\X: could be causing the drive to wake up.

[void]

http://www.voidtools.com/Everything-1.4.1.724b.x86.zip
http://www.voidtools.com/Everything-1.4.1.724b.x64.zip

1.4.1.724b should fix the issue.