@william-mandell said in Unable to upgrade SG-1100 appliance to 23.01 - Kernel panic:

@jimp

No Jim , sorry, but no. Not an older version of pfsense plus at all.

I was on the Newest version of pfSense Plus+ that was the release #, 'freshly' and (*natively) installed before > and updated to 23.01 obviously after 23.01 came out, but before I saw that it was being 'blocked' because of some problems going on.

Those statements are contradictory. Either you installed 23.01 directly or you were on 22.05 and upgraded to 23.01.

That said, I checked around and apparently it's a known issue that the 1100 and 2100 recovery installers are using an older ZFS version in the disk images.

While you could run zpool upgrade -a and let it upgrade that, if it didn't properly update the loader when you updated to 23.01 then it may not boot properly after. If you did reimage it with 23.01 and not an upgrade, then it's safe to run.

How and why would I want to boot it to the older version(s) ZFS boot environment , its has ZFS now. The 'old' environment always said it has an 'error' and shouldnt even running, but TAC said y'all had a special version, so it's fine.

If you upgraded from 22.05 to 23.01 and had a problem on 23.01, you could use the boot environment to boot back into 22.05 without reinstalling.

Can I ask again, how EXACTLY do I run a program that uses your special Chip' on board to verify and authenticate that my system is running authentic pfSense+ software. Does it need to be 'on'? Not sure if it's the same chip but whichever one displays whether it is on or not has always been off. Thought that chip was for VPN? Anyway, the trademarked pc sense chip to verify and authenticate - the software running.

The device that handles the authenticity part is used by the device when accessing the package repositories for packages and updates (all automatic). That is the "thoth" security chip.

VPN acceleration on 1100/2100 is handled by a different function, the SafeXcel cryptographic accelerator, which is unrelated.

@komsalov First check here:

https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors

Then check here:
https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide-versions.html#upgrading-from-versions-older-than-pfsense-2-5-0

If you are running a Netgate ARM device (1000, 1100, 2100, 3100) the AMD64 image on pfsense.org will not work.

If you are on 22.05 and want to stay there and make changes to packages you need to go to System > Update and set the update Branch to stay on 22.05.

If the branch is set to 23.01 it's going to try to pull things from 23.01.

The 3100 is fine on 23.01 in general, the problem that affected the 1100/2100 only affected the 1100/2100 and not other platforms.

@reggie14 not 100% sure why it worked the second time, BUT I did shut down all packages before the second attempt… didn’t uninstall… just shut them down.

@steveits said in Update Failing:

https://forum.netgate.com/topic/178049/pfsense-plus-23-01-updates-on-the-1100-and-2100-systems

Thanks so much. I will do the needful.

@jimp I'll post this question there, thanks.

@rcoleman-netgate

Ah thanks for the correction and the clarification! I'll look into requesting the 23.01 image from TAC.

@tse-0

Since all "Non Netgate HW" are on a "Install CE - Then Upgrade to Plus" path.

I think that what you see are normal, as the current "In prod" Plus-Release is 23.01.

/Bingo

@avr-it They only paused 1100/2100.

@dmart2112

You may be able to,

make a backup of the VM Work with shadow copies Or plain copy over the VM

If something occurs you will be fast back in the lab.

@steveits

Will do. Thanks

@alan-t You can but I believe you still need to go in order from 22.01 first.

@rcoleman-netgate I have the exact same problem as the OP here. Can you help? I tried an upgrade from 2.6.0 CE to 22.1 and it originally let me start it....but never finished or rebooted after hours of waiting. Now it just only shows it is up to date and with 2.6.0 as the only option in the Upgrade path.

@jimp Tested the 3/1/2023 release of CE 2.7 with E core enabled. No corruption and it completed the boot cycle successfully.

@rhammondwtg It sounds like they're working on adding a check to look for routers with the small partition (referenced in your link) and stopping the upgrade. That will let everyone else upgrade safely. But in the meantime it's off, so those of us with early-release models aren't left with a non-functioning router. So, manual (re)install, or wait.

It's something we are working on, but it's not ready yet.

Never mind. Just saw what I was missing in that image. The partition is 200M, not 200K. Carry on!

@dobby_ said in System > Update > Branch > Show nothing (after Upgrade to 23.0.1):

I was looking under that link here pfSense roadmap

I had assumed that was the case.
Those 5 bugs apply only to the plus branch (will not be incorporated in the community version)

Target version: 23.05

However if you look at most of the entries for 2.7 you will see

Target version: 2.7 Plus version: 23.05

The search I linked was for target version 23.05 or Plus version: 23.05 which gives a better idea of what is outstanding.

Agree...

What I am trying to do is not waste my time waiting for a download over a small bandwidth connection.

I would like to preload / download the upgrade package... which could take some time...

Once downloaded, then I can come back and upgrade...

Similar to TrueNAS in how they allow you to download the upgrade... then later come back at a convenient time to actually do the upgrade...

Can a preload be done ?

Thanks.