NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
XS508M Crashed. No Longer Have Any Confidence in This Device
My XS508M stopped working whilst I was away for work which is when I need my office network working reliably so caused me a lot of issues. Basically I use this as my main switch. My WAN router and my NAS (which hosts a number of key services) connect to it. All other switches, servers and clients are off that switch, so the loss of that switch meant all other LAN traffic stopped, as well as no incoming internet traffic which was what knackered me. When I returned and started my investigation, I was careful not to do anything that might lose the root cause so I fired up a laptop (no DHCP), set a static IP and then tried to connect to different appliances/devices. It was clear the XS508M was dead, anything connected to it was down and as it is unmanaged, nothing else I could do but unplugging/reconnected the AC lead, which immediately resulted in the entire LAN coming back to life and being contactable from the WAN once more. Since it is unmanaged I obviously cannot get any logs, cannot upgrade/downgrade the FW, what else can I do to determine the cause? Has anyone has this with a XS508M? Is this an unreliable switch? If it is not totally reliable, I will need to replace it, what a waste of money. What else should I use?ProBE with OS 6.4.2 locks up on Scrub
I have a ProBE, upgraded to an E7500 processor, 4GB of RAM, and OS 6.4.2. It has 6 3TB WD red's and a LOT of files filling it about 75%. It is my media drive, but does not run any media server software and ReadyDLNA is disabled. It does run DDClient, but nothing else that runs continuously. It is scheduled to do a Scrub every Tuesday. Twice now, it has completely locked up somewhere during the scrub. The start of the scrub is logged, the end is not. Normally, it takes about 14 hours to complete. By "locks up", I mean no RAIDar or other presence on the network and no display if the power button is pushed. A hard reset does gets it going again. One scrub did successfully complete between the two that did not. I just started a manual one, will see how that goes. So far, so good. Anything that I should look for as to a reason? No other clues in the logs I can find.
