Replacing a HP P410 RAID Card
I'm getting kernel panics and I'm suspecting it's the RAID card locking itself up based on the messages in the panic log. I'm not sure if it's really the card or not.
When it boots back up, it says there was a controller error: "A controller failure event occured prior to this power-up. (Previous lock up code 0xab)"
Here is the kernel panic log: http://imgur.com/mlxjf9t,SvVoJcz#0
So, I'm looking to replace the RAID Card but I'm not sure if I'm able to just physically replace the card and the raid array gets detected automatically and the configuration imported to the new RAID card.
What procedure should I follow?
Yes, you can replace a Smart Array controller with a like-model. The array configuration and metadata are on the disks, not the controller.
More questions...
- What type of server is this? I need the make and model of the system.
- If this is not an HP server, how long have you had it in this configuration?
- What specific operating system and release are you using?
- What type of disks are connected to the controller?
- Do you have cache and a battery or flash capacitor unit on the controller?
Depending on the answer to that question, your solution could be as simple as firmware or as complex as a system board replacement.
The HP Smart Array P410 RAID controller is often embedded on the system board (known as the P410i). It was the standard controller for G6 and G7 HP ProLiant servers and has a solid track record. I've only had to replace one or two out of a few thousand systems over the years.
This controller is also available as a standalone PCIe card, the P410. This was how the card was delivered with HP 100-series ProLiant servers.
If you are having problems, please update the firmware for the controller and related components. If this is an HP server, you can use the SPP bootable DVD. Otherwise, the firmware page for the controller is here.
- If this is an embedded controller, you may be due for a system board replacement.
- If this is a standalone controller, you may just have to replace the controller.
- This may just be a cache module failure on the controller.