The virtual machine configured with an RDM device hangs while booting or takes a long time to boot

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• The virtual machine configured with an RDM device hangs while booting or takes a long time to boot
• In the /var/log/vmkernel.log file of the ESX 4.x host or the /var/log/messages.log file of the ESXi 4.x host, you see errors similar to:
  
  Nov 6 08:01:01 esx3 vmkernel: 3:18:59:22.568 cpu1:4097)WARNING: NMP: nmp_CompleteRetryForPath: Retry command 0x28 (0x4100032fefc0) to NMP device "naa.60a9800050335749544a53754956686b" failed on physical path "vmhba3:C0:T0:L14" H:0x0 D:0x2 P:0x0 Valid sense data: 0x2 0x4 0x2.
  Nov 6 08:01:01 esx3 vmkernel: 3:18:59:22.568 cpu1:4097)WARNING: NMP: nmp_CompleteRetryForPath: Logical device "naa.60a9800050335749544a53754956686b": awaiting fast path state update before retrying failed command again...
  
  
• In the /var/log/vmkwarning.log file of the ESX 3.5 host or the /var/log/messages.log file of the ESXi 3.5 host, you see the error:
  
  WARNING: SCSI: CheckPathReady:2941: CheckUnitReady on vmhba2:3:13 returned I/O error 0x0/0x2 sk 0x2 asc 0x0 ascq 0x0
  
  
• The virtual machine boots properly if the RDM is removed
• The virtual machine boots properly if the RDM is added to the virtual machine when it is powered on

Environment

VMware ESXi 3.5.x Installable
VMware ESXi 4.0.x Installable
VMware ESXi 4.0.x Embedded
VMware ESX Server 3.5.x
VMware ESXi 3.5.x Embedded
VMware ESX 4.0.x

Resolution

This issue occurs when the ESX/ESXi host attempts to read from a device that is in a NOT READY state. A device may be in a NOT READY state for multiple reasons.

To resolve this issue, implement either or all of the following options, as applicable:

• In an ESX/ESXi 3.5 environment, if you see the message WARNING: SCSI: CheckPathReady:2941: in the logs, install Patch ESX350-200907407-BG for ESX 3.5 and ESXe350-200907401-I-BG for ESXi 3.5. For more information, see VMware ESX 3.5, Patch ESX350-200907407-BG: Updates vmkernel and hostd RPMs(1012543) and VMware ESXi, Patch ESXe350-200907401-I-BG: Updates Firmware(1012544).
• In an ESX/ESXi 3.5 or 4.x environment, ensure that the storport driver running on Windows is up to date. For more information, see the Microsoft Knowledge Base article 932755.
  
  Note: The preceding link was correct as of August 19, 2010. If you find the link is broken, provide feedback and a VMware employee will update the link.
  
  
• In an ESX/ESXi 3.5 or 4.x environment, ensure that the LUN accessed by the ESX host or the RDM device accessed by the virtual machine is in the READY state. To verify the readiness state of a LUN, contact your SAN administrator.