Error upgrading from 22.05 Release to 22.11 Development

[tedquade]

Enter an option: 13

Updating repositories metadata...
pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
Updating pfSense-core repository catalogue...
pkg-static: Repository pfSense-core has a wrong packagesite, need to re-create database
Fetching meta.conf: . done
Fetching packagesite.pkg: . done
Processing entries:
pkg-static: wrong architecture: FreeBSD:12:amd64 instead of FreeBSD:14:amd64
pkg-static: repository pfSense-core contains packages with wrong ABI: FreeBSD:12:amd64
Processing entries... done
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: Repository pfSense has a wrong packagesite, need to re-create database
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries:
pkg-static: wrong architecture: FreeBSD:12:amd64 instead of FreeBSD:14:amd64
pkg-static: repository pfSense contains packages with wrong ABI: FreeBSD:12:amd64
Processing entries... done
Unable to update repository pfSense
Error updating repositories!
Locking package pkg... done.
ERROR: Unable to compare version of pfSense-repo

Ted Quade

[stephenw10]

It's because 22.11 snapshots are not public yet. We still have a few glitches to iron out first.

There will be an announcement when they're available to upgrade to.

Steve

[kevindd992002]

@stephenw10 said in Error upgrading from 22.05 Release to 22.11 Development:

It's because 22.11 snapshots are not public yet. We still have a few glitches to iron out first.

There will be an announcement when they're available to upgrade to.

Steve

@stephenw10 , do we have any news on this? I'm upgrading from 2.7.0.a.20220714.0600 to 2.7.0.a.20220812.0002 and I'm getting the same upgrade issue. Do I just need to stay at the current version that I have?

[stephenw10]

On CE you can upgrade but if you were on an earlier 2.7 snap that was built on FreeBSD 12 (like you are) you need some manual steps to force the ABI switch.
See: https://www.netgate.com/blog/ce-snapshots-on-php-8.1-and-freebsd-main

So at the CLI run:

pkg-static -o ABI=FreeBSD:14:amd64 -o IGNORE_OSVERSION=yes update
pkg-static -o ABI=FreeBSD:14:amd64 -o IGNORE_OSVERSION=yes upgrade -fy pkg
pkg-static -o ABI=FreeBSD:14:amd64 -o IGNORE_OSVERSION=yes upgrade -fy pfSense-upgrade

You should then see the current 2.7 snaps available to upgrade to.

Steve

[kevindd992002]

@stephenw10 Thanks for the recommendation. Though I have a couple of question before trying to upgrade:

1. 

Does this mean I should try installing 2.6 (STABLE) on my box (which has 2.7.0.a.20220714.0600) first before trying to upgrade to the devel version?

2. If I remove all packages before upgrading and install them one by one after, will the package configuration be lost along the way?

3. 

Does it work with a ZFS install on a BIOS?

[stephenw10]

1. You should be able to upgrade in place from that version by running those three commands first. If you're going to reinstall just install the current 2.7 snapshot directly.

2. Package config should be retained. Some packages have an option to remove all config at uninstall but that is not the default.

3. If you are using a legacy BIOS that issue never applied, it will upgrade fine.
   However the new EFI loader in current snaps should allow that anyway. I haven't tested it yet though.

Steve

[kevindd992002]

What do the two other commands (after the first three) do?

Would it make sense to stay at 2.7 (or in general dev) or switch to 2.6 stable?

[stephenw10]

Those other command check that is can see updates and run the actual upgrade at the CLI. You can use those if you want or just use the webgui upgrade.

It depends why you're running dev in the first place. Was it just to test it? If this is a test box then it makes no sense to stay on an obsolete snapshot.

Steve

[kevindd992002]

@stephenw10 can you confirm if the update should work now without running those commands as mentioned here?

[grandrivers]

I wonder if the upgrade issue with zfs boot drives been fixed ?

[jimp]

@grandrivers said in Error upgrading from 22.05 Release to 22.11 Development:

I wonder if the upgrade issue with zfs boot drives been fixed ?

Yes, the EFI+ZFS upgrade issue has been fixed for a while. There is a new mechanism which updates the loader during the upgrade process.

[w0w]

It looks like 23.01 is available for upgrading from 22.05. Tried this on my test setup. You need to change the branch to "Experimental 23.01 devel" and then try the option 13. In my case the first time it ended in broken state, thanks to BOOT Environments I got it back and running, the second try was successful, it asked for pkg bootstrap -f and this time I did it, only pfBlockerNG-devel was broken after boot. Reinstalled packages, all seemed working until I went to option 13 and it searched for updates again telling me that everything is up-to-date and then asked me to proceed with update Y/N, I've chosen "NO" but no WEB UI since, everything looks working but not the WEB UI, restart does not help... I am not sure, am I doing something wrong or just 23.01 still not ready for testing?

[stephenw10]

Hmm, I suspect you are in a state somewhere between the two. Did you still have the dev branch selected when you ran the upgrade a second time?
Try running freebsd-version -kur that should report the same version for all three.

Steve

[w0w]

@stephenw10 said in Error upgrading from 22.05 Release to 22.11 Development:

freebsd-version -kur

I did another try now. This time I've uninstalled all packages, then switched to devel, went to option 13, it asked for pkg bootstrap -f
I did that and then again to the option 13, and it upgraded to the
23.01.a.20221111.0600
I've restored the configuration only for package manager.
The branch selection is now empty, but on the dashboard it shows

[stephenw10]

Hmm, was that instance upgraded from CE previously?
The branch selector will show empty like that if the NDI shows as no longer valid for some reason.

You shouldn't ever have to manually run the pkg bootstrap like that. Did you try upgrading through the the gui first?

Steve

[w0w]

@stephenw10 said in Error upgrading from 22.05 Release to 22.11 Development:

Hmm, was that instance upgraded from CE previously?

Yes.

@stephenw10 said in Error upgrading from 22.05 Release to 22.11 Development:

The branch selector will show empty like that if the NDI shows as no longer valid for some reason.

You shouldn't ever have to manually run the pkg bootstrap like that. Did you try upgrading through the the gui first?

No, I did not. I went to the console first, just did it out of habit... This bootstrap thing... I don't think it really needed, because it does not ask it every time I've tried to upgrade.

[stephenw10]

Hmm, well if it's still not showing you any branches it's because the server doesn't recognise the NDI for some reason. Has it changed?

[w0w]

@stephenw10
Perhaps I should clarify that the original version was CE 2.6, updated to 22.05, as you know, you have to update twice on 22.01 and then to 22.05. If now, for example, you have installed the latest CE 2.7 and trying to upgrade it to Plus version, you will get a downgrade effect like on the picture

If you try to do the such an upgrade, it will break your installation completely.

If you try to update the version 22.05 in console, you end with 23.01 version, but no branch appearing after upgrade.
NDI is still the same, and I can install packages and check for updates,

That make me think that some internal branch is selected somehow.

[kevindd992002]

@stephenw10

I'm trying to do a webgui upgrade now (I still haven't went thru it since two weeks ago when we were talking about this) but all I see now when I go to System -> Update is "unable to check for updates". Do you know what's causing this?

[stephenw10]

@kevindd992002
Run pkg-static -d update at the command line and see what error it returns.