Stuck on boot after update from 23.09.1

w0w

FreeBSD w0wkin_backup.xxxnetxxx 15.0-CURRENT FreeBSD 15.0-CURRENT #0 plus-devel-main-n256210-27a33170a82: Wed Jan 3 06:33:39 UTC 2024 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/obj/amd64/IdNrMCMq/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/amd64.amd64/sys/pfSense amd64
![stop.jpg]
If I interrupt the boot process and choose "Boot environments" by pressing 8, it picks the initial snapshot out of the 17 available. However, if I simply navigate by pressing "2" until it loops back to the first one of the 17, it boots up smoothly.

What could be causing this? I vaguely remember encountering a similar issue before but can't recall the specifics of how it occurred or what the solution was.

jimp

It's hard to know for certain what may be doing that since there are a couple different issues in the loader that we've been looking into that could be related.

There is one issue where the way the loader ends up loading some modules is problematic and even going to a loader prompt and running autoboot will let it boot successfully. In one case we also saw that happen from a specific USB device being plugged in while it booted (not all USB devices, just happened to one system).

If it's a VM, adding a serial console to the VM may help work around the problem. Similarly, if it's hardware and it has a serial port and the serial port is disabled in the BIOS, re-enabling it may allow it to work.

w0w

@jimp
Unfortunately autoboot hangs also and serial port was also enabled with the same hanging

Could there be a regression in the code? I see some patches for FreeBSD 13.

JonathanLee

@w0w me too, mine also corrupted all the other boot environments

w0w

The workaround is to include the following line in the configuration:

console="vidconsole,comconsole"

To ensure these setting persist through upgrades, use the /boot/loader.conf.local file.
I would like to draw your attention to the fact that I haven't used the serial console before. Also, the line boot_serial="NO” is already present in the file.

Nevertheless, I'm not certain that the issue lies, for example, in the fact that the boot code was updated incorrectly or that not all patches were applied.

JonathanLee

@w0w Mine would never boot any BE again after. I had to start from scratch and or use my backup SSD. It really messed it up for me.