[Solved] Attempt to Upgrade to Opnsense 26.7 hangs on reboot at "masks"

Started by BryanC1968, July 15, 2026, 04:19:31 PM

Previous topic - Next topic
Quote from: franco on July 15, 2026, 07:50:40 PMAllegedly this was fixed in late 15.1 RC cycle: https://github.com/opnsense/src/commit/56e59980b67
But the fix affects loader.efi, so it's not actually effective until the bootloader gets updated in ESP: https://www.freebsd.org/releases/15.1R/upgrading/#upgrade-loader-uefi

That's not something that happens as part of the OPNsense upgrade (should it?).

You're right. Doesn't change the fact that everyone including 26.7 would be affected either way by it unless they did a clean reinstall.


Cheers,
Franco

Quote from: jll544 on Today at 09:05:10 AM
Quote from: franco on July 15, 2026, 07:50:40 PMAllegedly this was fixed in late 15.1 RC cycle: https://github.com/opnsense/src/commit/56e59980b67
But the fix affects loader.efi, so it's not actually effective until the bootloader gets updated in ESP: https://www.freebsd.org/releases/15.1R/upgrading/#upgrade-loader-uefi

That's not something that happens as part of the OPNsense upgrade (should it?).
Patrick and meyergru have made some excellent instructions about upgrading the bootloader in a couple of topics so I am sure they can help you out in one of those topics :)

Quote from: Patrick M. Hausen on July 15, 2026, 06:03:22 PMSystem > Settings > Administration > Console
Quote from: meyergru on July 15, 2026, 06:22:19 PMYes.
I don't have the exact links anymore so could one of you do that part ?

Thnx! in advance ;)
Weird guy who likes everything Linux and *BSD on PC/Laptop/Tablet/Mobile and funny little ARM based boards :)

https://forum.opnsense.org/index.php?msg=243083

However, the process is different for BIOS and UEFI boot, sometimes it depends on the type of boot disk and / or partitioning.

This is the reason why there is no automatic bootloader update (or upgrade of zpool options, FWIW). And if you want to update like depicted in the link, you need to have booted the NEW system first, which sometimes does not work, so it is a catch-22. That is why Franco wrote:

Quote from: franco on Today at 09:19:41 AMDoesn't change the fact that everyone including 26.7 would be affected either way by it unless they did a clean reinstall.
Intel N100, 4* I226-V, 2* 82559, 16 GByte, 500 GByte NVME, Leox LXT-010H-D

1100 down / 450 up, Bufferbloat A+

I thought I'd share a related experience, though I didn't experience a direct crash. I have a CWWK S7 Pro (Intel N150) that was running 26.1.10_11. I had no issues with the `os-cpu-microcode-intel` package until attempting the upgrade to 26.7.

After rebooting, the upgrade process would start and then fail (log snippet below). I ended up power cycling the device, as I had no KVM connected to it. This left the system in an odd state where it was running the 15.1 kernel, but the OPNsense version was still showing as 26.1.10.
 
I ended up removing the `os-cpu-microcode-intel` package and then running `opnsense-update -u` from the command line. The normal upgrade process was just reporting "nothing to do."

[12/360] Extracting os-upnp-1.9: ....... done
Reloading plugin configuration
Flushing all caches...done.
Configuring system logging...done.
Reloading template OPNsense/Syslog: configd socket missing (@/var/run/configd.socket)
pkg-static: POST-INSTALL script failed
[13/360] Upgrading pciids from 20260522 to 20260624...
[13/360] Extracting pciids-20260624: ..... done
[14/360] Reinstalling libpci-3.15.0...
[14/360] Extracting libpci-3.15.0: .......... done
[15/360] Reinstalling x86info-1.31.s03_1...
[15/360] Extracting x86info-1.31.s03_1: ....... done
[16/360] Reinstalling os-cpu-microcode-intel-1.1...
[16/360] Extracting os-cpu-microcode-intel-1.1: .. done
Reloading firmware configuration
failed waiting for configd (doesn't seem to be running)
failed waiting for configd (doesn't seem to be running)
failed waiting for configd (doesn't seem to be running)