Latest pfsense+ 23.01 beta freezes on Hyper-v
-
Ok, so it just fails to boot at the first reboot during upgrade?
That's what we might expect given the previous failures.Do you have the upgrade log showing what was updated before that reboot?
Specifically did it update the boot loader?Steve
-
I ordered the update via GUI, I realized that some packages are pending update in the "Package Updater", but as recommended on the Netgate website, I didn't do any package update.
pfsense downloads the full update and tells you to restart the VM.
When starting the VM, it hangs at masks 0x00ff0000. 0x0000ff00. 0x000000ff. 0xff000000 and I don't have any more logs being shown in the VM console.
Exactly the same message posted by the colleague appears:
Even redoing the installation from scratch and increasing the VM disk size, the same error occurs.
Are there any other procedures you would recommend so that I can gather more logs? -
If you SSH to the firewall and then upgrade from the console menu using option 13 you can see exactly what happens before the reboot. That might give some idea as to what's happening.
However we did look into this for some time before release and didn't yet find the root cause.
-
@fiblimitless
Sorry for late reply was busy.
Here is what I get when I ran gpart show on my 22.05 vm before upgrade to 23.01 (can't run on upgraded as it does not boot)
-
Any updates on the error in question?
-
Any news, guys?
-
@snk said in Latest pfsense+ 23.01 beta freezes on Hyper-v:
Any news, guys?
Check the Redmine linked a few posts above.
-
There is one update and that's that this appears probably linked to the loader issues we are seeing in Azure: https://redmine.pfsense.org/issues/13895#note-9
Yet that doesn't apply directly because we are still unable to replicate it with multiple NICs defined.
However is everyone who is hitting this issue in Hyper-V using a VM with 3 or more NICs defined?
-
In my case I only have two nic's in my VM.
It would be the WAN and the LAN. However, with the LAN having a bridged vswitch between 3 ports.
Worse than even installing again and upgrading by upgrade, when jumping from version 22.05 to 23.01 the error persists.
I've tried several combinations of configurations, but without success... Keeping the ZFS standard.
I'll try the UFS pattern later. -
Ports on the vSwitch wouldn't make a difference. The actual NICs in the VM seemingly can.
You might try a single NIC install or adding more NICs, see if either makes any difference.
Or removing any other virtual hardware from the VM that might be using resources at boot.
Steve
-
I have 10 NICs (for not loosing NDI) and no problem. But I don't have dynamic Memory enabled.
-
make a new hyper-v VM choose "generation 1".
select the existing pfsense vm disk.boot perfectly! hope it helps.
-
This should be fixed with the loader changes on Plus 23.05 snapshots, if someone can try upgrading an affected Gen2 VM to 23.05 that would help testing:
https://redmine.pfsense.org/issues/13895
I still can't reproduce the original boot problem here (on 23.01 or otherwise)
-
@jimp said in Latest pfsense+ 23.01 beta freezes on Hyper-v:
This should be fixed with the loader changes on Plus 23.05 snapshots, if someone can try upgrading an affected Gen2 VM to 23.05 that would help testing:
https://redmine.pfsense.org/issues/13895
I still can't reproduce the original boot problem here (on 23.01 or otherwise)
I tried earlier today at 10:00am EST and it still froze... I got tired of it and deleted the vm. Any hint on what snapshot date I should wait for? May 3rd I presume?
-
The loader changes have been in for a while now, any recent snapshot should be OK if that was the problem.
-
@jimp Thanks Jim. I read through this whole thread for every hint or comment, and have given up.
IMHO, there is now way to go from 2.6 to 23.01 on Windows Server 2002 which is VM v10.
Perhaps? your Win11 v11 is the difference.
-
@rpotter28 Na, I am on Server 2022 with no problem. I think it is only a very few with problems.
Btw there was no announcement about the beta in the forum this time? But I guess it is a bug fix release anyways. -
@bob-dig Thanks for that, I am not usually in the very few having problems. Would love to solve it! I am testing on a fully patched/updated 2022 cluster with no other issues.
i have 2.7 running just fine, and received another 3 keys this morning so I will try to go to 23.01 from there. How did you get to 23.01?
-
Hmm, 2.7 does not hit this for you but 23.05 does?
-
S Snk referenced this topic on
-
D DEHAAS referenced this topic on
