[SOLVED] Upgrade in situ "Reloading firmware configuration"

[fbantgat7]

I've upgraded in situ rather than re-install 26.1 and the upgrade completed.  There was a glitch and a warning, so I am not sure the upgrade went as intended.

The upgrade was stuck at this point for quite a few minutes:

Code Select Expand

[165/179] Reinstalling unbound-1.24.2...
===> Creating groups
Using existing group 'unbound'
===> Creating users
Using existing user 'unbound'
[165/179] Extracting unbound-1.24.2: .......... done
[166/179] Reinstalling wpa_supplicant-2.11_7...
[166/179] Extracting wpa_supplicant-2.11_7: .......... done
[167/179] Reinstalling x86info-1.31.s03_1...
[167/179] Extracting x86info-1.31.s03_1: ....... done
[168/179] Reinstalling os-cpu-microcode-amd-1.1...
[168/179] Extracting os-cpu-microcode-amd-1.1: .. done
Reloading firmware configurationPerhaps I should have waited longer before I entered Ctrl+c:

Code Select Expand

^C
Launching the init system...[169/179] Upgrading zip from 3.0_4 to 3.0_5...
[169/179] Extracting zip-3.0_5: .......... done
[170/179] Reinstalling zstd-1.5.7_1...
done.
Initializing...[170/179] Extracting zstd-1.5.7_1: .......... done
.......done.
[171/179] Reinstalling boost-libs-1.89.0_1...
[171/179] Extracting boost-libs-1.89.0_1: .......... done
[172/179] Reinstalling curl-8.17.0...
[172/179] Extracting curl-8.17.0: .......... done
[173/179] Reinstalling kea-3.0.2...
[173/179] Extracting kea-3.0.2: .......... done
[174/179] Upgrading php83-curl from 8.3.28 to 8.3.30...
[174/179] Extracting php83-curl-8.3.30: .......... done
[175/179] Reinstalling strongswan-6.0.3_1...
[175/179] Extracting strongswan-6.0.3_1: .......... done
[176/179] Reinstalling syslog-ng-4.10.2...
[176/179] Extracting syslog-ng-4.10.2: .......... done
[177/179] Upgrading opnsense from 25.7.11_9 to 26.1.1...
[177/179] Extracting opnsense-26.1.1: .......... done
configd not running? (check /var/run/configd.pid).
Resetting root shell
Updating /etc/shells
Unhooking from /etc/rc
Unhooking from /etc/rc.shutdown
[Snip ...]
There was also a warning as it was rebooting:

Code Select Expand

>>> Invoking start script 'freebsd'
Sync KEA DHCP config...done.
Starting kea.
INFO/keactrl: Starting /usr/local/sbin/kea-dhcp4 -c /usr/local/etc/kea/kea-dhcp4.conf
INFO/keactrl: Starting /usr/local/sbin/kea-dhcp6 -c /usr/local/etc/kea/kea-dhcp6.conf
Starting hostwatch.
error: the argument '--user <USER>' cannot be used multiple times

Usage: hostwatch [OPTIONS]

For more information, try '--help'.
/usr/local/etc/rc.d/hostwatch: WARNING: failed to start hostwatch
>>> Invoking start script 'syslog'
>>> Invoking start script 'carp'
>>> Invoking start script 'cron'
Starting Cron: OK


>>> Invoking start script 'openvpn'
>>> Invoking start script 'sysctl'
Service `sysctl' has been restarted.
>>> Invoking start script 'beep'
Root file system: zroot/ROOT/default
Sat Feb  7 12:36:06 GMT 2026

*** OPNsense.internal: OPNsense 26.1.1 (amd64) ***The hosts on the LAN were able to receive IPv4/6 addresses and these guys are running at present:

Code Select Expand

:~ # ps axf | grep watch
10243  -  Is     0:00.00 daemon: /usr/local/opnsense/scripts/kea/kea_prefix_watcher.py[10246] (daemon)
10246  -  S      0:01.09 /usr/local/bin/python3 /usr/local/opnsense/scripts/kea/kea_prefix_watcher.py /var/db/kea/kea-leases6.csv (python3.11)
72154  -  Is     0:00.00 daemon: /usr/local/opnsense/scripts/routes/gateway_watcher.php[72212] (daemon)
72212  -  S      1:04.51 /usr/local/bin/php /usr/local/opnsense/scripts/routes/gateway_watcher.php interface routes alarmGiven the above was the upgrade successful?  Is there anything I should take care of before I try to reboot?

[franco]

Looks like partial upgrade. Personally I'd use opnsense-bootstrap here to ensure all the files are consistent.

As far as this goes and hangs:

> Reloading firmware configuration

Might be better to remove it temporarily and keep it under observation. Got one other report that the recent-ish AMD microcode causes boot stalls.


Cheers,
Franco

[fbantgat7]

Thank you for the suggestion to use opnsense-bootstrap.  It completed without any problems.  An update after it rebooted installed the following packages:

Code Select Expand

New packages to be INSTALLED:
        cpu-microcode-amd: 20251202
        cpu-microcode-rc: 1.0_2
        libpci: 3.14.0
        os-cpu-microcode-amd: 1.1
        pciids: 20251206
        x86info: 1.31.s03_1
The SoC on this box does not have any microcode applicable for it.  All seems to work fine now.

Thanks again for your help! :-)

[nero355]

Looks like partial upgrade. Personally I'd use opnsense-bootstrap here to ensure all the files are consistent.

So just to be sure :

Whenever the upgrade window/logging shows issues that can't be solved easily you can run : https://github.com/opnsense/update?tab=readme-ov-file#opnsense-bootstrap
After logging into your OPNsense via SSH and after succesfull outcome of the procedure the file integrity of the system should be restored to safely enough reboot into the latest version ?

If so : NICE!!! :)

[fbantgat7]

So just to be sure :

After logging into your OPNsense via SSH and after succesfull outcome of the procedure the file integrity of the system should be restored to safely enough reboot into the latest version ?

If so : NICE!!! :)

Yes, the opnsense-bootstrap script uninstalls all packages and re-installs them afresh.  You can select the major release branch to install, or can select snapshot mode to install from the latest development branch.  The process is pretty much automated and quite sleek.  :-)

The alternative would be to perform a fresh install, reformatting the drive.  I was about to do this, just as Franco pointed out to the opnsense-bootstrap handy tool.

[franco]

Keep in mind opnsense-bootstrap is a bit of a nuclear option. I normally don't recommend it without accessing the situation. Most of the time it's easy to just reinstall a package from the firmware GUI to get the files back to where they were supposed to be. The health audit will help you with finding the ones that have issues.


Cheers,
Franco