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

    Update from 23.09.1 to 24.03_1 always reverts

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    12 Posts 2 Posters 650 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.
    • J
      joec
      last edited by

      Hello everybody,
      I have the problem, than an update from 23.09.1 to 24.03_1 will always reverts.

      The update itself is running without errors the system is booting with 24.03_1. But after a few minutes it reboots and reverts to 23.09.1

      In the dashboard following ist shown:
      2024_08_07_07_20_06_pfSense_Nachricht_HTML_.png

      The system has enough RAM and diskspace.
      Before update I can see in the update dialog this message:
      pfSense-repoc: si_get_packages: failed to run the pkg info command: /usr/local/sbin/pkg-static info -R --raw-format json-compact pfSense-pkg-* 2>&1 pfSense-repoc: no pfSense packages installed

      Any clues?
      Thanks to all.

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

        @joec said in Update from 23.09.1 to 24.03_1 always reverts:

        Before update I can see in the update dialog this message:
        pfSense-repoc: si_get_packages: failed to run the pkg info command: /usr/local/sbin/pkg-static info -R --raw-format json-compact pfSense-pkg-* 2>&1 pfSense-repoc: no pfSense packages installed

        That's a known issue but it's only cosmetic, shouldn't cause a problem here.

        What do you have set in the update settings? I assume manual update verification is not enabled?

        Does System > Boot Environments show the failed 24.03 BEs?

        Steve

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

          Hello Steve,
          I cant see the option "manual update verification" ?
          As Branch 24.03 stable version ist set

          Yes. I can see the failed 24.03 BEs in the Boot Environment

          Johannes

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

            I assume you tried clicking 'Verify' manually when it boots into 24.03?

            Do you have the boot log from that boot into 24.03? Does it show an error at the console?

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

              Yes your'e right the first time I clicked on Verify.
              On the sceond try, I do nothing and the system booted by itself and going back to 23.01.

              No boot log

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

                Can you get a console log?

                It may be failing at the console something like this:

                Configuring crash dumps...
                No suitable dump device was found.
                /etc/pfSense-rc: /etc/rc.d/createswap: not found
                rc.bootonce_verify: ZFS support is required.
                
                *** SYSTEM BOOT FAILURE ***
                
                  Failed Boot Environment: default
                
                   R/r: Enter a recovery shell
                   Any: Shutdown immediately
                
                Enter an option:
                
                1 Reply Last reply Reply Quote 0
                • J
                  joec
                  last edited by

                  I can not find any of the above messages.
                  I attach a snippet of the system.log which shows the boot of V 24.03 until it reboots.

                  Perhaps it is helpful
                  boot.txt

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

                    The log there doesn't show output sent only to the primary console during boot. Are you able to view the video console when it first boots?

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

                      I will try later.

                      Thank you so far for your help-

                      Johannes

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

                        After another update to 24.03 pfSense remained stable (no reboot).
                        No error messages while startup.
                        However, DNS resolving no longer works. No external resolution, internal resolution works.

                        I then booted 23.09.1 again.
                        Now I have the problem that I can no longer install any packages.
                        Error:
                        WARNING: Current pkg repository has a new PHP major
                        version. pfSense should be upgraded before
                        installing any new package.

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

                          You would need to set the pkg repo branch back to 23.09.1 in 23.09.1 to install packages.

                          What are you using for DNS in 24.03? Is the service running? What exactly is failing?

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

                            Everything is running now.

                            The DNS problems resulting from a misconfigured gateway.

                            Thank's for your help.

                            Johannes

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