runningnas wrote:Updated yesterday, but still no HDD suspend. I then invested some time investigating the blkdevmonitor.sh output and eventually disabled two cron jobs manually. One was from the Surveillance Monitor (App is not installed, don't know how it went into the crontab), the other is the disk usage statistics gathering script disk_usage.sh, which runs every 10 minutes. I didn't found a way to disable that statistic gathering function via the UI (did I miss it?), so I had to disable it manually in the crontab.
Later on I could notice some drives to go to suspend, so this was at least a partial success. Have to watch it for a while now to see if it resolves my issue. I'm wondering if those crontab entries were there in the october firmware where HDD suspend was working the last time out of the box.
I'm a bit puzzled why the firmware offers a HDD suspend feature which it seems to sabotage by itself with that usage statistic.
Just to be helpful I do not have any disk_usage.sh in crontab. This is mine on a 4.2.2 20161214 on HS-251+:
10 2 * * * /sbin/qthin_check
0 2 * * * /sbin/qfstrim
12 2 * * * /sbin/hwclock -s
7 2 * * * /sbin/vs_refresh
16 2 * * * /sbin/clean_reset_pwd
0-59/15 * * * * /etc/init.d/nss2_dusg.sh
17 2 * * * /sbin/clean_upload_file
20 2 * * * /sbin/notice_log_tool -v -R
22 2 * * * /bin/rm -rf /mnt/HDA_ROOT/twonkymedia/twonkymedia.db/cache/*
15 2 * * * /usr/bin/power_clean -c 2>/dev/null
0 3 * * 0 /etc/init.d/idmap.sh dump
4 3 * * 3 /etc/init.d/backup_conf.sh
* * * * * /mnt/ext/opt/netmgr/util/lock_timer.sh
50 * * * * /sbin/qddns_check 2>/dev/null
I have just tweaked the time of some scripts so that they run all around 2 am.