NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadNA Ultra 4 DHCP fail, connection refused
5 days ago, my ReadyNAS started having network connection issues (coincident with Mirai DDOS attacks?) :P I first noticed when my backup service complained that it hadn't heard from the device in a few days.
RAIDar saw the readynas at 192.168.1.5. When I browsed into the admin page, I didn't see any error logs, but the network showed as disconnected. (Strange, since I was connected through my web browser.) I noticed the mac address was one digit off from what I thought it should have been. The ReadyNAS was also set to pull an address automatically from DHCP. I swear it used to be configured to have a static IP address. I tried to manually configure it to 192.168.1.5, but it wouldn't let me save the changes from the web interface. So I rebooted the ReadyNAS.
When it came back up, the IP address was 192.168.168.168. I read online that this means it wasn't able to get an IP address from DHCP. I swapped ports on the router, swapped cables, tried a direct connection to my PC (I changed my PC's IP address to 192.168.168.100, subnet mask to 255.255.255.0). When directly connected, I can ping the NAS, but I can't connect to the admin page. Chrome returns connection refused. I tried logging in through SSH (root@192.168.168.168) and similarly got a connection-refused response. All the status lights are green in raidar. Now I can't access anything on my NAS.
Running firmware ver 4.2.28. It's been one year since someone from support reinstalled my OS remotely for me. It's pretty much been working without issues, and I haven't made any changes to the system.
Any ideas? Thanks,
Derek
Thanks for the hint, mdgm!
I copied the network/interfaces file from the tech support partition into the normal boot partition and rebooted. Figured a blank configuration file can't be a good thing. Success! The machine pulled a new IP address from DHCP, and I could log back into frontview. :)
From there, I just had to reenable CIFS and reinstall EnableRootSSH. All my shares are accessible again, and crashplan seems to be running and synced up. Although the crashplan log file mentions something about not being able to install an update. This might be what caused my partition to fill up, but it's another problem for another time...
Thanks again, everybody, for all the help!
btw, these are the very helpful instructions I followed to get in through tech support mode and clear out some space in the OS partition.
15 Replies
Replies have been turned off for this discussion
This sounds like it might be a filling OS partition.
One option is to use paid Netgear support (ask for "per-incident" support).
Thanks, Stephen.
Is there another option to log in and delete log files if SSH doesn't work?
Derek
Hi dereky42,
I would agree with StephenB here. the fact that you cannot save any changes on your NAS is one sign of an OS partition being full.
As far as I know that NAS can be booted into tech support and a Level 3 engineer can remotely login to check OS partition.
Regards,
dereky42 wrote:I noticed the mac address was one digit off from what I thought it should have been. The ReadyNAS was also set to pull an address automatically from DHCP. I swear it used to be configured to have a static IP address.
It sounds like, in the midst of all this, you swapped ehternet ports, as eth1's MAC is one more than eth0. And your static adddress would be for the original port. Note that setting a static port on the NAS is not a good idea, at least not unless you also reserve it on your router. If the NAS is off (or offline, as it was here) and another device grabs the static address, problems arrise. Of course, with a reserved address on the router, the static address on the NAS is moot.
This is probably not the main cause of the problem, which likely s a full OS partition, as already diagnosed,but it added to the confusion.
Sandshark wrote:
dereky42 wrote:
I noticed the mac address was one digit off from what I thought it should have been. The ReadyNAS was also set to pull an address automatically from DHCP. I swear it used to be configured to have a static IP address.
It sounds like, in the midst of all this, you swapped ethernet ports, as eth1's MAC is one more than eth0. And your static adddress would be for the original port.
That's a likely explanation. It also applies to address reservation in the router, since that depends on the MAC address of the ethernet port.
Hmm..makes sense. I probably did swap the cable during my debugging.
So I managed to get into tech support mode and clear up 2.6 GB on the OS partition (crashplan had filled the space with update files). On rebooting the machine, raidar still reports 192.168.168.168 as the IP address. Strangely, the front LED panel of the readynas reports 192.168.1.5, which was my original statically-assigned IP. DHCP starts at over 100 on my network, so no conflicts. I can't log in through ssh or the web-based admin interface on either IP. I get a connection refused error. I can, however, ping the machine on 192.168.168.168.
I poked around a bit while I was logged in to see where the network was configured, but I'm not familiar enough with how this system to attempt changing the configuration files manually.
In tech support mode, the readynas did manage to get an IP address through DHCP, so I guess calling tech support is still an option. I really hope that they can fix it without reinstalling the OS. I don't want crashplan to resync 3+ TB of data over the internet again. Ugh...
Thanks for all the help so far. If there's anything else I can try, please let me know.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
