topic Re: Critical Lock-up Detected. Code=f112h in Disk Enclosures

Critical Lock-up Detected. Code=f112h

EricH_4 — Sun, 11 Oct 2009 02:27:26 GMT

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.

Re: Critical Lock-up Detected. Code=f112h

blackhawk_1 — Sun, 11 Oct 2009 11:52:17 GMT

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

Re: Critical Lock-up Detected. Code=f112h

EricH_4 — Tue, 13 Oct 2009 00:02:53 GMT

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.

Re: Critical Lock-up Detected. Code=f112h

Amol Garge — Tue, 13 Oct 2009 04:36:33 GMT

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.

Re: Critical Lock-up Detected. Code=f112h

EricH_4 — Tue, 13 Oct 2009 06:47:35 GMT

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?

Re: Critical Lock-up Detected. Code=f112h

Amol Garge — Tue, 13 Oct 2009 08:46:43 GMT

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.

Re: Critical Lock-up Detected. Code=f112h

EricH_4 — Tue, 13 Oct 2009 23:38:17 GMT

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

Re: Critical Lock-up Detected. Code=f112h

Amol Garge — Wed, 14 Oct 2009 07:36:50 GMT

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?

Re: Critical Lock-up Detected. Code=f112h

blackhawk_1 — Wed, 14 Oct 2009 09:08:13 GMT

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

Re: Critical Lock-up Detected. Code=f112h

EricH_4 — Wed, 14 Oct 2009 23:30:53 GMT

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.

Re: Critical Lock-up Detected. Code=f112h

Amol Garge — Thu, 15 Oct 2009 18:11:41 GMT

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

Re: Critical Lock-up Detected. Code=f112h

EricH_4 — Fri, 16 Oct 2009 00:17:23 GMT

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

Could you clarify further on this?

Re: Critical Lock-up Detected. Code=f112h

EricH_4 — Fri, 16 Oct 2009 01:57:36 GMT

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?

Re: Critical Lock-up Detected. Code=f112h

kunalsahoo — Fri, 16 Oct 2009 04:59:01 GMT

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..

Re: Critical Lock-up Detected. Code=f112h

EricH_4 — Thu, 22 Oct 2009 02:10:51 GMT

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?

Re: Critical Lock-up Detected. Code=f112h

kunalsahoo — Thu, 22 Oct 2009 22:07:32 GMT

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....

Re: Critical Lock-up Detected. Code=f112h

EricH_4 — Mon, 26 Oct 2009 23:27:58 GMT

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?

Re: Critical Lock-up Detected. Code=f112h

EricH_4 — Tue, 03 Nov 2009 01:18:14 GMT

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?

Re: Critical Lock-up Detected. Code=f112h

Amol Garge — Tue, 03 Nov 2009 06:43:25 GMT

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.

Re: Critical Lock-up Detected. Code=f112h

EricH_4 — Tue, 03 Nov 2009 06:50:32 GMT

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??