NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
SRX5308 non responsive 2-12 seconds LAN/WAN sporadically through day, drops all VPN connections too
I saw a simlar posting from 6/2015 that was not answered and closed "due to inactivity". I have (5) SRX5308 and they all exibit the same issue. In some cases I have RIP protocol enabled and in others I am using the SRX5308 as a standard firewall with a cable modem uplink. Sporatically and completely random and apparently the higher the firmweare version the more often it happens, the router becomes completely non-responsive for 2-12 seconds, and in most cases VPN connections if any are dropped. Weirdly enough, earlier firmware versions may have had entries in the logs about an exception with register values but newer firmware has absolutely nothing in the logs. I replaced the router with a Cisco 1841 router and the problem goes away compltely but obviously my netgear clients cant VPN in. Does not appear to be volume related either as it happens when the traffic is very low as well as when its averaging 20-30 Mbps. I opened a case with netgear but so far they havent any ideas and suggested it could be a device on the network causing a problem. I agree, its the netgear on the network thats causing the porblem. I like the firewall, especially its VPN thougthput but the constant hang even with its short duration prevents me from keeping this device on the network. Any suggestions? and since I suspect many of you will immediately start asking see the notes below: Currently running firmware: 4.3.4-2, also tried 4.3.3-6, 4.3.3-5, and I beleive an earlier one that came on the router when I bought it. 3 routers have VPN configured between them and one is completely stand alone (the one running RIP is stand alone at anothe location) The 3 with VPN are setup with NAT and the RIP is setup "Classical routing" All are configured for IPv4 only One of the 3 with VPN and NAT has a cable modem on WAN 1 and is configured for failover to DSL on WAN 2, the non-resposiveness still impacts WAN and LAN ports The NAT routers have public WAN IP's and private LAN IP's, the RIP one has public WAN and public LAN ip's. None have DMZ's configured The NAT has firewall rules for specific ports from WAN to LAN, no restrictions on outbound, the RIP router has no rules, all in and out permited, working as a router not a firewall. All have "respond to pings on internet ports" enabled All have "enable stealth mode" None have any blocking enabled (UDP or TCP flood) They all have VPN pasthrough checked None have session limits or throughput/bandwidth limits set None have content filtering enabled None have DHCP server enabled Hope that eliminates most initial questions...RN104 inaccessible and displaying btrfs_biomerge_bio_hook+a4 message
Model: RN10400 Firmware: 6.5.1 OS: Windows 10 Environment: Small Office Home Network Installed Storage: 4 x 4TB Hard Drives - 1 volume Issue: NAS unavailable. Hangs during bootup and displays btrfs_biomerge_bio_hook+a4 message in the display window with power light flashing. Does not appear in RAIDar. Performed USB Recovery and same error still occurs during bootup. Looking for next steps...
ReadyNAS NV+ syslogd taking 100% CPU
Hi - I've got a Sparc-based ReadyNAS NV+ that I've had for years. Currently running RAIDiator 4.1.14; 4 x 2TB drives in Raid-X configuration, with about 300G/5.5T free. Lately, the NAS box will become non-responsive during transfers and I have to pull the power, and re-install the OS in order to make it happy. Unfortunately, it's not happy for more than a few hours at a time lately, and I've had to do this once a day or so. By non-responsive, I mean that I can ping it, but not telnet/ssh/frontview, and the front-panel power-button seems to do nothing with a brief press. I've bought its replacement, and am transferring ~ 6TB off it via CIFS, and it is still locking up. This last time, I left top running in a terminal window, which was still updating, though slowly. top - 18:24:58 up 1 day, 1:18, 1 user, load average: 9.04, 9.07, 9.02 Tasks: 67 total, 5 running, 62 sleeping, 0 stopped, 0 zombie Cpu(s): 1.6% us, 98.4% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si Mem: 226352k total, 221632k used, 4720k free, 8976k buffers Swap: 767904k total, 1856k used, 766048k free, 188352k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1571 root 25 0 2128 960 800 R 97.7 0.4 1000:39 syslogd 1066 root 16 0 2992 1168 896 R 2.3 0.5 33:38.83 top 1 root 15 0 2000 592 496 S 0.0 0.3 0:05.09 init 2 root 34 19 0 0 0 S 0.0 0.0 0:00.03 ksoftirqd/0 3 root 10 -5 0 0 0 S 0.0 0.0 0:00.04 events/0 4 root 10 -5 0 0 0 D 0.0 0.0 0:00.03 khelper 5 root 10 -5 0 0 0 S 0.0 0.0 0:00.01 kthread 10 root 10 -5 0 0 0 S 0.0 0.0 0:09.36 kblockd/0 13 root 10 -5 0 0 0 S 0.0 0.0 0:00.01 khubd Syslogd with 1000 minutes of runtime, and 98.4% sys CPU seems very likely to be the cause of my problem. The rootfs wasn't full just prior to the CIFS transfer. nasgul:~# df / -i Filesystem Inodes IUsed IFree IUse% Mounted on /dev/hdi1 128000 11330 116670 9% / nasgul:~# df / -h Filesystem Size Used Avail Use% Mounted on /dev/hdi1 1.9G 642M 1.3G 33% / So, what's my next step here? A factory reset would be more palatable after I'm convinced that my data has been successfully backed up to the new NAS box. What can I do to keep the box up while I do my transfers and verifications? Thanks.