after a bit of struggling with my NAS I finally managed to spin-down the disks that, after upgrading to the last fw. (126.96.36.1995), had suddenly stopped to go to sleep.
I'm posting all the actions I carried out in the hope that this may be of help for others with a similar problem:
0. Logged in as admin via ssh to the NAS.
1. execute /etc/init.d/qulog.sh stop
2. execute /etc/init.d/LicenseCenter.sh stop (to avoid access to /mnt/HDA_ROOT/.logs/qlicense/log/qlicense.log)
3. execute /etc/init.d/QcloudSSLCertificate.sh stop
4. Changed IP address from DHCP to static (to avoid access to /mnt/HDA_ROOT/.config/dhclient/eth0.leases)
5. Commented out the entry for lock_timer.sh in the crontab file (to avoid access to /etc/config/cmd_timestamp)
6. Reload the crontab file
I came to these conclusions by examining the output of the Disk_Standby_Debug script, looking at all the disk accesses that were listed in the Standby1.log file.
Clearly steps 1,2 and 3 must be re-executed should the NAS be restarted.
Probably not all my interventions were necessary, but those listed at points 2,4 and 5 (in my case at least) have certainly been the key ones.
Merry XMAs to all of you and happy 2021.
Discussion about hard drive spin down (standby) feature of NAS.
1 post • Page 1 of 1
- New here
- Posts: 5
- Joined: Fri Feb 01, 2013 7:46 pm