Troubleshooting

Provider cannot find FC or ISCSI initiator

1. Verify the FC and ISCSI configurations on the host, SAN, and storage. Make sure that at least one initiator is installed on the host or the guest OS.
2. Verify the settings for Hyper-V. Ensure that the IP address, user name, password, and domain are set correctly, that the user is authorized to access WMI on the host, and that the domain is set as the host's computer name if it is not the domain user.
3. Ensure that the storage protocol setting and the existing initiator configuration are not in conflict.

Volume not supported by Volume Shadow Copy Service and Virtual Disk Service

Verify that the volume on the disk is supported by the Volume Shadow Copy Service and Virtual Disk Service. The disk must be from SAN Volume Controller or DS8000® and must be added to the guest OS as a pass-through disk. Virtual hard disks are not supported by the Volume Shadow Copy Service and Virtual Disk Service, although they may be supported on the LUN from SAN Volume Controller or DS8000.

Importing a shadow copy failed or locating a LUN failed while taking the shadow copy

Either the guest OS has no SCSI controller or the address on the SCSI controller on the guest OS is insufficient. Shut down the guest OS and add the SCSI controller to the guest OS.

Target LUNs are not attached to the host through the virtual port

1. Verify the virtual port configuration on the host, SAN, and storage.
2. Verify that the guest OS configuration files are on the LUN through the virtual port. The volume on the LUN must be assigned a drive letter. A mount point is not supported.
3. Ensure that the storage protocol is not set to ISCSI.

VMware virtual machine not recognized as virtual machine

The VMware virtual machine is not recognized as a virtual machine because the systeminfo in the VM is incorrect.

If the option SMBIOS.reflectHost = "TRUE" in the virtual machine’s configuration file (vmx) is added, the systeminfo is changed.