Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

ESX/ESXi host becomes unresponsive at vsd-mount when booting after attaching SAN Storage (1014101)

Symptoms

  • An ESXi/ESX host connected to a SAN becomes unresponsive during the boot process at  Loading VSD-Mount
  • The host boots normally when SAN is disconnected.
  • The host does not drop into a busy box shell.
  • If you press Alt+F12 at the console, you see these messages:

    WARNING: VMW_SATP_LSI: satp_lsi_issueCmdRetryOnLockViolation: MODE_SELECT10 command to path "vmhba1:C0:T0:L0" failed with status = 2/0 0xb 0x44 0x0
    WARNING: VMW_SATP_LSI: satp_lsi_setPreferredController: Could not write mode page data for path "vmhba1:C0:T0:L0"
    WARNING: VMW_SATP_LSI: satp_lsi_setPreferredController: Issuing forced satp_fastt_setPreferredController
    WARNING: VMW_SATP_LSI: satp_lsi_setPreferredController: Could not write mode page data for path "vmhba1:C0:T0:L0"
    WARNING: VMW_SATP_LSI: satp_lsi_tryToActivatePath: Disruptive switch to Standby Path "vmhba1:C0:T0:L0" failed during activation.
    WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device " t10.________________" - issuing command 0x4100020d0dc0
    WARNING: NMP: nmp_SelectPathAndIssueCommand: PSP selected path "vmhba1:C0:T0:L0" in a bad state (standby)on device " t10.________________".
    WARNING: NMP: nmp_CompleteRetryForPath: Retry command 0x0 (0x4100020d0dc0) to NMP device " t10.________________" failed on physical path vmhba1:C0:T0:L0" H:0x1 D:0x0 P:0x0 Possible sense data: 0xb 0x44 0x0.
    WARNING: NMP: nmp_CompleteRetryForPath: Logical device "t10.________________": awaiting fast path state update before retrying failed command again...

  • The ESXi/ESX host fails to mount the local vmfs volume while it tries to resolve the issue with mounting the SAN volumes.
  • This issue may occur with, but is not limited to, these disk arrays:
    • IBM DS 4800 FC SAN
    • Sun StorageTek 6140

Resolution

This issue occurs if the LUNs are presented incorrectly to the ESXi/ESX host.
 
To resolve this issue, ensure that you follow best practices for disk arrays in ESXi/ESX configuration:
  • Use the Multipathing Checklist in the Fibre Channel or SCSI SAN Configuration Guide for your version of ESXi or ESX.
  • Request a storage configuration best practices from your hardware vendor. Many vendors have a document that explains the configuration settings for use in conjunction with ESXi/ESX.
To work around this issue in the short term and start the ESXi/ESX host:
  1. Power off the ESXi/ESX host.
  2. Disconnect the Fiber Channel cables from the ESXi/ESX host.
  3. Start the host with only local storage available.

Additional Information

To find specific information about the SAN that is failing:
  1. Start the host successfully, reconnect the SAN storage cables and rescan the ESXi/ESX host.
  2. Check the VMkernel logs for messages with id " t10._____________".
  3. Use this information to contact your vendor for specific configuration details.

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

  • 16 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)
  • 16 Ratings
Actions
KB: