Frequent "lsi_mr3: mfi_TaskMgmt: ... Processing taskMgmt abort for device" messages on ESXi host

Products

• VMware vSphere ESXi

Issue/Introduction

ESXi host experiences repeated "Processing taskMgmt abort for device" messages on local disk(s) connected via a particular storage controller followed by affected virtual machine VSCSI I/Os. 
Guest OS I/Os running on the virtual machine are affected as well. 

vmkernel.log: 
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu60:9953953)lsi_mr3_####:##:##.#: mfi_TaskMgmt: 689: Processing taskMgmt abort for device: vmhba#:C#:T#:L#
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu60:9953953)lsi_mr3_####:##:##.#: mfi_TaskMgmt: 724: ABORT request for SN ########## Wld #######
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu60:9953953)lsi_mr3_####:##:##.#: mfi_TaskMgmt: 731: Cmd is not available with driver. Probably, it is completed already
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu60:9953953)lsi_mr3_####:##:##.#: mfi_TaskMgmt: 689: Processing taskMgmt abort for device: vmhba#:C#:T#:L#
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu60:9953953)lsi_mr3_####:##:##.#: mfi_TaskMgmt: 724: ABORT request for SN ########## Wld #######
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu60:9953953)lsi_mr3_####:##:##.#: mfi_TaskMgmt: 731: Cmd is not available with driver. Probably, it is completed already
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu48:9953953)VSCSI: 3402: handle #################(GID:####)(vscsi0:0):Reset request on FSS handle ########## (0 outstanding commands) from (vmm0:<VM NAME>)
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu48:9953953)VSCSI: 3446: handle #################(GID:####)(vscsi0:0):Added handle (refCnt = 3) to vscsiResetHandleList vscsiResetHandleCount = 1
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu22:2097731)VSCSI: 3700: handle #################(GID:####)(vscsi0:0):processing reset for handle ... state ##########
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu22:2097731)VSCSI: 3493: handle #################(GID:####)(vscsi0:0):Completing reset (0 outstanding commands)
YYYY-MM-DDThh:mm:ss.###Z In(182) vmkernel: cpu22:2097731)VSCSI: 3551: handle #################(GID:####)(vscsi0:0):reset processed removed handle from vscsiResetHandleList 0

Environment

VMware vSphere ESXi 

Cause

HBA driver / firmware or HBA / disk hardware issue. 

Resolution

Confirm that driver / firmware for the local controller is supported and compatible. Necessary to install compatible driver / firmware version for the controller. See Broadcom Compatibility Guide.
Engage a hardware vendor for further investigation from the hardware perspective. .