Cisco Bug: CSCut37134 - UCS B/C M4 Series MRAID12G Raid Controller goes inoperable/crashes
May 22, 2018
- Cisco Unified Computing System
Known Affected Releases
Symptom: UCS B/C Series M4 based servers with MRAID12 RAID controllers may intermittently crash or hang. Other symptoms: -ESXi host will become un-manageable and unusable - Able to KVM into server, but no control. - Able to ping CIMC and ESXi mgmt interface - Able to SSH/putty into ESXi, will take user/password. Once logged in, no control. The following faults may be seen in UCSM or CIMC: Critical F1004 'Controller 1 on server 3/4 is inoperable. Reason: Device non-responsive' Major F0181 'Local disk 1 on server 3/4 operability: inoperable. Reason: Drive state: unknown' Major F0181 'Local disk 2 on server 3/4 operability: inoperable. Reason: Drive state: unknown' The following driver is seen in ESXi: # esxcli software vib list | grep lsi lsi-mr3 lsi-msgpt3 And appears as applied to at least one adapter in: # esxcfg-scsidevs -a If adapters use megaraid_sas driver in the above command, you are not affected by this issue Conditions: 1. MRAID12G based RAID controller in use 2. VMware ESXi 5.5 ISO retrieved from VMware site between 11/12/14 to 1/5/15. Issue has also been observed on 6.0 ISO images 3. RAID driver: lsi-mr3/lsi-msgpt3 CAVEAT: 1. Prior to removing lsi-mr3/lsi-msgpt3, verify that the correct mega_raid driver is installed. 2. Use command to verify: 'esxcli software vib list' 3. If lsi driver is removed and mega_raid is not already installed, datastore access will be lost as there is no driver for the controller present.
Related Community Discussions
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases