Weird errors after update from 25.7 to 25.7.1

[Patrick M. Hausen]

Are you sure your disk/SSD does not have issues? If there are errors on your drive, of course opnsense-bootstrap will fail. It's not the tool which is at fault in this case.

Did you ruh an fsck? Best reinstall with ZFS, now that you are going to do it, anyway.

[crazywolf13]

I did a fresh install which fixed the issues.

My SDD does not have issues, at least that's what smart data is telling me it's on about 3% wear and has passed the overall smart check.

As multiple people with N100 seem to have this issue right after/during the update to 25.7.2 this does not seem like a full hardware issue to me.

[franco]

What's interesting about this is that updates seem to malfunction on N100 but a reinstall moving large amounts of data is not, which means the issue is likely in Sqlite operation as indicated by the error messages. It's an unfortunate situation to be in when the package manager relies on it.


Cheers,
Franco

[crazywolf13]

Yeah you are right.

For me the issue seems resolved, hopefully it does not re-appear.

Though as other seem to have the same problem, it may be quite unfortunate for all N100 users as it's quite a common device, no?

Let me know if I can provide any details.

[HARLEY_VH]

experienced similar situation when updating from 25.7 to 25.7.2
N305 system
bootstrap not successful
had to reinstalled from scratch, removed plugins (dark theme & os-ddclient), removed pihole DNS ip from config and re-attempted 25.7 to 25.7.2 update
not  successful
system is up & running but remains at 25.7
result of health audit -> all 68 pkgs are version missmatched which is expected considering

will wait and see

Code Select Expand

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 25.7 (amd64) at Thu Sep  4 12:50:44 EDT 2025
>>> Root file system: /dev/gpt/rootfs
>>> Check installed kernel version
Version 25.7 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 25.7 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense (Priority: 11)
>>> Check installed plugins
No plugins found.
>>> 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: .......... done
>>> Check for core packages consistency
Core package "opnsense" at 25.7 has 68 dependencies to check.
Checking packages: ..
ca_root_nss-3.108 version mismatch, expected 3.115
Checking packages: ...............
lighttpd-1.4.79 version mismatch, expected 1.4.81
Checking packages: ......
opnsense-25.7 version mismatch, expected 25.7.2
Checking packages: ..
opnsense-lang-25.1.11 version mismatch, expected 25.7.2
Checking packages: .
opnsense-update-25.7 version mismatch, expected 25.7.2
Checking packages: ...
php83-ctype-8.3.23 version mismatch, expected 8.3.24
Checking packages: .
php83-curl-8.3.23 version mismatch, expected 8.3.24
Checking packages: .
php83-dom-8.3.23 version mismatch, expected 8.3.24
Checking packages: .
php83-filter-8.3.23 version mismatch, expected 8.3.24
Checking packages: .
php83-gettext-8.3.23 version mismatch, expected 8.3.24
Checking packages: .
php83-ldap-8.3.23 version mismatch, expected 8.3.24
Checking packages: .
php83-pcntl-8.3.23 version mismatch, expected 8.3.24
Checking packages: .
php83-pdo-8.3.23 version mismatch, expected 8.3.24
Checking packages: .....
php83-session-8.3.23 version mismatch, expected 8.3.24
Checking packages: .
php83-simplexml-8.3.23 version mismatch, expected 8.3.24
Checking packages: .
php83-sockets-8.3.23 version mismatch, expected 8.3.24
Checking packages: .
php83-sqlite3-8.3.23_1 version mismatch, expected 8.3.24
Checking packages: .
php83-xml-8.3.23 version mismatch, expected 8.3.24
Checking packages: .
php83-zlib-8.3.23 version mismatch, expected 8.3.24
Checking packages: ....
py311-duckdb-1.3.1_1 version mismatch, expected 1.3.2
Checking packages: .
py311-jq-1.8.0_1 version mismatch, expected 1.10.0
Checking packages: ...
py311-numpy-1.26.4_6,1 version mismatch, expected 1.26.4_7,1
Checking packages: ..........
sudo-1.9.17p1 version mismatch, expected 1.9.17p2
Checking packages: ..
syslog-ng-4.8.2_3 version mismatch, expected 4.8.2_4
Checking packages: ... done
***DONE***



[franco]

> Warning to anyone here, using opnsense-bootstrap renders the running installation unusable

Which unfortunately proves the point that this isn't a software issue.

People have said bulk installs are fine so for one reason or another we're looking at an Intel instability during sqlite database or pkg sanity checking operations specifically.


Cheers,
Franco

[HARLEY_VH]

Well N305 update issue solved

kept on having update issues (25.7.x) with my BM N305 configuration
Moved everything to a proxmox vm configuration
was able to update to 25.7.5 with no fuss

[mkuech]

I found this thread after the update to 25.7 appeared to leave my system in a semi-broken state. It ran after the 25.7 update, but like the others, it wasn't able to update past that. I attempted the bootstrap, but something about that bricked my install.

I then downloaded the latest vga image and performed a fresh install from usb, which started me out on 25.7. The first time, the pkg db was corrupted after attempting to install the realtek plugins from the console (my lan interface requires it). Instead of trying to deal with that, I just started the installation process all over again. The second time, I did that realtek step manually in the live environment via console, and performed the installation with the opnsense-installer command.

It's now up again, however, it won't update past that, just like before... which is unfortunate, because a couple plugins are demanding an update.

And yes, N100 here too.

The most recent output from the "Updates" tab:

Code Select Expand

***GOT REQUEST TO UPDATE***
Currently running OPNsense 25.7 (amd64) at Sat Nov 29 03:12:08 CST 2025
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (162 candidates): .......... done
Processing candidates (162 candidates): ...... done
Checking integrity... done (1 conflicting)
  - py311-pyopenssl-25.3.0_1,1 conflicts with py311-openssl-25.0.0_1,1 on /usr/local/lib/python3.11/site-packages/OpenSSL/SSL.py
Checking integrity... done (0 conflicting)
The following 85 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
py311-pyopenssl: 25.3.0_1,1

Installed packages to be UPGRADED:
boost-libs: 1.88.0_1 -> 1.89.0_1
ca_root_nss: 3.108 -> 3.117_2
curl: 8.14.1 -> 8.17.0
kea: 2.6.3_1 -> 3.0.2
krb5: 1.21.3_1 -> 1.22.1
liblz4: 1.10.0,1 -> 1.10.0_2,1
libnghttp2: 1.66.0 -> 1.68.0
libpfctl: 0.15 -> 0.17
libucl: 0.9.2_1 -> 0.9.2_2
libunistring: 1.3 -> 1.4.1
libxml2: 2.14.5 -> 2.14.6
lighttpd: 1.4.79 -> 1.4.82
nspr: 4.36 -> 4.38.2
nss: 3.113.1_1 -> 3.118.1
ntp: 4.2.8p18_4 -> 4.2.8p18_5
openssh-portable: 10.0.p1_1,1 -> 10.2.p1_1,1
openssl: 3.0.17,1 -> 3.0.18,1
openvpn: 2.6.14 -> 2.6.16
opnsense: 25.7 -> 25.7.8
opnsense-lang: 25.1.11 -> 25.7.4
opnsense-update: 25.7 -> 25.7.8
pcre2: 10.45_1 -> 10.47
perl5: 5.40.2_2 -> 5.42.0_1
php83: 8.3.23 -> 8.3.28
php83-ctype: 8.3.23 -> 8.3.28
php83-curl: 8.3.23 -> 8.3.28
php83-dom: 8.3.23 -> 8.3.28
php83-filter: 8.3.23 -> 8.3.28
php83-gettext: 8.3.23 -> 8.3.28
php83-ldap: 8.3.23 -> 8.3.28
php83-mbstring: 8.3.23 -> 8.3.28
php83-pcntl: 8.3.23 -> 8.3.28
php83-pdo: 8.3.23 -> 8.3.28
php83-pear: 1.10.13 -> 1.10.16
php83-phpseclib: 3.0.46 -> 3.0.47
php83-session: 8.3.23 -> 8.3.28
php83-simplexml: 8.3.23 -> 8.3.28
php83-sockets: 8.3.23 -> 8.3.28
php83-sqlite3: 8.3.23_1 -> 8.3.28
php83-xml: 8.3.23 -> 8.3.28
php83-zlib: 8.3.23 -> 8.3.28
pkcs11-helper: 1.29.0_3 -> 1.31.0
py311-aioquic: 1.2.0 -> 1.3.0_1
py311-anyio: 4.9.0 -> 4.11.0
py311-attrs: 25.3.0 -> 25.4.0
py311-certifi: 2025.6.15 -> 2025.10.5
py311-charset-normalizer: 3.4.2 -> 3.4.4
py311-cryptography: 44.0.3_2,1 -> 45.0.7_1,1
py311-dnspython: 2.7.0,1 -> 2.8.0_1,1
py311-duckdb: 1.3.1_1 -> 1.3.2
py311-idna: 3.10 -> 3.11
py311-jq: 1.8.0_1 -> 1.10.0
py311-markupsafe: 3.0.2 -> 3.0.3
py311-numexpr: 2.11.0 -> 2.14.1
py311-numpy: 1.26.4_6,1 -> 1.26.4_10,1
py311-pandas: 2.2.3_2,1 -> 2.2.3_3,1
py311-pycparser: 2.22 -> 2.23
py311-pylsqpack: 0.3.22 -> 0.3.23
py311-pyyaml: 6.0.1_1 -> 6.0.3
py311-requests: 2.32.4 -> 2.32.5
py311-sqlite3: 3.11.13_11 -> 3.11.14_11
py311-trio: 0.30.0 -> 0.32.0
py311-truststore: 0.10.1 -> 0.10.4
py311-typing-extensions: 4.14.0 -> 4.15.0
py311-ujson: 5.10.0_1 -> 5.11.0
py311-urllib3: 1.26.20,1 -> 2.5.0,1
py311-vici: 5.9.11_1 -> 6.0.3
python311: 3.11.13 -> 3.11.14
readline: 8.2.13_2 -> 8.3.1
sqlite3: 3.50.2_1,1 -> 3.50.4_2,1
strongswan: 5.9.14 -> 6.0.3_1
sudo: 1.9.17p1 -> 1.9.17p2_2
suricata: 7.0.11_1 -> 8.0.2
syslog-ng: 4.8.2_3 -> 4.10.2
unbound: 1.23.1 -> 1.24.1
wpa_supplicant: 2.11_5 -> 2.11_7
zstd: 1.5.7 -> 1.5.7_1

Installed packages to be REINSTALLED:
cyrus-sasl-2.1.28_5 (provided shared library changed)
cyrus-sasl-gssapi-2.1.28 (provided shared library changed)
dnsmasq-2.91_1,1 (required shared library changed)
glib-2.84.1_3,2 (required shared library changed)
openldap26-client-2.6.10 (required shared library changed)
rrdtool-1.9.0_1 (direct dependency changed: perl5)

Installed packages to be REMOVED:
py311-openssl: 25.0.0_1,1

Number of packages to be removed: 1
Number of packages to be installed: 1
Number of packages to be upgraded: 77
Number of packages to be reinstalled: 6

The process will require 8 MiB more space.
[1/88] Upgrading libnghttp2 from 1.66.0 to 1.68.0...
[1/88] Extracting libnghttp2-1.68.0: .......... done
[2/88] Upgrading libpfctl from 0.15 to 0.17...
[2/88] Extracting libpfctl-0.17: ...... done
[3/88] Upgrading libucl from 0.9.2_1 to 0.9.2_2...
[3/88] Extracting libucl-0.9.2_2: .......... done
[4/88] Upgrading libunistring from 1.3 to 1.4.1...
[4/88] Extracting libunistring-1.4.1: .......... done
[5/88] Upgrading nspr from 4.36 to 4.38.2...
[5/88] Extracting nspr-4.38.2: .......... done
[6/88] Upgrading pcre2 from 10.45_1 to 10.47...
[6/88] Extracting pcre2-10.47: .......... done
[7/88] Upgrading perl5 from 5.40.2_2 to 5.42.0_1...
[7/88] Extracting perl5-5.42.0_1:
pkg-static: Fail to set time on /Archive/Tar/Constant.pm:No such file or directory
[7/88] Extracting perl5-5.42.0_1... done
Starting web GUI...done.
***DONE***

[mkuech]

Quick follow-up with additional info.

I did a ufs install out of concern for drive wear. I went back to the router to do another fresh install with zfs, just in case, when I saw a system message/error pop up on the monitor: bad dir info, mangled entry. That's on a fresh install with 100% proper shutdowns, plus it's connected to a UPS.

I suspected a failing drive, but nvmecontrol is reporting 6% wear, and nothing else concerning is popping out at me.

The other thing I failed to mention was that I restored a backup config once it was all back up and running, but before I attempted an update past 25.7. I'll be skipping that this round and attempt to fully update before I restore any configs.

[meyergru]

Using an N-Type Intel CPU oder Alder Lake or Twin Lake generation? Read this, point 23. ZFS will not keep the problems from occuring, only not crash your storage. You need to apply the tuneables, because FreeBSD, other than Linux, will not do that automatically.