Cluster validation fails for vVOL disk added to WSFC node.

Products

• VMware vSphere ESXi

Issue/Introduction

After adding a New Hard Disk to Windows Server Failover Cluster (WSFC) VM and configuring, the Cluster Manager validation check fails for this Quorum witness disk within the Windows Guest OS.

From ESXi host's /var/run/logvmkernel.log reports, below logs are available:

NMP: nmp_ThrottleLogForDevice:3849: Cmd 0x5f/0x2 (0x45b9a43c6708, 3241356) to dev "naa.xxxxx" on path "vmhba64:C1:T0:L100" Failed:
NMP: nmp_ThrottleLogForDevice:3859: H:0x0 D:0x2 P:0x0 Valid sense data: 0x6 0x2a 0x5. Act:NONE. cmdId.initiator=0x430cdd43b380 CmdSN 0xffff9982f7bcbc10 sllid: e2000000004d0000
ScsiDeviceIO: 4124: Cmd(0x45b9a43c6708) 0x5f, CmdSN 0xffff9982f7bcbc10 from world 3241356 to dev "naa.xxxxx" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x6 0x2a 0x5 sllid: e2000000004d0000
VVol: 2424: [vvolDev: naa.xxxxx] WRITE command (ioFlags 0x0, cmd 33) failed: Transient storage condition, suggest retry (0xbad00be)
NMP: nmp_ThrottleLogForDevice:3815: last error status from device naa.xxxxx repeated 1 times
VVol: 2424: [vvolDev: naa.xxxxx] WRITE command (ioFlags 0x0, cmd 33) failed: SCSI reservation conflict (0xbad0023)

Cause

Reservation release fails with Storage transient error, where the command is retried and is getting failed with reservation conflict. Because the reservation conflict is coming from the Storage array.

Resolution

Engage respective Storage Vendor to determine the cause of reservation conflict.