XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Issue installing latest pfSense Plus (24.03 release)

    Scheduled Pinned Locked Moved Compute
    19 Posts 5 Posters 1.1k Views 4 Watching
    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.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by

      Perfect, keep us posted!

      1 Reply Last reply Reply Quote 0
      • A Offline
        Affonso
        last edited by

        The same error

        Screenshot 2024-10-10 at 17.13.40.png

        1 Reply Last reply Reply Quote 0
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          Is there a way we can test that ISO? It's hard to reproduce if we don't have any way to test it here or in the community 😕

          A 1 Reply Last reply Reply Quote 0
          • A Offline
            Affonso @olivierlambert
            last edited by

            @olivierlambert let me talk to Netgate support and work some way out

            1 Reply Last reply Reply Quote 0
            • nikadeN Offline
              nikade Top contributor
              last edited by

              Googling the error "supervisor read data page not present" gives a lot of hints towards bad memory, are you using ECC or non ECC?

              A 1 Reply Last reply Reply Quote 0
              • A Offline
                Affonso @nikade
                last edited by

                @nikade

                The Dell R620 (Intel):

                # dmidecode -t memory | grep -i "ecc"
                	Error Correction Type: Multi-bit ECC
                

                The lab AMD Razor

                # dmidecode -t memory | grep -i "ecc"
                # 
                

                One server has ECC memory, the other doesn't. I believe it would be a very odd case of having "bad memory" on two completely different instances, and the fault being exactly the same on the different machines ... but as I said, this is not my area of expertise.

                1 Reply Last reply Reply Quote 0
                • A Offline
                  Andrew Top contributor @Affonso
                  last edited by

                  @Affonso I had a problem upgrading OPNsense to 24.7 which uses FreeBSD 14 using XCP 8.2.1

                  OPNsense had a kernel crash related to Xen using some FreeBSD kernel options. OPNsense was able to update their kernel to resolve the crash issue.

                  It was a OPNsense/FreeBSD issue, not a XCP issue. It has been resolved.

                  Here's the OPNsense github issue. I don't know if it's related.

                  A 1 Reply Last reply Reply Quote 1
                  • A Offline
                    Affonso @Andrew
                    last edited by

                    Thank you @Andrew I will mention this to pfSense. lets hope

                    A 1 Reply Last reply Reply Quote 0
                    • A Offline
                      Affonso @Affonso
                      last edited by

                      So just to give a quick update on how this went:

                      Since pfSense 24.03 is based on FreeBSD 15 I proceeded with a FreeBSD 15 installation on XCP-ng to see if the issue stemmed from there. FreeBSD15 installed and booted correctly.
                      From there I ended up testing the development snapshot 24.08.
                      Also installed correctly and booted.

                      So whatever issue was there between pfSense 24.03 and XCP-ng that was preventing it from booting, was only present on version 24.03.

                      A 1 Reply Last reply Reply Quote 1
                      • A Offline
                        Andrew Top contributor @Affonso
                        last edited by

                        @Affonso Looks like it might have been Bug 15684 in 24.03 that was resolved for 24.11 (release notes).

                        1 Reply Last reply Reply Quote 2
                        • First post
                          Last post