@stephenw10 curious as to what your testing will reveal. keep me posted!

If you registered the NDI for plus it will offer that. But you can force enable the CE repos from the advanced menu in the first installer screen. https://docs.netgate.com/pfsense/en/latest/install/install-walkthrough.html#advanced-options

@f.meunier said in 2.7.2 to 2.8.1 : GUI tells 2.8.1 available but no "branch" selection available: From the shell, pfSense-upgrade -C tells me ">>> Updating repositories metadata... done. 2.8.1 version of pfSense is available" but how can I tell it to fetch and install v2.8.1 ? Running pfSense-upgrade -C only checks if an upgrade is available. So what you see there is correct. Just run pfSense-upgrade and it should offer you the upgrade.

@stephenw10 I'm baffled too - unless there was some chicken-and-egg problem where it didn't know the repo to write because there was no repo to write etc. I thought I'd seen all the different ways a problem could manifest in the update system. Silly me :) Thanks, everyone!

Always appreciated!

Mmm, there's no mouse in the Net Installer (or any installer). Technically it's not a GUI it's a TUI so it's keyboard only.

I removed these lines: <loader readonly='yes' type='pflash' format='raw'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram format='raw'>/etc/libvirt/qemu/nvram/384971b7-7248-55e4-dd68-caa71cda114f_VARS-pure-efi-tpm.fd</nvram> So it defaulted to BIOS and now it always works

Yup some USB drives don't play nicely with one of the ports. It always the same though.

Hi all, Thanks for all the info provided, much appreciated. I can confirm that disabling in BIOS the WiFi card solved the issue. I was able to upgrade to 2.8.1 without an issue. Thanks!

It's still an open bug upstream: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283285

@SteveITS @patient0 THANK YOU BOTH!!! had ZERO knowledge or idea my issue was that EZ 2 solve; SOOOOOO many wasted hours SMH Yes, it is installing ATM

Hmm, OK. Can't be that then. In that case I would connect the new client device to trigger the issue then check the system log to see what events are being triggered when you do that.

Thanks. It turns out a number of the IPs in my DNS servers were no longer responding. Problem solved :)

Hmm, well it could also have been due to BE snapshots filling the disk. In both cases though it should have failed gracefully with a warning alert.

Try booting it in Legacy BIOS mode if you can.

@Unoptanio I made sure I had the newest BIOS from HP for my G9 and G10 servers, that made no difference. Even with 25.07.1 it's still unbootable under UEFI. If I switch to BIOS it boots just fine, so it's a UEFI issue for sure. As to the patches I have seen them, and they apply fine, but trying to jump to UEFI is still a no go, only BIOS on the HP's I have.. -Howard

@stephenw10 Yep. The upgrade completed without a problem after clearing those files. Thanks all for the assistance!

I upgraded from 24.11 to 25.0.7.1 on my netgate 2100 yesterday night without a hitch - off course i took screen shots of my various configuration and did have previous boot backup (and xml)

Hmm, what sort of tunnel? Is it somehow trying to pass the upgrade traffic across it?

Hmm, you added that cronjob yourself? Any particular reason? Do you have an url aliases with a large number of entries?