PFSense Hyper-V 2.2 to 2.3 upgrade fails
-
I've been running 2.2 through several upgrades as a Windows 2008r2 vm successfully and it's been great. Got notification of the 2.3 upgrade and decided to go ahead and install. Upon reboot, it could not find the boot drives. I watched the Hyper-V synthetic device drivers get loaded (or so I thought, it happens so quickly), but it can't find ANY drives after reboot. Caused me some panic attack, as that's our firewall that feeds the mail server and we all know what happens when email doesn't flow.
Anyway, long story short, I had to restore my vm hardrive to get the install back again. Is there any way of getting the 2.3 install to work on Hyper-V or am I stuck on 2.2.
-
Seems like there's more than a few Hyper-V 2.3 boot issues floating about, some suggesting an upgrade to 2012.
Take a look at:https://forum.pfsense.org/index.php?topic=109802.0 for some ideas, there are definitely other threads if you search the forum.
You might also want to have a look in "Virtualization installations and techniques":https://forum.pfsense.org/index.php?board=37.0, I'm sure they'll have more info.
-
Everything points to the apparently fact that PFSense doesn't have ATA support enabled in the boot configuration. I did multiple searches and tried multiple things, but it didn't work. I'm going to try the ATA support fix and see if that does it.
-
When you say it's failing to boot, is hyperv failing to find a boot device or is pfsense (freebsd) failing to find a device to mount?
If it's the 2nd one, take a look at this post, it sorted my problems.
https://forum.pfsense.org/index.php?topic=109802.msg612250#msg612250
