SG-1100 Failes to Boot; No Console Access
-
The power recently went out at my house. After the power was restored, my SG-1100 will not boot. Only the LED on the green circle lights up. It appears that I can connect to the console through USB console (COM port shows in the device manager, and the terminal connection does not have any errors), but no text is output. I have been able to connect to the console on this device in the past.
It appears that the device is bricked. Please tell me that there is another way to recover this device.
-
@curtisj Are you sure you are using the console at the right baudrate? It not that might very well translate into nothing happening. The SG-1100 console runs at 115200 baud by default (8N1)
-
Thanks, @keyser. I have double check. I have the connection set to 115200 baud.
-
@curtisj said in SG-1100 Failes to Boot; No Console Access:
device is bricked
It's possible the file system went bad.
But something like the ROM BIOS, that starts first resists very well against a power failure.
The BIOS should show some text over the console, before it looks for bootable devices ans starts trying to boot from it.The "power brick" is ok ?
-
I am sure the power supply to the device is functioning. I've tried multiple power sources.
-
@curtisj - does this help you at all - it worked for me (twice recently) https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html
I have around a dozen SG-1100 in production, they tend to arrive to me in two's or three's so I configure, and software upgrade them one after another, and ship them out. This gives me a some sort of impression of how consistently they behave. Anyway, the last three arrived with me just over a month ago, and I performed a vanilla out-of-the-box config on them, and then the upgrade to pFsense Plus. One decided to brick itself rather than take the upgrade (so I used the procedure above to recover it) and the other two took the upgrade just fine via the web ui. And now I'm thinking about it, there was one that I stuck a label-printed note onto the top that I was unable to serial console onto it.... Maybe I'll revisit that unit and use the warranty. As I'm supplying them to technically-capable users, but not neccessarily firewall technically familiar, I perform multiple reboots before shipping them out and always keep a copy of the final config. But again in this most recent batch one decided that it would be a brick after being DHL'd to the user. Used the procedure above, and blasted the config back onto it, and it's been fine since.