RDM disk becomes inaccessible on a Microsoft Failover Cluster after migrating or vMotioning a cluster node to another host.

Products

• VMware vSphere ESXi

Issue/Introduction

• The RDM disk became inaccessible during the vMotion of a Microsoft Failover Cluster virtual machine.

Environment

• VMware ESXi 7.x
• VMware ESXi 8.x

Cause

•  The inaccessibility of RDM disks is due to intermittent transient storage events in the underlying storage infrastructure, which temporarily disrupt connectivity.
•  Lost connectivity events are causing the RDM disk to become briefly inaccessible.

/var/run/log/vmkernel.log

cpu9:456302793)VMW_SATP_ALUA: satp_alua_issueCommandOnPath:843: Path (vmhba1:C0:T0:L46) command 0xa3 failed with transient error status Transient storage condition, suggest retry. sense data: 0x6 0x2a 0x5. Waiting for 20 seconds$

cpu9:456302793)VMW_SATP_ALUA: satp_alua_issueCommandOnPath:843: Path (vmhba2:C0:T1:L46) command 0xa3 failed with transient error status Transient storage condition, suggest retry. sense data: 0x6 0x2a 0x5. Waiting for 20 seconds$

cpu9:456302793)VMW_SATP_ALUA: satp_alua_issueCommandOnPath:843: Path (vmhba1:C0:T17:L46) command 0xa3 failed with transient error status Transient storage condition, suggest retry. sense data: 0x6 0x2a 0x5. Waiting for 20 second$ .

[scsiCorrelator] 37520844843###us: [esx.problem.storage.connectivity.lost] Lost connectivity to storage device naa.6#85982####f099f45116##000000###. Path vmhba1:C0:T0:L46 is down. Affected datastores: Unknown.

[scsiCorrelator] 37520844889###us: [esx.problem.storage.connectivity.lost] Lost connectivity to storage device naa.6#85982####f099f45116##000000###. Path vmhba1:C0:T17:L46 is down. Affected datastores: Unknown.

 

 

 

 

Resolution

• Engage the storage vendor to investigate transient storage events. Check SAN fabric components (switches, cables, HBAs) for stability and connectivity issues.