Grestorn

Hi! Just for your information, when downloading the latest version of StableBit Scanner, Chrome confronted me with a certificate warning...

I've been using StableBit Scanner for a while and keep noticing that the Service is always hanging after some time. The effect is that the tab "StableBit Scanner" shows "Initializing" indefinitely, and when trying to restart the service in the Windows Service panel, I get the message that the service doesn't respond. I have to use the task manager to kill the Scanner.Service.exe process to be able to start the service again. After that, it's working fine again. I suspect that the cause for the hang might be that the server is going into sleep after some time of inactivity (controlled by the tool "Lights Out"). Did you ever encounter that problem? Would the beta 2.5 version help with the problem? What's the difference between 2.4 and 2.5 anyway? Is there any danger in trying the beta?

After shutting down the Drive Pool Service, the drives are going into StandBy as expected. Is this behaviour intended and can be changed in any way? I would like to use DrivePool, but this effect makes me wonder if that's a good idea.

After trying to shut down service after service I found the culprit... It is the DrivePool Service... I installed StableBit DrivePool but I'm not using it yet. After I shut down the service, the "Performance" indicator of all HDDs not in use dropped down to zero. Why is the service accessing the disks all the time? Now I'm waiting for Windows to spin down the disks... Let's see if that's working now.

I'm currently testing StableBit Scanner and I'm quite impressed and I'm most likely going to buy it in the next days. However, there's one question I'd like to be resolved: Even before I've been installing StableBit Scanner, I realized that my disks never spin down. I've got several disks in my server, most of them being accessed from clients only in very specific situations. So they SHOULD actually be dormant most of the time. I use the Windows setting for spin down, currently set to 10 minutes to test the function. However, they never spin down. I followed all the advice given in your posting above, "Throttle queries not more often than ... " is set to 60 minutes, "Do not query if the disk..." is checked. I don't use "Query Power mode directly from disk", though, because as I understand it, that shouldn't be necessary. I turned on the "Performance" column and that shows me that there seems always to be a bit of traffic on the disks that should be idle. The performance varies between 600 B/s to 1.17 KB/s all the time. I suspect that there is some task accessing the disks continuously, therefor prohibiting them going to idle. Is my assumption correct? Is there any way to figure out which process that could be? Do you know any "usual suspects", like one of the other Dashboard add-ins or software, that is installed on a server?