Upgrade 2.3.1_1 to 2.3.1_5

  • I have four firewalls that I run.  Today I decided to do the upgrade to the latest.  3 of the 4 went well.  The 4th I had to do a complete rebuild.  When it rebooted a message came up about a interface mismatch and kept starting the command line configuration sequence.  I went through that and then selected option 15 to restore from console.  It restored and showed all my connections and vlans.  When I rebooted I got the same message again about an interface mismatch.  I finally just rebuilt it since I need to put it back into production.

  • Figured it out.  It was a hardware failure.  Lost two network ports on reboot.

  • I always reboot before an upgrade, make sure working before changing something.

  • @smcclos:

    I always reboot before an upgrade, make sure working before changing something.

    Sound strategy, primarily for those using older hardware. Many of the "I upgraded and it broke" posts here and support incidents we get end up being "I rebooted and it broke", not at all related to the upgrade.

  • Eeeexactly.

    I also always reboot AFTER upgrades/sw-installs. Mostly in Windows machines (ensure all changes get cachedout to disk), but in all my 'main' VMs as well, as I always make a backup right after first boot post upgrade/installs.

    When you have done and been around hardware and software enough, you learn that reboots or power-ons is when you beg for everything to work right, or at least boot to something 'fixable' :-P


    I always reboot before an upgrade, make sure working before changing something.

  • I usually just yell "yeeha" and press the update button…
    I live dangerously.

  • Well at least I make sure I have a current config backup first, but often enough (perhaps too much?) I "Yeehaww" it as well.

    So far so good, although I'm amazed at the one or two times older (6-8yrs) boxes have been routing traffic, doing site-site, etc. and after reboot I find all the hardware issues that have been lurking (hard drives, MB's cooked, etc.)

    Definitely not complaining, I think it's a testament to the software that once it's up it'll hang in to bitter end if there's any chance it can continue to run.

  • Hi!

    After applying the 2.3.1_5 update my firewall no longer booted…

    Something about reaching an EOF (End Of File I guess...)..

    I have reinstalled 2.3.1 and it offers me to install 2.3.1_5 again but I am not much tempted to retry the experience (the rescue option didn't work and it looks like the lack of Internet access confused one of my DNSes and it took a while before I realized it so it took me quite a while to have a working system again...).

    Have a nice day!


  • If a basic reinstall of 2.3.1 was done without a hitch, I wouldn't hesitate to try the update to _5.

    I've found the hardware support changes inherent in 2.3 show up pretty quickly if you're going to have an issue.
    Only one or two of the older systems I've tried had any issues at all.
    Anything that could install 2.3 has been very solid.

    I'd suggest you take a current config backup and do the update.
    Worst case, reinstall from scratch, restore the backup, reboot and you're back to where you started.

  • Dealing with computers, could have been anything.  A corrupt file.  A power flicker.  A gnat farted too close to the router.  Whatever.

    Yeah - It happens.  I'd go ahead and upgrade.  If it fails a second time, then its time to worry.

  • @Knight:

    ….it so it took me quite a while to have a working system again...).

    What should take time :
    Ones its up, you create a backup 'disk' (CD, USB stick, etc) so when your principal media dies (SSH, Hard disk etc) you can reboot 'in a snap'.
    Ones in a while, when you're up and running, and you modify your pfSense config, store it also in a save place - better yet : write it to your backup media …. ;)
    You do can all this while "all is good and you have plenty of time".
    Btw : you should only do this if the "internet access" is important for you. I do understand you have other things to do (as we all)  ;D

    Now, the update day arrives.
    Now, you are ready !
    Without even thinking, you hit that upgrade button.

    If things go downhill afterwards, well, you reboot from your backup media ..... and you're up. I assure you that you have a workable solution in 5 minutes, whatever the outcome will be : new version, or boot to old version.

    Added to that : something I don't do - but, which I should do :
    I'm running pfSense a a vanilla ancient Dell Office Desktop PC" (stripped down - I removed everything not needed on a firewall.
    What I should do : every time pfSense includes a new freeBSD kernel (meaning : new drivers etc) I install FIRST the original new FreeBSD OS.
    If that goes well, I'll have a pretty good that pfSense works also.
    Easier will be : run pfSense on pfSense certified machines .....

Log in to reply