REBOOTING AND LOCKING UP.

[Ayman Altounji]

ProLiant 3000
This server will reboot at random and sometimes it will lockup.The OS IS WINNT 4.0 and it has the newest bios upgrade,Does anybody know how to fix this problem?
Thanks,Ben

[Ayman Altounji]

Ben,
Have you run the latest SSD? This should update all your drivers, and at least eliminate that as a potential cause...It's on the Smartstart CD if you've got one...directory is \cpqsupsw\ntssd\ and just run setup..

Stephen

[Ayman Altounji]

We are running the latest ssd and rompaqs and it hangs at least 3 times per week

[Ayman Altounji]

I too have a customer with a Proliant 3000 which blue screens 2-3 times/day. I have replaced system board, all memory, and installed new hard drives (we needed faster drives). The system has dual 600 MHz processors, and is running NT4 with SP6a.

It got so bad, we reformatted the Hard drives (Raid 5) and installed a fresh copy of NT4.

System reboots (everyday) even when idle.

[Ayman Altounji]

Ben,
What does Insight Manager say? Is there something either there or in the Event Viewer that mentions a SysManagement driver (sysmgmt.sys)? Or are there other mentions in either one of those of other errors that seem unusual?

[Ayman Altounji]

Parrothead,
Two things I would check in regards to yours: First, I'd open the case and recheck every interlock on it (three I think). Second, have you tried swapping the power supply? If it's getting insufficient voltage that might cause the rebooting...

[Ayman Altounji]

I have not replaced the Power supply or the raid controller.

There was another message posted to the NT forum from Compaq that said to verify the Raid controller had the latest firmware. Have you heard of either bad power supplys or bad firmware on the array controllers (I think we have a 4200 array)

Mark

[Ayman Altounji]

Mark,
A weak power supply could cause the reboots, but a 'defective' firmware could too. If you don't have the latest rev on the controller, try updating--likewise if it is the latest, you might try going back to the previous version.

Oh, and for the record, I incorrectely responded to your name (Parrot vs. Parrothead)...Must be the Jimmy Buffet influence... :)

Stephen

[Ayman Altounji]

Stevepaq:
Thanks for your thoughts. I have considered replacing the P/S, however the system ran fine for 2 weeks in our technical shop (we ran anti-virus software, and did web updates... and no crashes). Then the first day server is delivered to customer site, whamo! Crash city (yes it was connected to a UPS).

I will verify the rompaq on the 4200 array controller.

Thanks again.

[Ayman Altounji]

Mark,
Something you just said--UPS--might be the culprit after all...Are you running the power management software that came with it?? I remember working at a site in Atlanta and it was the UPS power management software that caused the system to reboot every two hours or so...My suggestion if you haven't already tried it--unload the power mgmt software even for just a day and see if that helps....Kinda like eliminating the outside influences, so to speak.....Good luck!! Stephen

[Ayman Altounji]

Stevepaq:

Thanks for the thought. No we are not running any power/UPS software. Actually we did install Arcserve 6.6 (single server) and that is the ONLY software installed other than NT 4.0 and SP6a.

I have yet to check Computer Ass. web site, for issues, but I have run Arcserve for years without blue-screen issues.

Could it be a bad power supply?

Mark

[Ayman Altounji]

For intermittent lockup problems, you need to download and run the Compaq server diagnostics. Run the Compaq Inspect report. Print out this report and check the server health log. See if any errors were logged at the time of the lockups. This will normally indicate the hardware that is causing the problem. If nothing is logged, you may have an overheating processor or failing memory. When you have a processor hang or system lock due to a memory problem, the processor cannot log any error that occurred with the system. You can perform the processor and memory tests in a loop to see if you can cause the failure. Download and make the Compaq diagnostic program disk from this web address.

http://www5.compaq.com/support/files/server/us/download/9524.html