NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
FVS316G Frequent Rebooting
Greetings,
After close to three years of mostly trouble-free use, our FVS318G has started rebooting several times a day, obviously causing frequent network drop-outs. Once this started happening, but prior to enabling the logging, I was peridocally checking the Router Statistics and I haven't seen Up Time values more than a few hours.
We're not using the VPN functions, and connection and traffic-wise the unit should be relatively unstressed, since there's only a dozen or so devices active on the LAN, and not much of the traffic is going to/from the WAN.
We're running the 3.1.1-18 (latest/last) firmware (and have been since November of 2014).
I've started looking at the firewall logs, but other than the fact that it's noting the reboot, I'm not seeing an obvious cause. Apparently the log is automatically cleared after it's emailed, so here's the log that contains a reboot:
2016 Mar 25 11:39:25 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:39:25 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:39:25 [FVS318g] [dhcpd] Wrote 2 leases to leases file.
2016 Mar 25 11:39:29 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:39:29 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:39:29 [FVS318g] [dhcpd] Wrote 2 leases to leases file.
2016 Mar 25 11:39:34 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:39:34 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:39:34 [FVS318g] [dhcpd] Wrote 2 leases to leases file.
2016 Mar 25 11:39:38 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:39:38 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:39:38 [FVS318g] [dhcpd] Wrote 2 leases to leases file.
2016 Mar 25 11:39:39 [FVS318g] [dhcpd] DHCPDISCOVER from 8c:3a:e3:60:48:e6 via eth0.1
2016 Mar 25 11:39:40 [FVS318g] [dhcpd] DHCPOFFER on 192.168.1.111 to 8c:3a:e3:60:48:e6 (android-47f68eb15e1e3bd9) via eth0.1
2016 Mar 25 11:39:40 [FVS318g] [dhcpd] DHCPREQUEST for 192.168.1.111 (192.168.1.1) from 8c:3a:e3:60:48:e6 (android-47f68eb15e1e3bd9) via eth0.1
2016 Mar 25 11:39:40 [FVS318g] [dhcpd] DHCPACK on 192.168.1.111 to 8c:3a:e3:60:48:e6 (android-47f68eb15e1e3bd9) via eth0.1
2016 Mar 25 11:39:42 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:39:42 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:39:42 [FVS318g] [dhcpd] Wrote 2 leases to leases file.
2016 Mar 25 11:39:47 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:39:47 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:39:47 [FVS318g] [dhcpd] Wrote 2 leases to leases file.
2016 Mar 25 11:39:51 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:39:51 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:39:51 [FVS318g] [dhcpd] Wrote 2 leases to leases file.
2016 Mar 25 11:39:55 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:39:55 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:39:55 [FVS318g] [dhcpd] Wrote 2 leases to leases file.
2016 Mar 25 11:40:00 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:40:00 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:40:00 [FVS318g] [dhcpd] Wrote 2 leases to leases file.
2016 Mar 25 11:40:04 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:40:04 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:40:04 [FVS318g] [dhcpd] Wrote 2 leases to leases file.
2016 Mar 25 11:40:08 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:40:08 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:40:08 [FVS318g] [dhcpd] Wrote 2 leases to leases file.
2016 Mar 25 11:40:13 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:40:13 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:40:13 [FVS318g] [dhcpd] Wrote 2 leases to leases file.
2016 Mar 25 11:40:17 [FVS318g] [dhcpd] lease 192.168.1.110: no subnet.
2016 Mar 25 11:40:17 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:40:17 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:40:17 [FVS318g] [dhcpd] Wrote 1 leases to leases file.
2016 Mar 25 11:40:21 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:40:21 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:40:21 [FVS318g] [dhcpd] Wrote 1 leases to leases file.
2016 Mar 25 11:40:27 [FVS318g] [root] [SYSTEM START-UP] System Rebooted
2016 Mar 25 11:41:03 [FVS318g] [dhcpd] DHCPINFORM from 192.168.1.117 via eth0.1
2016 Mar 25 11:41:03 [FVS318g] [dhcpd] DHCPACK to 192.168.1.117
2016 Mar 25 11:41:15 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:41:15 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:41:15 [FVS318g] [dhcpd] Wrote 1 leases to leases file.
2016 Mar 25 11:41:21 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:41:21 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:41:21 [FVS318g] [dhcpd] Wrote 1 leases to leases file.
2016 Mar 25 11:41:56 [FVS318g] [dhcpd] Wrote 0 deleted host decls to leases file.
2016 Mar 25 11:41:56 [FVS318g] [dhcpd] Wrote 0 new dynamic host decls to leases file.
2016 Mar 25 11:41:56 [FVS318g] [dhcpd] Wrote 1 leases to leases file.
Thoughts? Any other logging I can enable to help spot the problem?
Hi Herbie555,
So, this could be a hardware issue, I don't see anything in the logs that would tell me this but the log data could be filling the memory causing the reboot. I would look to factory default the router and reconfigure manually. If the reboot still happens reflash the firmware again and see if the rebooting stops. Also, disable any logging period until you have completed the reset and firmware flash.
If you have already done all of this you will need to contact support and seek in-warranty hardware check.
Alex
7 Replies
Hi Herbie555,
So, this could be a hardware issue, I don't see anything in the logs that would tell me this but the log data could be filling the memory causing the reboot. I would look to factory default the router and reconfigure manually. If the reboot still happens reflash the firmware again and see if the rebooting stops. Also, disable any logging period until you have completed the reset and firmware flash.
If you have already done all of this you will need to contact support and seek in-warranty hardware check.
Alex
AlexPe, thanks for following up with me. I wanted to give everything you've suggested a good long try.
Resetting to defaults alone did not solve the issue. Have now reflashed firmware and reset defaults again. Will let this shake out for a few hours.
I'm disappointed with the idea that I might have a hardware problem after only 3 years on a device with no moving parts, but I'll stick with it to see what happens.
Thanks again.
Hi Herbie,
I can understand your frustration with the issue if it does become a hardware issue. More often than not with the Prosafe line of products a configuration entry or two gets corrupted or the device just begins to encounter issues after being in service for a long time. That is why we recommend the factory reset and reconfigure. I remember working on the FVS338 and that being the number 1 resolution for those machines. If that didn't fix it going forward it was definitely a hardware related issue in terms of dropping packets and/or random reboots.
Thanks for giving a try and being patient with this machine.
I hope it continues working in good operationg going forward.
AlexPe
So it looks like a full-reflash and reset to factory defaults did the trick. I'm now looking at Up-time of 4 days, 12-hours, whereas I was rebooting every couple of hours previously.
Thanks much.
Hi Herbie555,
On behalf of AlexPe, you're welcome. :) I'm glad that it is working now.
I encourage you to mark the appropriate reply as the “Accepted Solution” so others can be confident in benefiting from the solution. The Netgear community looks forward to hearing from you and being a helpful resource in the future!Cheers,DaneANETGEAR Community Team
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
