State in doubt" message indicates that the storage stack is unable to determine the status of the device, which is typically a result of physical layer interruptions or congestion at the hardware level.var/run/log/vmkernel.log logs show PDL errors triggering path failovers.YYYY-MM-DDTHH:MM:SS.MS+HH:MM cpu##:2098231)NMP: nmp_ThrottleLogForDevice:3867: Cmd 0x84 (0x45b####7ea48, 0) to dev "naa.#########################" on path "vmhba##:C0:T7:L##" Failed:YYYY-MM-DDTHH:MM:SS.MS+HH:MM cpu##:2098231)NMP: nmp_ThrottleLogForDevice:3875: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x25 0x0. Act:FAILOVER. cmdId.initiator=0x43####b5e0 CmdSN 0x####0e8YYYY-MM-DDTHH:MM:SS.MS+HH:MM cpu##:2098231)WARNING: NMP: nmp_DeviceRetryCommand:133: Device "naa.#########################"": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.YYYY-MM-DDTHH:MM:SS.MS+HH:MM cpu##:2097704)WARNING: VMW_SATP_ALUA: satp_alua_getTargetPortInfo:173: Could not find relative target port ID for path "vmhba##:C0:T7:L##" - Not found (195887107)YYYY-MM-DDTHH:MM:SS.MS+HH:MM cpu##:2098149)WARNING: NMP: nmpDeviceAttemptFailover:647: Retry world failover device "naa.#########################"" - issuing command 0x45b####7ea48YYYY-MM-DDTHH:MM:SS.MS+HH:MM cpu##:2098231)WARNING: NMP: nmpCompleteRetryForPath:364: Retry cmd 0x84 (0x45b####7ea48) to dev "naa.#########################"" failed on path "vmhba##:C0:T7:L##" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x25 0x0.YYYY-MM-DDTHH:MM:SS.MS+HH:MM cpu##:2098231)WARNING: NMP: nmp_PathDetermineFailure:3527: Cmd (0x84) PDL error (0x5/0x25/0x0) - path vmhba##:C0:T7:L## device naa.#########################" - triggering path failover.Engage the Storage and Fabric vendors to investigate the health of the storage array and the physical paths (switches, cables, and SFPs).