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

    23.09.1 -> 24.03a seems fail

    Scheduled Pinned Locked Moved Plus 24.03 Development Snapshots (Retired)
    27 Posts 3 Posters 2.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.
    • L
      Luca De Andreis @cmcdonald
      last edited by

      @cmcdonald

      OK, I carefully repeated the whole update process.
      I checked the boot sequence carefully and there is no upgrade attempt.
      The post upgrade 23.09.1->24.03 Beta system seems to boot from the snapshot related to 23.09.1 without even trying to upgrade.
      That is if I do not go to "play" with the BE ... if I go to force the snapshot, it starts correctly in 24.03.

      1 Reply Last reply Reply Quote 0
      • L
        Luca De Andreis @cmcdonald
        last edited by

        @cmcdonald

        Mhhhhh something is not working

        9ba81b18-8990-4d29-a143-69993a2a2d88-immagine.png

        If I click, relative to the last line of this image, on... start from this snapshot (24.03b) the system restarts in 23.09.1

        1 Reply Last reply Reply Quote 0
        • L
          Luca De Andreis @cmcdonald
          last edited by

          @cmcdonald

          cf16aaf3-8f5b-46b4-bcd7-31d901aef10c-immagine.png

          1 Reply Last reply Reply Quote 0
          • L
            Luca De Andreis @cmcdonald
            last edited by

            @cmcdonald

            Why this one ?

            b7744534-c094-4702-a7fc-74c46f0b185a-immagine.png

            I've just set a new default boot snapshot (change the star) .... I did not set a "one time boot mode"

            cmcdonaldC 1 Reply Last reply Reply Quote 0
            • cmcdonaldC
              cmcdonald Netgate Developer @Luca De Andreis
              last edited by

              @Luca-De-Andreis

              After the upgrade is performed the new BE is marked temporary for the next boot so that if boot verification fails, the system automatically reboots back into the old BE.

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

              L 2 Replies Last reply Reply Quote 0
              • L
                Luca De Andreis @cmcdonald
                last edited by

                This post is deleted!
                1 Reply Last reply Reply Quote 0
                • L
                  Luca De Andreis @cmcdonald
                  last edited by

                  @cmcdonald

                  Okay, but it doesn't make sense for this alert to appear... the system is running with the snapshot default_previous_20240302092838_20240305095307, the next is default_previous_20240302092838_20240305095307 (correctly, because it is the default) and the alert says... "this is a temporary boot", look the next from which the system will be rebooted is : default_previous_20240302092838_20240305095307 (that is what is now running).

                  4cfb226b-2028-4893-a089-a73aa6ae7500-immagine.png

                  89fa5a9b-6bff-482c-ab1f-1d2fb9974a7e-immagine.png

                  cmcdonaldC 1 Reply Last reply Reply Quote 0
                  • cmcdonaldC
                    cmcdonald Netgate Developer @Luca De Andreis
                    last edited by

                    @Luca-De-Andreis

                    what's the output of

                    bectl list
                    

                    When it's in that state?

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

                    L 2 Replies Last reply Reply Quote 0
                    • L
                      Luca De Andreis @cmcdonald
                      last edited by

                      @cmcdonald
                      BE Active Mountpoint Space Created
                      auto-default-20231208173430 - - 637M 2023-12-08 17:34
                      default_previous_20240302092838 - - 1.45G 2024-03-05 09:53
                      default_previous_20240302092838_20240305095307 NRT / 3.67G 2024-03-05 10:13
                      default_previous_20240302092838_20240305095307_20240305101257 - - 3.66M 2018-05-15 09:40

                      1 Reply Last reply Reply Quote 0
                      • L
                        Luca De Andreis @cmcdonald
                        last edited by

                        @cmcdonald

                        I've just upgrade to 24.03.b.20240306.0600

                        And the system reboot on a different snapshot, the upgrade is not completed

                        43009d65-9cb7-4ade-b397-18ec67193fd0-immagine.png

                        44d2a3e0-8ad4-4335-944f-6cb58a55a6c8-immagine.png

                        L 1 Reply Last reply Reply Quote 0
                        • L
                          Luca De Andreis @Luca De Andreis
                          last edited by

                          5c7dad2d-5eb1-4686-b46f-7c56e80f6a77-immagine.png

                          I've just upgrade (again).

                          PfSense reboot on 24.03b.20240306.0600

                          Is set "temporary BE" on 24.03b.20240307.0536 but is fully ignored

                          1 Reply Last reply Reply Quote 0
                          • stephenw10S stephenw10 moved this topic from Problems Installing or Upgrading pfSense Software on
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.