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

    2.1.5->2.2.2 system does not reboot after upgrade, requires power cycle

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    17 Posts 9 Posters 3.5k 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.
    • V
      vito
      last edited by

      I have had the same problem. Reported to support.
      Was this an issue for 2.1.5 to other 2.2.x versions?
      I had to wait to upgrade due to the limiter problem…which i thought was fixed in 2.2.2 :(
      (that is with support also)

      1 Reply Last reply Reply Quote 0
      • G
        grayknox
        last edited by

        My issue was resolved by rebooting from web interface. I was not able to ssh into either device.

        1 Reply Last reply Reply Quote 0
        • S
          sweepie
          last edited by

          After upgrading today from 2.1.5 to 2.2.2 I am having this same issue. Cant reboot or halt system from the webgui and can't connect with SSH. Do you recommend power cycling the server or should i wait?

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

            Waiting won't get you anywhere.

            1 Reply Last reply Reply Quote 0
            • G
              gordc
              last edited by

              So the only answer here to force a reboot?

              Does it let you reboot from the GUI after that?

              I have four firewalls and I have to travel to get to all of them.

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

                @gordc:

                Does it let you reboot from the GUI after that?

                Diagnostics - Command prompt - /sbin/reboot

                1 Reply Last reply Reply Quote 0
                • N
                  neik
                  last edited by

                  I have to say I don't find much "hilarity" in this. I don't think updates should be pushed out if they don't actually work as one would expect. I hope this gets fixed in a later release.

                  1 Reply Last reply Reply Quote 0
                  • jimpJ
                    jimp Rebel Alliance Developer Netgate
                    last edited by

                    @neik:

                    I have to say I don't find much "hilarity" in this. I don't think updates should be pushed out if they don't actually work as one would expect. I hope this gets fixed in a later release.

                    The 2.2.3 snapshots don't currently exhibit any of these symptoms, at least not for the scenarios I have tested. If others could try going from 2.1.x to 2.2.3 snapshots and posting the upgrade logs, it would be appreciated.

                    Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                    Need help fast? Netgate Global Support!

                    Do not Chat/PM for help!

                    1 Reply Last reply Reply Quote 0
                    • J
                      jdp0418
                      last edited by

                      Hi Jimp,
                      I have tested upgrading with one of the latest nanoBSD development images (pfSense-2.2.3-DEVELOPMENT-4g-i386-nanobsd-vga-upgrade-20150623-1513.img).  This upgraded my 2.1.5 (Soekris 6501-50 w/USB) without issue.  The unit rebooted, re-installed packages and came up fine.  It did leave the filesystem in RW mode, but a flip of the switch under the nanoBSD menu solves that.  It also comes back as RO after a reboot.

                      I just ran the "auto-updater" this morning with today's official release of 2.2.3.  I upgraded two 2.2.2 units successfully and one 2.1.5 unit successfully, with no rebooting or hanging issues whatsoever.  That is a better experience than the earlier versions.  :)

                      Sorry to be ignorant, but from where can I retrieve the upgrade logs?  I would like to help if you still need this information.

                      1 Reply Last reply Reply Quote 0
                      • jimpJ
                        jimp Rebel Alliance Developer Netgate
                        last edited by

                        If it all worked fine then there isn't much to report now :-)

                        We fixed all the known issues we could find with upgrading, 2.2.3 should be a much better experience for everyone all-around.

                        The upgrade log is in /conf/upgrade_log.txt if you want to review it.

                        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                        Need help fast? Netgate Global Support!

                        Do not Chat/PM for help!

                        1 Reply Last reply Reply Quote 0
                        • J
                          jdp0418
                          last edited by

                          Cool, thanks.  And thanks to the whole PFSense team for the most recent update!

                          1 Reply Last reply Reply Quote 0
                          • A
                            arl
                            last edited by

                            Newbie here.  Working through all things pfSense.  This was one of them.

                            I put an old Dell laptop to use with pfSense for routing and radius functions.  Had problem where, from the main console menu, when I choose reboot (option 5) it goes until it stops the system and the last message is the "Uptime…"  then it just hangs.  I have to force a hard power off.

                            Googled everything I could find, most folks suggested ACPI, so I went looking for it in the BIOS, but it's not there.  While I was there I noticed that this system had AHCI enabled for the HD controller, which is fine for windows and intel parties, but I dont' think it helps in pfSense under freeBSD!  Or am I wrong here ?

                            Anyway, I changed the HD controller function back to the Dell default of ATA, not thinking it was connected.  When I booted and did a reboot, it worked.

                            For what it's worth, something about AHCI seems to mess with the reboot process.  I'm running 2.2.5

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