NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN102 disappears from network
I got it this spring, but since I ran into some issues with the setup at the time and didn't have time to troubleshoot it then, I haven't made a concerted effort to setting it up until this last week.
What happens when I try to move stuff from an old external harddrive to the NAS (or from my desktop) is that the NAS stops responding completely after a couple of minutes - sometimes 5 minutes, sometimes 30.
The only way I have found to restart the NAS is to yank the power. (Is the "power button" on the front of the device supposed to be doing anything? It doesn't seem to).
By "stops responding" I mean that I cannot ping it, I cannot access the admin page ("Firefox can't establish a connection to the server at 192.168.1.113." Other browsers - same result).
I can't access the FTP shares or SMB shares that I have set up - the former because nothing responds at that IP. Nmap doesn't find anything alive at that IP on any port, and my router thinks that the device which used to have this IP presently is disconnected. Raidar 6.1 can't find it either.
The IP is statically set to 192.168.1.113 by DHCP from the router that the NAS is connected to (via ethernet. Yes, I've tried replacing the cable). NAS firmware version is 6.5.1, the disks are new and, when I reconnect the power to the NAS, it shows that the disks are healthy. Though it needs a 2+ hour resync every time I do that - although it usually stops responding before those 2 hours have passed.
Sometimes I wonder - and I have seen this hypothesis in other posts as well - that the connection drops when a user tries to write a lot of data at once to the NAS. If that is the case, how do I, as the "administrator" of the family NAS, technically enforce that nobody writes a whole GB-sized folder to the NAS in one go, but dice it up in more digestible chunks?
But on the other hand, I just tried it again, without sending any data at all. This time the NAS disappeared after about 5 minutes: the IP is no longer on the network. My router can't find it, RAIDAR can't find it... I'm not sure if it is still resyncing, and if so, when it expects to be done? I guess I'll continue writing this question tomorrow - it did after all say it expected the sync to take 3(?) hours.
--10 hours later--
The NAS had disappeared again. I did another 'caveman reset', brought it up, and rebooted it gracefully. It kept syncing for about 90 minutes this time before it went offline again.
Since rebooting via unplugging is a particularly bad idea to do, what else can I do to reconnect safely once it does drop from the network? I know of no way of connecting a monitor and other periferials directly to the device, so I have been trying to run it headless - is there a way around that that I'm not thinking of? It has USB ports, but I don't know how to attach a monitor that way...
Other details about setup: The router mentioned is an AT&T/U-verse cable modem of brand "Pace"; my computer runs Fedora Linux - if absolutely needed for troubleshooting I have access to Windows computers as well. My goal for the NAS is to share documents, and to replace the aging USB-connected harddrive that has served as a backup for several years.
The good thing is that I don't have anything on the NAS yet that is not also available elsewhere.
Any ideas?
17 Replies
Replies have been turned off for this discussion
I think if I was exeperiencing your scenario, particularly as you had initial setup problems and have no problem with losing all the data on your disks, I would perform a factory default reset and start again, allowing the unit to seek updates itself, as you cannot install 6.5 directly from some earlier versions
See here how to access the boot menu
BTW this will change the admin password to "password", also you have to press the blue button twice to shut down gracefully
- That is clearly not normal operation. I agree with bedlam1. If you have nothing on it yet, you should do a factory default and start again.
The power being unresponsive prooves that the NAS is crashed. Otherwise, it can be used indeed.
Not everyone that owns a 102 have these issues and of course you could try to troubleshoot it. But if you have notjing on it, factory default would save you time. If you have the same issue straight after factory default, the conclusion would that there is a hardware issue, either chassis or HDDs. If you don't, it was simply software
omicron_persei8 wrote:
That is clearly not normal operation.Totally agree here. A factory reset is a pragmatic thing to try if the data on the NAS is easily restored. BTW, it can also be done from the web ui (system->settings), which is a lot easier than using paper clips and counting blinking leds (esp. since you have no LCD display).
For a while I was seeing my RN102 lock up this way - in my case it was something done by plex (it only happened when plex was scouring the internet looking for metadata). So it would also be relevant to know if you have any apps running.
What model disks are you using? Have you checked the logs for disk errors?
The logs contained nothing about disk errors. And no, I had no apps running.
The disks are WD Blue 1TB Desktop Hard Disk Drive - 7200 RPM SATA 6 Gb/s 64MB Cache 3.5 Inch - WD10EZEX
I have now made a factory reset, and it had been running continuously for maybe 8 hours.
But: then I initialized a file transfer (SMB) and within about 5 minutes the NAS disappeared again.
- Hi. Can you try 6.5.2 Beta?
https://community.netgear.com/t5/ReadyNAS-Beta-Release/ReadyNASOS-6-5-2-T486-Beta-1/m-p/1116020#U1116020Tried the beta. Would that include a factory reset again?
I haven't done that yet, but: after installing 6.5.2 beta and rebooting it stopped responding to FTP after about 3 minutes of file transfers. I can no longer ping it either, so just the firmware upgrade made no difference.
Marking as "solved" - well, at least worked-around. So far it appears that if I limit myself to using FTP, and enforce rate limits (presently 1500kB/s*), it appears to be stable. I have been able to run file transfers continuously for over 15 minutes now, which is a first.
Tomorrow morning I'll experiment with SMB and a Windows system, and my Linux system with NFS, to see if the Linux implementation of SAMBA is to blame. Speaking of that, is there a way to get the NAS to enforce rate limits for other protocols than FTP?
*I also tried 2000kB/s, but then the NAS admin page disabled FTP on me. What is the highest permitted speed? Seems to be somewhere between 1500 and 2000kB/s.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
