NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
PWS442
Jan 11, 2024Guide
ReadyNAS RN314 Constant activity
I have a ReadyNAS RN31400 with 4 8TB WD drives. Latest firmware: 6.10.8. Purchased in 2014. It used to chatter constantly, but in March 2022, I disabled Plex, and it stopped. Was very happy until thi...
StephenB
Jan 11, 2024Guru - Experienced User
PWS442 wrote:
I've yet to disconnect it from the network.
A useful next step.
Do you have any cloud services enabled? (for instance ReadyCloud)? ReadyCloud should be disabled, since Netgear took the service down. I have seen a couple of logs recently that were flooded with errors from the ReadyCloud client on the NAS.
Do you have any ports forwarded to the NAS in your router?
PWS442
Jan 11, 2024Guide
Thank you sir.
Turns out that I was signed in to ReadyCloud. While I just turned it off, I didn't turn it on recently, and the NAS was behaving itself for 21 months prior to Dec 25, 2023. And, I noticed nothing in the Logs.
I do not have any port forwarding going on, AFAIK.
FWIW, I took a snapshot of the last 30 minutes. I have been on my wi-fi MacBook Air, talking to the external drive hooked up to my Mac Mini. (Disabling ReadyCloud did not seem to impact the noise coming from the NAS.)
The pattern just seems odd to me.
Thanks again.
- StephenBJan 11, 2024Guru - Experienced User
PWS442 wrote:
Turns out that I was signed in to ReadyCloud. While I just turned it off, I didn't turn it on recently, and the NAS was behaving itself for 21 months prior to Dec 25, 2023. And, I noticed nothing in the Logs.
FWIW, you couldn't have actually been signed into ReadyCloud because Netgear took down the service last summer.
Look in systemd-journal.log The errors I've seen look like this:
Jan 09 19:23:07 XXXXXXX leafp2p[2285]: "Name or service not known" Jan 09 19:23:07 XXXXXXX leafp2p[2285]: Detail: getaddrinfo failed in tcp_connect() Jan 09 19:23:12 XXXXXXX leafp2p[2285]: SOAP 1.1 fault: SOAP-ENV:Client [no subcode]
leafp2p is the VPN technology that was used by ReadyCloud.
PWS442 wrote:
Disabling ReadyCloud did not seem to impact the noise coming from the NAS.
Try rebooting the NAS. If that makes no difference then maybe disconnect it from the network.
PWS442 wrote:
I do not have any port forwarding going on, AFAIK.
Best to check the router settings, and make sure. Also, if you have uPNP enabled in your router, then turn it off.
- PWS442Jan 11, 2024Guide
1- ReadyCloud did say I was signed in. I turned it off.
2- where is systemd-journal.log?
3- I restarted the NAS at 4:30 this morning, just to see if things quieted down. They did not.
4- No Port Forwarding/Triggering on Router
5- UPnP was enabled. FMFBS but I think it should be on? Router can find things?
But I turned it off, and am going to reboot the NAS, as I still have the one minute on/off operation activity cycle still.
Thanks again.
- StephenBJan 11, 2024Guru - Experienced User
PWS442 wrote:
2- where is systemd-journal.log?
In the log zip file (which you download from the logs page in the web ui). What you see on the web page is a small fraction of what is logged.
PWS442 wrote:
5- UPnP was enabled. FMFBS but I think it should be on? Router can find things?
UPnP in the router allows any device on your home network to create their own port forwarding rules (with no administration on your part). So it does create a big security risk, and I recommend disabling it.
It has other uses for client devices (DLNA uses it for example). But disabling it in the router doesn't prevent devices on your network from using it.
PWS442 wrote:
1- ReadyCloud did say I was signed in. I turned it off.
Yeah I know. But you can't really be, since the service is shut down. If you for example click on the "Leave" control, you'll get an DNS error because the NAS can't find the cloud server.
PWS442 wrote:
3- I restarted the NAS at 4:30 this morning, just to see if things quieted down. They did not.
It would be good to figure out what is happening. The clatter might not be network-related - a failing disk is also a possible cause.
If you like, you can send me a link to the full log zip via private message (PM). You'd do that using the envelope icon in the upper right of the forum page. First upload the full zip to the cloud (dropbox, google drive, etc). Then get a lnk to it - making sure that anyone with the link can download it. Then include the link in the PM.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!