@mvikman Upvoted for the DL link.

@SteveITS thanks so much by the help. When I executed "certctl rehash" in Console, I can see the Update in the Branch 2.7.1 and 2.7.2. I updated from pfSense v2.7.0 to v2.7.2 and later form pfSense v2.7.2 to v2.8.1 without nay problem. Thanks so much again.

@stephenw10 Problem solved. I had to select the disk with the spacebar. In all menus before, i used enter to continue.

said in netgate-installer.iso.gz has no ISO file - only folder: @stephenw10 said in netgate-installer.iso.gz has no ISO file - only folder: Hmm, weird. How is the DVD drive attached on that? I used a 4K UHD capable BD drive connected via USB for the latest install. So in order to satisfy my curiosity, I connected the UHD BD drive to another mini and gave it a try. This time I got to the install menu. The previous tries were with a standard BD drive, which had made successful installations previously. This UHD drive is practically new with little mileage on it. So I can conclude that the ISO can work, which is good news if it gets to the point that using old version ISOs such as the 2.7.2 on hand won't do a scratch install and update to the current version. Until then I think I'll stick with that ISO.

I noticed that the kea2unbound version shipped with pfsense 2.8.1 equals this commit in the pfsense git repository Bring in Kea enhancements from Plus (marcos-ng comitted on Mar 26) After updating the version of /usr/local/bin/kea2unbound with this version: kea2unbound: use the new unbound fast-reload feature in v1.23 (rcmcdonald91 committed on Jul 2) the error seems to be gone. Steps # downlaod kea2unbound Commit 146391a curl https://raw.githubusercontent.com/pfsense/pfsense/146391aa0c5c25348f8f6fa36120332ccbb74ce0/src/usr/local/bin/kea2unbound -o ~/kea2unbound # set permissions chmod +x ~/kea2unbound # backup previous version cp /usr/local/bin/kea2unbound ~/kea2unbound.bak_RELEASE_2.8.1 # overwrite version mv ~/kea2unbound /usr/local/bin/kea2unbound

@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.