@jimp Well done, in fact I have thousand of files on it. After cleaned up, upgrade works fine. Thanks a lot...

@stephenw10 Thanks, since pfS runs in KVM, I can restore an old backup in a few seconds if there are problems.

@stephenw10 honestly I am not too sure at this point. First day after the fix, I've been randomly losing LTE links for shorts periods. Since last 2 days it's been all right, it would have been such a coincidence that the provider had problems at the same time. Though not impossible... Last night I lost IPSEC tunnel (one site only) for maybe ±30mins and then it came back. No indication of LTE down/gateway down during this time. I've adjusted the log level for IPSEC so I can go back when it happened (level was too high). We did NOT downgrade the units for now. We had NO init string using 2.7.2 and it was working fine!

@Unoptanio per the upgrade guide https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide-prepare.html#packages “The safest practice is to remove all packages before upgrading to a new release. The upgrade process will handle packages automatically, but packages are frequently a source of problems. To ensure a smooth upgrade, note the installed packages, remove them, perform the upgrade, and then reinstall when the upgrade is complete.” No it’s not required. pfSense will upgrade packages. Yes the package setting remain in the configuration file by default.

Vendors have firmware bugs similar to this quite often, and usually you'd see the OS failing suddenly for no good reason. Falling back to PCI IO access for the config space will probably only allowing boot-through, but any time something allocates memory into that region, it won't be going to DRAM... leading to data corruption. If you enable above 4GB decoding (and it successfully boots), there could be a change to the ACPI tables that the firmware generates. In any case, we'll need to find a way to let FreeBSD know not to use that memory region for allocations.

@SteveITS I went back and retraced my steps, ONLY to realized that I had actually been attempting to restore an OPNsense config and NOT a pfSense config into pfSense 2.8.0... Today I had been running the same exercise (prep for switching from Cable to Fiber) in both... Hence False Alarm: pfSense 2.8.0 was "Correct", in fact it was NOT a pfSense config!!! Restoring Today's Initial Chrome config into pfSense 2.8.0 works as expected... Lawrence Houston

Your root filesystem is down to 1.5G with only 345MB available. It is a space issue. Go to System> Boot Environments and remove any older snapshots you're no longer using. I usually recommend removing all but the currently running BE and one previous one. Then retry upgrading.

@stephenw10 Hi Stephen. That's why I posted -- the 25.07.1 update has been out for well over 24 hours and yet there was no upgrade available LED flashing. I upgraded last night so we'll see if it picks up when the next upgrade is available.

Ah, good and bad news then I guess. Thanks for following up. Yes, some SSDs will fail to a read-only state such that they appear to take changes but lose it at reboot. And that can be confusing!

Yup use Python mode if you have kea2unbound and DNS-BL.

@hspindel said in Upgrading 24.11 to 25.07 fails: @keyser Thank you. So do you concur that removing packages is a good idea? And I have to reinstall manually? Yes and yes

@luckman212 said in Auto update check, checks for updates to base system + packages and sends email alerts: That's why e.g. the current script isn't detecting 25.07.1 etc. Check that you've selected : [image: 1755701317878-103cf890-ded4-4473-8a21-21333f615049-image.png]

If it's the first time it's changed I can probably migrate it to the new NDI. Send it to me in chat and I'll check it.

That ^, It's actually taking up far more space. That error: pkg: "out of space" returned error code 3 confirms it out of disk space. I would remove all but the current and one previous BE and run the upgrade again.

Hmm, strange indeed.

Yup it's unclear how it gets added. If it was a config that got upgraded across a lot of versions though it has probably been there for a while. Future versions should handle that better.

That's a bios or efi function. It deppends how the BIOS presents it. If it boots pfSense you can use efibootmgr to set the boot order if you need to.

Same issue here from 24.11 to 25.11. Clearing /cf/conf/backup was the solution. Thanks for sharing !

Oh so you still see this even without pfSense involved at all? It must be a problem in the route then. Like something at your ISP routing packets via multiple routes perhaps. What happens if you route traffic over a VPN to somewhere else so you bypass anything the ISP is doing?