Netgate SG-2440 dead after 2.4.5 RELEASE upgrade
-
Looks like this isn't just related to the SG-2440 model. :(
https://forum.netgate.com/topic/151681/sg-1100-dead-after-2-4-5-release-upgradeThis has happened to me twice now with these updates. Thankfully I was prepared this time.
Console output gets to:
Boot: F1
and then nothing.
I highly recommend verifying a) that you have console access to the router before upgrading (because I needed to download drivers -- over the internet).
and b) having a copy of the firmware handy in case you need to reflash. Apparently one needs to create a ticket before getting this so, I'm not sure how that would work exactly when there hasn't officially been a problem yet.
-
Hmm, that's not any sort of failure mode I'm aware of. Usually if it hangs there it's because the console baud rate is mismatched. It will show Coreboot and bootloader at 115200 but switches to whatever baud it configured at that point.
You can open a ticket to request firmware at any time either directly at https://go.netgate.com/ or by emailing support@netgate.com.
We will usually come back to you very quickly though right now support is exceptionally busy.Steve
-
My SG-2220 came up just fine. Im not sure that the two models you list are similar enough to share much in the way of their design.
I will say that I did update to-
Current Coreboot Version
01.00.00.17the day before I upgraded the box to 2.4.5
-
I have two SG-2440's and swapped them without making any changes to terminal settings and putty worked fine, so I'm fairly confident it's not related to the baud rate (1152000) choice.
Also, holding reset to restore factory settings on the unit did not work -- the lights would never go off. As I understand it, resetting doesn't happen until fairly deep into the boot, so if it's not booting, I would expect the reset not to work. Testing with my other SG showed that this worked as expected.
I did file a ticket, got access to the firmware, re-flashed the device, and booting works normally again.
Who knows what happened -- one of the things I do before ever updating my NAS is to reboot it first to make sure that it comes up before mucking with the updated software because sometimes things break in-between boots and it makes troubleshooting easier. Perhaps giving that advice (and me actually following it) would help rule out this possibility here.
I'm thankful it's possible to re-flash these suckers!
-
I'm sorry you had a bad experience with that upgrade. I'm glad you were able to resolve it though.
Rebooting before upgrading is in our upgrade guide. We do try to link to that as much as possible.
https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html#pre-upgrade-rebootSteve
