SG-2220-M2 Boot Failure
-
Monster thunderstorm last night with multiple power outages. I woke up to my SG-2220 with the Ethernet lights blinking like normal but not passing any traffic, DHCP was not working. Plugged in a console cable, power cycled, and saw it was not booting. I hope it can be recovered by reloading an appropriate image for this device. This is not the hardware flaw that I experienced a few years ago. Where can I get a good image? Where can I find detailed instructions on the recovery process?
This is all I get when I boot it:
SeaBIOS (version SageBIOS-20170918_115908-localhost.localdomain)iPXE (http://ipxe.org) 00:14.0 C100 PCI2.10 PnP PMM+7FB816D0+7FAE16D0 C100
iPXE (http://ipxe.org) 00:14.1 C200 PCI2.10 PnP PMM 7FB816D0 7FAE16D0 C200
iPXE (http://ipxe.org) 00:14.2 C300 PCI2.10 PnP PMM 7FB816D0 7FAE16D0 C300
iPXE (http://ipxe.org) 00:14.3 C400 PCI2.10 PnP PMM 7FB816D0 7FAE16D0 C400
Press F12 for boot menu.
/
-
Open a ticket with us to get the recovery image: https://www.netgate.com/tac-support-request
If you press F12 what boot devices do you see available?
Steve
-
@stephenw10
Hi Steve,
Thanks for responding. I found those instructions in another post and opened a support ticket. Downloaded the code and followed the instructions provided. After selecting UFS for file system for legacy BIOS and using BSD partition tables, I was able to get it installed followed by a successful boot. Only disappointment was that I failed to record the device key for the replacement device back in 2020. So my most recent, usable, backup was 3 years ago.
I’m missing a fair amount of firewall rules from the last 3 years but all my VLANs and addressing are in place. It could have been worse.
Boot drive corruption probably happened before the storm. The storm caused power outages longer than the UPS could handle so it forced a reboot of the SG-2220. Who knows. I guess it’s time for an upgrade as well. This has been a great little device. -
If you send me your NDI in chat I may be able to retrieve the device key. You'll still need the encryption password of course.
