17xx-Controller in lock up State

[Alvin Lau_1]

I have two ProLiant DL380 G2 servers, and it appears the 5i controller cards on both are non-functional.

One server gives me the 17xx-Controller in lock up State error message.

The other server attempts to initialize the 5i controller but fails. It is unable to spin up any drives and eventually just sits there with a blinking cursor.

Any ideas on how to proceed? Will replacing the onboard 5i controller cards resolve these problems?

[Richard_387]

I also got the same problem. Have you got the answer ?

[John_325]

I am also having this problem. Has anyone found a solution? I think I might have found that it could be the Raid Controller going bad...

Please, any help would be greatly appreciated.

[David Seffren]

I have the problem as well. Hopefully someone will respond with a solution instead of dittoing the problem. I have a spare 5i controller which I will install on Sun 6/26/05.

[Jefferson Humber]

When I first got my MSA1000 we had an issue when on startup the controller locked itself (Critical lockup) and refused to budge... sounds similar to what you have here.

The engineer told me that the MSA (which is base on Smart Array technology) does this to protect the disks from being trashed.

I assume you have the latest firmware installed on the controller already ?

At the end it was a known issue (inside HP at least) with the MSA F/W at the time, but one of the disks was a bit suspect.

When the MSA locked up, one of the LED's on one of the 14 disks stayed on. Anyway the engineer swapped the disk, power cycled the MSA and it all came back to life.

Do you have any HDD LED's that stay illuminated when the controller locks up ? If so is it always the same disk ?

[George Nanobashvili]

I have identical problem. LED is on only on one (always the same HDD). the HDDs are fine because i had another similar server and they boot up fine there.

[Richard_387]

My Controller stop working right now. Anyone that already replace the controller got the problem solved ? Please let me know so I can replace mine too.

[Ryan Goff]

you can try the following steps when you have this issue:

1) reseat controller
2) disconnect all scsi cabling
3) attempt a firmware update with the firmware maintenance cd (latest at the moment is 7.4):
http://h18007.www1.hp.com/support/files/server/us/download/23331.html

if those three steps do not make the lock up error go away you have no choice but to replace the controller or systemboard if it is embedded.

[Eran Niditz]

how do i reset a 5312 array controller ????

[Vincent Fleming]

Open a new thread.

[Richard_387]

That's right, I already do that things. I finally change my SCSI Controller. Someone said that it is common problem for this card. The card is easy to be damage.

[Oliver Green]

Just in case anyone else reads this post . . . I have a Smart Array 6400 Series in a Proliant M350 G3 with exactly the same problem, and did this to correct it:

1. Unplugged server completly
2. Grounded myself
3. Removed Array Card & Cables
4. Removed Primary & Secondary Cache Battery Packs & Memory from controller board.
5. Left the system and components for 30 secs
6. Put it all back together & powered up

* Note none of the drive lights were on when the server first came up with the problem during a normal reboot. Array controller cache batteries had reported low on a previous boot though.

Oliver

[Jim Creek]

5i is not seated properly. (Make sure 5i card is seated properly or try reinstalling)
Wrong 5i/5i plus. 5i for ML370 G2 and DL380 G2 look the same in appearance but they are different. (Make sure that you are using the correct part number)
To see if it is caused by 5i or system board, remove 5i from DL380 G2 and disable 5i by using SCSI Interlock Disable switch. For ML370 G2 remove 5i. If after removing the 5i you do not get 17xx error on POST replace 5i otherwise replace system board.

[Marc Carney]

I'm in agreement. I had this problem this week on two different servers, one a DL380 and the other an ML370, both with 5i controller boards. On one of the servers reseating the 5i card worked, on the other I needed to replace the board.
Try reseating the 5i board, if that doesn't work then replace the 5i card.

Marc

[zbysek]

I had the same issue an reseating (turn off the server, take the 5i board out, put it back in, turn on the server) helped me to resolved the issue. I had nothing attached to the controller (no drives no SCSI devices).