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

    Latest update script failure

    Scheduled Pinned Locked Moved Plus 24.03 Development Snapshots (Retired)
    40 Posts 8 Posters 4.4k 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.
    • cmcdonaldC
      cmcdonald Netgate Developer @behemyth
      last edited by

      @behemyth

      Tomorrow's build will properly cleanup the pkg cache.

      Need help fast? https://www.netgate.com/support

      DefenderLLCD 1 Reply Last reply Reply Quote 2
      • DefenderLLCD
        DefenderLLC @cmcdonald
        last edited by DefenderLLC

        @cmcdonald said in Latest update script failure:

        @behemyth

        Tomorrow's build will properly cleanup the pkg cache.

        Package cache was cleared, ZFS pool has returned to it’s normal size, and zero install errors logged with today’s build! Nice work!

        903861fb-9ff7-4d7b-979b-54978e192e20-image.jpeg

        cmcdonaldC 1 Reply Last reply Reply Quote 1
        • cmcdonaldC
          cmcdonald Netgate Developer @DefenderLLC
          last edited by

          @DefenderLLC Awesome thanks for following up!

          Need help fast? https://www.netgate.com/support

          B 1 Reply Last reply Reply Quote 1
          • B
            behemyth @cmcdonald
            last edited by cmcdonald

            @cmcdonald

            Mine is failing this morning, apparently on the renaming of the boot environment.

            Updating repositories metadata...
            Updating pfSense-core repository catalogue...
            Fetching meta.conf: . done
            Fetching packagesite.pkg: . done
            Processing entries: . done
            pfSense-core repository update completed. 5 packages processed.
            Updating pfSense repository catalogue...
            Fetching meta.conf: . done
            Fetching packagesite.pkg: .......... done
            Processing entries: .......... done
            pfSense repository update completed. 736 packages processed.
            All repositories are up to date.
            Setting vital flag on pfSense...done.
            Renaming current boot environment from upgrade-upgrade-upgrade-upgrade-upgrade-upgrade-default-20240221223437-20240222100045-20240223161555-20240224222137-20240226110515-20240228113322 to upgrade-upgrade-upgrade-upgrade-upgrade-upgrade-default-20240221223437-20240222100045-20240223161555-20240224222137-20240226110515-20240228113322_previous...failed.

            cmcdonaldC 1 Reply Last reply Reply Quote 0
            • cmcdonaldC
              cmcdonald Netgate Developer @behemyth
              last edited by

              @behemyth

              This has been fixed.

              But you need to manually rename the current BE to something more sensible and then try the upgrade again.

              Need help fast? https://www.netgate.com/support

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

                With latest update I cleared all Boot Environments and updates to latest one with Defer Automatic Reboot and Boot Verification off. After restart I was still in the same Boot Environment as before (default-previous). No prompt (Boot Verification) or anything. After setting the new default Environment (24.03.a.20240301.0357) and rebooting I was stuck with no access. Connecting via Serial to have a look and while booting it was asking for the full path to shell and after Returning (use default) boot was interrupted and prompt was present. pfsense not started at all. Rebooted again and switched back to previous environment. This worked well.

                After deleting the upgraded environment I tried with updating from web UI as well as from console, same result. Not sure what happend. Updating to alpha versions worked well before, just now with the changes it is behaving strange.

                Might wait for a bit to update again.

                DefenderLLCD T 2 Replies Last reply Reply Quote 0
                • DefenderLLCD
                  DefenderLLC @boessi
                  last edited by

                  @boessi One thing I have been doing is renaming each boot environment back to "default" after each successful upgrade and some initial testing.

                  1 Reply Last reply Reply Quote 1
                  • T
                    townsenk64 @boessi
                    last edited by

                    @boessi I'm getting the same results as you are. I'm running on a VM. I'd be interested in knowing how you have it set up

                    DefenderLLCD 1 Reply Last reply Reply Quote 0
                    • DefenderLLCD
                      DefenderLLC @townsenk64
                      last edited by

                      @townsenk64 In that case, why not just backup your config file and redeploy to a new VM, upgrade that, then restore your config? It's a safe path forward for testing alphas and betas.

                      T 1 Reply Last reply Reply Quote 0
                      • B
                        behemyth @cmcdonald
                        last edited by

                        @cmcdonald

                        How do I change the boot environment name? Can i just call it default and do the upgrade?

                        DefenderLLCD 1 Reply Last reply Reply Quote 0
                        • DefenderLLCD
                          DefenderLLC @behemyth
                          last edited by

                          @behemyth said in Latest update script failure:

                          @cmcdonald

                          How do I change the boot environment name? Can i just call it default and do the upgrade?

                          I always rename mine back to default post-upgrade:

                          dde7e5b4-7e56-4ea8-afe9-c2a44ca51fa4-image.png

                          B 1 Reply Last reply Reply Quote 0
                          • B
                            behemyth @DefenderLLC
                            last edited by behemyth

                            @DefenderLLC

                            Yeah i got it, but my ZFS storage is almost maxed out now. I'm at 1.1g of 1.2g.

                            c1a18926-0c7a-433f-92c8-5e4a98d97728-image.png

                            And interestingly, it still says im on an older version, even after downloading the 20240301 image.

                            24.03-DEVELOPMENT (amd64)
                            built on Thu Feb 29 22:57:00 EST 2024
                            FreeBSD 15.0-CURRENT

                            The system is on the latest version.
                            Version information updated at Fri Mar 1 12:42:27 EST 202

                            62de2135-327d-45e0-b74b-d0789b1b551d-image.png

                            DefenderLLCD 1 Reply Last reply Reply Quote 0
                            • DefenderLLCD
                              DefenderLLC @behemyth
                              last edited by

                              @behemyth Just delete the boot environment that's no longer needed. That should free up your space that will allow to upgrade moving forward. Today's build actually clears the package cache.

                              cmcdonaldC 1 Reply Last reply Reply Quote 1
                              • cmcdonaldC
                                cmcdonald Netgate Developer @DefenderLLC
                                last edited by cmcdonald

                                @DefenderLLC

                                New renaming logic has been added that is more elegant.

                                Now we rename the current BE as "name_timestamp" and then name the new boot environment "name".

                                If you defer the reboot and decide to delete the upgraded BE we will rename the current back from "name_timestamp" to "name".

                                If the upgrade fails we do delete the failed BE and rename the current back to "name" automatically

                                It's pretty elegant

                                Need help fast? https://www.netgate.com/support

                                DefenderLLCD 1 Reply Last reply Reply Quote 1
                                • DefenderLLCD
                                  DefenderLLC @cmcdonald
                                  last edited by

                                  @cmcdonald said in Latest update script failure:

                                  @DefenderLLC

                                  New renaming logic has been added that is more elegant.

                                  Now we rename the current BE as "name_timestamp" and then name the new boot environment "name".

                                  If you defer the reboot and decide to delete the upgraded BE we will rename the current back from "name_timestamp" to "name".

                                  If the upgrade fails we do delete the failed BE and rename the current back to "name" automatically

                                  It's pretty elegant

                                  I noticed this morning and like it. :)

                                  1 Reply Last reply Reply Quote 1
                                  • T
                                    townsenk64 @DefenderLLC
                                    last edited by

                                    @DefenderLLC I did redeploy a new VM. No luck with that either. Generic 2.7.2 install & upgrade to 23.09.1 without issue.
                                    but it continues to fail to boot after upgrading to the 24.x dev build.

                                    cmcdonaldC 1 Reply Last reply Reply Quote 0
                                    • cmcdonaldC
                                      cmcdonald Netgate Developer @townsenk64
                                      last edited by

                                      @townsenk64

                                      I will test upgrades from 23.09.

                                      Need help fast? https://www.netgate.com/support

                                      G 1 Reply Last reply Reply Quote 0
                                      • G
                                        grandrivers @cmcdonald
                                        last edited by

                                        @cmcdonald I am stuck on 24.03-DEVELOPMENT (amd64)
                                        built on Tue Feb 13 1:00:00 EST 2024
                                        FreeBSD 15.0-CURRENT

                                        when reboot it hangs looking for path

                                        pfsense plus 25.03 super micro A1SRM-2558F
                                        C2558 32gig ECC  60gig SSD

                                        B 1 Reply Last reply Reply Quote 0
                                        • B
                                          boessi @grandrivers
                                          last edited by

                                          @grandrivers same, rolled back to prev env for now

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

                                            @cmcdonald with latest version (24.03.a.20240302.0116) I got following error while booting into the new environment. Sorry for the screenshot, will log proper output into logfile next time.

                                            df27d45f-1dbc-4a50-9bc2-d9270c80cd22-image.png

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