@kcomer Hello again. I have found that if you leave a browser open on the Disk page it can end up preventing the drives from powering down. But funnily enough doesn’t then wake them if you visit that page once they have powered down. Ie the polling seems to keep them awake but doesn’t wake them once they have entered standby. Also a few drive models are non responsive to > 20 minute settings. Take a look in the logs via @Flyer 's fancy new System - Log Manager to make sure there are no messages akin to:
Skipping hdparm settings: device ata-KINGSTON_SMS200S330G_50026B724C085CD1-part3 not confirmed as rotational
In the “Rockstor Logs” directly after attempting to set an idle spindown time.
The system will only apply settings (as indicated by the configured setting appearing next to the hour glass) if the drive can be confirmed as rotational.
Under the hood we simply use an hdparm -S120 command (for 10 mins in this example). So nothing special really. Oh and some drives will refuse to spindown unless their APM setting is also 127 or below (set by Rockstor via the hdparm -B switch). Though I haven’t found many that this affects. That is in part why we blended these 2 settings together. Note though that the drives do have to be idle for the set period prior to spin down.
Hope that helps and let us know how you get on, and thanks for offering to help on this one as well.
Just thought that we did have a report where an AAM setting on a drive was causing a false reading on the rotational status of the device and hence blocking the setting (and causing the ‘… not confirmed as rotational’ message). Please see:
If you are receiving this ‘Skipping hdparm setting’ message in your Rockstor logs when trying to add a setting.