FreeNAS virtualized on Hyper-V 2012 missing physical passthrough disks

Status
Not open for further replies.

vchrizz

Cadet
Joined
Mar 1, 2017
Messages
2
Hi,

I've got a small test-environment running some VMs on Hyper-V 2012 and would like to use FreeNAS as internal ISCSI Backup-Storage. I've also read in the forums several times that Hyper-V is horrible with FN but i would like to try to get this running though.
Generally i noticed some issues when changing virtual hardware, so i have to reinstall FN every time i change the hardware, but thats ok..

Its a server with two SSDs where the VMs are stored and two HDDs where VM-Backups are stored. As it's all testing, backups are only used for cases where some upgrade fails and one wants to get back a day or two. Right now a backup-VM has the HDDs directly assigned what works fine but is some kind of wasted storage (backups for a week take only about 30% of the disk) that could be also used for other VMs storing larger data.
So the idea is to run FN as VM and share the HDDs storage for more than one VM.

I've read that physical hardware is preferred but it would be overkill to run a second server for this small test-environment, so a virtual machine is preferred. So its a new Hyper-V VM (4 vCPU, 8GB, NIC: mac-spoofing allowed) with a 8GB virtual Disk on IDE0:0 and 4TB physical Disk on SCSI0:0 .
First i couldn't get the current stable release 9.10.2 to install, at the point "installing base os" the installation skips the process and jumps to the next "installing freenas" just to skip onto the next "installing feeenas ui" until the "installation finished" message is shown. Booting it up fails with mounting the rootfs. Same behaviour with installing on a physical disk.

The current nightly FreeNAS-10-MASTER-201702281640-64fed5578 installed on the virtual disk properly nearly without issues, networking is not working and HDDs won't show up.
After reading searching/reading some posts about Hyper-V, I had to configure the VMs NIC to allow mac-spoofing, else the network connection does not work. Some users reported the requirement of the legacy NIC but i didnt notice a difference, as long as mac-spoofing is allowed.
Now i don't understand why the physical HDDs won't show up in UI, as they are selectable while installation. On the forum I've found this thread where the problem was solved by using beta 10. Sadly, not for me as I'm already using the recent nightly.

What could i debug to (maybe) get this working?

EDIT: I found a bug report which seems to be the same problem that I've got, should I file another bug report or could it still be that I misconfigured something?

sg_vpd -a da0
Code:
[root@freenas] ~# sg_vpd -a da0
Supported VPD pages VPD page:
  Supported VPD pages [sv]
  Device identification [di]
  Third party copy [tpc]
  Block limits (SBC) [bl]
  Block device characteristics (SBC) [bdc]
  Logical block provisioning (SBC) [lbpv]
  0xcf
Device Identification VPD page:
  Addressed logical unit:
	designator type: T10 vendor identification,  code set: Binary
	  vendor id: MSFT
	  vendor specific: 0x771ee44feb948841b2e73726199bca84
	designator type: NAA,  code set: Binary
	  0x60022480771ee44feb943726199bca84
Third party copy VPD page:
Block Device ROD Token Limits:
  Maximum Range Descriptors: 8
  Maximum Inactivity Timeout: 0 seconds
  Default Inactivity Timeout: 0 seconds
  Maximum Token Transfer Size: 131072
  Optimal Transfer Count: 131072
Block limits VPD page (SBC):
  Write same non-zero (WSNZ): 0
  Maximum compare and write length: 0 blocks
  Optimal transfer length granularity: 0 blocks
  Maximum transfer length: 0 blocks
  Optimal transfer length: 0 blocks
  Maximum prefetch length: 0 blocks
  Maximum unmap LBA count: 4294967295
  Maximum unmap block descriptor count: 4096
  Optimal unmap granularity: 65536
  Unmap granularity alignment valid: 1
  Unmap granularity alignment: 0
  Maximum write same length: 0x0 blocks
  Maximum atomic transfer length: 0
  Atomic alignment: 0
  Atomic transfer length granularity: 0
  Maximum atomic transfer length with atomic boundary: 0
  Maximum atomic boundary size: 0
Block device characteristics VPD page (SBC):
  Medium rotation rate is not reported
  Product type: Not specified
  WABEREQ=0
  WACEREQ=0
  Nominal form factor not reported
  ZONED=0
  BOCS=0
  FUAB=0
  VBULS=0
Logical block provisioning VPD page (SBC):
  Unmap command supported (LBPU): 1
  Write same (16) with unmap bit supported (LBWS): 0
  Write same (10) with unmap bit supported (LBWS10): 0
  Logical block provisioning read zeros (LBPRZ): 0
  Anchored LBAs supported (ANC_SUP): 0
  Threshold exponent: 1
  Descriptor present (DP): 0
  Minimum percentage: 0
  Provisioning type: 2
  Threshold percentage: 0
Vendor VPD page=0xcf VPD Page:
Only hex output supported
VPD page code=0xcf:
00	 00 cf 00 14 01 00 00 00  15 8f a9 89 28 c9 8b 4d
10	 94 cd ef 51 fa a9 9d 33


sg_vpd -a da1
Code:
[root@freenas] ~# sg_vpd -a da1
Supported VPD pages VPD page:
  Supported VPD pages [sv]
  Unit serial number [sn]
  ATA information (SAT) [ai]
  Block limits (SBC) [bl]
  Block device characteristics (SBC) [bdc]
  Logical block provisioning (SBC) [lbpv]
Unit serial number VPD page:
  Unit serial number:	  WD-WCC4E0177022
ATA information VPD page:
  SAT Vendor identification: WDC
  SAT Product identification: WD40EZRX-00SPEB0
  SAT Product revision level: 80.0
  Device signature indicates PATA transport
  ATA command IDENTIFY DEVICE response summary:
	model: WDC WD40EZRX-00SPEB0
	serial number:	  WD-WCC4E0177022
	firmware revision: 80.00A80
Block limits VPD page (SBC):
  Write same non-zero (WSNZ): 0
  Maximum compare and write length: 0 blocks
  Optimal transfer length granularity: 0 blocks
  Maximum transfer length: 0 blocks
  Optimal transfer length: 0 blocks
  Maximum prefetch length: 0 blocks
Block device characteristics VPD page (SBC):
  Nominal rotation rate: 5400 rpm
  Product type: Not specified
  WABEREQ=0
  WACEREQ=0
  Nominal form factor not reported
  ZONED=0
  BOCS=0
  FUAB=0
  VBULS=0
Logical block provisioning VPD page (SBC):
  Unmap command supported (LBPU): 0
  Write same (16) with unmap bit supported (LBWS): 0
  Write same (10) with unmap bit supported (LBWS10): 0
  Logical block provisioning read zeros (LBPRZ): 0
  Anchored LBAs supported (ANC_SUP): 0
  Threshold exponent: 0
  Descriptor present (DP): 0
  Minimum percentage: 0
  Provisioning type: 0
  Threshold percentage: 0


camcontrol devlist -v
Code:
[root@freenas] ~# camcontrol devlist -v
scbus0 on ata0 bus 0:
<>								 at scbus0 target -1 lun ffffffff ()
scbus1 on ata1 bus 0:
<Msft Virtual CD/ROM 1.0>		  at scbus1 target 0 lun 0 (cd0,pass0)
<>								 at scbus1 target -1 lun ffffffff ()
scbus2 on camsim0 bus 0:
<>								 at scbus2 target -1 lun ffffffff ()
scbus3 on blkvsc0 bus 0:
<Msft Virtual Disk 1.0>			at scbus3 target 0 lun 0 (da0,pass1)
<>								 at scbus3 target -1 lun ffffffff ()
scbus4 on storvsc1 bus 0:
<WDC WD40EZRX-00SPEB0 80.0>		at scbus4 target 0 lun 1 (da1,pass2)
<>								 at scbus4 target -1 lun ffffffff ()
scbus-1 on xpt0 bus 0:
<>								 at scbus-1 target -1 lun ffffffff (xpt0)


Thanks
 

Attachments

  • Freenas-Install-HDDs.png
    Freenas-Install-HDDs.png
    26.3 KB · Views: 245
  • Freenas-Install-HDDs-not-visible-in-webui.png
    Freenas-Install-HDDs-not-visible-in-webui.png
    58.1 KB · Views: 263
Last edited:

vchrizz

Cadet
Joined
Mar 1, 2017
Messages
2
No, I also tried to use IDE1:0 instead SCSI but even after FN reinstall, still same issue.
Guess its something minor, as the disk is visible in several places in log while Installation. Just within the webui I don't see it to configure and use it.

What could I try else? I'm out of ideas :/
 
Status
Not open for further replies.
Top