@JonH Yeah, that's way to old. Most server certificates expired everywhere. The method of accessing Netgate update/upgrade server have changed. Etc. The fastest solution would be : go TAC, request a firmware for your device, burn it to a USB disk, and clean install. To get ZFS you have to 're-partition' the disk anyway, so a complete re install is pretty mandatory.

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

@stephenw10 Thank you!

@stephenw10 I can. i'll switch back to 24.01 and kick off another upgrade at the terminal.

@comet424 said in failed to fetch the repo data. Unable to perform update from 2.7.2 to 2.8.0 after restoring crashed 2.8.0 pfSense.: certctl rehash I just get a whole slew of errors when I run that command root: certctl rehash certctl: Skipping untrusted certificate c47d9980 (/etc/ssl/untrusted/c47d9980.0) certctl: Skipping untrusted certificate 0b7c536a (/etc/ssl/untrusted/0b7c536a.0) certctl: Skipping untrusted certificate 5e98733a (/etc/ssl/untrusted/5e98733a.0) certctl: Skipping untrusted certificate 03179a64 (/etc/ssl/untrusted/03179a64.0) certctl: Skipping untrusted certificate 5d3033c5 (/etc/ssl/untrusted/5d3033c5.0) certctl: Skipping untrusted certificate 4304c5e5 (/etc/ssl/untrusted/4304c5e5.0) certctl: Skipping untrusted certificate 4a6481c9 (/etc/ssl/untrusted/4a6481c9.0) certctl: Skipping untrusted certificate d853d49e (/etc/ssl/untrusted/d853d49e.0) certctl: Skipping untrusted certificate 26312675 (/etc/ssl/untrusted/26312675.0) certctl: Skipping untrusted certificate ee1365c0 (/etc/ssl/untrusted/ee1365c0.0) certctl: Skipping untrusted certificate 116bf586 (/etc/ssl/untrusted/116bf586.0) certctl: Skipping untrusted certificate 76cb8f92 (/etc/ssl/untrusted/76cb8f92.0) certctl: Skipping untrusted certificate 2e5ac55d (/etc/ssl/untrusted/2e5ac55d.0) certctl: Skipping untrusted certificate 0c4c9b6c (/etc/ssl/untrusted/0c4c9b6c.0) certctl: Skipping untrusted certificate 1320b215 (/etc/ssl/untrusted/1320b215.0) certctl: Skipping untrusted certificate dc45b0bd (/etc/ssl/untrusted/dc45b0bd.0) certctl: Skipping untrusted certificate 080911ac (/etc/ssl/untrusted/080911ac.0) certctl: Skipping untrusted certificate 18856ac4 (/etc/ssl/untrusted/18856ac4.0) certctl: Skipping untrusted certificate 349f2832 (/etc/ssl/untrusted/349f2832.0) certctl: Skipping untrusted certificate 7aaf71c0 (/etc/ssl/untrusted/7aaf71c0.0) certctl: Skipping untrusted certificate a8dee976 (/etc/ssl/untrusted/a8dee976.0) certctl: Skipping untrusted certificate 57bcb2da (/etc/ssl/untrusted/57bcb2da.0) certctl: Skipping untrusted certificate 9c2e7d30 (/etc/ssl/untrusted/9c2e7d30.0) certctl: Skipping untrusted certificate 5a7722fb (/etc/ssl/untrusted/5a7722fb.0) certctl: Skipping untrusted certificate f90208f7 (/etc/ssl/untrusted/f90208f7.0) certctl: Skipping untrusted certificate 08063a00 (/etc/ssl/untrusted/08063a00.0) certctl: Skipping untrusted certificate 3e44d2f7 (/etc/ssl/untrusted/3e44d2f7.0) certctl: Skipping untrusted certificate 5a4d6896 (/etc/ssl/untrusted/5a4d6896.0) certctl: Skipping untrusted certificate 442adcac (/etc/ssl/untrusted/442adcac.0) certctl: Skipping untrusted certificate b1b8a7f3 (/etc/ssl/untrusted/b1b8a7f3.0) certctl: Skipping untrusted certificate 1636090b (/etc/ssl/untrusted/1636090b.0) certctl: Skipping untrusted certificate 66445960 (/etc/ssl/untrusted/66445960.0) certctl: Skipping untrusted certificate c01cdfa2 (/etc/ssl/untrusted/c01cdfa2.0) certctl: Skipping untrusted certificate cb59f961 (/etc/ssl/untrusted/cb59f961.0) certctl: Skipping untrusted certificate 5e98733a (/etc/ssl/untrusted/5e98733a.0) certctl: Skipping untrusted certificate 57bcb2da (/etc/ssl/untrusted/57bcb2da.0) certctl: Skipping untrusted certificate 18856ac4 (/etc/ssl/untrusted/18856ac4.0) certctl: Skipping untrusted certificate 08063a00 (/etc/ssl/untrusted/08063a00.0) Any ideas on how to fix that?

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

@stephenw10 Yep; the php-fpm script hung right at config upgrade. Had to do ctrl-t to see what was stuck. Stayed there until the script timed out then threw an error and rebooted in 24.11.

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

To anyone following this thread: I'm on pfSense+ 25.07 now and testing a new version of the Auto update check script. Once 25.07 is released (in a few days I expect...) I will push this update, should work on current pfSense 2.8.x / 25.07.

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?