Hmm, what do you get after the reboot though? Just the BIOS output? How did you get to 25.07 in the end? There's a separate setting for denying DHCP to clients without a static mapping: Deny Unknown Clients

@stephenw10 Agreed all my subsequent research indicates this should not have been possible to configure! I created the tunnel and got a warning that existing binding would not work, can't rember exact words, I assumed just WAN which was fine for me. Tunnel worked and I still had GUI access to pfSense for several weeks. But, don't think I every restarted pfSense between then and upgrade to 25.07, so might have failed then.

Ah, nice catch. Hmm...

There shouldn't be anything special required there. You should be able to use any two drives in a ZFS mirror. I'd recommend using identical drives though if you can.

You have any output from the console where it fails? What device is this?

I did a fresh install of 2.8.0 and do not get the error anymore.

@stephenw10 @Gertjan Thanks for the comments. Ultimately, I downloaded Netgate Installer and fumbled around all day until I figured out how the menu worked. My SG-2440 is now updated to 25.07 and I still have to check all the settings before I put back in a box and remember to keep it updated as time goes on. It will do as a backup for when my 5100 croaks and allow me to stay online until I obtain whatever Netgate's future replacement will be. I appreciate the forum.

If should show the 'system is unregistered' message in the upgrade page if that's the case. If you send me your NDI in chat I can check it.

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.