Update from 2.7.0.a.20220812.0002 to PHF 8.1 and FreeBSD Main Failed

bimmerdriver

I'm running 2.7.0.a.20220812.0002 which I installed using ZFS. It's running in a generation 2 (which uses UEFI) on Windows Server 2019. I understand that upgrade in place with ZFS and EFI is not supported, but I tried it anyway, since it's easy to revert to a checkpoint. It would not boot.

Would it make any difference if I reverted to 2.6.0?

Is there even a rough estimate of when the problems with ZFS and EFI will be fixed?

jimp

It doesn't matter where you come from at the moment, it's a problem upgrading in place with EFI and ZFS no matter what on any platform, bare metal and virtualized. We're still investigating, no ETA. The easiest thing to do is a fresh install from a 2.7.0 snapshot and restore the configuration, which would have you up and running quickly.

cmcdonald

@bimmerdriver

If you are curious, you can repair this particular failure mode by upgrading the FreeBSD UEFI loader:

Boot into the latest pfSense 2.7.0 installer ISO and enter the Rescue Shell
Mount the EFI partition mount -t msdosfs /dev/gpt/efiboot0 /mnt
Copy the UEFI loader from the ISO media to the mounted EFI partition cp /boot/loader.efi /mnt/efi/boot/BOOTx64.efi
umount -f /mnt
reboot

If you attempt this procedure, let us know how it goes. We are still investigating but feel like we have a pretty good understanding of what is going on here and how to resolve it. Feedback appreciated.

thestryker6

@cmcdonald said in Update from 2.7.0.a.20220812.0002 to PHF 8.1 and FreeBSD Main Failed:

@bimmerdriver

If you are curious, you can repair this particular failure mode by upgrading the FreeBSD UEFI loader:

Boot into the latest pfSense 2.7.0 installer ISO and entire the Rescue Shell

Mount the EFI partition mount -t msdosfs /dev/gpt/efiboot0 /mnt

Copy the UEFI loader from the ISO media to the mounted EFI partition cp /boot/loader.efi /mnt/efi/boot/BOOTx64.efi

umount -f /mnt

reboot

If you attempt this procedure, let us know how it goes. We are still investigating but feel like we have a pretty good understanding of what is going on here and how to resolve it. Feedback appreciated.

This worked for me having done a console upgrade which was causing failure to boot.

bimmerdriver

@cmcdonald Sorry for the delay to reply. I didn't have a chance to try this until today and I found when I made another attempt to upgrade, it worked without me having to try this. I appreciate your reply, even though I ended up not needing to try it.