Messages

Aha! Thank you Franco, that's good to know. Appreciate the help.

Cheers,

Chris

Hi All,

I just completed the upgrade to 23.1 and seem to be up and running fine. I virtualise my OPNsense box using Proxmox and made a backup of the VM before and after the upgrade.

Right before the upgrade, the complete backup was ~1GB. Compression is involved here but I always remember the file system, according to OPNsense itself, occupied around 1.7GB. After the upgrade (and cleaning of some left over logs), OPNsense is again reporting around 1.7GB used by the file system. However, backing up of the VM from within Proxmox yields a backup size of almost 2.4GB! How can this be?

A quick df -h from OPNsense's shell reveals that there seems to be a new filesystem mounted and I'm thinking this is where all that extra disk usage is coming from.

Code Select Expand

root@OPNsense:/var # df -h
Filesystem                  Size    Used   Avail Capacity  Mounted on
/dev/gpt/rootfs             7.5G    1.7G    5.2G    24%    /
devfs                       1.0K    1.0K      0B   100%    /dev
/dev/gpt/efifs              256M    1.7M    254M     1%    /boot/efi
devfs                       1.0K    1.0K      0B   100%    /var/dhcpd/dev
devfs                       1.0K    1.0K      0B   100%    /var/unbound/dev
/usr/local/lib/python3.9    7.5G    1.7G    5.2G    24%    /var/unbound/usr/local/lib/python3.9

This seems really strange to me so if anyone can share their thoughts, that would be greatly appreciated.

Cheers,

Chris

Hello,

Thought I'd update the thread in case anyone stumbles across this in future.

I had another go at attempting to fix and it seems like all that was needed was to run an fsck on the root file system. I booted into the OS under single user mode (option 2 during boot) and simply ran fsck, following the prompts through as you normally would until the cleanup was complete. I suspect the corruption was due to a hard crash of the hypervisor a while back.

I rebooted and re-attempted the upgrade via the web GUI and it succeeded!

Cheers,

Chris

Bump anyone? Thank you for any help should I receive it!

Perhaps I could add the following info:

No reboot happens like usual, the update process just ends here.

If I check for updates again, the only package that shows is:

Code Select Expand

Package name: base
Current version: 22.7.7
New version: 22.7.9

Running a health audit reveals the following:

Code Select Expand

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 22.7.10_2 (amd64/OpenSSL) at Sat Jan 14 14:51:34 GMT 2023
>>> Check installed kernel version
Version 22.7.9 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 22.7.7 is incorrect, expected: 22.7.9
>>> Check for missing or altered base files
Missing files: 1
mtree: sbin/kldconfig: Invalid argument
./sbin/kldconfig missing
>>> Check installed repositories
OPNsense
>>> Check installed plugins
os-qemu-guest-agent 1.1_1
os-upnp 1.4_2
>>> 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" has 63 dependencies to check.
Checking packages: ................................................................. done
***DONE***

Hi All,

Hoping for a bit of guidance here as to what OPNsense is getting stuck on.

I just tried to update my virtualised OPNsense router running version 22.7.8, but I am seeing the following error once it gets to the upgrade of the base & kernel packages:

Code Select Expand

!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!!
! A critical upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Installing kernel-22.7.9-amd64.txz... done
Installing base-22.7.9-amd64.txz...chflags: /sbin/kldconfig: Invalid argument
failed, chflags error 0
***DONE***

My Google-Fu is failing me on this one and I've been unsuccessful in finding anything similar here on the forums, which has surprised me.

Apart from this error, all else seems to be working flawlessly...

Can anyone lend a hand in helping any further? It would be much appreciated.

Kind regards,

Chris