TS-453BE does not enter standby after FW 4.4.3.1354 update

Discussion about hard drive spin down (standby) feature of NAS.
Post Reply
WilNasU
Starting out
Posts: 12
Joined: Sat May 23, 2020 3:01 pm

TS-453BE does not enter standby after FW 4.4.3.1354 update

Post by WilNasU » Tue Jul 28, 2020 6:19 pm

After 4 weeks support my new TS-453BE entered the first time in to standby mode.
Unfortunately after Firmware 4.4.3.1354 and app update I encounter the same again: The NAS does not enter standby mode. It is just burning energy, entertaining the HDs and is noisy (HDs).

Former support session:
- I did read this article: https://www.qnap.com/en/how-to/faq/arti ... ndby-mode/
- I followed the support advices from the first support session: Switching off all applications, disconnect the NAS from the network (for 2 days) and starting the disk standby debug
loop: for (( i=1; i<=30; i=i+1 )); do ./Disk_Standby_Debug --file 300 ; echo -----${i}------;sleep 300; done 2>&1 | tee /tmp/Standby_test.log
But as in the first session after the echo: Last file access: the “for loop” hangs and the out-put file is 0 bytes long.
- From the remote session I had no feedback but somehow it worked after 4 weeks.

The main reason changing to a new NAS was that my old one has no standby mode. But now unfortunately the QNAP does not enter and is even burning more energy as the disks are almost continuously active.

Meanwhile I checked the contab and found entries like:
0-59/15 * * * * /etc/init.d/nss2_dusg.sh backup of surveillance station
0-59/10 * * * * /etc/init.d/storage_usage.sh ??
*/10 * * * * /sbin/config_cache_util 0 ??
33 * * * * /sbin/qddns_check 2>/dev/null ??
Do the listed jobs stop the NAS to enter standby? Should I disable the commands as they run in short intervals?
I did set the standby time out to 15 min.!

Appreciate help to fix the standby issue, as the system burns energy for nothing and is rather noisy.

WilNasU
Starting out
Posts: 12
Joined: Sat May 23, 2020 3:01 pm

Re: TS-453BE does not enter standby after FW 4.4.3.1354 update

Post by WilNasU » Tue Aug 04, 2020 6:11 pm

Meanwhile I followed the topic viewtopic.php?f=55&t=154344
and stopped the syslog server. I stopped also all apps again but no change the thing does not enter standby.
There are so many topics on the net about QNAS standby that I get lost what to do.
I just wanted a simple NAS to access data and save energy when not used. Unfortunately only the first point is valid.
Maybe QNAO should offer two configurations: Home with power safe mode as default and business!
Any succession what to stop based on the blkdevMonitor_v2.log log?

============= 25/100 test, Tue Aug 4 11:40:18 CEST 2020 ===============
<<7>[10514.413753] md9_raid1(2422): WRITE block 1060216 on unknown-block(8,16) (1 sectors)
<7>[10514.413782] md9_raid1(2422): WRITE block 1060216 on unknown-block(8,0) (1 sectors)

============= 26/100 test, Tue Aug 4 11:40:52 CEST 2020 ===============
<7>[10604.195830] rsyslogd(9234): dirtied inode 19928 (kmsg) on md9

============= 27/100 test, Tue Aug 4 11:42:23 CEST 2020 ===============
<7>[10713.957924] jbd2/md9-8(2435): WRITE block 632448 on unknown-block(9,9) (8 sectors)

============= 28/100 test, Tue Aug 4 11:44:11 CEST 2020 ===============
<<<<<7>[10724.364907] jbd2/md9-8(2435): WRITE block 632456 on unknown-block(9,9) (8 sectors)

============= 29/100 test, Tue Aug 4 11:44:22 CEST 2020 ===============
<7>[10789.867949] jbd2/md9-8(2435): WRITE block 616472 on unknown-block(9,9) (8 sectors)
<7>[10789.940773] jbd2/md9-8(2435): WRITE block 536776 on unknown-block(9,9) (8 sectors)

============= 30/100 test, Tue Aug 4 11:45:27 CEST 2020 ===============
<<<<7>[11030.215755] md9_raid1(2422): WRITE block <<<<<<7>[11031<<

============= 31/100 test, Tue Aug 4 11:49:29 CEST 2020 ===============
<<<7>[11045.321936] jbd2/md9-8(2435): WRITE block 622480 on unknown-block(9,9) (8 sectors)

============= 32/100 test, Tue Aug 4 11:49:42 CEST 2020 ===============
<7>[11054.850757] gen_band<7>[11055.404923] jbd2/md9-8(2435): WRITE block 622496 on unknown-block(9,9) (8 sectors)

============= 33/100 test, Tue Aug 4 11:49:52 CEST 2020 ===============
<<<<7>[11062.464878] rsyslogd(9234): dirtied inode 19928 (kmsg) on md9

============= 34/100 test, Tue Aug 4 11:50:02 CEST 2020 ===============
<<<<7>[11115.904776] md9_rai<<<<<7>[11116.915767] hal_enc_fan(2584): dirtied inode 1723436 (em_0.inf~) on tmpfs
<<<<<<7>[11118.997531] md9_raid1(2422): WRITE block 10<

============= 35/100 test, Tue Aug 4 11:50:58 CEST 2020 ===============

Post Reply

Return to “HDD Spin Down (HDD Standby)”