Unable to access the LUN when multiple initiator access is not configured on a storage array
search cancel

Unable to access the LUN when multiple initiator access is not configured on a storage array

book

Article ID: 308261

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • Unable to power on the virtual machine.
  • In the hostd.log file located on /var/log on the ESXi host, you see the error similar to:
The system cannot find the file specified. Cannot open the disk '/vmfs/volumes/4ee0f315-c2262f60-d173-0019b9bacced /VM/VM.vmdk' or one of the snapshot disks it depends on.

VMware ESX cannot find the virtual disk "/vmfs/volumes/4ee0f315-c2262f60-d173-0019b9bacced/VM/VM.vmdk". Verify the path is valid and try again.
  • The ESXi host is able to ping the iSCSI target but unable to access the LUN where the VMDK is stored.
  • At least one different ESXi host on the same cluster can successfully access the same LUN.


Environment

VMware vSphere ESXi 5.0
VMware vSphere ESXi 5.1
VMware vSphere ESXi 5.5

Cause

This issue occurs when multiple initiator access is not configured on a storage array.

Resolution

To resolve this issue, ensure that multiple iSCSI initiators sessions are allowed and properly configured on a given storage array.
Note: The procedure varies from vendor to vendor. Consult with your Storage Array vendor for further information regarding these settings.

Example:
  • On Synology storage array, select the Allow multiple sessions from one or more iSCSI initiator.
  • On Dell Equalogic storage array, select the Enable shared access to the iSCSI target from multiple initiators.


Additional Information