Can we get an upgrade to 25.7.2 that doesn't break our platform pls!!

[TheTecnophen]

I can't upgrade from 25.7 to 25.7.2 on my N100 without breaking OPNsense. It literally reboots itself and then won't go into the GUI. I'm having to re-install every single time I try. PLEASE FOR THE LOVE OF GOD!!!

[BrandyWine]

Well, single user mode, mount the disk, go from there.

It's also a "community" version, so I am not sure we can criticize those offering a free product.
Open source free stuff comes with the risks.

Are you running UFS or ZFS filesystem?

[franco]

> PLEASE FOR THE LOVE OF GOD!!!

I'm not here to bash you, but "buy once cry once" is becoming more evident these days. We write software and include software that increasingly breaks when bad cheap hardware is used which breaks the software by returning garbage results to it. N100 and friends have been a disaster. Intel is taking a hit. This is only going to get worse.


Cheers,
Franco

[TheTecnophen]

Running UFS. This is not my first rodeo with OPNsense. Honestly, been using it for years now without hiccup using suricata and adblockhome for my home lab. N100 is actually quite fine: Intel chipset, Intel NICs, lots of RAM and NVME so don't know what you're talking about Franc. Lots of people use N100, it's a good option. Honestly have 2 as I also run CAKE on OpenWRT on a symmetrical gigabit line without issue. I'm just saying, I have backups for a reason, but I can't use them if I can't install the platform that the plugins are looking for. I wouldn't have to re-install the platform if the 25.7.2 update didn't kill my Opnsense software after install. Yes I understand it's opensource and "community" and all that and no software is absolutely perfect. BUT. When you release an update that breaks the entire platform and then you leave the user unable to not only update (which isn't THAT big of a deal) but then the plugins won't install either because of said update not being implemented, it's a bit of an annoyance to put it subtly.

[franco]

I understand your points, but you're asking at the wrong end.  N100 vs. FreeBSD is not our battle.



Cheers,
Franco

[TheTecnophen]

Nice. So let's deploy an update to a stable platform that breaks it for a bunch of users then throw your hands up and say "not my problem". good job..

[Monviech (Cedrik)]

You didnt even say so far what your issue is. What is the crash that happens, why doesn't it boot?

Can't you get any diagnostics at all?

Just saying "It does not work plz fix" does not help here.

[meyergru]

1. As already noted, you first posting does tell us nothing about what is potentially wrong.

2. When you opt to use a cheap N100 box, you should not be too surprised that it is not as well maintained as Deciso hardware, for starters. And BTW, as you will soon see, your "glorious" N100 maybe is not as rock-solid as you think. I use one, too, but I do not complain about OpnSense.

3. What Franco told you between the lines is that there are known problems with current micorocode updates on N100 CPUs in FreeBSD, which manifest only on UFS setups, which you also deliberately chose over the recommended ZFS setup. Had you gone with ZFS, you would not have ended up in this spot in the first place.

4. What you should do before an upgrade to more current releases of OpnSense is pointed to here, #23.