PfSense+ 22.05 -> 23.01 Boot Failure after Upgrade
-
Upgraded 22.05 pfsense+ to 23.01 today and stuck at boot with the following error:
Loading kernel..
/boot/kernel/kernel text=0x1a8f80 text=0x1052b58 text=0x1a260c0 data-0x140 data=0x2618c4+0×59d73c 0x8+0x1ccba8+0×8+0×1d7685/
loading configured kernel modules
/boot/kernel/zfs.ko size 0x5b2878 at 0x3ba5000
/etc/hostid size=0×25
/boot/kernel/opensolaris.ko size Oxaab0 at 0x4158000
/boot/entropy size=0×1000
staging Oxaa200000 (not copying) tramp Oxb6ac0000 PT4 Oxbab7000
Start @ Oxffffffff803a9000
EFI framebuffer information:
addr, size 0x0000000 , 0×500000
dimensions 1280 × 1024
stride 1280
masks 0x00ff0000. 0x0000ff00. 0x000000ff. 0xff000000Anyone have any ideas how to get beyond this? I have changed boot environment and gone back to 22.05 for now but I would like to make sure this is up to date pretty soon for security reasons..
-
J jimp moved this topic from Problems Installing or Upgrading pfSense Software on
-
What type of hardware or hypervisor is this installation running on?
-
- Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
4 CPUs: 1 package(s) x 4 core(s)
AES-NI CPU Crypto: Yes (active)
- CPU: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz (3292.45-MHz K8-class CPU)
- Real memory = 8589934592 (8192 MB)
- Avail memory = 7926775808 (7559 MB)
- Intel(R) I217-LM LPT
- Intel(R) Gigabit CT 82574L
- Intel(R) PRO/1000 PT 82572EI (Copper)
- HP NC552SFP/Emulex OCE11102 Dual-Port 10Gb Network Adapter
- Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
-
@roach32 FYI on security, there are patches in the System Patches package for 22.05.
-
thanks for this. unfortunately, all pkgs moved to php8.1 so cannot install system patches package on plus 22.05. Getting this msg:
WARNING: Current pkg repository has a new PHP major
version. pfSense should be upgraded before
installing any new package. -
@roach32 oh that’s great they added a warning! Interesting I don’t see that yet on my 22.05 but might be triggered by trying an install or update.
In System/Update change your branch to Previous Stable Version which is now 22.05, then you can install/update packages. Change to Current to upgrade to 23.01.
-
I'm not aware of anything that would prevent that specific system from booting, I mostly asked because we had some similar reports from Hyper-V users that it stopped there, but we haven't been able to consistently reproduce that in lab conditions.
To start with I'd check System > Advanced, Admin Access tab and make sure you do not have the serial console enabled.
-
Also if you get those pkg errors, you might want to force a reinstall of pkg after selecting the previous stable/22.05 branch.
: pkg-static bootstrap -f : pkg-static update -f -
@steveits you rock! that worked great
-
many thanks Jim. serial console isn't enabled. at any rate, I ordered a brand new server to replace this unit today since I have been wanting to upgrade to a proper powerful server to go the TNSR route and retire this one workstation-class box that isn't upgrading to 23.01. the 6 others will remain on pfsense +.
-
I'm also having this problem with Hyper-V, the system won't finish booting.
I left it for more than 2 hours, before returning with the snapshot.
It simply hangs on the message: masks 0x00ff0000. 0x0000ff00. 0x000000ff. 0xff000000
And it doesn't go away for hours. -
-
My installation of pfsense has 15GB of disk, which leads me to believe that there is no space.
I just tried to update again and it failed again.
I'm completely tied hand and foot. -
Like it filled at update or was already full?
if you roll back to an earlier snapshot how much is used?
-
This is my gpart status
-
That doesn't show how much of the drive is in use. I assume you see a lot less used space in the hypervisor?
-
Do you think if I increase the size from 20GB to 80GB it will solve this installation error?
-
Probably, if it;s simply filling the drive at upgrade.
-
Would you have any tutorial on how to expand the space within pfsense?
-
In some cases,
touch /root/force_growfsand then rebooting is sufficient. But that depends on which part of the disk is running out of space. That's quick and easy to try.A clean install of a recent base is best if you can.
