vmhba# adapter statistics indicate a high volume of failed READ and WRITE commands.VMware ESXi 7.x
VMware ESXi 8.x
This issue occurs due to a hardware-level communication failure between the ESXi hypervisor and the local storage controller (MegaRAID SAS Invader).
Validation:
The /var/run/log/vmkernel.log highlights the following error state: Host Status [0x1] NO_CONNECT
This is identified as a physical layer issue and troubleshooting within ESXi will not resolve the underlying connectivity issue.
Workaround:
A hard reboot of the ESXi host may temporarily re-initialize the vmhba# adapter and restore path connectivity; however, this does not address the root cause of the hardware instability.