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

compaq ML350 G2 server hangs and unexpectedly restarts

 
john cerbus
Occasional Visitor

compaq ML350 G2 server hangs and unexpectedly restarts

server freezes up completely
when performing folder copy commands etc. to and from network...Also, after a few hours, server will shut down and restart on its own...
have clean install of windows server 2000 (a few performance
counter issues - nothing major)
have installed all microsoft/hp updates including
rom flash ..

also have latest health mgmt drivers and agents so known fan/ thermal restart issue should be solved...

only events indicate previous shutdown was unexpected - no reason given...

we have 15 pc's windows 2000, NT and XP pro
and another compaq 1600 server running novell on the same net...

any suggestions greatly appreciated.

thanks,

john
3 REPLIES
Terry Hutchings
Honored Contributor

Re: compaq ML350 G2 server hangs and unexpectedly restarts

Even if this were a thermal issue, there would be an error logged in the event viewer concerning this.

Is the server ASRing when the machine locks up? What hardware is installed in this server? I would say this could be caused by a problem with a processor or ppm.
The truth is out there, but I forgot the URL..
john cerbus
Occasional Visitor

Re: compaq ML350 G2 server hangs and unexpectedly restarts

only hardware is orig NIC
smart array 532 controller
4 drives
original video (on NIC)
(single card w/ NIC and video?)

256 MB RAM

no addtl hardware...

when it hangs it never reaches the point where it shuts down automatically
it will stay permanently
despite ASR bios set for 10 min etc. til restart...

Terry Hutchings
Honored Contributor

Re: compaq ML350 G2 server hangs and unexpectedly restarts

If possible I would recommend pulling the Remote Insight Board (single card w/ NIC and video) to see if the same issue happens without it installed.

This machine has one processor installed? If the RIB can be ruled out, then I would say it's likely a processor problem.
The truth is out there, but I forgot the URL..