Upgrading to 2.5.0 on HyperV boot loops

DD

@mdalacu https://forum.netgate.com/topic/154360/gen2-pfsense-2-4-5-p1-elf64_loadimage-read-failed-windows-2012r2-hyper-v

mdalacu

@dd said in Upgrading to 2.5.0 on HyperV boot loops:

https://forum.netgate.com/topic/154360/gen2-pfsense-2-4-5-p1-elf64_loadimage-read-failed-windows-2012r2-hyper-v

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...

Michael Sh.

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.

mdalacu

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.

alt text

Raul Ramos

@michael-sh said in Upgrading to 2.5.0 on HyperV boot loops:

ZFS

ZFS in a Virtual Disk? Very brave! Should not be a problem with boot!

JeffNL

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.

mdalacu

@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/.

n7n

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

@n7n said in Upgrading to 2.5.0 on HyperV boot loops:

Has no one found a fix for this?

Using myself Hyper-V on Windows 10 Pro 'lastest edition ' (I guess).
Gen1 type.
Went from 2.4.5-px to 2.5.0 to 2.5.1.
Not using ZFS, but the default one.
No issues what so ever.

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.