topic Re: 1786 Drive Array automatic recovery Needed in ProLiant Servers (ML,DL,SL)

1786 Drive Array automatic recovery Needed

becky77 — Mon, 08 Sep 2008 15:16:49 GMT

Hello,

We lost a drive on our ML350 server and a new 36 gig drive was put in on Friday. 3 days later we are still seeing 1786 Drive Array automatic recovery Needed

Launching Array diagnostic utility displays the following but there doesn't seem to be a way to force a recovery here.
Logical drive 1 status = Ready for recovery

HP Array utility displays Waiting for Rebuild however you can't see the physical grouping of drives. They all display in a single raid 5 configuration.

Server is not under Warranty and sort of at a loss to get this thing backup. thanks

Re: 1786 Drive Array automatic recovery Needed

KarloChacon — Mon, 08 Sep 2008 22:16:21 GMT

hi

ml350 generation? g1? g2? ...?

would you mind uploading an array diagnostic utility report here?

regards

Re: 1786 Drive Array automatic recovery Needed

becky77 — Tue, 09 Sep 2008 16:02:10 GMT

ok put in a new 36.4 drive, updated the firmware and rebooted the server and the attached is the information from the Array diagnostics - all 6 drives are configured as one array but 2 of the drives are 10 K and the other 3 are 15 K. Is this a problem? Shouldn't all drives be the same speed? Also the event logs list this as an event - my concern is that even after waiting a day or so we will still see this in the event logs Someone replaced the drive already and we appear to be waiting and waiting which is why I decided to update the server today with a new drive. The drives are only 36 gig. - thanks

Event Type: Warning
Event Source: Storage Agents
Event Category: Events
Event ID: 1200
Date: 9/9/2008
Time: 12:17:22 PM
User: N/A
Computer: servername
Description:
Drive Array Logical Drive Status Change. Logical drive number 1 on the array controller in Slot 3 has a new status of 6.
(Logical Drive status values: 1=other, 2=ok, 3=failed, 4=unconfigured, 5=recovering, 6=readyForRebuild, 7=rebuilding, 8=wrongDrive, 9=badConnect, 10=overheating, 11=shutdown, 12=expanding, 13=notAvailable, 14=queuedForExpansion)
[SNMP TRAP: 3034 in CPQIDA.MIB]
Data:
0000: 1a 00 06 03 00 01 05 06 ........
0008: 0f 00 00 00 00 00 00 00 ........
0010: 03 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........