Anyone Else Having the SG1100's Drive Fail on Heavy Remote WireGuard Use
Is anyone else having the SG1100's drive fail on heavy remote WireGuard use?
I have had 2 x SG1100's drives fail on me after about 1 year. Those were not all WireGuard, though; IPSec/PPTP at first and later Wireguard later for the second.
I may have the same issue with a 3rd SG1100 unit I purchased after the other 2's warranties expired, and Netgate would not replace them. The first failed and bought a second; the second failed a year later and bought a third.
I am only remote 7 hours away for the next three weeks, so I cannot physically check. Still, I only receive a few Kilobytes after handshake/connecting to WireGuard from remote, and I cannot truly connect. It sort of looks like the same symptoms that the last failure had: very slow drive performance right before full drive failure.
I have been a network security consultant for the past 30 years. This new one has only been connected to a CyberPower UPS, so it isn't a power issue. On the RJ-45 side, WAN is a brand new Netgear Modem, and LAN is a Netgear Switch, then Netgear WiFI, etc.
Please let me know if anyone else is having this issue. I may have to switch to Cisco Firepower 1000, which I really really really do not want to do.
@StokedOnIt You can check write life remaining via : https://docs.netgate.com/pfsense/en/latest/troubleshooting/disk-lifetime.html
Any packages installed? Some heavily recommend an SSD.
Or heavy logging for some reason?
@SteveITS Thanks for replying; there are no packages besides the Wireguard stuff. Should not be doing excess logging and I will check the drive write life. Still, it should last at least 5 years.
@StokedOnIt In a vacuum I’d agree. We haven’t set up many 1100s, specifically, for clients but in general I don’t know that we’ve seen a drive failure [edit: on any model]. Though we do things like turn off logging of the default block rules and often set up a RAM disk.
Mmm, wireguard itself doesn't log much. I wouldn't expect that to affect it by itself.
UPDATE: Well, it looks like this issue is the ISP's (Optimum internet of California) fault. The signal sending from the modem wasn't strong enough to send more than a few KB back per minute. The issue is completely on their system's end, as we are using a brand new DOCSIS 3.1 Netgear modem.