SCSI Host Status H:0x7 observed in the vmkernel logs

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms 

• VMware ESXi hosts repeatedly report losing access to datastores, triggering "Lost access to storage volume due to connectivity issues" events in the vCenter .
• In your ESXi logs, you may see the following error: /var/run/log/vmkernel.log
  YYYY-MM-DDTHH:MM.601Z cpu10:2098354)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.##########################" state in doubt; requested fast path state update...
YYYY-MM-DDTHH:MM.601Z cpu10:2098354)ScsiDeviceIO: 4173: Cmd(0x45b9d316efc8) 0x2a, CmdSN 0x7beb5 from world 2097225 to dev "naa.######################" failed H:0x8 D:0x0 P:0x0----------This status is returned when the HBA driver has aborted the I/O
YYYY-MM-DDTHH:MM:SS.419Z cpu78:2098730)NMP: nmp_ThrottleLogForDevice:3874: Cmd 0x2a (0#############) to dev "naa.###############################" on path "vmhbaXX:CX:TX:LX" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL
YYYY-MM-DDTHH:MM:SS.385Z cpu32:2097258)ScsiDeviceIO: 3485: Cmd(0#############) 0x28, CmdSN 0x800e0000 from world 3043630 to dev "naa.########################" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.

 

Environment

• VMware vSphere ESXi 7.x
• VMware vSphere ESXi 8.x
• VMware vSphere ESXi 9.x

Cause

This status H:0x7 is returned when a device has been reset due to a Storage Initiator Error. This typically occurs due to an outdated HBA firmware or possibly (though rarely) as the result of a bad HBA.
A mismatch between the currently installed HBA driver version and the hardware firmware version, might prevents the host from processing I/O requests correctly.

Resolution

Please reach out to the hardware vendor and make sure that you are on the correct driver/firmware version.

Additional Information

If the issue persists despite using certified versions, contact the hardware vendor to investigate physical HBA health, SFP integrity, or SAN switch configuration.