F1004, Controller .... is inoperable; Reason: CIMC did not detect storage

[Walter Dey]

Infrastructure is at 2.2.6d.

Customer needed NVIDIA M& GPU, which requires 2.2.7.

B200-M4 at 2.2.6d

We created Host Firmware package 2.2.7 and linked this to the propriate Service Profile.

Capability Catalog was also updated to 2.2.7.

Now, we see an ugly critical error poping up: 

F1004, Controller .... is inoperable; Reason: CIMC did not detect storage ! see attachment !

Facts:

- OS is installed on local disk and is booting and working !

- decommission / reack of the blade doesn't clear the error 

[Paul Felts]

Hello Walter, 

What OS is the blade currently running? If you're running ESXi please provide the output for the following command from the ESXi CLI:

esxcfg-scsidevs -a

-AJ

[Walter Dey]

Hi Paul

No, it's Windows, I think 2008 R2 !

I just remember, that most likely they did not update the drivers (was 2.2.3d before the upgrade).

Walter.

[Paul Felts]

Hello Walter, 

We want to make sure that the RAID Controller is running the megaraid_sas driver and not ls_mr3. 

-AJ

[Walter Dey]

Thanks Paul

- Am I correct ? you are referring to Windows Raid Controller setting (not the one done by HFP ?) ?

- how can I find out, and how can it be fixed ? is this part of driver iso package ?

Walter.

PS. Despite this error, OS and data on the local disks are available and working ! this error just popped up, after we applied a HFP 2.2.7 and did a Capability catalog update to 2.2.7

[Paul Felts]

Hello Walter, 

Please see the following document: http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/hw/C240M4/install/C240M4/raid.html#70245

-AJ

[Walter Dey]

This document refers to C-Series ! we have B200-M4 ? does your comment about raid controller apply as well ?

[Paul Felts]

Walter, 

The section that is linked is hardware agnostic.

-AJ

[Cristobal Segovia Tapia · Accepted solution]

Defect ID

Symptom

First Bundle Affected

Resolved in Release

CSCuv46749

When using Cisco B200 M4 blade servers with the UCSB-MRAID12G storage controller, the following random, incorrect transient alerts or faults are no longer reported: Critical Fault [F1004] Controller Inoperable, Reason: Device reported corrupt data. Critical Fault [F1004] Controller Inoperable, Reason: Device non-responsive.

2.2(3g)A, 2.2(6d)C, 3.0(2c)B

3.1(1g)

[Walter Dey]

Thanks Cristobal !

Is there a similar defect for C-series server, e.g. 

SR 680411058 : F1004 : Equipment Inoperable StorageController 3

Walter.