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

    Significant issues upgrading from 22.05 to 14 Nov 23.01 build

    Scheduled Pinned Locked Moved Plus 23.01 Development Snapshots (Retired)
    6 Posts 3 Posters 1.0k 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.
    • G
      gabacho4 Rebel Alliance
      last edited by

      I tried to upgrade an SG-5100 running 22.05 to the 14 November 23.01 build via the console. Upgrade seemed to go without a hitch until the router rebooted and I no longer had network access. When I checked in the console, I see the following (with errors) during the boot process:

      Welcome to Netgate pfSense Plus 23.01-DEVELOPMENT...
      
      Dump device does not exist.  Savecore not run.
      ..cp: /dev/null: Function not implemented
      .ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/lib/engines /usr/local/lib/compat/pkg /usr/local/lib/ipsec /usr/local/lib/perl5/5.32/mach/CORE
      32-bit compatibility ldconfig path:
      done.
      >>> Removing vital flag from php81... done.
      External config loader 1.0 is now starting... ada0p1 ada0p3 mmcsd0p1 mmcsd0p2 mmcsd0p3
      Launching the init system...KLD cpuctl.ko: depends on kernel - not available or version mismatch
      linker_load_file: /boot/kernel/cpuctl.ko - unsupported file type
      /usr/local/etc/rc.d/microcode_update: WARNING: Can't load cpuctl module.
      .... done.
      Initializing.................. done.
      Starting device manager (devd)...done.
      Loading configuration......done.
      Configuring WireGuard tunnels...done.
      Updating configuration...done.
      Checking config backups consistency...done.
      Setting up extended sysctls...done.
      Setting timezone...done.
      Configuring loopback interface...done.
      Starting syslog...done.
      Starting Secure Shell Services...done.
      Setting up interfaces microcode...done.
      Configuring loopback interface...done.
      Configuring VLAN interfaces...KLD if_ix.ko: depends on kernel - not available or version mismatch
      linker_load_file: /boot/kernel/if_ix.ko - unsupported file type
      KLD if_ix.ko: depends on kernel - not available or version mismatch
      linker_load_file: /boot/kernel/if_ix.ko - unsupported file type
      KLD if_ix.ko: depends on kernel - not available or version mismatch
      linker_load_file: /boot/kernel/if_ix.ko - unsupported file type
      KLD if_ix.ko: depends on kernel - not available or version mismatch
      linker_load_file: /boot/kernel/if_ix.ko - unsupported file type
      done.
      Configuring WAN interface...KLD if_ix.ko: depends on kernel - not available or version mismatch
      linker_load_file: /boot/kernel/if_ix.ko - unsupported file type
      KLD if_ix.ko: depends on kernel - not available or version mismatch
      linker_load_file: /boot/kernel/if_ix.ko - unsupported file type
      KLD if_ix.ko: depends on kernel - not available or version mismatch
      linker_load_file: /boot/kernel/if_ix.ko - unsupported file type
      done.
      Configuring MGMT_ACCESS interface...KLD if_igb.ko: depends on kernel - not available or version mismatch
      linker_load_file: /boot/kernel/if_igb.ko - unsupported file type
      done.
      Configuring MGMT_VLAN interface...KLD if_ix.ko: depends on kernel - not available or version mismatch
      linker_load_file: /boot/kernel/if_ix.ko - unsupported file type
      done.
      Configuring KIDS_VLAN interface...KLD if_ix.ko: depends on kernel - not available or version mismatch
      linker_load_file: /boot/kernel/if_ix.ko - unsupported file type
      done.
      Configuring CAMERAS_VLAN interface...KLD if_ix.ko: depends on kernel - not available or version mismatch
      linker_load_file: /boot/kernel/if_ix.ko - unsupported file type
      done.
      Configuring PARENTS_VLAN interface...KLD if_ix.ko: depends on kernel - not available or version mismatch
      linker_load_file: /boot/kernel/if_ix.ko - unsupported file type
      done.
      Configuring WIREGUARDUTAH interface...done.
      Configuring CARP settings...done.
      Syncing OpenVPN settings...done.
      Configuring firewall.....Starting PFLOG...done.
      Setting up gateway monitors...done.
      Setting up static routes...done.
      Setting up DNSs...
      Starting DNS Resolver...done.
      Synchronizing user settings...done.
      Configuring CRON...done.
      Bootstrapping clock...done.
      Starting NTP Server...done.
      Starting webConfigurator...done.
      Starting DHCP service...done.
      Configuring firewall.....Configuring IPsec VPN... done
      Generating RRD graphs...done.
      Starting watchdog daemon...done.
      Starting UPnP service... done.
      Starting syslog...done.
      Configuring IPsec VPN for dynamic hosts... route: route has not been found
      done
      Configuring filter for dynamic IPsec VPN hosts... done
      Starting CRON... done.
       Starting package WireGuard...done.
       Starting package FRR...done.
      Netgate pfSense Plus 23.01-DEVELOPMENT amd64 Mon Nov 14 06:04:55 UTC 2022
      Bootup complete
      KLD if_wg.ko: depends on kernel - not available or version mismatch
      linker_load_file: /boot/modules/if_wg.ko - unsupported file type
      KLD if_wg.ko: depends on kernel - not available or version mismatch
      linker_load_file: /boot/modules/if_wg.ko - unsupported file type
      
      

      I am using ix0 for WAN and ix1.[100-160] for my internal VLANs. I don't seem to be able to recover from this issue on my own. Welcome any ideas or things I can do to help troubleshoot.

      M 1 Reply Last reply Reply Quote 0
      • M
        michaellacroix @gabacho4
        last edited by

        @gabacho4

        I had the same issue with the same nics. ixo for wan and ix1 for lan and vlans. haproxy and my bridge really crapped out as well.

        1 Reply Last reply Reply Quote 0
        • jimpJ
          jimp Rebel Alliance Developer Netgate
          last edited by

          It looks like it didn't fully upgrade the new kernel and modules properly somehow. It probably got interrupted in the middle of updating somewhere.

          Probably best to contact TAC and reinstall 22.05 clean, restore the configuration, then upgrade to 23.01 again.

          Or you could reinstall 22.05, upgrade to 23.01, then restore the configuration.

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

          M G 2 Replies Last reply Reply Quote 0
          • M
            michaellacroix @jimp
            last edited by

            @jimp I think your second option is best to upgrade to 22.05 then 23.01 and then restore config

            1 Reply Last reply Reply Quote 0
            • G
              gabacho4 Rebel Alliance @jimp
              last edited by

              @jimp I’ll give it another go from 22.05 to 23.01 and worry about the config once I can get it to upgrade. There was no interruption when I did the upgrade this time around. I watched the console display the whole time. The 5100 downloaded the new files, rebooted, installed everything, rebooted again, and I found myself in the state described. I am running my install on an m.2 ssd with zfs of that matters at all. Will apprise once I try the reinstall and upgrade again.

              1 Reply Last reply Reply Quote 0
              • jimpJ
                jimp Rebel Alliance Developer Netgate
                last edited by jimp

                It's possible you have a partial install on both the MMC and SSD and it's booting the wrong disk and thus kernel.

                https://docs.netgate.com/pfsense/en/latest/troubleshooting/boot-issues.html#multiple-disk-boot-issues

                You should wipe both the MMC and SSD and then reinstall to only the SSD, or at least wipe the MMC and then reinstall on SSD.

                Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                Need help fast? Netgate Global Support!

                Do not Chat/PM for help!

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