Netgate sg-2440 bricked after update from 2.4.3 to 4.4.4



  • I've run the system/updates to update 2.4.3 to 4.4.4 on a sg-244UI0. Installation appeared to go well in Web UI, but the box never came back up after a reboot.
    I've connected to the (mini USB serial) terminal and get no response.
    I've downloaded community versions of 2.4.4, both the ADI and AMD64/serial and have flashed those onto USB sticks.
    When I power cycle the 2440 with either USB stick plugged in, I see nothing at all on the terminal.
    Yes, I know the 2.4.3 to 2.4.4 upgrade takes a while. It's been hours.
    Yes, I know how to connect to the terminal.
    Any ideas? You think they'd have tested this on Netgate hardware.



  • 2.4.4 definitely works via the ADI image. I've done it many times. If your status light doesn't stay solid red, I'm going to have to ask that you check the terminal settings. Also verify the image was written correctly. If the status light stays solid red, contact support.



  • I've seen before that upgrading bricks a Netgate unit. I have a suspicion though that it happens because the unit was about to brick anyway, maybe because the flash memory is going bad?

    I've also seen the flash memory go bad and adding your internal card brings it back to life.

    You should at least see the bios when it boots. If not then it's likely bricked.

    The Netgate hardware is definitely not quality stuff so I hope its under warranty. Also maybe it's the clock chip issue. https://www.netgate.com/blog/clock-signal-component-issue.html

    Sorry to hear about the issues but if it's under warranty open a ticket with them.


  • Rebel Alliance Netgate Administrator

    Hello, Please open a ticket at https://go.netgate.com, Please provide the serail number of the unit that is not working, we will be able to take a look see what we can do to help you out.

    In reference to: You think they'd have tested this on Netgate hardware.
    We do, extensively, it sounds like there might have been a physical issue causing this problem (bad RAM, storage or other board level component died).