Invalid argument errors while trying to upgrade from 26.1.11 to 26.7

[Shad]

Hello guys,

Following the php2shell crisis, I tried to upgrade to 26.7.
For some reasons, I got the failed signature error while fetching the new packages.
I read that changing mirrors could help, but ended out with another error :

Code Select Expand

***GOT REQUEST TO UPGRADE***
Currently running OPNsense 26.1.11_10 (amd64) at Thu Oct 22 20:13:25 CEST 2026
Fetching packages-26.7-amd64.tar: ............................................................................. done
Fetching base-26.7-amd64.txz: .... done
Fetching kernel-26.7-amd64.txz: ... done
Flushing temporary package files...find: /usr/local/include/boost/thread/is_locked_by_this_thread.hpp: Invalid argument
find: /usr/local/include/boost/thread/interruption.hpp: Invalid argument
find: /usr/local/include/boost/thread/future.hpp: Invalid argument
find: /usr/local/include/boost/thread/externally_locked_stream.hpp: Invalid argument
find: /usr/local/include/boost/thread/externally_locked.hpp: Invalid argument
find: /usr/local/include/boost/thread/executors/work.hpp: Invalid argument
find: /usr/local/include/boost/thread/executors/thread_executor.hpp: Invalid argument
find: /usr/local/include/boost/thread/executors/serial_executor_cont.hpp: Invalid argument
***DONE***
I then ran an health audit, and got this as a result :

Code Select Expand

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 26.1.11_10 (amd64) at Thu Oct 22 20:19:17 CEST 2026
>>> Root file system: /dev/ada0p2
>>> Check installed kernel version
Version 26.1.11 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 26.1.11 is correct.
>>> Check for missing or altered base files
Error 2 occurred.
usr/bin/lldb:
sha256digest (0x9afbd73a548f72d1271c9c3625905d2843009fd594127adb5bbadf8bbecc6f4b, 0xac0dde3bbcfc81ba2c0d5cd11f112b0976f0c18185e438c7db9654d4b38d03cd)
>>> Check installed repositories
OPNsense (Priority: 11)
>>> Check installed plugins
os-apcupsd 1.2_3
os-ddclient 1.31_1
os-gdrive-backup 1.0_1
os-isc-dhcp 1.0_6
os-mdns-repeater 1.2
os-nut 1.9_1
>>> 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:
boost-libs-1.89.0_2: checksum mismatch for /usr/local/include/boost/phoenix/scope/detail/cpp03/preprocessed/lambda_40.hpp
boost-libs-1.89.0_2: checksum mismatch for /usr/local/include/boost/thread/executors/serial_executor_cont.hpp
boost-libs-1.89.0_2: checksum mismatch for /usr/local/include/boost/thread/executors/thread_executor.hpp
boost-libs-1.89.0_2: checksum mismatch for /usr/local/include/boost/thread/executors/work.hpp
boost-libs-1.89.0_2: checksum mismatch for /usr/local/include/boost/thread/externally_locked.hpp
boost-libs-1.89.0_2: checksum mismatch for /usr/local/include/boost/thread/externally_locked_stream.hpp
boost-libs-1.89.0_2: checksum mismatch for /usr/local/include/boost/thread/future.hpp
boost-libs-1.89.0_2: checksum mismatch for /usr/local/include/boost/thread/interruption.hpp
boost-libs-1.89.0_2: checksum mismatch for /usr/local/include/boost/thread/is_locked_by_this_thread.hpp
Checking all packages..........
py313-botocore-1.43.14: checksum mismatch for /usr/local/lib/python3.13/site-packages/botocore/data/forecast/2018-06-26/service-2.json
Checking all packages...... done
>>> Check for core packages consistency
Core package "opnsense" at 26.1.11_10 has 68 dependencies to check.
Checking packages: ..................................................................... done
***DONE***
AI tells me that there are .pkgtemp files that are locking the upgrade process and give me directions to follow, but I'd rather ask you guys before doing something stupid.

Any help would extremely valuable !

[(MARLOO)]

Hi,

First, back up your configuration.

Then, check disk/storage health:

-------------------------------------
df -h
dmesg | grep -iE 'ada0|error|fail|cam'
smartctl -a /dev/ada0
-------------------------------------

Reinstall only the two packages flagged by the health audit:

-----------------------------------------------------
pkg update
pkg install --force --reinstall boost-libs py313-botocore
---------------------------------------------------------

Retry the upgrade.

Afterwards, check:

--------------------------
opnsense-version
---------------------------

If it fails again, check:

-------------------------------------
smartctl -a /dev/ada0
dmesg | grep -iE 'ada0|error|fail|cam'
-------------------------------------


https://docs.opnsense.org/troubleshooting.html
https://docs.opnsense.org/manual/updates.html

[Shad]

Hello (MARLOO),

Thanks for yout input.
For some reason, smartctl is not found (and I don't find it in the packages tab in the GUI).

df -h

Code Select Expand

Filesystem                   Size    Used   Avail Capacity  Mounted on
/dev/ada0p2                  111G     54G     48G    53%    /
devfs                        1.0K      0B    1.0K     0%    /dev
/dev/ada0p1                  260M    1.3M    259M     1%    /boot/efi
devfs                        1.0K      0B    1.0K     0%    /var/dhcpd/dev
devfs                        1.0K      0B    1.0K     0%    /var/unbound/dev
/usr/local/lib/python3.13    111G     54G     48G    53%    /var/unbound/usr/local/lib/python3.13
/lib                         111G     54G     48G    53%    /var/unbound/lib

dmesg | grep -iE 'ada0|error|fail|cam'

Code Select Expand

[47284] /mnt: inode 8334247: check-hash failed
[47284] /mnt: inode 8334247: check-hash failed
[47284] /mnt: inode 8334246: check-hash failed
[47284] /mnt: inode 8334246: check-hash failed
[47284] /mnt: inode 8334245: check-hash failed
[47284] /mnt: inode 8334245: check-hash failed
[47284] /mnt: inode 8334244: check-hash failed
[47284] /mnt: inode 8334244: check-hash failed
[...]
[1861689] /mnt: inode 8334244: check-hash failed
[1861689] /mnt: inode 8334244: check-hash failed
[1861689] /mnt: inode 8334245: check-hash failed
[1861689] /mnt: inode 8334245: check-hash failed
[1861689] /mnt: inode 8334246: check-hash failed
[1861689] /mnt: inode 8334246: check-hash failed
[1861689] /mnt: inode 8334247: check-hash failed
[1861689] /mnt: inode 8334247: check-hash failed
We are talking about ~1175 lines here... smells really bad I guess ?

smartctl -a /dev/ada0

Code Select Expand

smartctl: Command not found.
pkg install --force --reinstall boost-libs py313-botocore

Code Select Expand

pkg: unrecognized option `--reinstall'
I then tried without the --reinstall argument :

Code Select Expand

Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
The following 2 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
        boost-libs-1.89.0_2 [OPNsense]
        py313-botocore-1.43.14 [OPNsense]

Number of packages to be reinstalled: 2

8 MiB to be downloaded.

Proceed with this action? [y/N]: y
[1/1] Fetching py313-botocore-1.43.14.pkg: 100%    8 MiB   8.5MB/s    00:01
Checking integrity... done (0 conflicting)
[1/2] Reinstalling boost-libs-1.89.0_2...
[1/2] Extracting boost-libs-1.89.0_2: 100%
pkg: Fail to rename /usr/local/include/boost/thread/executors/.pkgtemp.serial_executor_cont.hpp.au7FxGhtawrY -> /usr/local/include/boosutors/serial_executor_cont.hpp:Invalid argument
opnsense-version

Code Select Expand

OPNsense 26.1.11_10 (amd64)
Am I good for a reinstall ?

[Shad]

UPDATE : I found the smart package in the community repo.

I ran a short test : smartctl -t short /dev/ada0

Result :

Code Select Expand

smartctl 7.5 2025-04-30 r5714 [FreeBSD 14.3-RELEASE-p16 amd64] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     GIM128
Serial Number:    2022120800350
Firmware Version: U0707A0
User Capacity:    128,035,676,160 bytes [128 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      mSATA
TRIM Command:     Available
Device is:        Not in smartctl database 7.5/5706
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Oct 23 07:34:24 2026 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x02) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (  120) seconds.
Offline data collection
capabilities:                    (0x11) SMART execute Offline immediate.
                                        No Auto Offline data collection support.
                                        Suspend Offline collection upon new
                                        command.
                                        No Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        No Selective Self-test supported.
SMART capabilities:            (0x0002) Does not save SMART data before
                                        entering power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        (  10) minutes.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0032   100   100   050    Old_age   Always       -       0
  5 Reallocated_Sector_Ct   0x0032   100   100   050    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   050    Old_age   Always       -       18487
 12 Power_Cycle_Count       0x0032   100   100   050    Old_age   Always       -       204
160 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       0
161 Unknown_Attribute       0x0033   100   100   050    Pre-fail  Always       -       100
163 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       10
164 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       303794
165 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       3728
166 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       336
167 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       617
168 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       7000
169 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       92
175 Program_Fail_Count_Chip 0x0032   100   100   050    Old_age   Always       -       0
176 Erase_Fail_Count_Chip   0x0032   100   100   050    Old_age   Always       -       0
177 Wear_Leveling_Count     0x0032   100   100   050    Old_age   Always       -       0
178 Used_Rsvd_Blk_Cnt_Chip  0x0032   100   100   050    Old_age   Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   050    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   050    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age   Always       -       165
194 Temperature_Celsius     0x0022   100   100   050    Old_age   Always       -       40
195 Hardware_ECC_Recovered  0x0032   100   100   050    Old_age   Always       -       492
196 Reallocated_Event_Count 0x0032   100   100   050    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   050    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0032   100   100   050    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0032   100   100   050    Old_age   Always       -       0
232 Available_Reservd_Space 0x0032   100   100   050    Old_age   Always       -       100
241 Total_LBAs_Written      0x0030   100   100   050    Old_age   Offline      -       564087
242 Total_LBAs_Read         0x0030   100   100   050    Old_age   Offline      -       9288
245 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       471940

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     18487         -

Selective Self-tests/Logging not supported

The above only provides legacy SMART information - try 'smartctl -x' for more

[(MARLOO)]

Your SMART output looks ok

those repeated check-hash failed messages are UFS filesystem corruption

It can be caused by:
--An unexpected shutdown or power loss
--A RAM problem
--A faulty mSATA cable or connector
--an SSD failure that is not visible in SMART

I would not try the 26.7 upgrade or keep reinstalling packages until the filesystem is repaired.

Reboot and select Single User Mode from the FreeBSD/OPNsense boot menu. Then run:

----------------------
fsck -y /
reboot
----------------------

After reboot, check whether the errors are gone

--------------------------------
dmesg | grep -i "check-hash"
opnsense-checkhealth
--------------------------------

If the health audit is clean, try the upgrade from the console.

If check-hash failed comes back after fsck, or fsck cannot repair it, do a clean reinstall and restore your config backup.

 after the upgrade completes successfully, he will automatically have:
-OPNsense 26.7
-FreeBSD 15.1
-Updated kernel, base system, and packages

This is the safest way and should/must clear those errors.

[nero355]

Your SMART output looks ok

Actually I think something weird is going on :

Code Select Expand

195 Hardware_ECC_Recovered  0x0032   100   100   050    Old_age   Always       -       492

Could be the SATA cable, SATA Controller or something wrong with the SSD components inside itself.

And then there are all those unknown values :

Code Select Expand

160 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       0
161 Unknown_Attribute       0x0033   100   100   050    Pre-fail  Always       -       100
163 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       10
164 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       303794
165 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       3728
166 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       336
167 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       617
168 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       7000
169 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       92

I would replace it and then keep an eye on the values with the new drive and hope for the best...

[(MARLOO)]

Could be the SATA cable, SATA Controller or something wrong with the SSD components inside itself.

Fair point about the ECC count. To be sure, I'll rerun the SMART tests, including a long test, and monitor the values.

Since this is a firewall and the filesystem is already showing corruption, to be safe I'd buy a well-known brand that supports smartctl. They're available on Amazon today for less than €50

Kingston, Transcend, Samsung, Crucial and SanDisk usually expose SMART attributes that smartctl can read properly, instead of leaving everything as "Unknown_Attribute" like the GIM128 does.
Transcend, for example, explicitly states S.M.A.R.T. support for its mSATA 230S SSDs

[Shad]

Thanks, new disk on the way, once received I'll try what you said on the present disk.