HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Proliant ML330 G3 Server

 
Ted_50
Occasional Contributor

Proliant ML330 G3 Server

I recieved this error after rebooting from a long weekend. "Error 215: non functioning voltage regulator module for processor 1 and 2". Do I need a new voltage regulator or is there an adjustment? and what might have caused this problem?

Thanks,
Ted
4 REPLIES
Brian_Murdoch
Honored Contributor

Re: Proliant ML330 G3 Server

Ted,

Update to the latest system BIOS as a first step since HP are always adding support and fixes for Intel CPU's to the BIOS.

http://h18023.www1.hp.com/support/files/server/us/download/23628.html

If the problem perists you may have to get the system board replaced since the PPM (Processor Power Modules -Previosuly called VRM's) are integrayed into the system board on the ML330 G3.

I hope this helps.

Brian
Ted_50
Occasional Contributor

Re: Proliant ML330 G3 Server

How am I supposed to update the BIOS if the server will not start????
Brian_Murdoch
Honored Contributor

Re: Proliant ML330 G3 Server

Sorry Ted,

You didn't make it clear that the server would not start but it makes sense if it's a continuous, solid fault. Some errors can be bypassed by pressing F1 when prompted. In your case you'll need to log a call with HP and get them to come and fix it.

Some part numbers:-

ML330 G3 System board - 324709-001
2.4Ghz Xeon CPU - 325034-001
2.8Ghz Xeon CPU - 324708-001
3.06Ghz Xeon CPU - 333055-001

It could be a CPU pulling down one of the voltages.

Regards,

Brian
NITIN TYAGI
Occasional Visitor

Re: Proliant ML330 G3 Server

Ted ,
I really don't think that both of the PPM shoul be going bad at the same time unless
system board or powersupply have gone bad......
so try booting the server with one processor...and....
try doing a power recycling