Upgrade from pfSense 2.1.5 to 2.2 on Hyper-V

After the release of pfSense 2.2 it was time to upgrade some installations. They resides on Windows Server 2012 R2 Hyper-V. After the first reboot my test machine did not come up. The screen looks like this:

pfSense 2.2 Upgrade 01The error message is quite interesting at first:

Mounting from ufs:/dev/ad0s1a failed with error 19.

After little goggling I’ve found this article:

Mounting from ufs:/dev/adaxs1a failed with error 19.

and after simple entering of one ? the answer to the problem was in front of me:

pfSense 2.2 Upgrade 02The disk names were change from




So to boot I’ve typed:

pfSense 2.2 Upgrade 03and voilàpfSense 2.2 Upgrade 04

Now the only thing that is left if to make changes to the boot configuration

You have the option to for form console

8) ShellpfSense 2.2 Upgrade 05and edit the file pfSense 2.2 Upgrade 06Mine looked like this:pfSense 2.2 Upgrade 07and after the change like thispfSense 2.2 Upgrade 08

Of if you will you can make the change using the web gui

go in the Diagnostics menu and selecting the Edit FilepfSense 2.2 Upgrade 09From there you just naviage to the “/etc/fstab” and edit the text.pfSense 2.2 Upgrade 10After changes test that the system is booting from the correct partition.


10 thoughts on “Upgrade from pfSense 2.1.5 to 2.2 on Hyper-V

  1. This is exactly what happened to me upgrading to pfsense 2.3 it had been smooth sailing to that point. Thanks for great article. Bacon saver you are 🙂

  2. Thank you Stefan!!! You saved me a lot of time. I just upgraded from 2.6 to 3.1 and was getting the same error. After I found this post it was a snap to fix. The file names were even the same as in this post.

  3. Instead of editing fstab you can ran a script that will convert /etc/fstab to UFS labels rather than disk device names.

  4. Great Post! For anyone running Hyper-V on a 2008 R2 or earlier, you have to upgrade your host server to 2012 R2. There is no avoiding this if you want to run the latest version of PFSense. After you upgrade to 2012R2, the steps above will work and you will be able to see your partitions.

  5. Thanks!!!! It works perfectly for me… and you make save some money…. kkkkkk

  6. Getting a similar error while trying to boot on a Firebox from CF card. But when I enter “?” I don’t get anything listed for GEOM devices. What might I need to do from there? Thanks in advance!!

Comments are closed.