OPNSense managed to destroy itself during an update, still people wonder why companies buy Fortinet...

@buherator out of curiosity in what way and what update ?

@kstrlworks Clean install from ISO (latest minor) -> firmware update from webUI to latest patch. The updater removed basic files, then failed to extract the updated ones so everything just stopped working.

@buherator Oh interesting! I checked mine, given I installed it a long while ago, and it's running the latest minor version now with no crashes or errors. Must have been something that changed in the installer, maybe?

@kstrlworks It looks like a transient error, most likely a corrupt download. Shit happens ofc, but he only acceptable reason for bricking the system would be hardware error which is very unlikely because other VMs on the same host run just fine.

@buherator Oh, without a doubt, I was more asking to know if my instances were running the same version as yours, to validate if it was affecting my instances as well. I should also specify that all my OpnSense instances run on bare metal as an additional data point, if that helps at all.

Are you running Open vSwitch for the networking, or do you have dedicated lines for the VM? I had terrible inconsistency with Open vSwitch on a VM with OpnSense, but I tested this setup in 2016.

@kstrlworks Oh sry, I'm on 25.7<whatever is the latest patch>. I simply use two bridged interfaces on Proxmox. Based on my above observations I think this is more of a design issue of moving around files during the upgrade process, and *maybe* something you can mitigate with some ZFS magic (I'm on UFS).

@buherator Oh, interesting! Yup, we're on the same version. I am using ZFS as well. It definitely might be due to the installation process, it sounds like then.