ProLiant Servers (ML,DL,SL)
1850850 Members
2939 Online
104056 Solutions
New Discussion

ProLiant DL380 - Server Stops on Boot

 
Tiago Frontoura
New Member

ProLiant DL380 - Server Stops on Boot

I have a ProLiant DL380 server that stoped before entering windows server.
It shows 3 error messages: 1727, 1770, 1720, all related to one of the disks.
I've made the test of unplugging all of the disks and plugging one at a time, but the server stops, even not plugging the "dead" disk.
I'm suspecting that the RAID controller has a problem, but I would like your opinion.
For any addicional information, don't hesitate to ask.

4 REPLIES 4
Johan Guldmyr
Honored Contributor

Re: ProLiant DL380 - Server Stops on Boot

Hi!

What kind of RAID controller do you have?
The meaning of the errors can be found in this guide: "HP ProLiant Servers Troubleshooting Guide"

1720 - Hard drive detects imminent failure
1727 - Drives changed
1770 - Upgrade Firmware.

So. I would guess you have a broken disk and that you should upgrade the firmware.

What you can do is to try to boot on the smartstart CD and look in ACU what is going on.
The ADU on the smartstart CD might also give you some useful information.
Tiago Frontoura
New Member

Re: ProLiant DL380 - Server Stops on Boot

I may buy the smartstart CD. Thanks for the tip.
But, I've made the test of removing all disks and plugging each one at a time, and sometimes it stops with only 3 disks plugged, and none of these 3 disks is the dead one.
That's why I suspect that the problem is from the RAID controller.

Johan Guldmyr
Honored Contributor

Re: ProLiant DL380 - Server Stops on Boot

Does it stop after all the disks have been initialized? Are you sure it just doesn't boot because the raid/data is pooched?

The smartstart CD is free. Can be found in the download section of hp.com.
Michael A. McKenney
Respected Contributor

Re: ProLiant DL380 - Server Stops on Boot

Go into your RAID configuration setup. it should report which disk is bad. It could be your firmware needs to be upgraded to clear the error. Try upgrading the firmware on the controller and drives first.