[RN202-100NES] Spin-down not working - wake up after seconds

Yep, I will try it now for 30 mins

I will tell you then the results :)

Awesome.

I still am not sure as to the root cause for why your RN spins up so frequently. I see some messages being written to the log then the changes from connman but these shouldn't spin back up the device.

hm ok... kohdee

I found out that smbd, nmbd and readynasd writes to md0 sometimes and wakes up the HDDs.

but I tried also to remap the directorys of these 3 processes to tmpfs: mount -t tmpfs tmpfs /var/readynasd and also for samba - but no success also. :(

I tried it now with ipv6 deactivated and deactivated wake on lan.

It still Spinning up frequently, but spinning up times between last spinning times are a bit longer i think.

I take more time to test it more precisely

OK problem solved: Problem was definetly IPv6

on Firmware 6.4.2 RC1 - Wake on LAN activated - IPv6 deactivated now HDD spindown works like a charm.

after I activate IPv6 on one eth device on the NAS - spindown will be interrupted seconds after spin down...

Jan 20 07:59:47 NAS noflushd[2231]: Spinning up disk 1 (/dev/sda) after 2:01:50.
Jan 20 07:59:52 NAS noflushd[2231]: Spinning up disk 2 (/dev/sdb) after 2:01:42.
Jan 20 08:05:07 NAS noflushd[2231]: Spinning up disk 2 (/dev/sdb) after 0:00:11.
Jan 20 08:49:35 NAS noflushd[2231]: Spinning up disk 1 (/dev/sda) after 0:44:33.
Jan 20 08:51:06 NAS noflushd[2231]: Spinning up disk 2 (/dev/sdb) after 0:40:55.

Would be nice if you can report it to the firmware development Team. I am available to debug it more for fixing in :)

For now I think its either ICMPv6 echos (Router advertisment) or a DNS problem, which is locally installed on the readynas.

But I have one question: I have a "LeafNets" ethernet device (I think its an ethernet device for leafp2p ) ?

and after spindown issue fixing I got these 4 lines from systemd-journal:

Jan 20 09:10:09 NAS leafp2p[1540]: Get notification
Jan 20 09:10:13 NAS leafp2p[1540]: soap error
Jan 20 09:10:13 NAS leafp2p[1540]: err = SOAP 1.1 fault: SOAP-ENV:Client [no subcode]
Jan 20 09:10:13 NAS leafp2p[1540]: "Name or service not known"
Jan 20 09:10:13 NAS leafp2p[1540]: Detail: getaddrinfo failed in tcp_connect()

But I have NAS replication deactivate...

So 1) Is LeafNets an ethernet device for leafp2p ?

2) leafp2p is for remote Replication only ?

3) Are these critical error messages from leafp2p and why I get these if remote replication isnt activated ?

and thanks for your help in HDD spindown issue mdgm-ntgr kohdee

You can now mark a post that resolved the problem as the solution if you wish.

If you have ever enabled Remote, Replicate or ReadyCLOUD the leafp2p service will be running. Yes the LeafNets adapter is the adapter for this service.

Note sure on point #3. Is your NAS connected to the internet? If you set a static I.P. did you remember to specify the DNS server addresses?

Thanks mdgm-ntgr

Point 3: only want to know if these lines are critical errors or not :)

Jan 20 09:10:09 NAS leafp2p[1540]: Get notification
Jan 20 09:10:13 NAS leafp2p[1540]: soap error
Jan 20 09:10:13 NAS leafp2p[1540]: err = SOAP 1.1 fault: SOAP-ENV:Client [no subcode]
Jan 20 09:10:13 NAS leafp2p[1540]: "Name or service not known"
Jan 20 09:10:13 NAS leafp2p[1540]: Detail: getaddrinfo failed in tcp_connect()

---

@MisterT87 wrote:

Thanks mdgm-ntgr

 

Point 3: only want to know if these lines are critical errors or not :)

Jan 20 09:10:09 NAS leafp2p[1540]: Get notification
Jan 20 09:10:13 NAS leafp2p[1540]: soap error
Jan 20 09:10:13 NAS leafp2p[1540]: err = SOAP 1.1 fault: SOAP-ENV:Client [no subcode]
Jan 20 09:10:13 NAS leafp2p[1540]: "Name or service not known"
Jan 20 09:10:13 NAS leafp2p[1540]: Detail: getaddrinfo failed in tcp_connect()

 

---

They are an indication that your NAS might not be able to reach internet services.  That would affect AV updates, NTP time synchronization, and checks for software updates, not just replicate, remote, and readycloud.

So you should confirm that the NAS can reach the internet.  Manually doing a "check for updates" is one way.  If you happen to be using static IP addresses, check the DNS server config (since it is most frequently overlooked), but also the subnet mask and gateway.

Thanks StephenB thats it!

There was a missing DNS entry. fixed it and now all is working fine

Again thanks to you for great help :)

Have a nice day!