NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Keep getting NETWORK CHANGED message since upgrading to 6.9.0
Yesterday I upgraded the firmware on my RN 316 to the latest firmware 6.9.0. Since upgrading I have noticed that I keep getting the words NETWORK CHANGED on the NAS display which will then change to ...
Thanks for the detailed information. We are now able to duplicate the issue using a Nighthawk S8000 switch. After updating the firmware to the version I mentioned earlier, the problem went away. You can now download 6.9.1-T119 here, and it should resolve the issue. Please confirm if it works for you.
Further to Sandshark reply, I changed the NAS to DHCP this morning just to see if that would make any difference.
2 minutes into a large data transfer and again "NETWORK CHANGED" "No IP Address" "192.168.0.22"
There is a DEFINITE problem with OS 6.9.0. It is not my configuration causing this as I have changed my configuration to what you suggested.
Can someone PLEASE flag this up to the support people to investigate. I have a second RN 316 server that is awaiting a firmware upgrade and that is not going to happen until this is resolved.
I should know not to upgrade to .0 firmware updates. I was bitten on the bum recently with iOS upgrades on my watch, iPads and iPhones where none of them work correctly even after three software patches.
do you have shell-access to the box?
I did see link up/down alot in my dmesg.
If you can login to it, can you type 'dmesg -T' in it and see if the timestamps does tell you anything fun?
I have not started troubleshoot it yet, but, it might be a bug in the linux-kernel that is in use, but im not sure yet.
but from what I can see in my own logs, it seem like the OS thinks that the network interface is switching between up and down, that might explain your problems as well as my own.
// T
Tinyhorns I don't have shell access, but from what I have seen of your problem above, I'd say it is a similar one to mine. It is like there is something in this firmware release that is making network connectivity reset momentarily and then restart whenever disk access is initiated - hence the "No IP Address" message I get on the NAS display, which then changes to the MAC assigned IP of "192.168.0.22". It is annoying that nothing appears in the normal NAS logs which are viewable via the normal control panel.
We cannot be the only two people having this sort of problem and it is pretty annoying that there doesn't seem to be anyway of speaking to Netgear support people without having a paid support package.
amrob2 It seems like I have the option to use "chat-support" during office-hours on my product still.
I will try and get their attention on monday if they do not spot this in here first.
Imho, this is clearly related to the 6.9.0 upgrade, and hopefully it this will get to their attention, they can start looking at it.edit: I would not upgrade your 2nd ReadyNAS just yet mate.
// T
Dont't worry Tinyhorns my second NAS will most certainly not be receiving firmware update 6.9.0 :smileytongue:
I must make a point of never installing .0 firmware updates in future as they are the ones that usually are buggy. I will always wait for the .x releases which will usually contain the fixes.
Still, it coule be worse. This could be apple and we could be discussing ios 11 which has had 3 software patches so far which have all failed to addres some of the serious bugs in it :smileylol:
amrob2 wrote:...
We cannot be the only two people having this sort of problem and it is pretty annoying that there doesn't seem to be anyway of speaking to Netgear support people without having a paid support package.
Had the same problem after I updated two RN314s. One didn't develop the problem (so far), while one did. I tried the usual --- changed cable, switched ports, switched switches using different ports ... nothing worked. Originally using DHCP, but using static IP didn't solve the problem either.
I reinstalled the 6.9.0 firmware and that seemed to have fixed the problem ... for now. A backup (to the other RN314) is scheduled later today, so I'll see how that goes.
I tried to reapply the 6.9.0-image again.
But, after putting som load on the box, same error as before.
So, it did not help for me.
Edit: MD5 (ReadyNASOS-6.9.0-x86_64.img) = ef5899fc20c48270ac149bdf8d498536 <-- Image currently in use.
// T
[Mon Oct 30 17:24:47 2017] bond0: link status definitely up for interface eth0, 1000 Mbps full duplex [Mon Oct 30 17:24:47 2017] bond0: now running without any active interface! [Mon Oct 30 17:24:47 2017] bond0: link status definitely up for interface eth1, 1000 Mbps full duplex [Mon Oct 30 17:24:47 2017] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready [Mon Oct 30 17:25:18 2017] Adjusting tsc more than 11% (8932621 vs 8751289) [Mon Oct 30 17:25:23 2017] nfsd: last server has exited, flushing export cache [Mon Oct 30 17:25:23 2017] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [Mon Oct 30 17:25:23 2017] NFSD: starting 90-second grace period (net ffffffff88f13980) [Mon Oct 30 17:34:03 2017] e1000e: eth0 NIC Link is Down [Mon Oct 30 17:34:03 2017] e1000e 0000:01:00.0 eth0: speed changed to 0 for port eth0 [Mon Oct 30 17:34:03 2017] bond0: link status definitely down for interface eth0, disabling it [Mon Oct 30 17:34:03 2017] bond0: first active interface up!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
