Nope the _1 tag was only to add a fix for this.
See: https://forum.netgate.com/topic/187620/pfsense-plus-software-version-24-03-release-is-here

If you just upgraded to it you will have that. Some parts of the gui do not show that minor revision.

Most likely it aborted the upgrade process part way through for some reason and ended up with a partial upgrade. That results in library mismatches or just missing.

If it still has access to the repos you may be able to run a forced pkg re-install to complete it.

However I would probably just install 2.7.2 clean and restore your config into it.

Steve

Neither of those sound like a problem with installing or upgrading so you should open a new thread.

@stephenw10 you will notice above i did...

eventually got it upgraded to 2.7 then did a restore of backup again and then a resupply of credentials, followed by haproxy which was the critical/missing app to allow inbound routing.

G

@jimp it was interesting that it came up with almost the exact same solution except for the -c parameter, which suggests it didn't just copy your solution. I find AI brilliant and use it daily in my tech work.

The 3100 is not an aarch64 device. It's armv7 (arm32)

Open a ticket with TAC and request the 3100 recovery image.

https://www.netgate.com/tac-support-request

Steve

Hmm, well glad you're up and running. You should be able to restore an older config into a newer pfSense version though.

Not currently. In CE at least.

You should consider making pfSense more robust and less fragile.
Bricking the user's router as a result of an unsuccessful upgrade should not be an option.
The config update should be the last step that only executes after a successful, complete upgrade.
If the config is corrupt, the device should not brick as it does. There should either be an option to reset to factory, which does not work in my case and immediately outputs the same error and menu. Instead, on each successful boot after a config file update (archive bit), a backup copy of it should be taken and restored if the config is found to be broken.
Seeing how pfSense struggles to update (which also takes forever) and then bricks itself, I have no choice then to wipe out the lab and cross it off the list of solutions to our router replacement, which is a damn shame because otherwise pfSense is perfect.

The console was not locked before upgrading?

You are seeing errors when booting?

If it was running ZFS you can roll back the ZFE BE snapshot.

If it's UFS you could try a manual filesystem check:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-check.html#manual-filesystem-check

Otherwise a clean re-install to 24.03 is probably the quickest way back:
https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html

Steve

The debug shows the connection is just timing out.

Can you: ping ews.netgate.com ?

@stephenw10 thanks, I’ll try!

No worries. Good result! 👍

@tordini thanks, I switched over to the non-devel package also and it's working fine.

The only minor issue I have now is the percentage of domains blocked counter on the dashboard is pegged at 100% which is wrong. I had this issue a long time ago, I ignored it back then and I'll do the same now.

You can't run that dd command from the loader prompt. You would need to boot the installer and choose the shell from the initial menu there. Then clean the eMMC and exit back to the installer to continue.

Steve

@chicknbread

Same problem. Solved by Steven's suggestion. Thank you.

Yup use that if you need to do it off-line.

But is that the case? You can't define a WAN to use with the on-line installer?

I just wanted to add my thanks too – I was trying to install the same latest Realtek drivers to support a generic dual port 2.5G NIC (uses 8125 chipset) but got stuck with the version mismatch error preventing the driver to load.

I should have just come to this Forum first!

Phil

Ah, yup hopefully that will help.

Hmm, nope that should work fine.

If it fails like that it will drop to the command line with the network still configured.

Try to ping the servers:
ping ews.netgate.com
Or connect dircetly:
curl https://ews.netgate.com

If those don't show the issue try using the legacy installers:
https://atxfiles.netgate.com/mirror/downloads/