2026-07-05T18:26:30.100Z cpu8:2097962)lsi_mr3: megasas_hotplug_work:518: event code: 0x71.2026-07-05T18:27:17.257Z cpu5:2097564)lsi_mr3: mfi_TaskMgmt:690: Processing taskMgmt abort for device: vmhba1:C2:T0:L02026-07-05T18:27:17.257Z cpu5:2097564)lsi_mr3: mfi_TaskMgmt:724: ABORT request for SN 1257101388 Wld 20972172026-07-05T18:27:17.257Z cpu5:2097564)lsi_mr3: mfi_TaskMgmt:739: TA : SMID 1928 IN 29814904s OUT 0s TM 29814912s Delta 8s2026-07-05T18:27:17.257Z cpu5:2097564)WARNING: lsi_mr3: mfi_TaskMgmt:743: Abort not supported on C2:T0:L0 for SMID 19282026-07-05T18:27:17.645Z cpu24:2098062)ScsiDeviceIO: 4124: Cmd(0x45b8d92b6e08) 0x2a, CmdSN 0x1631dad7 from world 2097217 to dev "naa.################################" failed H:0x8 D:0x0 P:0x02026-07-05T18:27:19.254Z cpu7:2098096)lsi_mr3: mfi_VirtReset:633: VR : SMID 1921 IN 29814902s OUT 0s TM 29814913s Delta 11sVMware vSphere ESXi
The issue is caused by a physical hardware failure or degradation of the local disk(s) backing the RAID volume. When a physical disk drops offline or enters a degraded state, the lsi_mr3 controller loses communication with the logical device, triggering a continuous recovery loop of SCSI host resets (H:0x8).
To resolve this issue, perform the following steps:
Hardware Validation:
Hardware Replacement:
Storage Rescan:
VM Recovery: