Critical Lock-up Detected. Code=f112h

[Amol Garge]

Hello,

At the time of startup, which ever controller boots up first, will become the master controller. The other controller will serve the purpose just the same.

[EricH_4]

Hi Amol,

I was told that the active controller must be directly in front of the SAN switch. In this case, can I just power up with the left controller first, and after it has finished booting, hot-plug the controller on the right?

[Amol Garge]

or, you can remove the active controller(right), let the other controller(left) become active and reinsert the other controller(right).

There is no rule which says that the active controller should be behind the SAN switch, unless some specific reason was told to you.

Your current setup will work ok.

[EricH_4]

But I've read somewhere that hot-unplugging an active controller may cause the MSA to lockup? I would prefer a safer alternative.

[rodionovan]

Critical Lock-up Detected. Code=f112h

We have 2 units of MSA1000 with 4.24 version of firmware.

After installing new disk we got  “03 Critical Lock-up Detected. Code=f112h”.

When we inserting this disk by “hot plug” method, everything works fine, but after rebooting MSA1000 we have this error anyway.

When this drive isn‘t inserted, everything initializes fine.

The drive is mirror of system disk (RAID 1)

Disk specification:

Firmware:HPB3

Model number: BF01885A34

Drive CPN: 286774-004

CT: 25A34016COK40Q

PN: *9W7006-038*

SN: *3JY09MTE“

And the HP additional sticker with other SN: 8G33LSG1T11W (why there is 2 SN‘s?)

After reading this topic http://h30499.www3.hp.com/t5/Disk-Array/Critical-Lock-up-Detected-Code-f112h/m-p/4511648#M32929 I’ve understood that we have to update the firmware of controller, but we have some questions.

1. The firmware of disk, that worked was HPB4, and on disk which we are inserting is HPB3. In theory HPB4 is newer, than HPB3, and have to run without updating wirmware? Or Maybe this disk is refurbished, and there is newer firmware than written on it?
2. Where can we got information about steps of updating MSA1000 firmware?
3. The main thing is that we have not to lose the configuration of MSA1000 while updating, how it is possible to provide this?

[rodionovan]

Abbreviations and acronyms:

Disk1 – “new” disk from store (HPB3) BF01885A34

Disk2 – disk from PMS 10 slot (HPB4)  BF018863B8

Disk3 – disk from DS20 (HPB4)  BF018863B8

SYS –  SYSTEM array, 8 slot

PMS – PMS array, 10 slot

State: Disk 1 in SYS “hot-plug” only, Error – critical lock-up after MSA restart

Working with SYS

• Cold change Disk1 on Disk3

Start -> Error – critical lock-up

• Cold remove Disk3
• Hot plug Disk3

Restart -> Error – critical lock-up

• Cold remove Disk3

The result of this experiment gives us knowing that case isn't in drive's firmware.

State: SYS has no drive in, MSA starts fine

• Hot-plug Disk1 to SYS
• Rebuilding SYSTEM array
• Cold remove Disk2 from PMS
• Cold plug Disk3 disk to PMS

Error – critical lock-up SYS

• Cold remove Disk1 from SYSTEM array

Error – critical lock-up PMS

• Cold remove Disk3 from PMS

Initializing OK

• Hot plug Disk2 to PMS

Initializing OK

• Cold remove Disk2 from PMS
• Hot-plug Disk2 to SYS
• Rebuilding SYSTEM array
• Restart -> Initializing OK
• Hot plug Disk1 to PMS

State: Disk1 in PMS “hot-plug” only, Error – critical lock-up after MSA restart

What can you say?