Unrecoverable System Error Error code 0x0000002D

[GScala]

Has anyone found a solution to this error?
Unrecoverable System Error code 0x0000002D, 0x00000000 in IML on HP Proliant DL360 G5.

[KarloChacon]

as usual update to latest Proliant support pack 8.15 and update to latest firmware 8.4

[GScala]

Thank you Karlo. I will try that and let you know if that resolves the issue.

[Andrés Zuccarino]

Hi GScala,
You solved the problem, applying these firmware updates?
Sorry for my English

Regards,

Andres

[GScala]

Hi Andres,
Applying these firmware updates did not fix the problem. I still do not have a solution for this.

Regards,

Gerald

[James Kennedy_4]

Try downgrading the HP Proliant iLO2 Management Controller Driver for Windows Server 2003 to version 1.8.

[GScala]

Thank you James, I will try that.

-G

[Andrés Zuccarino]

Thank you,
Already this the version 1.11:

Http: // h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp? Lang=en*cc=us*prodTypeId=3709945*prodSeriesId=1842753*swItem=MTX-295127d6d21d4885a860038d5b*prodNameId=3288152*swEnvOID=1005*s wLang=8*taskId=135*mode=5

Regards,

Andres.

[James Kennedy_5]

1.11 does not fix the problem, only 1.8 did, for me.

[Andrés Zuccarino]

Lamentably in our case, the mistake was reproducing with this version (1.8.0.0) :(

"The software is installed but is not up to date.

Current Version: 1.8.0.0"

Regards,

Andres.

[Graeme Bray]

Whats your physical hardware configuration?

I had an Intermodule Bus Error on one of my servers that I had fixed by moving a NIC card.

[GScala]

Andres,

I apologize, but are you saying that 1.8 did not fix the problem for you? Thank you.

Regards,
-G

[Andrés Zuccarino]

Lamentably this version I do not solve the problem, for several months we had 1.8.0.0 and approximately every 15 days the reebot is produced.
Yesterday apply the version 1.11 we are going to see that it happens.
Now I am trying to evaluate if the problem only is provoked during long loads of disc.

Regards,
Andres.

[GScala]

Thank you Andres. I am at version 1.13. Please keep me posted about your disc testing. I continue to troubleshoot and will let you know if I find a resolution.

Regards,
-G

[Andrés Zuccarino]

Scala, care that there are two different devices observes:

-HP iLO Management Channel Interface Driver (for this one we have the version 1.13)

-HP Proliant iLO 2 Management Controller Driver (for this device it is the James was referring on the version 1.8, certainly I comment to you that since actualize to the version 1.11 I restart 2 times in one day.

Regards,

Andrés.

[GScala]

Okay, thank you Andres, much appreciated.

[Andrés Zuccarino]

Really as James was saying HP's new versions Proliant iLO 2 Management Controller Driver provokes restarts, I will return to the version 1.8.0.0, let's hope that at some time HP deals with the problems....
Attach an image with the restarts after applying these updates.

Regards,
Andrew

[Andrés Zuccarino]

Hi GScala, Your do you continue with the problem?
We separate the load in two severs, and the problem stopped happening, which demonstrates that in our case it is not a topic of incompatibility with Virtual Server of Microsoft, but it is a fault of hardware that on having demanded it provokes some fault.

Regards,

Andres

[GScala]

Yes, I still experience this problem. So it looks like it is a hardware issue. Have you heard anything from HP about it?
Thank you Andres.

[Andrés Zuccarino]

Hi GScala, the error changed, now the following appears:

*** Hardware - Malfunction
Call your hardware vendor for support
NMI: Parity Check / memory parity error
*** the system is halted ***

That have application in these servers? In our case the problems appear only in the server that we have Microsoft Virtual Server 2005 and Hypper-V.

Rergards,

Andres

[cevers]

We are experiencing the same issues on a Proliant DL380 G5.
We've had the system board and p400 controller replaced, which made no difference. Before having these parts replaced we were seeing the server fail about every third day, however now we are lucky to see it stay up for more than a couple of hours.
Has anyone had any progress with this fault?

[GScala]

I have not made any progress here.

[TarunJain]

Hi,
It should be a hardware failure for sure.
You must have tried some of following steps but just in case you haven't.

1. Have you tried checking system on minimum configuration?
2. Which PCI-e and PCI-X devices are installed in this server? Try removing them.
3. Disable the ASR (for testing only)
4. RUN offline diagnostics via Smart Start CD.
## Offline diagnostics will take more than hour depending on the loops and number of hard drives, This will check all the hardware components. It is also helpful to determine if the issue could be reproduced without OS

[syati]

Hi,

Is there any soluiton for this? I facing the same issue. Can anyone help?

Thank you.

[Torsten.]

May depend on the server model:

http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c02662362&sp4ts.oid=1121516