22.1 install and a couple of days later boot/re-boot failure

[rwize]

22.1 was installed and it rebooted the device after the install and things came back online.  (upgrade done from GUI)

However the appliance was rebooted and then failed to start.  I had to go onsite urgently for the client and through the console view saw the system booting and then looping on Archive tar failure and re-trying.

This device has been running for about a year and we only encountered this issue after the 22.1 upgrade; of course it maybe coincidental.

I found a thread where someone said you can CNTRL+C to skip and this worked, THANK GOD.

But now I am reading I should perform a clean install and restore::: any suggestions appreciated.

I also do not see a clean / simple way to backup the device configuration including OPENvpn users and certificates - any thoughts / suggestions appreciated.

[aimdev]

This may be a long-shot, but after the upgrade to 22 from 21 when I powered down the opnsense system (pressing the power down button), it rebooted.
This was reproducible, and there was no apparent reason why this would occur.
I then reset the bios.
The reboot issue has gone (fingers crossed!!)
This issue did not occur with 21, so I wonder if 22 modifies the bios in some way?

[rwize]

This may be a long-shot, but after the upgrade to 22 from 21 when I powered down the opnsense system (pressing the power down button), it rebooted.
This was reproducible, and there was no apparent reason why this would occur.
I then reset the bios.
The reboot issue has gone (fingers crossed!!)
This issue did not occur with 21, so I wonder if 22 modifies the bios in some way?

Thanks for the suggestions... I was onsite in an emergency capacity with the entire accounting office not able to work as many of their programs required web authentication to verify subscriptions (stupid especially in tax season if internet goes out) ...

The immediate solution I found thanks to a forum post was to use the CTRL+C to cancel the archive load retry attempts and the box booted fine and is seemly fully functional... but if it has a reboot for any reason it will get stuck again and require console mode intervention...

I have backed up the config and setup a new box which is also an upgrade and once I do the swap tomorrow I will try your suggestions on the old box to see what happened and what can make it work great again

Cheers