No disk on Hyper-v Clean install of 2.4



  • The issue: When I try to install 2.4 in a 2012r2 hyper-v gen1 vm, the installer does not see any disks, and as such won't install. (see screenshots)

    Snapshots used:

    • 20170129-1056

    • 20170131-1611

    • 20170201-1242

    Things I have tried:

    • I tried using a gen2 vm and had a different problem. (see screenshots)

    • I tried using a SCSI controller instead of the IDE controller on the gen1 vm and had the same problem of no disks found.

    • I tried installing 2.3 on the same gen1 vm with an IDE controller, and it worked without any issues!

      Since 2.3 installed without having issues, I don't think it is the vm…









  • Gen 2 is not supported in freebsd. It may be supported in the march time frame, from what I heard.

    There should be no problems with Gen 1. I'm using it and I frequently install from scratch with no problems. I have one ide controller for the pfsense drive and one ide controller to mount the iso.

    All of the hyper-v settings are defaults and when I install pfsense, I hit return for all of the prompts, using defaults.



  • The only settings I changed were

    • Changed the memory allocation from 512 to 1024

    • Added an extra CPU core

    • Added an extra NIC




  • Are you reusing a VM? If so, try creating a new one from scratch. I assign two virtual processors and 2000 MB of ram, not dynamic. Also two virtual nics, both connected to virtual switches, to which physical nics are connected. I don't think any of those changes should affect anything, however.

    The only other consideration might be hyper-v updates. Last time I updated the server was in October and if I recall, there were a couple of updates from the July time frame that caused problems. I thought they were supposed to have been fixed in freebsd, however.



  • The server does have all available windows updates installed.

    I made a fresh VM and tried the latest snapshot (20170202-1057), and it still does not see any disks to install onto. I have attached an export of the VM in case that is of any interest. The only changes made were increasing the ram to 2048, 2 cpu cores, and add an extra nic.

    [pfSense 2.4 gen1.zip](/public/imported_attachments/1/pfSense 2.4 gen1.zip)



  • Here is the thread where the updates were discussed: https://forum.pfsense.org/index.php?topic=120101.0

    The symptoms are different, so it may not be the same issue.



  • It works! slightly different symptoms, but same fix. Thanks for the help :)

    @dmds:

    On the installer boot prompt, select
    3. Escape to the loader prompt
    set hw.ata.disk_enable=1
    boot

    after installation do it again.

    after boot exit to shell with 8.
    ee /boot/loader.conf
    add the line
    hw.ata.disk_enable="1"



  • Glad it worked. Lucky guess. I guess that answers the question of whether the fix for this issue has made it into pfsense. Apparently not.



  • I see on redmine that this problem is marked as resolved, bug #6913. Should I resubmit this to redmine now that it appears to be an issue again?



  • @Dustin:

    I see on redmine that this problem is marked as resolved, bug #6913. Should I resubmit this to redmine now that it appears to be an issue again?

    Well, it's strange that this issue was considered to be closed, but based on your experience, it appears not to be. It's probably a good idea to resubmit it.

    The freebsg bugzilla references two updates, KB3172614 and KB3179574. Which one did you deinstall? I deinstalled the first, but didn't have to deinstall the second.



  • I didn't uninstall any updates, just added hw.ata.disk_enable=1 and that made it work.



  • @Dustin:

    I didn't uninstall any updates, just added hw.ata.disk_enable=1 and that made it work.

    Well, based on that, it seems pretty clear the problem isn't fixed.



  • Submitted to redmine. Bug #7213



  • @Dustin:

    Submitted to redmine. Bug #7213

    Great, thanks for posting. I'll be watching for the response.


Log in to reply