You will need to upgrade to 23.09_1 first. You should then see both 24.03 and 24.11 offered. And from either of those you will see 25.07.

OK try at the command line: pfSense-repoc -ND What error is shown? Send me your NDI in chat and I can check what it should be seeing.

INstalled on my desktoip hyper-v and set wan and lan to DHCP then transfered image to remote hyper-v server.

@stephenw10 Thank you!

@Gertjan said in BootLoader not found, please install an OS: @opticalc Well, the (cut short) TPM story is : if something changes the boot files on the boot partition, then the user should be warned when the system boots. That's the IMHO, whole idea behind TPM protection. On the other had, end user devices do have a TPM so they can install Windows 11. If its actually used to protect the system, only your BIOS can tell you that. OK, thanks - all that makes sense. But theres still got to be something weird going on with the pfsense installer, given linuxmint worked fine on a single partition, and pfsense gave so many problems?

@eloich Thanks, this worked. Was back online in 2 mins of reboot and I didnt remove any packages this time either.

@stephenw10 again... no errors. It's kind of wild... [2.8.1-BETA][admin@waw-staff-vpn.cic.com]/root: pfSense-upgrade -dC >>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: Fetching data.pkg: pfSense-core repository is up to date. Updating pfSense repository catalogue... Fetching meta.conf: Fetching data.pkg: pfSense repository is up to date. All repositories are up to date. Your system is up to date [2.8.1-BETA][admin@waw-staff-vpn.cic.com]/root:

You should put that in loader.conf.local so it survives future updates. You can set that temporarily to allow 2.8 to boot at the loader prompt as show above. Also see: https://redmine.pfsense.org/issues/16237

@Gertjan I understand all of that. In the end, it was all locking up so frequently, i wiped everything and did a reinstall with 2.7.2. all has been solid ever since. I know there isn't anything to go on with this because I'm not providing any logs, but as I said in an earlier post, uninstalling all packages and rebooting as per the documentation, still resulted in errors during the upgrade. as of now, all is back up and running perfectly.

Yeah unless you actually need that wifi card it's better to remove it. It doesn't work in 2.8 yet anyway and just uses resources.

Indeed the memory can be an issue especially with larger upgrades. The memory usage during ZFS upgrades has been improved in 25.07 (to be released soon) to address the issue. You can check the system log for signs of processes being killed abruptly. If however you're still using UFS it's more likely to have been some other issue.

I decided to check out the repo to see what build looks like for CE. I noticed that 2.8.0-RELEASE is still not an available branch in the repo. The master branch version is currently 2.9.0-DEVELOPMENT. Is netgate going to post the 2.8.0-RELEASE branch for the main package and FreeBSD-src?

Upgrading from the local console is always the safest way. That is using the root user. More importantly you will see all the output from upgrade including after the reboot. So if there's some issue with hardware in the new OS version you will see it and be able debug.

@chpalmer said in Strange behavior with gateway: ??? When the default gateway is set to a failover group the 'Default' column in the gateways list should show the tiers. But in this screenshot it doesn't: https://forum.netgate.com/post/1221365 That's unexpected.

@stephenw10 Unfortunately I am going to have to wait till I can bring down the network to test. If I take it down now and it doesn't come back up I will be having some hell to pay from the family...lol.

@Wolfgangthegreat For example (this is checked by default): [image: 1753113612568-8544523b-d69b-4088-b221-d2532912455c-image.png]

There was a backend issue that's now fixed.

Yup, there was a backend issue. Should be good now.

The repo seems to be back online today Jul 19th, I was able to complete the fresh install.