To do 25.07 or not?! That is the question!
-
@stephenw10 said in To do 25.07 or not?! That is the question!:
No panic shown or crash report?
Is it booting UEFI or legacy?
No panic and it’s legacy
@stephenw10 any ideas about BIOS?
-
Like BIOS settings? Not really. It could be an ACPI bug that's exposed by the larger kernel in 25.07 taking up more space. But I'd expect a panic if that was the case.
-
said in To do 25.07 or not?! That is the question!:
24.03
My pfSense saga…
Before 25.07 on 24.03 I had no issues at all, but every newer update started causing spontaneous reboots. I was ready to blame the hardware and even considered buying a new box.
Then I noticed something: my smart power switch (ezOutlet5 - Internet Enabled IP & Wi-Fi Remote Power Switch) was set up for automatic operations, pinging both WiFi and wired networks. The green light on it was blinking, which basically meant it thought something was wrong.
Turns out it was the switch cutting power and rebooting the box — this is my hypothesis.
I disabled the automatic mode and—voila—no more issues.
Posting this for group posterity in case it saves someone else the same headache.
-
Wow, that's painful! Nice to find a cause though.
-
Today I upgraded my 4200 from 24.11 to 25.07.1 via the web interface.
Upgrade went well. I rebooted before starting, the removed all the packages, upgraded, deleted the Nexus package (which I don't think I need since I'm not doing multi-instance management) and installed the new versions of the rest of the packages.
I tested multi-wan failover/fail-back, VLANs, etc and all those aspects seem to work normally. I have Starlink and T-Mobile Home Internet as my primary and backup services, respectively. I don't have VPNs.
Packages are apcupsd, cron, mailreport, pfBlocker_NG, Status_traffic_totals, System_patches.
The only problem I can see is it appears all my history for Status_traffic_totals is gone.
I thought all packages left their data intact upon removal/reinstallation unless explicitly directed otherwise. What happened in this case?
-
Are you using RAM disks?
Also can we assume you mean a 4200 upgraded from 24.11 to 25.07.1?
-
@stephenw10 no, I don't use RAM disks.
Yes, 4200, not 4300. I've edited that.
-
@Mission-Ghost said in To do 25.07 or not?! That is the question!:
from 24.07 to 25.11
And I assume that is also a typo?
-
@stephenw10 yes, 24.11 to 25.07.1...jeez I'm losing my marble.
I had months of usage measurements and now they're gone:
Before the upgrade, I removed the status_traffic_totals package in accordance with the best practices, and after I added it back. I did not see nor choose any other options. Other packages, like cron, email reports and pfBlocker retained all their configurations and data.
-
Hmm, I'm not sure Traffic Totals does back it up. That would be a lot of data in the config. The RRD data is not saved by default.
Do you have a BE you can roll back to to get the data?
-
@stephenw10, I'm not sure either. I didn't use or restore a backup. I did a normal in-place ZFS upgrade.
If I had not removed the package, the data should have stayed in the BE and not been a factor in terms of being 'a lot of data in the config'?
But, logically then, It seems removing the package deleted the data with it, unlike other packages normal expected behaior. (It does occur to me that the config may have been saved; right away in v25 it retained the selection of the two WANs for display. I did not have to restore that after the upgrade. So maybe it did delete just the data and not the config?)
It may not be worth the effort to migrate the data back from v24 to v25, but it is useful for me and the record to know that the package manager/the package/pfSense apparently does not save this particular package's data like the other packages or as implied in the upgrade instructions. Unless this is actually a bug and should not have happened. I'd be interested in knowing which is true.
So, is it reasonable to leave the status_traffic_totals package in place during the next upgrade and only remove the other packages, given I want to retain the data?
Should this discrepancy in the behavior of this package compared with the others and the upgrade instructions be documented somewhere or, if it's a bug, fix it?
