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

ML350 G4 "Ready for Rebuild" SA 641

 
Graeme Bray
Regular Advisor

ML350 G4 "Ready for Rebuild" SA 641

Hello all,

I have a ML350 G4 that has a SA 641 that is stuck in "Ready for Rebuild." The server has 3 logical drives and one has rebuilt already. The other two are just sitting in a "Ready for Rebuild" status.

I've attached the ADU report.
4 REPLIES
cnb
Honored Contributor

Re: ML350 G4 "Ready for Rebuild" SA 641

Hi Graeme,

Replace drive 1:0. Both Logical drives are affected by this drive which failed due to a timeout and read failures.

You could try to reseat it but it may not recover/rebuild. The firmware it's at (HPB9) is supposed to address timeout and recovery issues, so it doesn't appear to be a firmware revision issue.

....
Physical Drive 1:0 Informational

Active Spare Map 0x00000000
Spare Status 0x00
Spare To Replace Map All Zeroes (32 x [0x00])
Replaced Marked OK Map 0x00000000
Media Exchanged Media Exchange Ready Status
-------------------- -------------
False Informational

Cache Failure Failed From Cache Data Loss Status
--------------------------- -------------
False Informational

Expand Failure Success (0x00)
Unit Flags Unit Flags Status
------------------------------- --------
Rebuild Aborted From Read Error Critical

....

Rgds,

Graeme Bray
Regular Advisor

Re: ML350 G4 "Ready for Rebuild" SA 641

So the new drive that HP just installed we should try to reseat?

My only issue is the below entry in the event log:

Event Type: Warning
Event Source: CPQCISSE
Event Category: None
Event ID: 24603
Date: 4/20/2010
Time: 8:06:02 AM
User: N/A
Computer: F11STVCMD1
Description:
Recovery of logical drive 3, configured on
Array Controller in slot 4, was aborted while rebuilding physical drive with DEVICE ID 0 on Port 1 due to an unrecoverable read error. The physical drive reporting the error is DEVICE ID 2 on Port 1.
Data:
0000: 00 00 00 00 07 00 52 00 ......R.
0008: 00 00 00 00 1b 60 35 84 .....`5Â
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
cnb
Honored Contributor

Re: ML350 G4 "Ready for Rebuild" SA 641

Indeed. Since you provided more information and a more closer look indicates a couple of issues:

Drive 1:0 Timeout, but more interesting is the Last Failure Reason and READ ERRORS HARD on 1:2.

Smart Array 641 in slot 4 : Storage Enclosure 1 : Drive Cage on Port J1 : Physical Drive 1:0 : Physical Drive Status

SCSI Bus 0 (0x00)
SCSIID 0 (0x00)
Block Size 512 Bytes Per Block (0x0200)
Total Blocks 67.8 GB (0x087aa6c0)
Reserved Blocks 0x00000440
Drive Model COMPAQ BF0728B26A
Drive Serial Number 3LQ4M9GA0000902661Q5
Drive Firmware Revision HPB9
SCSI Inquiry Bits 0x32
Compaq Drive Stamped Stamped For Monitoring (0x01)
Last Failure Reason Timeout (0x07)
Device Flags Device Flag Status

----

Smart Array 641 in slot 4 : Storage Enclosure 1 : Drive Cage on Port J1 : Physical Drive 1:2 : Physical Drive Status

SCSI Bus 0 (0x00)
SCSIID 2 (0x02)
Block Size 512 Bytes Per Block (0x0200)
Total Blocks 67.8 GB (0x087aa6c0)
Reserved Blocks 0x00000440
Drive Model COMPAQ BF07288576
Drive Serial Number ANA1P5301Y060510
Drive Firmware Revision HPB2
SCSI Inquiry Bits 0x3a
Compaq Drive Stamped Stamped For Monitoring (0x01)
Last Failure Reason No Failure (0x00)

-----
Smart Array 641 in slot 4 : Storage Enclosure 1 : Drive Cage on Port J1 : Physical Drive 1:2 : Monitor and Performance Statistics (Since Factory)

Serial Number ANA1P5301Y060510
Firmware Revision HPB2
Product Revision COMPAQ BF07288576
Reference Time 0x00281fbc
Sectors Read 0x0000001b66a6a0de
Read Errors Hard 0x00000244
Read Errors Retry Recovered 0x00000119

Since ID 2 is being reported as the offender by the driver, start with 1:2.

If HP replaced 1:0, then I'm curious as to why they didn't replace/check 1:2?

Anyway, HTH.

Rgds,

cnb
Honored Contributor

Re: ML350 G4 "Ready for Rebuild" SA 641

IMHO:

I would have expected them to use the same drive type as the other existing members.


Normally not an issue, but different geometry drives mixed in an array can occasionally come into play during recovery issues.

Rgds,