ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Proliant DL180 G6 Smart Array P410 error 0x15

kboutin
Occasional Visitor

Proliant DL180 G6 Smart Array P410 error 0x15

I have an SBS 2003 server that has been spontaneously rebooted multiple times over the last week.  When it comes back up there is no indication that there was a problem.  Nothing in the event log, HP System Management shows all green for the controller and the drives in the array.

 

This morning, the server was down.  When I went to look at it, 2 drives had orange lights.  Rebooting the machine showed everything green again.  The only exception was that we saw an error (it went by pretty fast) that said:

 

A controller failure event occurred prior to this event.  

 

it also gave an error of 0x15.  Unfortunately, this is all I could see from it.

 

Firmware on the P410 is 3.66.

 

Thoughts?  Help?

2 REPLIES
Lincy_Zachariah
Valued Contributor

Re: Proliant DL180 G6 Smart Array P410 error 0x15

Hi,

 

Try updating the controller firmware to the latest which is 5.70. Link to the firmware:

 

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=3884339&swItem=MTX-601169bc8ce241e7b817df269c&prodNameId=3884340&swEnvOID=1005&swLang=8&taskId=135&mode=4&idx=3

 

Issues Fixed with this firmware are:

•Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.

•Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card

•Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.

•Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB). •Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).

•Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.

•Fixed an issue where a controller configured for 100% read cache could cause a false "A cache error was detected. Run a diagnostic report for more information" error to be displayed in the 'Cache Status Details' column in ACU.

•Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory c03011608.

•Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.

•Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.

•Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).

•Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.

•Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.

•Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.

•Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.

•Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.

•Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA C03161926. •Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA c03127437. •Fixed an issue in which 3TB drives were not managed as spares.

•Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory c03083515.

•Fixed an issue that caused the 5.70 component (cp017182.exe) to fail during installation under the German Language version of the OS. This issue is fixed in the 5.70(B) component (cp017780.exe).

•Firmware version 5.70(D) resolved an issue in a configuration supporting multiple HP Smart Array controllers. After flashing an HP Smart Array P812 controller, then the flash operation would terminate without flashing any other controllers in the system.

Thanks & regards,
I work for HP
A quick resolution to technical issues for your HP Enterprise products is just a click away HP Support Center Knowledge-base
See Self Help Post for more details
______________________________________________________
Was the post useful? Say thanks by clicking the white KUDOS Star!

Lincy_Zachariah
Valued Contributor

Re: Proliant DL180 G6 Smart Array P410 error 0x15

 

 

you can aslo try the guided troubleshooting optin forthis model of server:

 

http://h20584.www2.hp.com/hpgt/guides/select?lang=en&cc=us&prodTypeId=15351&prodSeriesId=3884339

Thanks & regards,
I work for HP
A quick resolution to technical issues for your HP Enterprise products is just a click away HP Support Center Knowledge-base
See Self Help Post for more details
______________________________________________________
Was the post useful? Say thanks by clicking the white KUDOS Star!