Is the hdparm setting persistent or does it need to be run each boot?
Code:
idle3ctl -d /dev/sda
Idle3 timer is disabled.
IIRC the WD drives need a full power cycle for this to take effect. I'd be interested to see if there's any correlation with HGST drives trying to do a similar thing...
From what I understand, hdparm may need to be run on each boot.
Idle3ctl sound like a neat tool, I'll check it out! Thanks
I've started keeping a dump of SMART logs so that I can track changes over time.
I don't know of any tools out there that can already do this but here's my crude method:
# for f in /dev/sd*[^1-9] ; do smartctl -a -d sat $f >> /root/smartdump-`date +"%m-%d-%y"`.txt ; done
Eventually, I'd like to dump the logs, parse the data into a database, then run queries to track various changes.
Anyways, I've kept these logs and have found that the Load_Cycle_Count has not increased on my drives since using hdparm. Also I should note that my system has not been power cycled.