PFSense hangs up while booting
-
I'm hoping for some help here for my system that suddenly stopped working. It posts and starts booting, but hangs before loading the OS. The boot sequence looks like:
Loading kernel... /boot/kernel/kernel text=0x19ba10 text=0xfdab90 text=0x17dcbb0 data=0x100 data=0x222690+0x3dc970 0x8 +0x1c74604+0x8+0x1d5994 Loading configured modules... /bootikernel/cryptodeu.ko size 0x76f8 at 0x359d000 /bootikernel/opensolaris.ko size 0xle2b0 at 0x35a5000 can't find '/etc/hostid' /boot/entropy size=0x1000 /bootikernelizfs.ko size 0x5d6ea0 at 0x35c5000 staging 0x0d000000 (not copying) tramp 0x96b37000 PT4 0x96b2e000 Start @ 0xffffffff8039c000 ... EFI framebuffer information: addr, size 0xa0000000, 0x7e9000 dimensions 1920 x 1000 stride 1920 masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000 (information text)It was working fine one day and started doing this the next. Any ideas on what might have happened and how to get it working again would be appreciated.
-
That's an EFI loader/console issue. Do you know it was actually showing anything more past that point before the console menu is shown?
It could well be booting past that but just not displaying it. Then hanging at the interfaces assign screen for example.
What pfSense version is that? What version was initially installed? What hardware is it?
Steve
-
@stephenw10, auto updates we're on so it should be pretty recent. Video used to work as it was set up that way. It never makes the beeps to indicate that it has loaded. It's running on a protectli vp4630.
Thanks.
-
@stephenw10 said in PFSense hangs up while booting:
That's an EFI loader/console issue. Do you know it was actually showing anything more past that point before the console menu is shown?
It could well be booting past that but just not displaying it. Then hanging at the interfaces assign screen for example.
What pfSense version is that? What version was initially installed? What hardware is it?
Steve
I was getting this error too on my HP EliteDesk 805 G6 running Proxmox. For some weird reason, after a few reboots on a fresh installation (I believe I selected GPT UEFI/BIOS during setup) PfSense loads perfectly fine. I update from CE to Plus and it seems like it downloads AMD files to make 'it work' during upgrade. After that, I restart multiple times and I no longer get stuck on the screen OP listed.
This happens on both running it bare metal as well as in a VM (Proxmox). HP EliteDesk is set to UEFI but secure boot is disabled.
-
pfSense will never upgrade itself automatically. You would have to have upgraded it manually. If it was originally installed using a much older version (<2.6) then it may not have seen that issue at the time.
-
@stephenw10, I had seen the settings for update check, but I guess that just notifies you if you are not running the latest version. It was on 2.7.1. This morning I got a keyboard plugged in and broke out of the autoboot. I had it print out some information from the console and not seeing anything, I just told it to "boot" and it wound up booting all the way through. It was on 2.7.1 and I'm updating to 2.7.2 now. Hopefully this doesn't happen again as I didn't really do anything to get it working. Maybe it just worked after a couple of boots like @rtorres.
Thanks
-
@stephenw10 Not too sure but when I would reboot while in CE, I'd get stuck on the message OP posted but after a couple of reboots I was able to load and update to pfSense Plus. Which in turn, looking at the upgrade process, downloaded amd64 files and prevent the hang up on that screen.
I'll see if I can replicate when 24.03 releases. I like to do a clean install from CE to pfSense Plus when a major release comes out.
Since OP said that he was able to boot after a few reboots, what can cause the issue? At first I thought it was due to running pfSense in Proxmox but it even happened on bare metal.
-
If you're running pfSense as a VM on Proxmox (like I am), you'll likely go through multiple reboots with no problems... then one day it will just happen. Not sure exactly the cause... I assume something more than dumb luck triggered it to happen...
Either way the fix was simple enough in my case.- Power off then on (or "reset") the VM while viewing the console via Proxmox UI
- When you see the initial Proxmox BIOS boot/splash screen, press F2 to enter it
- Go to "Device Manager" >> "OVMF Platform Configuration"
- Update the "Change Preferred" value to a more common (if there is such a thing) resolution value E.G. 1024x768
In my case the original value was 1280x800 - Select "Commit Changes and Exit", then back out to the main BIOS screen.
- NOTE: Make sure you "Reset" when exiting the BIOS... not "Continue". This forces the new configuration to be applied and will be seen by pfSense
That should do the trick.
