NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Ready NAS 104 Crashes when changing Network settings putname+14, kfree+168
Seem to be having trouble changing my network settings, currently have 2 Nics teamed and set to use Transmit Load Balancing (Layer 2), initially I was trying to just change the MTU size, but when I do so the NAS seems to become unresponsive and displays error putname+14, power button does nothing and the only way to get it back is to pull the power.
Following this I decided to delete the bond entirely, same thing happened, in fact have tried changing various setting on it now and each seems to have the same effect albeit a different error ocasionally such as putname+14, kfree+168 and a couple of others I didnt note at the time.
None of the changes take effect after restarting. Current OS version was 6.9.4 (Hotfix 1), have since tried upgrading to latest beta to see if this resolved the issue, It did not.
Anyone seen this before or have a solution?
jgisin wrote:
I have this same issue. I'm trying to delete the bond0 so I can create a new one and I get kfree+168 on the LCD. Same thing if I just try to modify the bond. WTF? How about some reliefe from this nonsense?
I am running the latest 6.10.2
Hopefully it's on the list of things to be fixed.
One thing you could try is doing an OS reinstall from the boot menu. That will
- reset the network to default settings (no bonding, MTU=1500, dhcp)
- change the admin password back to password
- disable volume quota (can be changed back on the volume settings wheel)
See pages 28-29 here: http://www.downloads.netgear.com/files/GDC/READYNAS-100/ReadyNAS_%20OS6_Desktop_HM_EN.pdf
FWIW, the RN100 series performance is mostly limited by it's relatively slow processor and memory. There's not a lot of performance gain to be had with bonding. I'd just use it with one ethernet connection myself.
27 Replies
Replies have been turned off for this discussion
Dremscape wrote:
None of the changes take effect after restarting. Current OS version was 6.9.4 (Hotfix 1), have since tried upgrading to latest beta to see if this resolved the issue, It did not.
6.9.5 has been released for about a week now - so if you are running beta or release candidate you should update it.
If you are running the 6.10 beta, then stay with it - you aren't able to downgrade back to 6.9.x.
Dremscape wrote:
Following this I decided to delete the bond entirely, same thing happened
Perhaps also try removing one of the ethernet cables.
If you are on the 6.9.x branch, maybe also try 6.9.3 and see if that changes the behavior.
Oddly 6.9.5 didn't show up for me under stable release which is why I went for the Beta, unfortunately the 6.10 one so no way back.
Have already tried unplugging cables but seems to make no difference, found a similar issue on an old thread (Link bellow) around bonded nics but creating rather than removing or altering, seemed to be fixed for them in 6.9.3, wondering if the issue may of crept back in but gone unnoticed or be linked to any fix that may of been implemented for this.
I have exactly the same issue, i am trying to Bond Eth0 and Eth1 and everytime i make the link it locks up solid and gives me the kfree+168, i had this on 6.9.4 and now on 6.9.5 exactly the same. I have 4*4gb drives raid 10.
Have now updated to latest stable build 6.10.0, yet the issue still remains, any attemt to change the NIC settings to anything else results in it locking up and erroring.
Hi Dremscape,
Can you download the system logs then provide it to us? We will further what is causing the error.
You may upload it to Google Drive then send to me the download link via PM (private message).
Regards,
I have this same issue. I'm trying to delete the bond0 so I can create a new one and I get kfree+168 on the LCD. Same thing if I just try to modify the bond. WTF? How about some reliefe from this nonsense?
I am running the latest 6.10.2
jgisin wrote:
I have this same issue. I'm trying to delete the bond0 so I can create a new one and I get kfree+168 on the LCD. Same thing if I just try to modify the bond. WTF? How about some reliefe from this nonsense?
I am running the latest 6.10.2
Hopefully it's on the list of things to be fixed.
One thing you could try is doing an OS reinstall from the boot menu. That will
- reset the network to default settings (no bonding, MTU=1500, dhcp)
- change the admin password back to password
- disable volume quota (can be changed back on the volume settings wheel)
See pages 28-29 here: http://www.downloads.netgear.com/files/GDC/READYNAS-100/ReadyNAS_%20OS6_Desktop_HM_EN.pdf
FWIW, the RN100 series performance is mostly limited by it's relatively slow processor and memory. There's not a lot of performance gain to be had with bonding. I'd just use it with one ethernet connection myself.
- Thank you. I will try your suggestion and report back.
Does the OS reinstall affect any volume, share, user or sharing protocol settings?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
