SG2100 stuck on update or package install
-
@stephenw10 Now I see both options and locked the "previous stable" which is 22.05.1 in my case (shouldn't it be 23.01 btw. from the usual way?) I'll give it 10 min, then I'm going to reboot and try to install a package and see
-
You should be good if you want to stay on 22.05.1 now.
I'm looking into an issue upgrading to 23.05.1...
-
The options there are 'stay on the currently installed version' or 'upgrade to the latest release'.
We could probably add 23.01 in there if there's a use case but it normally wouldn't be once 23.05 had been released.
Steve
-
@stephenw10 Both options are what is needed for me now. Packages now install smoothly so I'm on my way now. I'll try to store our config into the current "locked" version and see if the import runs on the usual tracks.
-
@stephenw10 That's what disturbed me most, as there was no way to escape this deadlock: no old version, new version offered but not able to update (gui+shell). That was the staring point to this thread. I wondered why nobody else had this problem before or even mentioned....
-
Yes, it's because 22.05.1 is an edge case. It was only ever created to allow for some hardware changes before 23.01 was ready. Since 23.01 was released most of the 2100s that were installed with 22.05.1 would have been upgraded and anything newer would have had 23.01 by default.
There's a problem with upgrades we're looking into now....
-
Ok, because of differences in the pkg system you cannot upgrade to 23.05.1 directly. So you should now see 23.01 as the only upgrade option. From there you can upgrade to 23.05.1.
If you find it is failing to upgrade on a system then was on-line today it may have pulled in the newer pkgs. If that's the case set the upgrade repo back to 22.05.1 and then run at the command line:
pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgradeThat will restore the original pkgs and you can then set the branch to 23.01 and upgrade.
Steve
-
@stephenw10 I see on my testdevice 23.05.1 (latest) and 22.05.1 (previous), which is unusal. I'm muchg aware of the bis step from FBSD12 to 14 with 22.x to 23.01, so before then we have to check all old systems for the ZFS Update and the maybe too small /boot.
The Import and pkg uninstall+reinstall worked as I'd expected it from last week. The points that concerned me most are solved so far.
Thanks for the help!
-
If those devices were supplied loaded with 22.05.1 the loader partition should be large enough to upgrade to 23.01. I just tested that here.
Steve
-
Additionally @michael_samer if they are running ZFS they will be big enough, too.
-
@stephenw10 said in SG2100 stuck on update or package install:
If those devices were supplied loaded with 22.05.1 the loader partition should be large enough to upgrade to 23.01. I just tested that here.
Steve
This about 60 (SG3100) boxes are 1-5 years old in widely spreaded around (and ZFS more by luck than wisdom). Very rarely reinstalled with a newer build, but updated as usual. I'm glad I read about the 23.01 Rollout and its size problems. Anyway we are aware of it and that's OK. So no Enerprise Rollout (dynfi) but one by one.
You will surely read from me, if got stuck again, but in most cases I get things running on my own :-)
-
The EFI loader issue only affected aarch64 devices (1100 or 2100) so any 3100s should be fine. Though 3100s (arm32) cannot run ZFS so maybe that was a typo?
-
S SteveITS referenced this topic on
-
@stephenw10 Ah OK; thought the problems were over all 23.01 Upgrades. Never watched which Hardware it was reported on.
