Update To 26.03 fails (HyperV Gen2)

CDe80

We have some virtual Pfsense Plus running as hyperv-vms.
Some running gen 1 which did the update without any problem, but the gen2 machines all fail to boot. After the automatic reboot the vm fails to start and is turned off. When powereing vm on again the old "working" boot envirmonment 25.11 ist started.
Behavior like here: https://redmine.pfsense.org/attachments/4786

stephenw10

@csde80 said in Update To 26.03 fails (HyperV Gen2):

https://redmine.pfsense.org/attachments/4786

Is that the correct link? Same memmap output? Or simply that it fails after the uefi console output?

Do you mean 25.11 or 25.11.1? Can you try upgrading to 25.11.1 first?

CDe80

@stephenw10 Doesn't matter if i upgrade from 25.11 or 25.11.. Sorry i wanted to link the thread not the attachment. https://redmine.pfsense.org/issues/13895 But the bootprocess stops on line...

"masks 0X00XXXXX XXXXXXXX XXXXXXX"

haven't the exact hexcode yet, but i can check that later.

stephenw10

@csde80 said in Update To 26.03 fails (HyperV Gen2):

https://redmine.pfsense.org/issues/13895

Hmm. OK. That was resolved at the time. Some regression perhaps.

What server version are you running?

Are you able to test a clean 26.03 install?

CDe80

@stephenw10 Server 2025. Fresh install will take some time. I'll check it.

Bob.Dig

Had no problem upgrading on WinServer25, just saying. But then, netgate has probably insights in that anyway. ;)

CDe80

clean install with netgate-installer worked. I had two vms with this error. I'll check another vm later.

CDe80

@Bob.Dig your VMs is Gen2?

Bob.Dig

@csde80 It is. Though I don't know what all the loader.efi do...

stephenw10

Hmm, is it possible those VMs were created before the loader fixes went in for that closed bug?

I expect the loader to be upgraded but it might fail to do so if, for example, there isn't enough space in the efi partition. It should show an error at upgrade for that though.

CDe80

@stephenw10 yes first install may be a few years ago..

I think I'l try to reinstall

stephenw10

If you can it would be a very good test. That would pretty much prove an older boot loader issue.

CDe80

@stephenw10 Thanks, clean install and configrestore worked like expected.

stephenw10

Nice. Good to know.