lvau

Getting the correct power state of the disk is a little tricky. There are really 2 separate mechanisms that control whether a disk has spun down or not, the OS and the disk's firmware.
 
Here are the tricky parts:
The disk's firmware can spin a drive down at any time without the OS's knowledge. But this is typically disabled on new drives. This behavior can be modified under Disk Control in the StableBit Scanner. In order to get the actual power state of the drive we can query it directly, instead of asking Windows. The problem here is that, to Windows, this appears as disk access and it will prevent the OS from ever spinning down the drive. What the StableBit Scanner does by default is it always asks the OS and it never queries the drive directly. This ensures that the OS will spin the drive down correctly. even though we're querying it for the power state. But the issue here is that just because the OS thinks that the drive is active doesn't mean that it's actually spun up. If the disk's firmware has spun down the drive, the OS has no way to know that. The StableBit Scanner deals with this by reporting in the UI that the drive is Standby or Active. Since we can't attempt to query the drive directly without your explicit permission (this will upset Windows' power management), this is the best answer we can give you.
 
The Query power mode directly from disk option, which is found in Disk Settings, is there to work around this shortcoming. When enabled, the StableBit Scanner will attempt to query the power mode directly from the disk. Keep in mind that this can fail if it can't establish Direct I/O to the disk, in which case we fall beck to relying on the OS.
 
The way it works is like this:
Query the OS. If the disk has spun down then this must be the case. The disk is in Standby. If the disk is Active (spun up) then we can't trust the OS because the disk firmware could have spun it down. If the user has not explicitly allowed us to query the power mode from the disk, we must assume Standby or Active. If the user has allowed us to query the power mode from the disk, query the power mode. If the query succeeds, set the mode to Active or to Standby (not both, because we know the power state for sure). If the query fails, fall back to the OS and set the mode to Standby or Active. So when should you enable Query power mode directly from disk?
 
When you don't want to use the OS's power management features to spin the disk down. Why would you do this?
 
Pros:
You can control the spin down on a per disk basis. You get exact disk power states being reported in the StableBit Scanner with no ambiguity. Avoid disk spin up issues when querying SMART (I will explain below). Cons:
Requires Direct I/O to the disk. To the OS (and to any other program that queries the OS) the disk will appear to be always spun up. When the OS spins down a disk it flushes the file system cache prior to spinning it down. This ensures that the disk is not spun up very quickly after that because it needs to write some additional data to it from the cache. When the firmware spins a disk down, this does not happen and there is a chance that the disk will be spun up very quickly after that to perform another write. From my experience, this is not common in practice. What about S.M.A.R.T. queries?
 
In the StableBit Scanner, by default, SMART is queried from WMI first. If Direct I/O is not available then all the SMART data has to come from WMI. Typically this would not spin up a disk.
 
If Direct I/O is possible to the disk then at least some additional SMART data will come from Direct I/O (and if WMI doesn't have the SMART data then all of the SMART data comes from Direct I/O). One potential problem here is that Windows considers any communication with the disk, disk activity. So if you're communicating with the disk to retrieve SMART every couple of minutes then Windows will not spin the disk down.
 
You can avoid this problem in 2 ways:
Don't let Windows control your disk spin down and set up a Standby timer in Disk Control (this has the pros and cons as outlined above). Set Throttle queries in Settings -> Scanner Settings -> SMART -> Throttle queries. Set the throttle minutes to something higher than the Windows disk spin down time (which can be examined in Power Options under the Windows Control Panel). The option Only query during the work window or if scanning controls SMART queries and has no effect on power queries. Again, by default power queries do not spin up a disk unless you've manually enabled Query power mode directly from disk (in which case you are effectively saying that you don't want the OS to ever spin down a disk).

After re-enabling "Realtime Duplication", which I had previously disabled because I have just one SSD for the landing zone, these checks have disappeared completely. According to the documentation it says that if "Realtime Duplication" is disabled, the Duplication will be ensured to be consistent "at night". So it seems it was exactly that and there is no schedule to plan what "at night" is and when exactly it will happen. My suggestion to the developers: give Drivepool an option to let the user schedule when the Duplication consistency check is being performed. Some of us are working at night and so do I, and just force performing this check at a time the developer thinks is good, is not the best way at all. Thanks.

yea this was discussed previously and i'd tried it in the past, does not work for me either.  just edited both json and restarted.  set my spindown to 1m.   drives keep on spinning away.  

only time i can get them to spindown is stopping the service(s) entirely. 

I ended up moving to unraid to solve this problem. I still maintain that DrivePool (and Scanner) is one of the best pieces of software I ever purchased on Windows, but it is a shame to see this remain unresolved.

Yea, unraid was/is a non starter for me due to existing data and the filesystem difference etc.  i have a few hundred TB and it would be all kinds of incomprehensible mess I dont have time for with kids. 

Now had i saw this whole data obsession/hobby thing becoming what it was.. i definitely would have taken a different path if i was starting from scratch but it is what it is.

I will concur that the stablebit suite is without parallel windows side.  its served me well for quite some time and I honestly hope it will serve me well until that fateful day hopefully some time a reaaaaally long time from now lol.  I love it.

that being said, the spindown issue is not inconsequential.  when youre looking at a chassis with 30x7200rpm disks crammed within a half an inch of one another in an upstairs office spinning 24/7, the summer months prove a huge issue.  I just cant run my air cold enough without making the rest of the house a fridge.   Theres also the power savings however miniscule from letting them spin down.   The age old argument surrounding which is the lesser evil for longevity etc. 

i know until i began using drivepool, i always had my drives spin down and would still be doing so if i were able.

New to StableBit DrivePool, how do I ensure drives will sleep when unused.  I have a basic setup and drives are not sleeping according to smartctl.  I do not have BitLocker enabled.  Note: this is something I want to validate before buying
Windows 10 Pro
Power Profile - Balanced -  has 5 min Drive Sleep enabled
Drives are Internal SATA (5 x 8TB WD, 3 x 6TB WD)