@KarstenV Thanks for the report and comments and screen shot. By design and until we get a notification system in place we log the reason for no response to /opt/rockstor/var/log/rockstor.log. I suspect that the samsung’s are not being correctly identified as rotational. I wanted to err on the cautious side and do nothing unless we can confirm a device is rotational. In the meantime, as I know you already know, we can watch this log using the following command.
tail -f /opt/rockstor/var/log/rockstor.log
@Flyer is actually making great progress on a log reading facility within the WebUI but for now we will have to command line it.
Could you open a new forum post that we can link to here as I would like to work out why this is happening with these drives. If it turns out that your rockstor.log has the following in every time you try and set the spindown on the Samsungs then we can take it from there.
“Skipping hdparm settings: device not confirmed as rotational”
Could you also in the new thread (as this may take a few posts back and forth) post the the output of:-
udevadm info --query=property --name devNameOfASamsung
By the way the APM setting is blended in with the spindown setting via the slider as sometimes too higher APM setting can inhibit spindown, so I presented the two together.