Upgrading to 2.5.0 on HyperV boot loops
Hi i have tried to upgrade my firewall 2.4.5-RELEASE-p1 (amd64) to 2.5.0 from GUI and all went fine until it installed the new kernel (with success) and rebooted.
Then after the restart the boot menu appeared as usual and after timeout imidiadly rebooted again. And it kept like this a few times until the VM stopped.
I have tried all the possible combinations in boot menu to make it to work. Nothing excapes the bootloop until i choose the old kernel. Then the upgrade process continues it reaches the pfsense shell menu but GUI will not work and nothing else works with old kernel.
What can i do to upgrade it. I already restored from backup and i am ready to start again if someone has an ideea.
The HyperV VM is running on a win 2012 R2 configured as Generation 2, Version 5 with Secure Boot disabled.
@mdalacu No one else is using HyperV on 2.5.0? Thx.
swinn last edited by
@mdalacu I run pfSense 2.5 on Hyper-V 2019 as Gen2 without any issues.
Thanks, but i am running 2.4.5_p1 just fine with gen2...so it's not this.
Anyway i have to sort this out soon because of squid borks daily in 2.4.5 and a lot of people are saying that 2.50 fix this...
I have the same problem, but at first after upgrade I had mountroot> from new kernel. Any attempts to manually mount have failed. I did a clean install and got bootloop.
I using Hiper-V on 2016 VM Gen2, ZFS. I have tried every possible installation option for ZFS + Gen 2 but no success. Works on UFS. FreeBSD of the same version works fine on ZFS + Gen 2.
Trying to boot from the install media (CDROM) also fails (v2.5.0), resulting in a bootloop.
So the problem is with the kernel i think.
This is the error.
Raul Ramos last edited by Raul Ramos
I also had the problem upgrading to 2.5.0
Quick-fix was to just re-install and restore a backup.
The VM’s (two, pfSense CARP failover) are on Hyper-V.
The original installation was:
Generation 2, with ZFS
The new installation is:
Generation 1, default filesystem settings during install
I guess not all update scenarios have been tested before releasing the update.
@jeffnl Yes, this was the onlyu way i could find to upgrade the firewall. A brand new machine gen 1 and restore settings from backup. Some packages would not work until I re-saved every page of configuration again, to recreate all the files, I presume.
I hope it will me stable at least. Squid was my main problem with 2.4.5/.
I have exactly the same problem.
I also had the mountroot problem after updating from 2.4.5 to 2.5.1.
I "fixed" that by booting from the old kernel.
However, after the upgrade completed, I now experience the boot loop problem as above.
Has no one found a fix for this?
Gertjan last edited by
provels last edited by provels
Probably doesn't help, but I'm using 2.5.1 on Hyper-V on 2012R2, Gen1, ZFS without issues, either running or upgrading. But I did build myself a fresh 2.5.1 with restored config after a while, just because.