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

    [SOLVED - manual upgrd] Upgraded to 2.1.4 and now my WG Firebox X700 won't boot!

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    38 Posts 11 Posters 8.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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      @bennyc:

      Making no progress here with that darn CF. Any hints on how to safely mount that BSD partition in windows?

      The easiest way to do this, by far, is to do it from a BSD install. If you don't have a BSD machine then run a FreeBSD live CD like GhostBSD.

      Steve

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

        @stephenw10:

        @bennyc:

        Making no progress here with that darn CF. Any hints on how to safely mount that BSD partition in windows?

        The easiest way to do this, by far, is to do it from a BSD install. If you don't have a BSD machine then run a FreeBSD live CD like GhostBSD.

        Steve

        Virtual machine with FreeBSD installed and connect the disk to it with an USB to SATA adapter, just about any USB enclosure will do.

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

          Not that I'm surprised, but I thought it was worth reporting I'm now 2 for 2 on upgrading my Watchguard X750's using the manual update method.

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

            @phatty:

            Not that I'm surprised, but I thought it was worth reporting I'm now 2 for 2 on upgrading my Watchguard X750's using the manual update method.

            Thank you for your almost realtime feedback on your update attempts. I would like to clarify one point before I am going to give my Alix backup machine a try: What do you mean by "manual update method"?
            1.) From the webGUI: "System -> Firmware -> Manual Update" or 2.) From the console menu: "13) Upgrade from console"?

            I have never used method 1.) before. Instead I used method 2.) or "Auto Update" from the webGUI.

            I strongly suppose that update method does not matter as long as all selectable mirrors carry the same update files. Can you confirm the BluegrassNet mirror having had a more recent time stamp compared to the auto-selected mirror?

            Regards,
            Peter

            1 Reply Last reply Reply Quote 0
            • B
              bennyc
              last edited by

              @phatty:

              for a very short second, I was able to wait and eventually see the boot options for which slice to boot off of…

              Thank you for that. While downloading the GhostBSD iso (also tnx at Steve for the hint), took a shot at this and after a couple of tries I got to boot slice 2. Now I have again console access, much better ;D

              I will repeat upgrade attempt tomorrow evening. Are there logs kept on the system about past upgrade attempt? I'm curious to know where it went wrong, or what went wrong… (there's always something to learn)

              4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
              1x PC Engines APU2C4, 1x PC Engines APU1C4

              1 Reply Last reply Reply Quote 0
              • B
                bennyc
                last edited by

                It is repeatable. I tried twice upgrading again, with exact same outcome as described here below.

                Booted in 2.1.3, nano 2g image. Went to 'auto-update'

                A new version is now available
                
                Current version: 2.1.3-RELEASE
                  NanoBSD Size : 2g
                       Built On: Thu May 01 15:52:17 EDT 2014
                    New version: 2.1.4-RELEASE
                
                  Update source: https://updates.pfsense.org/_updaters 
                

                -> invoke auto upgrade

                  Auto Update Download Status
                ----------------------------------------------------
                  Current Version : 2.1.3-RELEASE
                  Latest Version  : 2.1.4-RELEASE
                  File size       : 76070249
                  Downloaded      : 24739580
                  Percent         : 33%
                ----------------------------------------------------
                

                File size reflects here : https://updates.pfsense.org/_updaters/

                latest-nanobsd-2g.img.gz                           25-Jun-2014 21:26            76070249
                

                Seems to get the correct image in my case…

                I tried following in console: this is partial output:

                
                Broadcast Message from root@pfsense.localdomain
                        (no tty) at 11:06 CEST...
                
                Installing /root/latest.tgz.
                
                Broadcast Message from root@pfsense.localdomain
                        (no tty) at 11:13 CEST...
                
                NanoBSD Firmware upgrade is complete.  Rebooting in 10 seconds.
                
                *** FINAL System shutdown message from root@pfsense.localdomain ***
                
                System going down IMMEDIATELY
                
                pfSense is now shutting down ...
                
                Jun 28 11:13:40 ovpns3: link state changed to DOWN
                lighttpd[53693]:ovpns1: link state changed to DOWN
                 (server.c.1558) server stopped pflog0: promiscuous mode enabled
                Bump sched buckets to 256 (was 0)
                Bump sched buckets to 256 (was 0)
                Bump sched buckets to 256 (was 0)
                Bump sched buckets to 256 (was 0)
                Bump sched buckets to 256 (was 0)
                Bump sched buckets to 256 (was 0)
                Bump sched buckets to 256 (was 0)
                Bump sched buckets to 256 (was 0)
                pflog0: promiscuous mode disabled
                Waiting (max 60 seconds) for system process `vnlru' to stop...done
                Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
                Waiting (max 60 seconds) for system process `syncer' to stop...
                Syncing disks, vnodes remaining...0 0 done
                All buffers synced.
                Uptime: 2h5m18s
                usbus0: Controller shutdown
                uhub0: at usbus0, port 1, addr 1 (disconnected)
                usbus0: Controller shutdown complete
                usbus1: Controller shutdown
                uhub1: at usbus1, port 1, addr 1 (disconnected)
                usbus1: Controller shutdown complete
                usbus2: Controller shutdown
                uhub2: at usbus2, port 1, addr 1 (disconnected)
                usbus2: Controller shutdown complete
                usbus3: Controller shutdown
                uhub3: at usbus3, port 1, addr 1 (disconnected)
                usbus3: Controller shutdown complete
                usbus4: Controller shutdown
                uhub4: at usbus4, port 1, addr 1 (disconnected)
                usbus4: Controller shutdown complete
                Rebooting...
                þþþþÿ
                1  pfSense
                2  pfSense
                
                F6 PXE
                Boot:  1
                

                After that, we were back at a dead box.
                Interestingly, I never got the (very brief) serial console again until I cycled the box.
                Could it be there is something wrong with this 2g image? Or am I missing something here?

                For a small version upgrade, this is requiring way more attention then anticipated. ::)

                4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
                1x PC Engines APU2C4, 1x PC Engines APU1C4

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  Look at the update files here:
                  http://files.bgn.pfsense.org/mirror/updates/

                  Now look here:
                  https://updates.pfsense.org/_updaters/

                  Notice that the standard Nano upodate images are a different size to the VGA updates but at the _upaters URL they are the same (except the 512MB image). It seems likely they are all the VGA images.
                  Edit: Finally mangaed to open the files on Android.  ::) Both have the same MD5 and both are decsribed as the VGA update in the MD5 file.

                  Go the manual update method by downloadibng the update file manually from the mirrors and uploading that to your box.

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • B
                    bennyc
                    last edited by

                    @stephenw10:

                    Edit: Finally mangaed to open the files on Android.  ::) Both have the same MD5 and both are decsribed as the VGA update in the MD5 file.

                    Go the manual update method by downloadibng the update file manually from the mirrors and uploading that to your box.

                    That explains a lot. I've seen your new thread, so I'll hold off a bit with an upgrade, I'm not in a rush and who knows I can help others by testing once the situation is a bit more clear.

                    4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
                    1x PC Engines APU2C4, 1x PC Engines APU1C4

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

                      I'm surprised they haven't fixed this issue yet.  Usually they are very good at fixing upgrade issues.  There is no way of telling they have fixed it or not unless someone keeps trying and be a guinea pig… Who will make the stand?  :D

                      EDIT:  Better yet, what is the link to the nano 2gb so I can manually upgrade it?

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

                        @m4f1050:

                        I'm surprised they haven't fixed this issue yet.  Usually they are very good at fixing upgrade issues.  There is no way of telling they have fixed it or not unless someone keeps trying and be a guinea pig… Who will make the stand?  :D

                        EDIT:  Better yet, what is the link to the nano 2gb so I can manually upgrade it?

                        You can find all neccessary information about the manual update method here: https://forum.pfsense.org/index.php?topic=78713.msg429345#msg429345
                        I have meanwhile updated my Alix and my Soekris with this method.

                        Regards,
                        Peter

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

                          @pvoigt:

                          @m4f1050:

                          I'm surprised they haven't fixed this issue yet.  Usually they are very good at fixing upgrade issues.  There is no way of telling they have fixed it or not unless someone keeps trying and be a guinea pig… Who will make the stand?  :D

                          EDIT:  Better yet, what is the link to the nano 2gb so I can manually upgrade it?

                          You can find all neccessary information about the manual update method here: https://forum.pfsense.org/index.php?topic=78713.msg429345#msg429345
                          I have meanwhile updated my Alix and my Soekris with this method.

                          Regards,
                          Peter

                          Actually, just rebooted my firebox and booted it from 2nd mount point (2.1.3), it's the actual image that's bad.

                          Where is the NYI mirror link?

                          EDIT:  NVM, found it..  https://www.pfsense.org/download/mirror.php?section=updates

                          1 Reply Last reply Reply Quote 0
                          • X
                            xbipin
                            last edited by

                            i upgraded again the alix using console and upgrade from url method and pointed it to a upgrade file on the mirror and all went perfect and everything works fine

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

                              Success, finally!  Thanks pvoigt for pointing me to the right direction.

                              
                              Broadcast Message from root@xxx.xxx.net
                                      (no tty) at 8:50 EDT...
                              
                              NanoBSD Firmware upgrade in progress...
                              
                              Broadcast Message from root@xxx.xxx.net
                                      (no tty) at 8:50 EDT...
                              
                              Installing /root/firmware.tgz.
                              
                              Broadcast Message from root@xxx.xxx.net
                                      (no tty) at 8:55 EDT...
                              
                              NanoBSD Firmware upgrade is complete.  Rebooting in 10 seconds.
                              
                              *** FINAL System shutdown message from root@xxx.xxx.net ***
                              
                              System going down IMMEDIATELY
                              
                              1 Reply Last reply Reply Quote 0
                              • B
                                bennyc
                                last edited by

                                @m4f1050:

                                I'm surprised they haven't fixed this issue yet.  Usually they are very good at fixing upgrade issues.  There is no way of telling they have fixed it or not unless someone keeps trying and be a guinea pig… Who will make the stand?  :D

                                I too find it very strange, not 1 reaction from ESF. One would think that when releasing a new version, there would be some follow-up? Steve even made a separate thread for it….
                                No problem testing it again on my test-firebox once there is a new image available....

                                4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
                                1x PC Engines APU2C4, 1x PC Engines APU1C4

                                1 Reply Last reply Reply Quote 0
                                • B
                                  bennyc
                                  last edited by

                                  As stated here: https://forum.pfsense.org/index.php?topic=78713.0
                                  Issue is fixed. I just upgraded my Firebox from 2.1.3 -> 2.1.4, using auto-upgrade (gui-easy-way), and all is fine!

                                  Thanks for the fix guys! :)

                                  4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
                                  1x PC Engines APU2C4, 1x PC Engines APU1C4

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