SG-2440, 2.3.3-RELEASE-p1, unable to standalone boot 2.3.4-RELEASE for reinstall

  • Hi!

    I have an SG-2440 with an Crucial M600 SATA installed and running 2.3.3-RELEASE-p1.  My install has become corrupt (topic=131166), but seems to 'mostly' function but without the ability to update.  As recommended, I have checked the SMART data and the logs do not show errors.  I have also saved my current configuration.

    I would like to fresh-install 2.3.4.  I thought this would be simple, but I am not able to stand-alone boot 2.3.4-RELEASE from a USB.  I obtained pfSense-CE-memstick-serial-2.3.4-RELEASE-amd64.img and used Win32DiskImager to write it to a freshly formatted USB drive.

    From Putty, the boot looks like this (screen-1, attached, not sure how to display it here).  The 2.3.4 release on USB is option #1.  It proceeds to 2.3.4 boot, screen shot #2.  Setting or not-setting option 6 to verbose makes no difference, the boot process stops at screen shot #3.  The text boot log from Putty is also attached.

    Any idea why the stand alone boot is not working?  Is there an easier way to re-install pfsense?

    Thanks for the help on a holiday weekend!!!  :)



  • Galactic Empire

    Hi Gary,

    Make sure your console settings are as described here:

    You are using wrong pfSense image. The image you want to download is labeled Netgate ADI. Its full name is: pfSense-CE-memstick-ADI-2.3.4-RELEASE-amd64.img.gz

    You can download the image from however, if this is a new purchase (or under 1 year old) you can download factory pfSense image from You will first need to activate support for your unit here

  • Ah, what a difference the correct image makes!  :-)

    I'm back up and running now on version 2.3.4.  Something in the 2.3.3 release was mucked up enough that I had to fresh install twice and reformat the M600 SATA on the second re-install.  Pfsense configuration files are amazing!

    One tip for anyone running pfblocker and recovering with a fresh install and configuration file restore:  pfblocker needs a forced update before DNS starts working correctly.  Pfsense was up, but my home network was down until the update completed.

    Thanks Ivor!


  • Moderator

Log in to reply