mash.m 0 Posted January 27 Report Share Posted January 27 Hi, recently i changed my system from WHS2011 to Windows 10 Pro 64. Made a clean install to a 1TB M2 SSD and installed DB 3.7. Pool was correctly mounted and is up and running find. I made a 150 Gbyte partition on the ssd for the system. The rest is now definded as landingzone. there are 3 folders that are configured with duplication. i have also a power monitor (arduino) which shares the power load of this server so i can easy see when the drives are sleeping. without spinned up hdd´s the server need only 10 watts in idle mode. with spinned up drives it takes at least 16 watts. power monitor usage now i have the problem that the pool drives spin up often in a 1 hour intervall. i checked the task scheduler, but there is nothing. windows search service is also disabled. on WHS2011 i had similar problems. But after deinstallation of the intel RST driver the problems where gone and pool drives sleeps when there was no usage. these drivers are currently not installed on the windows 10 system. Any tips how to find out what service or process is awekeing the pool drives? Best Regards, Markus Quote Link to post Share on other sites
mash.m 0 Posted January 28 Author Report Share Posted January 28 I stoped every service which was possible, but still no success. Stopped the defender and all sheduled tasks. still no sucess. i think it is not possible to get windows 10 to sleep the hdd´s permanent if they are not in use. i let run the resource monitor to see what happens, but there are often requests to the disks which are not really necessary. maybe the drive idle feature can stop hard disks from spin up if there is no real access to the storage. Now i have installed windows server 2019 essentials to see if this is the better system for my requirement. last way will be buying two 8tb ssd´s... markus Quote Link to post Share on other sites
CBers 110 Posted January 28 Report Share Posted January 28 I wouldn't use any part of your OS disk in the DB pool, it's not recommended. Try and use a separate SSD as your LZ drive. Quote Link to post Share on other sites
w3wilkes 202 Posted January 30 Report Share Posted January 30 Have you enabled Drive Idle in the DB settings? This is experimental, but is touted as a power saver so I guess it will down the pool drives when not in use. I understand why not to use the same drive as the system for a regular pool drive. However, Doesn't a LZ drive get cleared on a regular basis to make room for more data? I would think that primary (and duplicate folders/files) are pushed off the LZ to regular drives. There is a file loss exposure if the LZ drive fails, but this is the case regardless of whether it's a partition on the system drive or a dedicated LZ SSD. You can always open a ticket and ask the developer for some specific guidance on using a portion of the system drive as a LZ. Submit a request – Division-M - Support (division-m.com) CBers 1 Quote Link to post Share on other sites
mash.m 0 Posted February 8 Author Report Share Posted February 8 Hi, system drive is a dedicated ssd. first partition of this ssd is for the system. second partition is (now) the LZ drive. The pool are two HDD´s with some folder duplication activated. nothing is in touch with the system. i also try to enable the drive idle. but after leavong the menu it is again deactivated. See attached screenshot. Now that the system is running windows server 2019 the hdd´s are sleeping untill they are used as they should. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.