Search the VMware Knowledge Base (KB)
View by Article ID

iSCSI datastore is inaccessible to the host (2150992)

  • 0 Ratings
Language Editions

Symptoms

  • iSCSI datastore is  inaccessible to the host.

  • LUN is visible under devices, however it is not visible as a datastore.

  • When trying to "Add Storage", it gives a warning on formatting the LUN if proceeded.

  • Only the iSCSI LUNs show up on the host connected device list, but they cannot be mounted as VMFS Datastores.

  • I/O errors may be observed when we check the iSCSI LUNs, Partition info and Hexdump addressing Host busy with Abort commands.

    hexdump: /vmfs/devices/disks/naa.6000d310033e28000000000000000003: Device or resource busy
    <YYYY-MM-DD>T<TIME>.628Z cpu22:65920)VMWARE SCSI Id: Could not get disk id for vmhba1:C0:T5:L0
    <YYYY-MM-DD>T<TIME>.196Z cpu36:67172 opID=e85c5cae)WARNING: xpt_scsi_adapter_discover:1224: unable to find target 1: No connection
    <YYYY-MM-DD>T<TIME>.317Z cpu29:68000 opID=55b3417f)vmw_ahci[0000001f]: atapiIssueCommand:Unsupported ScsiCommand: 0x9e, cdblen(0x10) is bigger than limit(0xc)
    <YYYY-MM-DD>T<TIME>.337Z cpu20:65959)WARNING: iscsi_vmk: iscsivmk_TaskMgmtIssue: vmhba64:CH:0 T:1 L:1 : Task mgmt "Abort Task" with itt=0x134 (refITT=0x133) timed out.
    <YYYY-MM-DD>T<TIME>.207Z cpu31:66363)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba64:CH:0 T:1 CN:0: iSCSI connection is being marked "OFFLINE" (Event:4)
    <YYYY-MM-DD>T<TIME>.335Z cpu31:66363)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000002 TARGET: iqn.2002-03.com.compellent:5000d310033e2821 TPGT: 0 TSIH: 0]
    <YYYY-MM-DD>T<TIME>.335Z cpu31:66363)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.123.41:29514 R: 192.168.123.10:3260]
    <YYYY-MM-DD>T<TIME>.419Z cpu29:67375)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.6000d310033e28000000000000000003" state in doubt; requested fast path state update...
    <YYYY-MM-DD>T<TIME>.587Z cpu31:66363)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x43069f4ed1c0 network resource pool netsched.pools.persist.iscsi associated
     

  • In thevmkernel.log you may see similar entries:

    YYYY-MM-DDT04:46:45.217Z cpu1:66104)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x28 (0x439500ced340, 66728) to dev "naa.600140593c9775cd3e97d449edb347dd" on path "vmhba64:C1:T0:L0" Failed: H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL
    YYYY-MM-DDT04:46:45.217Z cpu1:66104)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.600140593c9775cd3e97d449edb347dd" state in doubt; requested fast path state update...
    YYYY-MM-DDT04:46:45.217Z cpu1:66104)ScsiDeviceIO: 2927: Cmd(0x439500ced340) 0x28, CmdSN 0x5 from world 66728 to dev "naa.600140593c9775cd3e97d449edb347dd" failed H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.
    YYYY-MM-DDT04:46:45.359Z cpu1:65696)NMP: nmp_ThrottleLogForDevice:3546: last error status from device naa.600140593c9775cd3e97d449edb347dd repeated 10 times
    YYYY-MM-DDT04:46:45.603Z cpu1:65692)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.600140593c9775cd3e97d449edb347dd" state in doubt; requested fast path state update...


  • In thevmkwarning.log you may see similar entries:

    YYYY-MM-DDT04:46:47.602Z cpu1:69214)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.600140593c9775cd3e97d449edb347dd" state in doubt; requested fast path state update...
    YYYY-MM-DDT04:46:48.606Z cpu1:69236)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.600140593c9775cd3e97d449edb347dd" state in doubt; requested fast path state update...

Note: This log excerpt is an example. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs when the iSCSI adapters are configured to use Jumbo frames and the MTU is set to 9000.

Resolution

To workaround the issue:

  1. Check the MTU at which the vmkping fails.
  2. Reset the MTU to 1500.

    You should now be able to restore the VMFS datastore access

  3. Reconfigure the MTU values to 9000 to be able to communicate to the storage

Note: The Physical Network switch we notice the MTU was set to 9000, which needs to be replaced with the MTU value 9216.

For more information, see:

 

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: