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

    Upgrade to 2.1.2: Stuck on 2.1

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    81 Posts 29 Posters 31.3k 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.
    • C
      cmb
      last edited by

      Go to Diag>nanobsd and check the upgrade log, what does that show?

      1 Reply Last reply Reply Quote 0
      • P
        phil.davis
        last edited by

        Negative. 8 Alix boxes running 2.1.2 ATM.

        and I have 11 Alix/nanoBSD running 2.1.2 - they are working nicely.

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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

          @cmb:

          Go to Diag>nanobsd and check the upgrade log, what does that show?

          Showing success upgrade.
          Only errors I've noticed where:

          
          Misc log:
          
          fdisk: invalid fdisk partition table found
          bsdlabel: /dev/ad0s3: no valid label found
          bsdlabel: /dev/ad0s3: no valid label found
          bsdlabel: /dev/ad0s3: no valid label found
          tar: Failed to set default locale
          tar: Failed to set default locale
          shutdown: [pid 90083]
          
          
          1 Reply Last reply Reply Quote 0
          • M
            mrsunfire
            last edited by

            @doktornotor:

            @mrsunfire:

            2.1.2 seems to be broken for ALIX.

            Negative. 8 Alix boxes running 2.1.2 ATM. And please do not multipost about the same issue.

            Don't know exactly why you deletet my post with error updating my ALIX APU1C to 2.1.2. This thread is a different issue, but ok. I will go on…

            After resetting my pfsense because it was stuck on "Reboot after updating firmware", my serial console isn't working anymore. I only can connect via SSH. The connection is fine, because I see the ALIX booting till you can select from what you want to boot. As default I chose F1: pfsense, then it starts to boot up, but nothing more happens.

            What to do?

            Also strange: I now use a i386 version of pfsense, with 2.1.1 I used the AMD version.

            Netgate 6100 MAX

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

              0/ I deleted nothing, I'm not even a moderator. Regardless, it has been deleted because you posted two idential posts in two different threads. Just do NOT do that.
              1/ APU != ALIX. You seriously are confusing people here. Totally different HW!
              2/ Last time I've heard, cross-arch upgrades are not exactly something supported. Why don't you just do a fresh install and restore the config?
              3/ The APU is something far from tested as well.

              1 Reply Last reply Reply Quote 0
              • M
                mrsunfire
                last edited by

                OK, the APU is from the same manufactor of the ALIX but called different. I will try a fresh install and come back later.

                Netgate 6100 MAX

                1 Reply Last reply Reply Quote 0
                • K
                  kaput
                  last edited by

                  I'm seeing the same issue on an ALIX board. The upgrade goes through with no errors reported on screen/console, but when it reboots, it boots back into 2.1. The upgrade log has only the following that appears notable.

                  fdisk: invalid fdisk partition table found
                  bsdlabel: /dev/ad0s3: no valid label found
                  bsdlabel: /dev/ad0s3: no valid label found
                  bsdlabel: /dev/ad0s3: no valid label found
                  shutdown: [pid 75726]

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

                    @kaput are you on 4g image?

                    1 Reply Last reply Reply Quote 0
                    • K
                      kaput
                      last edited by

                      Yes.

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

                        Can someone test 4g image to see if it's not broken? I had no problems upgrading 2g images, but 4g gives problem.

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

                          Provide the whole upgrade log. The part being quoted isn't the problem.

                          We tested the 4GB version more than others, as it's the most common one in use.

                          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
                          • K
                            kaput
                            last edited by

                            http://pastebin.com/YX8vK7C1

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

                              Here's your problem:

                              gpart set -a active -i 1 ad0
                              gpart: table 'ad0' is corrupt: Operation not permitted
                              

                              Try this:

                              gpart bootcode -b /boot/mbr ad0
                              

                              Then try the upgrade again.

                              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
                              • K
                                kaput
                                last edited by

                                Thanks, jimp. Missed that perm issue in the log.

                                Unfortunately, running "gpart bootcode -b /boot/mbr ad0" also results in the exact same error, noting that ad0 is corrupt.

                                1 Reply Last reply Reply Quote 0
                                • P
                                  prohidium
                                  last edited by

                                  I have the exact same issue with same error in my upgrade log on a 2g install on an Alix box.

                                  I also had the issue on a 4g install but I opted to flash a new image and swap cards. The 2g box though is 4 hours round trip away so I would love to fix the issue and update remotely.

                                  I also had another 4g box that updated just fine. So, 2 out of 3 are broken and would not update with autoupdate or manual update.

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

                                    Other things to try:

                                    Set the boot slice on Diagnostics > NanoBSD, see if it actually changes.

                                    or

                                    gpart recover ad0
                                    

                                    or

                                    sysctl kern.geom.debugflags=16
                                    boot0cfg -v -s 1 ad0
                                    fdisk -a /dev/ad0
                                    sysctl kern.geom.debugflags=0
                                    

                                    (For fdisk make sure to specify the values it asks and press 'y' to confirm!)

                                    We have yet to be able to reproduce this effectively, but several people have hit it. It would be helpful to know some more about the original setup that failed. Was it your own CF or did it come with the device? Had it ever been upgraded before, and if so how many times? What was its original version of pfSense on that CF card before upgrading?

                                    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
                                    • S
                                      sashka
                                      last edited by

                                      Slice does not change; nor I can copy ad0s2 -> ad0s1.

                                      1 Reply Last reply Reply Quote 0
                                      • K
                                        kaput
                                        last edited by

                                         gpart bootcode -b /boot/mbr ad0
                                        gpart: table 'ad0' is corrupt: Operation not permitted
                                        
                                        
                                        gpart recover ad0
                                        gpart: recovering 'ad0' failed: Function not implemented
                                        
                                        
                                        1 Reply Last reply Reply Quote 0
                                        • S
                                          sashka
                                          last edited by

                                          
                                          fdisk -a /dev/ad0
                                          
                                          

                                          I get an Intput/Output error.

                                          This is compact flash card. It was installed as 2.0 and then upgraded to 2.0.3 and later 2.1.

                                          1 Reply Last reply Reply Quote 0
                                          • R
                                            robi
                                            last edited by

                                            In my case I had pfSense nanobsd v1.2.3 upgraded to v2.0, that one upgraded to v2.1 - all of them upgraded OK. Now when I wanted to upgrade to v2.1.2, It seems corrupted. I'm preparing a fresly flashed CF card with config already put in.

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