StarWind Software

I am trying Starwind Virtual San Free on two ESXI compute nodes.

I set up Hyper-V 2016 as a VM on each ESXI machine and installed Starwind software as "Starwind Virtual SAN Service". I successfully set up HA between the two nodes and exported a 256GB LUN. When I add the two servers in vSphere under "Dynamic Discovery Targets", I see ESXI properly discovering the target under "Path" and the target address matches what was exported by Starwind software. When I go to Devices, I rescan and rescan but do not see the LUN.

Here is what I have done to debug:

1) ESXI hosts can ping the Hyper-V Ms
2) Turned off firewall in Hyper-V using "netsh advfirewall currentprofile state off"
3) Used a third Windows10 VM and Microsoft iSCSI Initiator to connect to iSCSI target and I can connect and see the LUN in Drive Manager

Thanks for looking!

After having discovered the paths, your steps in the previous post miss creating a datastore. Did you do this before trying to rescan to be able to see the LUN?

Yes, I tried creating a datastore using the vsphere web client. New Datastore -> VMFS -> Select host with available Disks/LUNs and I see nothing there. Tried this on multiple ESXI instances and no luck but it seems like microsoft iscsi initiator can see it no problem. Any other settings I need for ESXI? Should I try to change ports?

Solved! Sector size was set to 4096 when esxi expects 512 only.

Hi goldserve,
Yes, you should select 512 sector size for ESXi.
Glad to hear the issue is solved