Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Cannot upgrade from 2.1.4 to 2.2.2

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    12 Posts 4 Posters 1.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M Offline
      mwoffenden
      last edited by

      On my home page I see the message:


      Update available. Click Here to view update.


      When I click "here" I see:


      A new version is now available

      Current version: 2.1.4-RELEASE
        NanoBSD Size : 4g
            Built On: Fri Jun 20 17:06:12 EDT 2014
          New version: 2.2.2-RELEASE

      Update source: https://firmware.netgate.com/auto-update/m1n1wall/


      Here's the issue. I've tried both manual and auto-update, many times.  They all SEEM to proceed normally, however, at the end of the process the system remains at the older version.  Why?

      1 Reply Last reply Reply Quote 0
      • D Offline
        doktornotor Banned
        last edited by

        Probably because it did not reboot. Reboot it manually and re-apply the update manually once again.

        1 Reply Last reply Reply Quote 0
        • M Offline
          mwoffenden
          last edited by

          @doktornotor:

          Probably because it did not reboot. Reboot it manually and re-apply the update manually once again.

          Not sure I understand.  Reboot BEFORE upgrading, or after?  Also, what's the right way to reboot?

          1 Reply Last reply Reply Quote 0
          • D Offline
            doktornotor Banned
            last edited by

            https://redmine.pfsense.org/issues/4653

            1 Reply Last reply Reply Quote 0
            • GertjanG Offline
              Gertjan
              last edited by

              @mwoffenden:

              @doktornotor:

              Probably because it did not reboot. Reboot it manually and re-apply the update manually once again.

              Not sure I understand.  Reboot BEFORE upgrading, or after?  Also, what's the right way to reboot?

              Afterwards.
              Only then pfSense boots from the NEW kernel.
              The right way to do it, is:
              Login into GUI. Goto the menu  Diagnostics: Reboot System and hit the Yes button.
              Or, login using SSH and type the command 'reboot'.

              No "help me" PM's please. Use the forum, the community will thank you.
              Edit : and where are the logs ??

              1 Reply Last reply Reply Quote 0
              • M Offline
                mwoffenden
                last edited by

                So I invoked auto upgrade.  Here's what happened.


                Auto Update Download Status
                –--------------------------------------------------
                  Current Version : 2.1.4-RELEASE
                  Latest Version  : 2.2.2-RELEASE
                  File size      : 71699610
                  Downloaded      : 71699610
                  Percent        : 100%


                pfSense download complete.


                pfSense is now upgrading.

                The firewall will reboot once the operation is completed.


                This is where things get very confusing.  Nothing happens on the screen at all at this point.  After waiting for 5 minutes, I rebooted manually (Diagnostics/Reboot).  After doing all of that, there's NO upgrade to be had.  Back to square 1.


                2.1.4-RELEASE (i386)
                built on Fri Jun 20 17:06:12 EDT 2014
                FreeBSD 8.3-RELEASE-p16

                Update available. Click Here to view update.


                Any other ideas?

                1 Reply Last reply Reply Quote 0
                • M Offline
                  mwoffenden
                  last edited by

                  Then I went thru the manual upgrade process, which actually auto-rebooted.  Same result:


                  2.1.4-RELEASE (i386)
                  built on Fri Jun 20 17:06:12 EDT 2014
                  FreeBSD 8.3-RELEASE-p16

                  Update available. Click Here to view update.

                  1 Reply Last reply Reply Quote 0
                  • C Offline
                    cmb
                    last edited by

                    The not rebooting post-upgrade issue doesn't apply to nano versions. What does the upgrade log under Diag>nanobsd show?

                    1 Reply Last reply Reply Quote 0
                    • M Offline
                      mwoffenden
                      last edited by

                      NanoBSD firmware upgrade log attached…please advise on how I might be able to get this working!

                      [NanoBSD Firmware upgrade.txt](/public/imported_attachments/1/NanoBSD Firmware upgrade.txt)

                      1 Reply Last reply Reply Quote 0
                      • C Offline
                        cmb
                        last edited by

                        The key part there is "fdisk: invalid fdisk partition table found". That's something that has happened on occasion for unknown reasons. It appears to be an issue with the CF card itself, but in many cases rewriting the card fixes it (probably because it remaps something in the process of rewriting it). Pulling the img off of an affected card, and writing it out to another card or even back to the same card, fixes the issue which seems to indicate there isn't actually anything wrong in software. Unfortunately you'll need to pull the card and rewrite it. Can rewrite it with 2.2.2, then restore your 2.1.4 config backup.

                        1 Reply Last reply Reply Quote 0
                        • M Offline
                          mwoffenden
                          last edited by

                          @cmb:

                          Pulling the img off of an affected card, and writing it out to another card or even back to the same card, fixes the issue which seems to indicate there isn't actually anything wrong in software. Unfortunately you'll need to pull the card and rewrite it. Can rewrite it with 2.2.2, then restore your 2.1.4 config backup.

                          Thanks for the update.  How would I do this?

                          1 Reply Last reply Reply Quote 0
                          • C Offline
                            cmb
                            last edited by

                            https://doc.pfsense.org/index.php/Writing_Disk_Images

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.