Very nice with the disk spin down feature.
Sadly it does not seem to work on my 4 old SAMSUNG HD154UI disks, who seem completely unresponsive to the commands.
I know they can spin down, it worked in the Netgear NAS they lived in before, and I have also had them spin down using hdparm from the command line.
The other disks in the system (all never) seems to respond, and adds the value selected (I used 10 minutes as a test)
Forcing the disks into standby, seemed to work for all of them.
This is a nice start for this feature
I’m still uncertain on how to set the APM feature, but am sure I will work it out.
@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.
3.8-13.07 is now available!
I have created a new thread and suplied the data you requested.
Hello all! We just released 3.8-13.08.
Almost forgot to reply here, 3.8-13.09(5213dd5) was released last night (pacific time).
Happy sunday folks! 3.8-13.10(ca1d9b5) is now available.
A total of three issues were merged. Two of them are UI improvements, something @ganti_priya has been methodically working on. Third is an improvement to AD configuration by @ScarabMonkey. Way to go about fixing issues you use and care about! pleasure to merge them.
I am happy to announce that 3.8-13.11(ec65d1c) is now available.
I’ve merged three pull requests in this update. @Flyer’s Logs Manager is the big one. It’s a really cool feature and I encourage everyone to use it and provide your feedback. Thank you @Flyer for sticking with it and doing an impressive job!
@phillxnet made an important improvement to disk state management. We can now store generic auxiliary information and assign roles to HDDs, paving way for features like backup disks etc…
@ganti_priya fixed a replication related UI bug. Happy to merge three pull requests from three different contributors, making this update special! Thank you!
Happy Sunday! 3.8-13.12(b0ca110) is now available!
We closed two issues in this update. I fixed a small annoyance while configuring SNMP by making the dependency pre installed. @ganti_priya made yet another much appreciated UI improvement.
I’ve also changed the testing updates repo location – Thanks to our increasing number of active users, the hosting charges are getting a bit too expensive. A good problem to have :), but gratipay anybody?
Hello Everyone! 3.8-13.13(41dd23b) is now available.
Hello Everyone, sorry to be slacking a bit since the last update, I’ve been extra busy. But the good news is 3.8-13.14 (fdbd093) is now available!
I’ve merged two pull requests in this update, both by @Flyer. One is a neat fix to the network widget regression put in place by yours truly. Second is an improvement to the users screen of the UI. Thanks @Flyer, your contributions are greatly appreciated!
We’ve been testing 4.6 kernel for couple of weeks now and it’s been going on pretty well without any issues. There are many BTRFS changes which we should all be grateful for. I’ve added it to our testing repo, but it’s not yet default. I think it will be in the next update. If you like to get it in the meantime, update your kernel-ml package.