I updated from 24.7.7 to 24.7.8 today and when I check on updates AFTER updating to 24.7.8 (and rebooting), I got a list of 18 upgrades available - all of them install without error - but the updates are still available to install afterward running/installing the updates. Rebooting did not help - updates stay persistent that they want to update the next time I check for updates.
Can anyone provide some clarity or instructions for proper maintenance in this situation?
Because of third party repos (again).
I'm unsure why this happens now more than ever, but there is also nothing that can be done from the "OPNsense" repo perspective. The package manager probably needs a fix here which would be better than burden third party repos with immediate rebuilds all the time.
Cheers,
Franco
While you're talking about 24.7.8 ......
I've tried to upgrade a few times and all attempts are failing.
Here is a copy of my log:
***GOT REQUEST TO UPDATE***
Currently running OPNsense 24.7.8 at Wed Nov 6 14:12:04 EST 2024
Updating OPNsense repository catalogue...
Waiting for another process to update repository OPNsense
Updating mimugmail repository catalogue...
mimugmail repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating mimugmail repository catalogue...
mimugmail repository is up to date.
All repositories are up to date.
Checking for upgrades (1 candidates): . done
Processing candidates (1 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: .......... done
Nothing to do.
Nothing to do.
Starting web GUI...done.
Fetching base-24.7.8-amd64.txz: ... done
Fetching kernel-24.7.8-amd64.txz: ................................ done
!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!!
! A critical upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Installing kernel-24.7.8-amd64.txz...rm: /boot/kernel.old/xhci.ko: Invalid argument
rm: /boot/kernel.old: Directory not empty
failed, rm error 0
***DONE***
Try to move /boot/kernel.old to somewhere else. UFS corruption?
# mv /boot/kermel.old /tmp
That's how I usually deal with defunct inodes. ;)
Cheers,
Franco