Hi! I have been trying to upgrade to the latest version 25.1 from 24.7.12_4 but I get the following error output:
Fetching packages-25.1-amd64.tar: ... done
Fetching base-25.1-amd64.txz: ................................ done
Fetching kernel-25.1-amd64.txz: ............ done
Extracting packages-25.1-amd64.tar... done
Extracting base-25.1-amd64.txz... done
Extracting kernel-25.1-amd64.txz... done
Please reboot.
>>> Invoking upgrade script 'sanity.sh'
Passed all upgrade tests.
>>> Invoking upgrade script 'cleanup.sh'
find: fts_read: No such file or directory
>>> Error in upgrade script '90-cleanup.sh'
During troubleshooting, I booted into single-user mode and ran fsck (fsck -y, fsck -y -f, also tried with mount -o -u / ) to check for errors before attempting the upgrade again.
Health audit doesn't have any errors.
Additional info:
@OPNsense:~ # grep "/boot" /etc/fstab
/dev/gpt/efiboot0 /boot/efi msdosfs rw 2 2
root@OPNsense:~ # gpart show -l
=> 40 1000215136 nda0 GPT (477G)
40 532480 1 efiboot0 (260M)
532520 2008 - free - (1.0M)
534528 999680000 2 zfs0 (477G)
1000214528 648 - free - (324K)
fts_read() is a function for traversing the file system... to some degree there appears to be glitch on it.
I'm not sufficient in ZFS with regard to error correction so someone else can help shed light on it (zfs clear/scrub maybe).
Technically, I think the script is correct not to proceed not knowing what the underlying problem could be.
Cheers,
Franco
zpool status -v zroot
please. fsck does not work with ZFS.
Yes, of course, I forgot to attach it:
root@OPNsense:~ # zpool status -v zroot
pool: zroot
state: ONLINE
status: Some supported and requested features are not enabled on the pool.
The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
the pool may no longer be accessible by software that does not support
the features. See zpool-features(7) for details.
config:
NAME STATE READ WRITE CKSUM
zroot ONLINE 0 0 0
nda0p2 ONLINE 0 0 0
errors: No known data errors
root@OPNsense:~ #
also ran scrub:
root@OPNsense:~ # zpool status -v zroot
pool: zroot
state: ONLINE
status: Some supported and requested features are not enabled on the pool.
The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
the pool may no longer be accessible by software that does not support
the features. See zpool-features(7) for details.
scan: scrub repaired 0B in 00:00:57 with 0 errors on Thu Jul 17 10:30:59 2025
config:
NAME STATE READ WRITE CKSUM
zroot ONLINE 0 0 0
nda0p2 ONLINE 0 0 0
errors: No known data errors
root@OPNsense:~ #
I even made a 'find *' :), no errors
Few details:
run
truss -f -d -a -p <PID of /bin/sh /usr/local/sbin/opnsense-shell (OPNsense command menu)> -o /root/upgrade_trace.log
and got too much errors after start update from command menu in another session like:
60731: 5.464751513 open("/usr/local/etc/libmap.d",O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC,0165) ERR#2 'No such file or directory'
60731: 5.467072157 readlink("/etc/malloc.conf",0x30cfd008c9e0,1024) ERR#2 'No such file or directory'
60731: 5.468693765 fstatat(AT_FDCWD,"/sbin/opnsense-update",0x30cfd008d610,0x0) ERR#2 'No such file or directory'
60731: 5.468735611 fstatat(AT_FDCWD,"/bin/opnsense-update",0x30cfd008d610,0x0) ERR#2 'No such file or directory'
60731: 5.468771042 fstatat(AT_FDCWD,"/usr/sbin/opnsense-update",0x30cfd008d610,0x0) ERR#2 'No such file or directory'
60731: 5.468806410 fstatat(AT_FDCWD,"/usr/bin/opnsense-update",0x30cfd008d610,0x0) ERR#2 'No such file or directory'
61279: 5.469671042 open("/usr/local/etc/libmap.d",O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC,0165) ERR#2 'No such file or directory'
61279: 5.472075607 readlink("/etc/malloc.conf",0x125f6213a750,1024) ERR#2 'No such file or directory'
61279: 5.473656127 fstatat(AT_FDCWD,"/sbin/id",0x125f6213b2f0,0x0) ERR#2 'No such file or directory'
...
Full error grep upgrade_trace.err.zip attached.
Early I update this installation without any problems, didn't do anything to the current install.. Why am I seeing so many errors? How critical are these errors really for the update itself, or are they possibly just remnants of old validation steps?