In the vmkernel.log in /var/run/log/, the below log snippet is observed:
2024-10-24T16:00
:47.419Z cpu78:2098730)NMP: nmp_ThrottleLogForDevice:3874: Cmd 0x2a (0x45bae81287c0, 3043630
) to dev "naa.6006016082224f00265a5362fc957f4e
" on path "vmhba65:C0:T0:L2" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL
2024-10-24T16:00:58.385Z cpu32:2097258)ScsiDeviceIO: 3485: Cmd(0x459b4b0d5280) 0x28, CmdSN 0x800e0000 from world 3043630 to dev "naa.6006016082224f00265a5362fc957f4e" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.
This status is returned when a device is 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.
Engage the hardware vendor to investigate the Storage Initiator Error.