2.3.6-DEVELOPMENT upgrade to 2.4



  • I recently attempted to upgrade my 2.3.6-DEVELOPMENT nanoBSD system to 2.4 using these instructions https://docs.netgate.com/pfsense/en/latest/install/upgrading-64-bit-nanobsd-2-3-to-2-4.html . Everything seemed to go well, but when I rebooted, I noticed I was still on 2.3.6-DEVELOPMENT. It looks like I might be running the full install of pfSense as opposed to the nanoBSD install. This is the banner when logging in over SSH *** Welcome to pfSense 2.3.6-DEVELOPMENT (amd64 full-install) on pfsense ***

    I tried to upgrade but got back an error message:

    [2.3.6-DEVELOPMENT][admin@pfsense]/root: pfSense-upgrade 
    ERROR: It was not possible to identify which pfSense kernel is installed
    [2.3.6-DEVELOPMENT][admin@pfsense]/root: 
    

    I did some looking around and trying to reinstall the base packages but get a message saying a Major OS version upgrade is detected:

    [2.3.6-DEVELOPMENT][admin@pfsense]/root: pkg install pfSense pfSense-base pfSense-default-config pfSense-kernel-pfSense pfSense-rc pfSense-repo pfSense-upgrade
    pkg: Warning: Major OS version upgrade detected.  Running "pkg-static install -f pkg" recommended
    [2.3.6-DEVELOPMENT][admin@pfsense]/root: pkg-static install -f pkg
    pkg-static: Warning: Major OS version upgrade detected.  Running "pkg-static install -f pkg" recommended
    [2.3.6-DEVELOPMENT][admin@pfsense]/root: 
    

    It looks like the pkg config is pointed at the right repositories

    [2.3.6-DEVELOPMENT][admin@pfsense]/root: cat /usr/local/etc/pkg/repos/pfSense.conf 
    FreeBSD: { enabled: no }
    
    pfSense-core: {
      url: "pkg+https://pkg.pfsense.org/pfSense_v2_4_4_amd64-core",
      mirror_type: "srv",
      signature_type: "fingerprints",
      fingerprints: "/usr/local/share/pfSense/keys/pkg",
      enabled: yes
    }
    
    pfSense: {
      url: "pkg+https://pkg.pfsense.org/pfSense_v2_4_4_amd64-pfSense_v2_4_4",
      mirror_type: "srv",
      signature_type: "fingerprints",
      fingerprints: "/usr/local/share/pfSense/keys/pkg",
      enabled: yes
    }
    

    The webConfigurator GUI states that it's Unable to check for updates

    Could someone help me troubleshoot this upgrade to 2.4?



  • Found part of the problem, pkg.pfsense.org doesn't resolve

    [2.3.6-DEVELOPMENT][admin@pfsense]/root: /usr/sbin/pkg bootstrap -f
    The package management tool is not yet installed on your system.
    Do you want to fetch and install it now? [y/N]: y
    Bootstrapping pkg from pkg+https://pkg.pfsense.org/pfSense_v2_4_4_amd64-pfSense_v2_4_4, please wait...
    pkg: Error fetching https://pkg.pfsense.org/pfSense_v2_4_4_amd64-pfSense_v2_4_4/Latest/pkg.txz: No address record
    A pre-built version of pkg could not be found for your system.
    Consider changing PACKAGESITE or installing it from ports: 'ports-mgmt/pkg'.
    

    I did change it to use https://files00.netgate.com/pfSense_v2_4_4_amd64-pfSense_v2_4_4 instead and that helped with the /usr/sbin/pkg bootstrap -f command to work. However, I did have to manually create a /etc/resolv.conf file for some reason and put a DNS server in there.

    I disabled RAM disks, rebooted, and was able to re-install the packages with:

    [2.3.6-DEVELOPMENT][admin@pfsense]/root: pkg install pfSense pfSense-base pfSense-default-config pfSense-kernel-pfSense pfSense-rc pfSense-repo pfSense-upgrade
    pkg: Warning: Major OS version upgrade detected.  Running "pkg-static install -f pkg" recommended
    Updating pfSense-core repository catalogue...
    pfSense-core repository is up to date.
    Updating pfSense repository catalogue...
    pfSense repository is up to date.
    All repositories are up to date.
    The following 153 package(s) will be affected (of 0 checked):
    

  • LAYER 8 Netgate

    I would stop wasting time and install a fresh 2.4.4-p2 and restore the configuration.

    Note that there is NO GUARANTEE that a configuration file from a development version will import correctly but I expect you will not have any problems.



  • @Derelict Yep, that is what I'm going to have to do. Especially since the I can't reach the HTTP or SSH interfaces anymore. Just waiting for a USB to female serial cable to arrive.


Log in to reply