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

    Architecture change of 2.3.5-p1 with fresh install and restore fails

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    3 Posts 1 Posters 987 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.
    • S
      sepp_huber
      last edited by

      Hi,

      want to do an architecutre change of my 2.3.5-1 (i386) to 2.3.5 amd64.
      Background: we have CARP setup running and first I want to change the architecture of the Backup node.
      The Master and Backup node must run both an the 2.3.5-1 Version.

      Before doing this I read this here carefully:
      https://doc.pfsense.org/index.php/Upgrade_Guide#Changing_architecture_.2832-bit_to_64-bit_or_vice_versa.29_during_upgrade

      A backup of the 2.3.5-p1 i386 config is existing.
      I have downloaded the 2.3.5 current Version for amd64 and started a fresh install.
      The new installed system comes up with an 2.3.5 and not with 2.3.5-p1
      The I started the restore of my config backup from 2.3.5-1 (i386) to the new amd64.
      During the reboot it seems, that it installs almost everything new…( Remove 40 Packages

      There is an error message after the first boot:

      
      /etc/rc.initial: /etc/rc.banner: not found
      /etc/rc.initial: /usr/local/sbin/read_global_var: not found
      
      

      I can log in on the webconfigurator, but when I check for updates
      "Unable to check for updates"
      When I reboot the system it is complete broken!

      The next try was to do an fresh install and da an upgrade to 2.3.5-p1 before the config restore.
      I changed the repostory settings in the UI to "Legacy stable version (Security/Errata only 2.3.x)" and
      After the upgrade the new installed system comes up with an 2.3.5-p1.
      After the config restore it comes up again with 2.3.5 … strange.

      But it ends in the same result ... the system is broken after reboot.

      My repository directory looks like this:

      
      lrwxr-xr-x  1 root  wheel  62 Jan 22 14:39 .conf -> /usr/local/share/pfSense/pkg/repos/pfSense-repo-legacy-23.conf
      -rw-r--r--  1 root  wheel  26 Oct 24 11:18 FreeBSD.conf
      lrwxr-xr-x  1 root  wheel  62 Jan 22 14:58 pfSense.conf -> /usr/local/share/pfSense/pkg/repos/pfSense-repo-legacy-23.conf
      
      less /usr/local/etc/pkg/repos/pfSense.conf
      FreeBSD: { enabled: no }
      
      pfSense-core: {
        url: "pkg+https://pkg.pfsense.org/pfSense_v2_3_5_amd64-core",
        mirror_type: "srv",
        signaqture_type: "fingerprints",
        fingerprints: "/usr/local/share/pfSense/keys/pkg",
        enabled: yes
      }
      
      pfSense: {
        url: "pkg+https://pkg.pfsense.org/pfSense_v2_3_5_amd64-pfSense_v2_3_5",
        mirror_type: "srv",
        signature_type: "fingerprints",
        fingerprints: "/usr/local/share/pfSense/keys/pkg",
        enabled: yes
      }
      
       uname -a
      FreeBSD XXXXXXXXX 10.3-RELEASE-p26 FreeBSD 10.3-RELEASE-p26 #1 00efe4d5333(RELENG_2_3): Mon Dec 11 08:14:03 CST 2017     root@ce23-amd64-builder:/builder/pfsense-235/tmp/obj/builder/pfsense-235/tmp/FreeBSD-src/sys/pfSense  amd64
      
      

      It seems that pfsense is confused about the repositories

      Any ideas?

      1 Reply Last reply Reply Quote 0
      • S
        sepp_huber
        last edited by

        When system is complete disconnected and then the restore is done …
        the selected repo is 2.4.2 in /usr/local/etc/pkg/repos/pfSense.conf!

        It seems that I cannot use the "old" 2.3. Version after a restore.

        Is there a possibility to enforce this... I cannot find a switch in the config.xml?

        1 Reply Last reply Reply Quote 0
        • S
          sepp_huber
          last edited by

          Got it  :P

          In the config.xml there is a switch for the repo and it had the value

          
          <pkg_repo_conf_path>/usr/local/share/pfSense/pkg/repos/pfSense-repo.conf</pkg_repo_conf_path>
          
          

          … but in the UI it is configured as "Legacy stable version (Security/Errata only 2.3.x)"

          When I change it to the legacy repo manually

          
          <pkg_repo_conf_path>/usr/local/share/pfSense/pkg/repos/pfSense-repo-legacy-23.conf</pkg_repo_conf_path>
          
          

          The restore of all areas then selects the right repo…

          So in my opinion there is a bug in the backup of the repo configuration to config.xml.

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