@stephenw10 said in Upgrade 24.11 > 25.07.1 fails: Nothing yet. What do you see from: mount -p pfSense/ROOT/default / zfs rw,noatime,nfsv4acls 0 0 devfs /dev devfs rw 0 0 pfSense/tmp /tmp zfs rw,nosuid,noatime,nfsv4acls 0 0 pfSense/var /var zfs rw,noatime,nfsv4acls 0 0 pfSense/home /home zfs rw,noatime,nfsv4acls 0 0 pfSense /pfSense zfs rw,noatime,nfsv4acls 0 0 pfSense/var/log /var/log zfs rw,noexec,nosuid,noatime,nfsv4acls 0 0 pfSense/var/db /var/db zfs rw,noexec,nosuid,noatime,nfsv4acls 0 0 pfSense/cf /cf zfs rw,noexec,nosuid,noatime,nfsv4acls 0 0 pfSense/var/empty /var/empty zfs rw,noatime,nfsv4acls 0 0 pfSense/var/tmp /var/tmp zfs rw,nosuid,noatime,nfsv4acls 0 0 pfSense/reservation /pfSense/reservation zfs rw,noatime,nfsv4acls 0 0 pfSense/var/cache /var/cache zfs rw,noexec,nosuid,noatime,nfsv4acls 0 0 pfSense/cf/conf /cf/conf zfs rw,noexec,nosuid,noatime,nfsv4acls 0 0 pfSense/ROOT/default/cf /cf zfs rw,noexec,nosuid,noatime,nfsv4acls 0 0 pfSense/ROOT/default/var_cache_pkg /var/cache/pkg zfs rw,noexec,nosuid,noatime,nfsv4acls 0 0 pfSense/ROOT/default/var_db_pkg /var/db/pkg zfs rw,noexec,nosuid,noatime,nfsv4acls 0 0 tmpfs /var/run tmpfs rw 0 0 [24.11-RELEASE][root@gateway.nlfunhouse.com]/root:

@stephenw10 I was finally able to reboot the pfSense box late last night, and since it's back up, I'm not getting the error messages anymore. I'll report back if it pops up again.

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

@patient0 None of the links I found was exactly what I experienced. I have described what I have tried, what did or did not work and the servers I tried with are both different from the ones previously posted and newer. What I have written adds more information about the issues and hopefully helps someone and I was hoping that one of the developers/testers would tell me what to try and/or ask about logs/screenies/commands or whatever which may be useful.

Mmm, not able to replicate that. The ISO file is gzipped. You can extract it and upload it to a hypervisor to install a VM. If you're seeing the ISO contents it looks like your OS has "helpfully" mounted the file which is probably not what you want.

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)