2.3.5_1 update bricked my SG-4860



  • I upgraded my SG-4860 from 2.3.5 to 2.3.5_1 last night and failed to restart.  It's totally dead, the console port is unresponsive and DHCP appears to have stopped, I can't get at the UI at all but the SATA and STATUS leds on on and DC power is on the board.  It doesn't appear to respond to the hardware reset either - this is weird - it seems to be completely hung up.

    It was a plain installation, two WAN connections and a LAN with AutoConfigBackup and Notes installed, just a plain firewall.  Luckily I still had my old Dell in the storeroom (the old firewall that the SG-4860 had replaced) and I was able to get back on-line fairly quickly and load the 2.3.5 release using my Gold membership to restore the configuration.

    Any suggestions for unbricking it?



  • Hi,

    Cable it up, and see here for further instructions : pfSense Forum » pfSense English Support » Official pfSense Hardware - do what the forum user "Ivor" says, for example  : https://forum.pfsense.org/index.php?topic=145551.0



  • Thanks you but the console is completely unresponsive - nothing displays when it is rebooted although the USB driver does load and PUTTY thinks it's connected to COM4 - I've tried every baud rate from 1200 to 256000 and it doesn't even display garbage characters which I would expect if the the baud rate was wrong.  Holding the RESET button down for a minute does nothing.

    The network ports (green/orange if cables are connected) and SATA/STATUS light are all lit when the unit powers up but after about a minute (the normal boot up time) they all turn off.  It's not the power supply, that's good and the USB and internal J5 connectors all have +5V.  Removing the SATA card and WiFi card doesn't help either.

    I'm guessing maybe the BIOS has been corrupted - the CPU heat sink does not get very warm either so it's not doing any work.



  • I sent a support request to Netgate and I very quickly received an RMA to return it to them - I'm impressed, I wasn't expecting such a rapid response.  I'm going to Fed-Ex it back to them.

    The speed at which the RMA came though suggests to me that they think it's a hardware issue, not a software issue.  I'm happy to say that it's out of my hands now and I can get back to my day job - LOL.