Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

Critical Lock-up Detected. Code=f112h

SOLVED
Go to solution
EricH_4
Advisor

Critical Lock-up Detected. Code=f112h

I have 2 units of MSA1000 with this controller error on bootup. Is there any way to resolve this issue? Have tried the following:

- reseated fibre cables
- reseated controllers

and the problem still persists.

Pls advise.
25 REPLIES
blackhawk_1
Advisor

Re: Critical Lock-up Detected. Code=f112h

What f/w are you running on ?
There were lot of fixes in f/w v5.20 or v7.00 whichever is applicable here.

F/w v4.48 release notes extract:
"Fixes an issue where the MSA1000 array controller could get a â Critical Lockup F112hâ
when inserting new disk drives or migrating disk drive from non smart array based SCSI
controllers"

Try reseating the affected controller as well
EricH_4
Advisor

Re: Critical Lock-up Detected. Code=f112h

Thanks for your reply. The existing firmware is 4.24. And we have already tried cycling the power to the MSA as well as reseated the controllers but the problem still persists.
Amol Garge
Trusted Contributor

Re: Critical Lock-up Detected. Code=f112h

4.24 is ancient firmware!!!

Upgrade firmware asap.

MSA will perform better and will be more stable.

You can do it step wise by going to 4.48 and then to 5.20.
EricH_4
Advisor

Re: Critical Lock-up Detected. Code=f112h

Yes, but according to an HP engineer, we were asked to replace the controllers. The new controllers seem to be having FW4.48 (unsure at this time). Is it just a matter of powering down the MSA, remove the existing controllers and insert the new ones to get everything up and running?
Amol Garge
Trusted Contributor

Re: Critical Lock-up Detected. Code=f112h

Exactly, power down the MSA, insert the new controllers and zone the controllers to the servers.
But, I would still like to update the controllers to the latest version of active passive firmware which is more stable.

EricH_4
Advisor

Re: Critical Lock-up Detected. Code=f112h

Is there any way I can do a backup of the configuration from the existing controllers and dump them into the new ones?
Amol Garge
Trusted Contributor

Re: Critical Lock-up Detected. Code=f112h

To be very honest, I have never seen or heard anyone taking a config backup of the MSA1000 and restore it on the replacement controller, coz I think that the feature does not exist in MSA1000.

Maybe I missed something , Can any one else help Eric on this one?

KunalSahoo, any comments?
blackhawk_1
Advisor

Re: Critical Lock-up Detected. Code=f112h

There is no such option in MSA for backing-up config
EricH_4
Advisor

Re: Critical Lock-up Detected. Code=f112h

So it means that the replacement is just plug-and-play? Coz I do not want to reconfigure the whole array, or risk any kind of data loss due to the controllers' newer firmware version.
Amol Garge
Trusted Contributor
Solution

Re: Critical Lock-up Detected. Code=f112h

No, there's no loss of config after the controller replacement.
EricH_4
Advisor

Re: Critical Lock-up Detected. Code=f112h

Amol: according to your previous reply: "insert the new controllers and zone the controllers to the servers"

Could you clarify further on this?
EricH_4
Advisor

Re: Critical Lock-up Detected. Code=f112h

We will be getting the other two controllers by today. My question is: what if the firmware on these controllers are 7.10 (Active/Active) and the existing controllers we are using version 4.24 (active/passive). Will it work with my current setup? Do we need to reconfigure anything?
kunalsahoo
Valued Contributor

Re: Critical Lock-up Detected. Code=f112h

Hi Eric/Amol.....
sorry for late response ...

Eric, dont worry about configuration...

Reason...
1.Metadat's will be on disk drives.
2 Configuration stays in both controllers...and you have to upgrade only one controller and once it is done successfully the other will clone it automatically....so @ any given point of time the config is safe with 1 controller.......all the best

Cheers..
EricH_4
Advisor

Re: Critical Lock-up Detected. Code=f112h

Hi guys, I connected the console cable to the MSA1000 controller and did a show tech_support and found that one of the cache is disabled:

Cache:
128 megabyte read cache
128 megabyte write cache Version 2
Cache is GOOD, but Cache is temporarily disabled.
Disable Reason: Wrong Cache Board.
No unflushed data in cache
Battery:
Module #1 is fully charged and turned off.

I have searched the KB and could not get any info on "Wrong cache board". Is the accelerator bad, or could it be the battery?
kunalsahoo
Valued Contributor

Re: Critical Lock-up Detected. Code=f112h

hi , one of the cache needs to be replaced now....unfortunately controller would be repalced....module 1 is fine...log a case with HP support....
EricH_4
Advisor

Re: Critical Lock-up Detected. Code=f112h

Replaced the controllers and one of them still showed:

Cache:
128 megabyte read cache
128 megabyte write cache Version 2
Cache is GOOD, but Cache is temporarily disabled.
Disable Reason: Wrong Cache Board.
No unflushed data in cache
Battery:
Module #1 is fully charged and turned off

Is there a way to clear the cache?
EricH_4
Advisor

Re: Critical Lock-up Detected. Code=f112h

Hi guys,

Is there a way to set the controller in slot 1 or 2 as the active or passive unit? Is it true that the active controller must always be the one that is connected to the SAN switch directly behind it?

Amol Garge
Trusted Contributor

Re: Critical Lock-up Detected. Code=f112h

The only way to failover a controller is by removing the other any controller can be active at a given point of time, irrespective of the slot.
EricH_4
Advisor

Re: Critical Lock-up Detected. Code=f112h

Hi Amol,

OK, the thing is, I've replaced my old controllers and put in 2 new ones. Before the replacement, the controller on the left was the active unit and the one on the right was passive.

After the replacement, the controller on the right became active instead. What could cause it to switch sides??
Amol Garge
Trusted Contributor

Re: Critical Lock-up Detected. Code=f112h

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
Advisor

Re: Critical Lock-up Detected. Code=f112h

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
Trusted Contributor

Re: Critical Lock-up Detected. Code=f112h

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
Advisor

Re: Critical Lock-up Detected. Code=f112h

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

Re: Critical Lock-up Detected. Code=f112h

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?