The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)
View by Article ID
ESX host fails when using an LSI SCSI controller
Symptoms
When using an ESX/ESXi host with LSI SCSI controllers, such as Dell PERC or IBM ServeRAID, you experience these symptoms:
The ESX/ESXi host fails
The host gets disconnected from vCenter Server
Virtual machines do not run
Cannot access the ESX/ESXi host using an SSH session
Local console access may be available, but log in attempts fail
Network stack is active and replies to ping requests
In the lsi.txt file of the host, located at /tmp, you see entries similar to:
Event Sequence Number : 2320
Timestamp : 1/5/2012 ; 16:47:48
Event code : 15
Locale : Boot/Shutdown event
Class : Dead (visible after next controller boot)
Description of the event : Fatal firmware error: Line 156 in ../../raid/1078int.c
Argument Type Value: 18
Argument Type : MR_EVT_ARGS_STR
String : Line 156 in ../../raid/1078int.c
Note: The lsi.txt file is a log file in ESX/ESXi 4.x and 5.0 that captures events from LSI branded disk controllers. This log is gathered when grabbing a diagnostic log bundle of the host or by issuing a vm-support command at the console and will have a name similar to lsi.xxxxxx.log e.g lsi.60513027.log.
Cause
This issue occurs if you are using an outdated firmware on the LSI branded SCSI/RAID controllers. This includes models of the Dell PERC and IBM ServeRAID controllers.
Resolution
To resolve this issue, apply the firmware update available for the LSI branded SCSI controller.
Note: The preceding link was correct as of January 19, 2012. If you find the link is broken, provide feedback and a VMware employee will update the link.
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
