01-11-2008 03:44 PM
For no apparent reason the ML350 locked up yesterday and kicked all the users off the network.
Upon arrival I found the machine in limbo, nothing but a hard reboot was possible.
Upon restart the machine hangs on "Applying Computer Settings"
Managed to get it rebooted in safe mode, the event log shows no error applicable for this. Ofcourse there were plenty of errors due to booting in safe mode but nothing logged for the time the server locked up.
Item we have tried so far include:
Chfdsk - Worked fine no errors
Updated to latest NIC, Raid Controller drivers
Tried disabling plenty of services and booting but no luck
I have read plenty of articles on the web wich suggests it might be the NIC driver or APC Software, We do not have any APC software.
I have just tried accessing the server after leaving it sit on Applying Computer Settings overnight in the hope it might just take time, however still no change after 10 hours of sitting.
Any suggestions would be helpfull as ther is allot fo work involved if this machine can't be fixed.
Regards and thank you in advance
Solved! Go to Solution.
01-11-2008 08:48 PM
I suppose it is W2003 SP2?}
does the server have proliant support pack installed? if so which version?
- remove network cables
- reboot server
- wait for Windows log in
- plug network cables
- reboot again if the issue continues install this NIC driver version
01-11-2008 10:27 PM
Yes it is a 2003 sp2 and we tried you suggestion with the cable and have this driver.
This is why it is so frustrating, there is no evidence or reasoning as to why it doesn't boot.
Someone mentioned in these forums about a offline diag tool. Is this available anywhere for download that you may know?
01-11-2008 10:48 PM
I did not understand very well what you said above
you passed Applying settings or not?
you say you have that driver I mean that version(it is an old one)?
what about proliant support pack?
I would not say this But I'm not a fan (big fan) at the diagnostic tool I mean the one that test HW apart from faulty HDDs and memories I've never found that tool discovering something else (well this is my case)
if you what to try download smartstart cd and go to maintain server and test.
01-11-2008 11:07 PM
We have updated the NIC to 18.104.22.168 and still the same problem.
Support pack I am not sure of at this stage but I am about ot go onsite again to attempt further diag.
01-12-2008 05:32 AM
01-12-2008 08:36 AM
well Mi6t0 I think that was done in safe mofe
"Managed to get it rebooted in safe mode, the event log shows no error applicable for this."
so he apply the updates for the controller, let me ask you I suggested proliant support but how did you guess that the issue exactly was the controller?
04-23-2008 12:22 AM
I just starting the same problem with an ML350 G5. The server was running fine for months then this. Is your server ok after you updated your bios and raid driver?
01-10-2009 06:08 PM
This problem started occuring after I applied a bunch of windows updates, unfortunately, they were many, so if it was one of those updates that caused a conflict with the HP RDX service, its pretty difficult to determine which one.
At the moment I have to wait 2-4 hours to see the desktop, then I will disable both HP RDX services and reboot, if it then goes well, it has to be it.
Im running SBS 2003 32-bit on a HP ML350 G5.
01-11-2009 07:46 PM
Once there, you can trouble shoot, even put the network cable back in and use the network.
We have also seen something simlar this weeked after installing MS patches with SMS & Windows update service. I'm not sure if that is related yet.