HDD wont go into hibernation mode (AS3102T)

[foffe77]

I had my NAS for a few month now and it has been working really fine. I've seen in the logs that the harddrive goes into hibernation mode several times a day. Until a week ago.

I've noticed that the HDD is working almost all the time. And according to the logs it will not enter hibernation anymore. I did the diagnostic tool (settings/hardware/energy) to see what process prevent the hibernation mode. This process is exactly every 5 minutes accessing the HDD:

Service: actmand
Description: -
Storage: System Volume
Status: Write

Even if I put the timer to 5 minutes it will not go to hibernation.

What does the actmand process do? I've asked the support but it seemes to take the looooong time to answer...

[orion]

I got some other services active which are the applications that I installed (for example, googledrived). So my NAS cannot go to disk hibernation mode. That's expected behavior. However I did not see any "actmand" activities in diagnostic tool. Not sure what it is. I think you should send a support ticket to asustor to check it. https://support.asustor.com/

[Antonios]

It's been reported here that ADM 3.0 does not let HDDs spin down.

While there was no such problem with previous (non-beta) ADM version.

So, what happened is maybe an ADM update to 3.0 ?

[foffe77]

I updated the NAS a few days before an update, and it worked fine just after the update. But maybe ADM 3.0 is the cause anyway.

I been in contact with the support, but they don't come up with any solution, just the same answer in every mail. I uninstalled all my apps except KODI and UPnP media server. Disabled the UPnP server but the problem persists.

I can hear that the HDD is almost constantly working. Quiet for 5-6 seconds than working for a few minutes again. I have no idea how to solve this.

[foffe77]

The logs in my router shows this activity from my NAS

2017-9-12 08:32:22 AS3102T-99E4 myip.dtdns.com
2017-9-12 08:32:19 AS3102T-99E4 ip.changeip.com
2017-9-12 08:32:19 AS3102T-99E4 ip1.dynupdate.no-ip.com
2017-9-12 08:32:19 AS3102T-99E4 checkip.dyndns.org
2017-9-12 08:32:19 AS3102T-99E4 myip.dtdns.com
2017-9-12 08:30:58 AS3102T-99E4 ip.changeip.com
2017-9-12 08:30:58 AS3102T-99E4 ip1.dynupdate.no-ip.com
2017-9-12 08:30:58 AS3102T-99E4 checkip.dyndns.org
2017-9-12 08:30:58 AS3102T-99E4 myip.dtdns.com
2017-9-12 08:29:51 AS3102T-99E4 myip.dtdns.com
2017-9-12 08:29:38 AS3102T-99E4 myip.dtdns.com
2017-9-12 08:29:32 AS3102T-99E4 myip.dtdns.com
2017-9-12 08:29:28 AS3102T-99E4 myip.dtdns.com
2017-9-12 08:29:26 AS3102T-99E4 myip.dtdns.com
2017-9-12 08:29:24 AS3102T-99E4 ip.changeip.com
2017-9-12 08:29:24 AS3102T-99E4 ip1.dynupdate.no-ip.com
2017-9-12 08:29:24 AS3102T-99E4 checkip.dyndns.org
2017-9-12 08:29:24 AS3102T-99E4 myip.dtdns.com
2017-9-12 08:28:17 AS3102T-99E4 ip.changeip.com
2017-9-12 08:28:17 AS3102T-99E4 myip.dtdns.com
2017-9-12 08:28:17 AS3102T-99E4 ip1.dynupdate.no-ip.com
2017-9-12 08:28:17 AS3102T-99E4 checkip.dyndns.org
2017-9-12 08:26:50 AS3102T-99E4 myip.dtdns.com
2017-9-12 08:26:43 AS3102T-99E4 ip.changeip.com
2017-9-12 08:26:43 AS3102T-99E4 ip1.dynupdate.no-ip.com
2017-9-12 08:26:43 AS3102T-99E4 checkip.dyndns.org
2017-9-12 08:26:43 AS3102T-99E4 myip.dtdns.com
2017-9-12 08:25:39 AS3102T-99E4 myip.dtdns.com
2017-9-12 08:25:37 AS3102T-99E4 myip.dtdns.com
2017-9-12 08:25:36 AS3102T-99E4 ip.changeip.com

What is it doing?

[vitosx]

Reviving this thread a little, I too see problems with HDD hibernation. But in my case it is with a USB connected drive, which has no access ongoing according to Diagnostic tool. The drive won't go to sleep though. I reported this to Asustor support and I am waiting for answer.

The logs in my router shows this activity from my NAS

2017-9-12 08:32:22 AS3102T-99E4 myip.dtdns.com
2017-9-12 08:32:19 AS3102T-99E4 ip.changeip.com
...

This communication is clearly for checking external (Internet) IP address, maybe it is used by EZ-Router... I don't use it, so I am not sure, but I don't see such traffic from my NAS on my router.
I see actmand process on my NAS, but it is not making any drive access (at least not frequent ones).

[foffe77]

I still haven't solved this issue but I found a work around.

I noticed that after reboot the disc will not go in hibernation mode for 5-6 days. After 5-6 days the hibernation works fine. This is not temporarily, during the last few month there has been a few reboots, power outage, ADM update and so on. Every time, after 5-6 days, the hibernation works fine.

What does the NAS do for 5-6 days after a reboot that prevents hibernation?

[Antonios]

I suspect that even the developers themselves couldn't answer about this 5-6 days thing.

Maybe they should think about hiring someone (knowledgeable) to test these things before rolling them out every month or so.

Just saying...

[foffe77]

I agree. I had a lot of communication with the support, but they havent figured out what the cause is. They think that I shall format and reinstall everything...

[js_online]

I got similar issue with AS6204T.
I did debug, you can see my post here.

You can check if this is ACTMAND by stopping it from command line in Putty:
cd /volume0/usr/builtin/sbin/
actmand -stop

#Checked if it stopped:
ps -ef | grep actmand

Wait for time defined in Settings --> Hardware --> Energy Control --> Disk Hibernation. I set 5 minutes for debug purposes.
If actmand was reason disks will hibernate.

To see more details do debug with emboardmand, so it will show you exactly how many seconds each disk is idle and if timer is reset means that there is IO activity.
cd /sbin/
emboardmand -stop
#Checked if it stopped:
ps -ef | grep emboardmand (use kill 9 for pid if not stopping after repeating command multiple times)
#Run debug
emboardmand -debug > /tmp/emboardmand.log
Open files in WinSCP and refresh it for updates, or do tail -50 /tmp/emboardmand.log to see last 50 lines of output file
Remeber to stop debugging by emboardmand -stop or kill 9 pid of emboardmand