Well, I spend one full day trying to setup FreeNAS 11-RC in a Hyper-V test environment. The host was a Windows 10 Pro x64 AU and I always got stuck at the mountroot prompt even dough the drive /dev/da0 was properly partitioned during installation, and the flash process using the ISO image seemed to be good in a test virtual drive of 16GB.
I tried using 9.10, same issue.
I checked the fingerprint of the downloaded images to ensure the iso downloads were fine. They were.
I tried VHD and VHDX.
I tried fixed and expandable drives.
I tried using the drive in the IDE and SCSI virtual devices
I tried Generation 1 and Generation 2
I tried BIOS and UEFI boots.
I tried to clean the partition doing gpart destroy -F da0 before installing
I tried mountroots as ufs and zfs
I tried multiple devices such as /dev/da0, /dev/da0p1, /dev/da0p2, freenas-boot/ROOT/default, ...
I tried to edit the grub config as suggested in the setup instructions, adding set kFreeBSD.kern.cam.boot_delay="50000" in the normal boot section
At the same time I made Google consume hundreds of KWh searching for a method to make it work. This morning I tried using the legacy 8.3. It doesn't have the drivers for Hyper-V so I added the Legacy Network Adapter. It installed without any problem. Then I tried to install again the FreeNAS 11-RC and it worked!!!!!!
After a few tests I have identified the issue. FreeNAS 9.10 and above doesn't properly boot if the Legacy Network Adapter is not present in the system, stopping in the infamous mountroot prompt. This is really weird, after everything is setup, FreeNAS is actually using the Virtual Network Adapter and not the Legacy Network Adapter.
I am not a FreeBSD expert but it is really weird that a network adapter could be affecting the file system mount. Anyway, I hope I could avoid many others the painful experience I had yesterday.
I tried using 9.10, same issue.
I checked the fingerprint of the downloaded images to ensure the iso downloads were fine. They were.
I tried VHD and VHDX.
I tried fixed and expandable drives.
I tried using the drive in the IDE and SCSI virtual devices
I tried Generation 1 and Generation 2
I tried BIOS and UEFI boots.
I tried to clean the partition doing gpart destroy -F da0 before installing
I tried mountroots as ufs and zfs
I tried multiple devices such as /dev/da0, /dev/da0p1, /dev/da0p2, freenas-boot/ROOT/default, ...
I tried to edit the grub config as suggested in the setup instructions, adding set kFreeBSD.kern.cam.boot_delay="50000" in the normal boot section
At the same time I made Google consume hundreds of KWh searching for a method to make it work. This morning I tried using the legacy 8.3. It doesn't have the drivers for Hyper-V so I added the Legacy Network Adapter. It installed without any problem. Then I tried to install again the FreeNAS 11-RC and it worked!!!!!!
After a few tests I have identified the issue. FreeNAS 9.10 and above doesn't properly boot if the Legacy Network Adapter is not present in the system, stopping in the infamous mountroot prompt. This is really weird, after everything is setup, FreeNAS is actually using the Virtual Network Adapter and not the Legacy Network Adapter.
I am not a FreeBSD expert but it is really weird that a network adapter could be affecting the file system mount. Anyway, I hope I could avoid many others the painful experience I had yesterday.