Prblem with iSCSI on Win Server 2012R2 with HyperV role

Question

Hi all,
I have some problems with iSCSI on Win server. The problem is the following.
When I restart server it cannot find the path with VMs configuration and VMs can't start. After few minutes all problems are gone and HyperV can find everything but I must start VMs manually.
The server is DELL R710 with Broadcom NICs. I tried to configure LAN interfaces for iSCSI in two ways. First - from OS and second - from Broadcom BACS with disabled NDIS/Ethernet and enabled iSCSI. The results are the same.
I have two more servers connected to the storage in the same way and everything is fine there.
 Events are following:
1. Source MSiSCSI. ID 108
Status 0x00001069 determining that device interface \\?\{8e7bd593-6e6c-4c52-86a6-77175494dd8e}#MsVhdHba#1&3030e83&0&01#{2accfe60-c130-11d2-b082-00a0c91efb8b} does not support iSCSI WMI interfaces. If this device is not an iSCSI HBA then this error
can be ignored.  
2. Source bxois. ID 1
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
3. Source MSiSCSI. ID 113
iSCSI discovery via SendTargets failed with error code 0xefff0003 to target portal *10.10.45.36 0003260 B06BDRV\L4SC&PCI_163914E4&SUBSYS_02351028&REV_20\5&2457021e&0&30050200_0 10.10.45.37.
4. Source Hyper-V-Config. ID 4096
The Virtual Machines configuration 72D1CB1A-A7E3-425A-A709-DA9F6BF0E1A9 at 'I:\VM\exch01-t' is no longer accessible: The system cannot find the path specified. (0x80070003).
5. Source SMagent. ID 1
Message from SM agent service: SMagent: The SMagent service attempted to start but terminated. Possible causes include:  [1] The access virtual disk is disabled in NVSRAM. [2] No RAID controller modules with compatible firmware were found. [3] The default
logical unit number (LUN) assigned to the access virtual disk (typically 7 or 31) is not in the range supported by the host or is already in use by the host for another device. See your storage management documentation for more details.   
The Host Context Agent did NOT start because 0 RAID controller modules were found.
  

Answer 1

Hi Sergey,
>>When I restart server it cannot find the path with VMs configuration and VMs can't start. After few minutes all problems are gone and HyperV can find everything but I must start VMs manually.
As a workaround you can set the "startup delay" for VMs .
>>Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
The possible cause may be the network stack is not fully prepared when the initiator was trying to connect to persistent targets. The initiator will try to connect. When the network stack is fully prepared, the connection should be successfully established.
If you receive this error when the iSCSI target device that is listed on the  
Favorite Targets tab no longer exists, you can resolve this issue by removing the iSCSI target device from the list of favorite targets. 
If you receive this error, and you cannot access an iSCSI target device that is still configured on the network, make sure that the client computer has network connectivity to the iSCSI target. Additionally, make sure that name resolution is working correctly. 
If you have successfully connected to your iSCSI target device despite this error, it indicates that the connectivity issue was temporary. Therefore, you can safely ignore this Error event.
https://support.microsoft.com/kb/976072?wa=wsignin1.0
Best Regards
Elton JI
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.