pfSense CE 2.8.0 upgrade stalls after reboot and gets stuck in Stage 2

[i386DX]

@crepsv does it start if you enter bootloader prompt (ESC during autoboot countdown) and setup console to run dual console with

set console="comconsole,efi"
boot

I have a couple of Gen11 machine but didn't have the time to check

[crepsv]

Freeze here :

[stephenw10]

Does it actually have a comconsole? Anything shown there?

[Gertjan]

@crepsv

Just guessing : Is this some special kind of Logitech keyboard ?
I'm trying to understand why the kernel wants to root mount from usbus0 - or do you have a USB drive attached somewhere ?

[crepsv]

I tried an USB keyboard attached on the server, that's all.
I usually use the iLO console on HPE server.

Maybe a problem to boot on the SSD (da0/da1/da2 in Raidz-1) disk from the raid controler ?

[stephenw10]

Does it eventually time out and show an error?

Does it still respond to keyboard input?

Seeing something appear to stall at that point always makes me check the other consoles to be sure it's not just switched there.

[dave.opc]

HPE Proliant microserver Gen10 +v2
upgrading from 2.7.2 to 2.8.0 - got same issue
fresh 2.8.0 install after that - same issue
for now installing 2.7.2 from scratch untill this issue is fixed...

[stephenw10]

Probably going to need more info here to be able to fix it. Nothing we test on does that.

[dave.opc]

@stephenw10
probably this is related to freebsd 15 as 2.7.2 installed no problem after that.
and upgrades 2.7.2 -> 2.8.0 on virtual machines (xcp-ng) went smooth

[Gertjan]

@dave-opc said in pfSense CE 2.8.0 upgrade stalls after reboot and gets stuck when loading:

related to freebsd 15

Get a copy, and install a 'native FreeBSD 15' to find out ?

[crepsv]

@stephenw10

From VGA screen attached to the server (no iLO) :

No USB drive attached, only USB logitech keyboard attached in front of the HP server.
Keyboard input not responding after this screen.
No timeout.

I will wait for additionnal information or new release.

[dave.opc]

@Gertjan
sorry - impossible, the pc is used for pfsense and we don't have another one to experiment on.

[stephenw10]

One thing you could try here is booting verbose. Interrupt the boot to the boot loader prompt at the menu (OK>) and run: boot -v

That might give you more info about what it's actually waiting for there.

But those driver access errors are not good. They are attached via a hardware drive controller?

[crepsv]

@stephenw10

set console="comconsole,efi"
boot -v

[stephenw10]

Hmm, this seems familiar. It's similar to something we hit with a quirky UART implementation on specific hardware.

What does it show for detecting the UART(s) whenbooting verbose?

What happens if you set the console to EFI only?

[crepsv]

In "efi" only, the server reboot after this screen :

set console="efi"
boot -v

[stephenw10]

Hmm, well that's not helpful!

[InstanceExtension]

@stephenw10 Watching these other postings to see if any of them apply to my situation, nothing quite the same as far as I can tell.
Is there a boot option that will force the boot process to run a line at a time?

[eracerxrs]

Just tried to upgrade today and encountered the same problem as OP, freezing in nearly the identical location.

My pfsense instance is a proxmox vm, with the Intel Xeon D-1736NT host CPU passed through, 3 SR-IOV VFs passed through, q35 machine, SeaBIOS, VirtIO SCSI single controller, local ZFS volume.

Before I took this screenshot, it was freezing after the virtual IDE CD/DVD Drive was detected with no media, so I removed it from the hardware spec. Now it simply freezes at the preceding line.

Sorry I don't yet have time to start trouble shooting, I had to restore the snapshot to the previous 2.7.2, I just wanted to put it out there.

[InstanceExtension]

Supermicro just released new IPMI Firmware and a BIOS update for my X12SDV-4C-SPT4F motherboard. This seems like a good opportunity to see if that had any impact on the CE 2.8.0 upgrade and possibly the Intel firmware update package it has.

Sadly the CE 2.8.0 upgrade still did not succeed with the new IMPI and BIOS updates.

So, I tested a number of boot loader methods I see listed above.

set console="comconsole,efi"
set console="efi"
boot -v

Unfortunately, none of those seemed to have an impact either.

I did try all console methods again just to make sure the boot process did not end up somewhere else. That also did not make a difference. Stuck loading at the same spot.

Not sure what else to do at this point. Back on the working CE 2.7.2.