NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNas 312 Firmware Upgrade Failing
Hi,
I have an issue with our ReadyNas 312. It's currently running firmware 6.1.6, and seems to have dropped off our domain. So when I logged in, I noticed a popup saying there is a firmware upgrade to 6.4.0. So I clicked on the 'Update' button. The update looked ike it downloaded OK, but then gave an error saying "Cannot write file". So I tried a manual update, downloaded Firmware 6.4.0 to my laptop from http://kb.netgear.com/app/answers/detail/a_id/29938 then unzipped it, and uploaded the .img file. The readynas said it would upgrade after a reboot, and asked if I wanted to reboot now. I said yes. I then waited 15 minutes, but the ReadyNas never comes back up. I've opened a cmd prompt, and ping the IP, but the network never comes back up. I have to perform a hard reboot, the ReadyNas then comes back, but on the same old firmware. I've tried again, running a constant ping test, I can see the ReadyNas reboots, as the ping stops, but then it never returns, until you do a hard reboot again.
Anyone have any ideas? I'm unable to performt he firmware upgrade either automatically or manually!
Thanks
Ben
You may wish to copy it to the data volume first (just in case the information in that log file turns out to be needed to troubleshoot this problem). Then it should be fine to delete the copy on the root volume.
Once the space on the root volume is freed up you should be able to update the firmware.
3 Replies
Replies have been turned off for this discussion
Think I found a possible cause, looking at the log screen I see "Volume: System volume 'root' usage is 100 %. This condition should not occur in normal conditions. Please contact technical support.". If I use Putty to SSH in, and i run du -sh * I can see 'log' dir is 3.1Gb in size. Going down into var/log/samba I can see log.winbindd.old is 3.1Gb is size. Now, the question is, can I safely delete this file?
You may wish to copy it to the data volume first (just in case the information in that log file turns out to be needed to troubleshoot this problem). Then it should be fine to delete the copy on the root volume.
Once the space on the root volume is freed up you should be able to update the firmware.
Moved it to the data share, which seemed to fix the issue. I rebooted, then performed the firmware upgrade to 6.4.0 successfully.
I downloaded the log.winbindd.old file to my laptop, then tried to open it, but 3.1gb txt files don't play well with notepad or notepad++. Had to use gsplit to split it into 31x 100mb files. Below is a sample of the contents. Every file from 1-31 have pretty much the same 2 lines, timed a few miliseconds apart. The main issue looks to have started @ 2015/10/30 17:34:23 through to 2015/10/30 19:26:11
[2015/10/06 10:01:06, 0] ../source3/winbindd/winbindd.c:1415(main)
winbindd version 4.0.14 started.
Copyright Andrew Tridgell and the Samba Team 1992-2012
[2015/10/06 10:01:06.657377, 0] ../source3/winbindd/winbindd_cache.c:3179(initialize_winbindd_cache)
initialize_winbindd_cache: clearing cache and re-creating with version number 2
[2015/10/06 10:11:54.069186, 0] ../lib/util/util_tdb.c:343(tdb_chainlock_with_timeout_internal)
tdb_chainlock_with_timeout_internal: alarm (40) timed out for key domaincontroller1.domain.net in tdb /var/lock/samba/mutex.tdb
[2015/10/06 10:11:54.069713, 0] ../source3/winbindd/winbindd_cm.c:877(cm_prepare_connection)
cm_prepare_connection: mutex grab failed for domaincontroller1.domain.net
[2015/10/06 10:13:38.877342, 0] ../source3/libsmb/cliconnect.c:1948(cli_session_setup_spnego)
Kinit failed: Clock skew too great
[2015/10/30 10:46:59.436600, 0] ../source3/winbindd/winbindd.c:993(winbindd_listen_fde_handler)
winbindd: Exceeding 200 client connections, no idle connection found[2015/10/30 17:34:23.067654, 0] ../source3/winbindd/winbindd.c:993(winbindd_listen_fde_handler)
winbindd: Exceeding 200 client connections, no idle connection found
[2015/10/30 17:34:23.067869, 0] ../source3/winbindd/winbindd.c:835(new_connection)
Faild to accept socket - Too many open files
[2015/10/30 17:34:23.068211, 0] ../source3/winbindd/winbindd.c:993(winbindd_listen_fde_handler)
winbindd: Exceeding 200 client connections, no idle connection found
[2015/10/30 17:34:23.068435, 0] ../source3/winbindd/winbindd.c:835(new_connection)
Faild to accept socket - Too many open files
[2015/10/30 17:34:23.068760, 0] ../source3/winbindd/winbindd.c:993(winbindd_listen_fde_handler)
winbindd: Exceeding 200 client connections, no idle connection found.....
[2015/10/30 19:26:11.933531, 0] ../source3/winbindd/winbindd.c:835(new_connection)
Faild to accept socket - Too many open files
[2015/10/30 19:26:11.933885, 0] ../source3/winbindd/winbindd.c:993(winbindd_listen_fde_handler)
winbindd: Exceeding 200 client connections, no idle connection found
[2015/10/30 19:26:11.934122, 0] ../source3/winbindd/winbindd.c:835(new_connection)
Faild to accept socket - Too many open files
[2015/10/30 19:26:11.934459, 0] ../source3/winbindd/winbindd.c:993(winbindd_listen_fde_handler)
winbindd: Exceeding 200 client connections, no idle connection found
[2015/10/30 19:26:11.934681, 0] ../source3/winbindd/winbindd.c:835(new_connection)
Faild to accept socket - Too many open files
[2015/11/02 09:30:07, 0] ../source3/winbindd/winbindd.c:1415(main)
winbindd version 4.0.14 started.
Copyright Andrew Tridgell and the Samba Team 1992-2012
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
