NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
roger_armstrong
Apr 13, 2012Aspirant
ReadyNAS loses network connectivity
We're using a ReadyNas 6 Ultra Plus for backup of ESX servers (using ghettoVCB with the ReadyNAS mounted as an NFS datastore) and a ReadyNAS Ultra 4 plus as an NFS datastore. Unfortunately, both ReadyNAS devices occasionally (every few months) disappear from the network (i.e. become unreachable via NFS, http, icmp etc). The disks are OK and if the device is rebooted then everything is fine again.
This is bad when its being used for backup, but even worse when its an NFS datastore.
To detect and automate the recovery, I installed monit (apt-get install monit) and configured it to ping the default gateway to check if all is OK with the network - if it fails several times in a row, it reboots the ReadyNAS. This happened last night during a backup.
Its pretty alarming that both ReadyNAS devices just go offline like this. Anyone else experiencing such issues?
Both are running 4.2.19 firmware.
This is bad when its being used for backup, but even worse when its an NFS datastore.
To detect and automate the recovery, I installed monit (apt-get install monit) and configured it to ping the default gateway to check if all is OK with the network - if it fails several times in a row, it reboots the ReadyNAS. This happened last night during a backup.
Its pretty alarming that both ReadyNAS devices just go offline like this. Anyone else experiencing such issues?
Both are running 4.2.19 firmware.
17 Replies
- StephenBGuru - Experienced UserI agree it is strange. But it might be interesting to turn off the spin-down for a couple days, and see if the symptoms change.
- tfierens1AspirantI'm not spinning down my drive and it still occurs.
As for slow access, I don't have that problem! It just can't be accessed!! In case you are wondering if I'm not patient enough and wait for the control panel to respond... It is not the case as I usually go immediately to windows explorer and try to access a folder and it throws me an error that the specific share is not available. I then open a command line window and then try to ping my Nas drive and as expected th ping times out.
The only option I'm left with is a reboot via th front button of the NAS.
I can open th control panel on all browser i.e IE, chrome, Firefox, safari on windows/iPhone and iPad. So that part is good.. Now all that's needed is for th drive to say connected!!! :x :x :x
As mentioned, I have the very latest firmware .21 - StephenBGuru - Experienced User
What model (your signature says x6, but of course that won't run .21).tfierens wrote: As mentioned, I have the very latest firmware .21
I suggest that you should fork onto a different thread. Your symptoms seem different from kakemann81's. In his case, the NAS is still accessible from Windows Explorer, in your case the NAS is totally non responsive. - kakemann81Aspirant
StephenB wrote: I agree it is strange. But it might be interesting to turn off the spin-down for a couple days, and see if the symptoms change.
Thank you for your advice.
I will try it out, and see what happens. - tfierens1AspirantMy model is the readynas ultra 6
- tfierens1AspirantMy model is the readynas Ultra 6.
In regards to 4.2.21 not applying, unless I'm missing something here, this link seems to say otherwise http://www.readynas.com/?p=6469. Now I'm going to go reboot my drive as I cannot access it at this time but when I applied 4.4.21, it did say "applied successfully."... Now whether or not it did is another story. One thing I did notice is that I had to download this manually as it was t appearing via the automatic update section.
I don't think I'm in the wrong thread as the title of this thread is "losing network connectivity" which exactly what is happening to me and while the described behaviour might be slightly different they are still very similar because a) it does lose network connectivity, b) it seems to happen when copying large files and c) it has only started to happen since upgrading to 4.2.20.
Thanks. - StephenBGuru - Experienced UserIt is really hard to give troubleshooting suggestions to two different people on the same thread. Even if you are staying on topic, it is difficult for the rest of us to sort through what you have done/not done, what kakemann81 has done/not done, and what outcomes you saw. It would be simpler if one of you starts a new thread.
Related Content
NETGEAR Academy

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