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

    PFSense Plus Upgrade fail to mount ZFS root fs.

    Scheduled Pinned Locked Moved CE 2.7.0 Development Snapshots (Retired)
    8 Posts 2 Posters 912 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.
    • K
      Keno5net
      last edited by

      Long time user but my first post.

      Started when my long time appliance Protectli Vault expired unexpectedly.
      I used a temporary backup system to get online and realized that the original system hadn't been backed up recently.

      Sprained my hip trying to kick myself.

      I ordered a replacement that was available overnight:
      MOGINSOK Firewall Mini PC MGCN51N
      Intel Celeron 5105 with Intel UHD Graphics
      4xIntel i226 2.5Gb Ethernet

      When I got the system it had PFSense Plus pre installed which I found odd as I know that is not per the license agreement. I decided to reinstall from the proper source.

      I got the config.xml file off the uSATA drive from the old system and did a search and replace to correct the NIC designations.

      I loaded the 1.7 Development branch on the new system so the NICs would be recognized, restored the config and it was working well.

      Ungraded to PFSense Plus to get off the DEV stream and that is where the problems started.

      On reboot after the update the system failed to mount the root file system on zfs so I returned to the temporary backup system.

      I reinstalled 2.7 to see if the upgrade would work on a default config but the system would not upgrade returning:

      Unable to check for updates.

      Attempting the same from the console I got a series of:

        Could not load client certificate /etc/ssl/pfSense-repo-custom.cert

      Culminating in:

      pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/PFSense_plus-v22_01_amd64-pfSense_plus_v22_01//packagesite.txz: Authentication error
 Unable to update repository pfSense
 Error updating repositories!

      I perused the forums and found similar problems went away after some time to allow the cert to be replaced. So I waited overnight and it worked but still could not find the /root file system on the ZFS install.

      I have now reinstalled 2.7 on ufs but now have the cert problem back.

      Should I:

      Stick with 2.7 Dev.
      Install 2.6 and attempt to upgrade via USB NIC.
      Look for another distro that will work with the i226 NICs.
      Or are there any other options that I have missed?

      PS I did go through the troubleshooting section without success.

      K S 2 Replies Last reply Reply Quote 0
      • jimpJ jimp moved this topic from Problems Installing or Upgrading pfSense Software on
      • K
        Keno5net @Keno5net
        last edited by

        @keno5net
        Latest problem:
        After reinstall of 2.7 on ufs partition and waiting 24 hr for certs to update and allow upgrade to Plus the upgrade appeared to go well until the reboot at which time the system went into a boot loop. The system would get acpi not found errors and reboot repeatedly.

        Is there any way to speed up the cert updating process to avoid a 24 hour wait between retries?

        1 Reply Last reply Reply Quote 0
        • S
          SteveITS Galactic Empire @Keno5net
          last edited by

          @keno5net said in PFSense Plus Upgrade fail to mount ZFS root fs.:

          Ungraded to PFSense Plus to get off the DEV stream

          I don't use the development releases, but this statement confuses me a bit because upgrading from 2.7 would get you to 23.01 which is also in development. They aren't going to go from 2.7 to 22.05, and downgrade the OS from FreeBSD 14 to 12.

          Further your error references 22.01 which is more confusing. IIRC from other posts the current upgrade path is from 2.6 to 22.01 (same release) then again to 22.05. Unless I'm mistaken it seems like it is trying to do that from 2.7 which is not going to be a valid path.

          From another post I read, there was a 22.05.01 released for the 8200 model just to add that driver so I don't think it's available outside of 2.7/23.01?

          TL,DR: I'd just stay on 2.7 until the release happens and upgrades to Plus are allowed. They're at the release candidate stage I believe, so maybe a few weeks?

          Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
          When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
          Upvote 👍 helpful posts!

          K 1 Reply Last reply Reply Quote 0
          • K
            Keno5net @SteveITS
            last edited by

            @steveits
            Ok thanks I may try installing V 2.6 using a usb nic to see if I can get the upgrade from there, hopefully the certs are faster, if not I'll stick with 2.7 until it is released.

            To be complete this was the error that proceeded the reboot on the boot loop.

             acpi_wmi0: <ACPI-WMI mapping> on acpi0
 acpi_wmi0: cannot find EC device
 device_attach: acpi_wmi0 attach returned 6
            S 1 Reply Last reply Reply Quote 0
            • S
              SteveITS Galactic Empire @Keno5net
              last edited by

              @keno5net What version of Plus did they preinstall? If it was working that implies they found one with the right drivers, or maybe put the drivers in manually...

              Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
              When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
              Upvote 👍 helpful posts!

              K 1 Reply Last reply Reply Quote 0
              • K
                Keno5net @SteveITS
                last edited by

                @steveits
                Sorry I didn't record that.

                Atm I have the system running 2.6 as a 'router on a stick' using a usb nic but I may need to obtain another activation code. On 2.7 installs it remembered the first one but not on the 2.6 and i doubt the first one will work again. Do you know if I can get another without a support subscription?

                S 1 Reply Last reply Reply Quote 0
                • S
                  SteveITS Galactic Empire @Keno5net
                  last edited by

                  @keno5net We provide Netgate hardware to our clients, so I have not upgraded a router, but I think it's just a token from the store?

                  https://docs.netgate.com/pfsense/en/latest/install/migrate-to-plus.html

                  I think adding a NIC changes the calculated Netgate ID hence the new token.

                  From the above page it looks like it offers a specific Plus version so if it had been trying to go from 2.7 to 22.01, I would be shocked if that didn't fail.

                  Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                  When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                  Upvote 👍 helpful posts!

                  K 1 Reply Last reply Reply Quote 0
                  • K
                    Keno5net @SteveITS
                    last edited by

                    @steveits
                    Thanks for your help.
                    I guess I will try another token and if it still has problems I'll go with 2.7 for the foreseeable future.

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