Just upgraded to 26.1.6, but health check sticks.....
***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 26.1.6 (amd64) at Thu Apr 9 14:21:30 BST 2026
>>> Root file system: zroot/ROOT/default
>>> Check installed kernel version
Version 26.1.6 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 26.1.6 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense (Priority: 11)
>>> Check installed plugins
os-chrony 1.5_3
os-ddclient 1.30_2
os-theme-vicuna 1.51
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
Checking all packages: .......... done
>>> Check for missing or altered package files
Checking all packages: ....
Can anyone else confirm?
# killall pkg pkg-static
Package manager didn't change so not sure why stuck. Also use this for QA during release testing and it was ok.
Cheers,
Franco
I may have bigger issues.
Whilst it was hung, I decided to reboot. Never came up again.
I've just swapped out the DEC750v2 with another and imported config and we're back.
Time to put a console port on this one..
The update from v26.1.5 to v26.1.6 was completed successfully. Post-reboot, all systems are functioning normally as of now.
>> Can anyone else confirm?
No. A bit slow but working fine. Only finding was hostwatch not on automatic which I wasn't surprised about, easy fix
So that's 90 minutes I'm not getting back.
All I did was upgrade to 26.1.6 from .5 on a DEC750v2.
It rebooted and everything was working, but out of habit, after an upgrade I always run a health check.
It stalled on the 4 dots for ages, so I rebooted. Never came back.
I quickly put in a replacement 750v2, imported my config and we're back.
So I then put the original one on console, and it's weird. I have a screenshot I'll try and link later but I saw something about "no pool to import". Leaving it for about 25 minutes, it does sort of begin to boot, but slow.
It hangs at "Initializing.........done." forever, then does a bit more 20 mins later.
Rather than waste time, I reinstalled 26.1.2 serial iso, upgraded to 26.1.6 and it's fine.
I have zero idea what the heck happened.
Quote from: ProximusAl on April 09, 2026, 05:16:08 PMI have zero idea what the heck happened.
How old was the OPNsense installation ?
Sounds like ZFS issues that sometimes happen when the FreeBSD Bootloader is too old...
Quote from: nero355 on April 09, 2026, 11:08:08 PMQuote from: ProximusAl on April 09, 2026, 05:16:08 PMI have zero idea what the heck happened.
How old was the OPNsense installation ?
Sounds like ZFS issues that sometimes happen when the FreeBSD Bootloader is too old...
4 months...Device was new in December 25 and fresh installed with 25.7 then.
Updated to 26.1.6 from previous 26.1.5 ; upgrade initially hung in GUI but completed cleanly via CLI (pkg update -f, pkg upgrade, opnsense-update, reboot).
Unbound + dnscrypt-proxy stack fully operational post-upgrade (correct listeners, dig tests OK, dnscrypt query logs PASS).
Firewall/NAT, IPv6 (track6), and WebGUI all behaving as expected so far.
System hostwatch is running correctly after the update and "Automatic Discovery" is enabled on the desired interfaces.
Please double‑check under Interfaces → Neighbors → Discovery that "Automatic Discovery" is ticked and that the correct interfaces are selected, then apply the changes.
Thanks
Quote from: (MARLOO) on Today at 12:06:01 AM...
upgrade initially hung in GUI but completed cleanly via CLI (pkg update -f, pkg upgrade, reboot).
This is wrong.
There's never been any official OPNsense guidance about running those pkg commands.
Also, this is not Linux. Reboot and Shutdown -r do different things, and you never want to do a reboot in (OPNsense) FreeBSD
> Also, this is not Linux. Reboot and Shutdown -r do different things, and you never want to do a reboot in (OPNsense) FreeBSD
If you're in a hurry you can use
# yes | opnsense-shell reboot
I agree about running pkg alone... it doesn't handle base/kernel and is only (mostly) safe on minor updates.
Cheers,
Franco
Thanks for the correction. I shouldn't have used pkg update -f && pkg upgrade or plain reboot.
In my case the upgrade was:
pkg update -f
pkg upgrade
opnsense-update
reboot
The only non‑recommended parts are the manual pkg usage and direct reboot. The system update was done correctly via opnsense-update.
From now on I'll follow the official upgrade path through the GUI/console and only use opnsense-update plus yes | opnsense-shell reboot if needed from shell.