NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
upgrade from 6.8.1 to 6.9 disabled eth0,1,2,3
I upgraded my readynas 4220 from 6.8.1 to 6.9.0 and the three onboard ethernet ports are showing DHCP enabled in the gui but do not link to the switch. It seems as if they are administrativly disabled. I have tried factory reset and os reinstall as well as restoring the network configuration from a 4220 with the same configuration (as a matter of fact they are of exactly the same manufacturing run so the motherboards are identical) with no sucess. how can I get the system to rediscover (actually renable) the onboard ethernet ports?
No the interfaces were not bonded.
I was able to solve the problem by executing the following steps:
1) enable ssh access
2) login and su to root
3) ifconfig <interface> down (for each non-functioning interface)
4) restart
5) went directly to ssh before opening Frontview
6) login and su to root
7) ifconfig <interface> up (for each non-functioning interface)
Interface links came up and bi directional data flow started.
8)Frontview correctly displayed the link status and was able to control the links where as before the links stayed down in spite of enabling them in Frontview.
I'm not sure why this worked. A factory reset should have worked as I would think that at first boot after the reset the hardware would be scanned. Without studying the inner workings of frontview its hard to say if it was an O.S. issue, Frontview issue or combination.
We can mark this as problem solved but root cause unknown.
3 Replies
Replies have been turned off for this discussion
Hi scottonaharley!
We had issues reported on ReadyNAS models regarding Network interfaces getting disabled an/or reset after the update.
Were your Eth ports configured as a bond? You may want to check on the Beta FW ReadyNASOS 6.9.1-T129 Beta 2.
Please let us know if this helped.
Regards,
Marc
NETGEAR Community TeamNo the interfaces were not bonded.
I was able to solve the problem by executing the following steps:
1) enable ssh access
2) login and su to root
3) ifconfig <interface> down (for each non-functioning interface)
4) restart
5) went directly to ssh before opening Frontview
6) login and su to root
7) ifconfig <interface> up (for each non-functioning interface)
Interface links came up and bi directional data flow started.
8)Frontview correctly displayed the link status and was able to control the links where as before the links stayed down in spite of enabling them in Frontview.
I'm not sure why this worked. A factory reset should have worked as I would think that at first boot after the reset the hardware would be scanned. Without studying the inner workings of frontview its hard to say if it was an O.S. issue, Frontview issue or combination.
We can mark this as problem solved but root cause unknown.
You might want to reboot the NAS and see if the work-around sticks.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
