Consistency check, Drive 0 failed?

Frank C. frankc at ultraonline.net
Fri Aug 24 10:47:55 CDT 2007


Ok, so I was in Openmanage and decided it would be a good idea to do a 
consistency check on my vdisk.  Good idea?  I dunno, you tell me, I'm a 
raid n00b.

Not 10 seconds after I started the check, Drive 0 failed, hotspare is 
building, here is my /var/log/messages in relation:

Aug 24 10:26:02 box1 Server Administrator: Storage Service EventID: 
2058  Virtual disk Check Consistency started:  Virtual Disk 0 (vdu) 
Controller 0 (PERC 5/i Integrated)
Aug 24 10:26:08 box1 Server Administrator: Storage Service EventID: 
2095  SCSI sense data Sense key:  B Sense code:  0 Sense qualifier:  0:  
Physical Disk 0:0:0 Controller 0, Connector 0
Aug 24 10:26:22 box1 last message repeated 5 times
Aug 24 10:26:22 box1 Server Administrator: Storage Service EventID: 
2346   Error occurred: Error on PD 00(e1/s0) (Error 02).:  Physical Disk 
0:0:0 Controller 0, Connector 0
Aug 24 10:26:22 box1 Server Administrator: Storage Service EventID: 
2123  Redundancy lost:  Virtual Disk 0 (vdu) Controller 0 (PERC 5/i 
Integrated)
Aug 24 10:26:22 box1 Server Administrator: Storage Service EventID: 
2057  Virtual disk degraded:  Virtual Disk 0 (vdu) Controller 0 (PERC 
5/i Integrated)
Aug 24 10:26:23 box1 Server Administrator: Storage Service EventID: 
2048  Device failed:  Physical Disk 0:0:0 Controller 0, Connector 0
Aug 24 10:26:23 box1 Server Administrator: Storage Service EventID: 
2076  Virtual disk Check Consistency failed:  Virtual Disk 0 (vdu) 
Controller 0 (PERC 5/i Integrated)
Aug 24 10:26:23 box1 Server Administrator: Storage Service EventID: 
2065  Physical disk Rebuild started:  Physical Disk 1:0:5 Controller 0, 
Connector 1
Aug 24 10:26:23 box1 Server Administrator: Storage Service EventID: 
2196  Dedicated hot spare unassigned physical disk 0:0:5:  Virtual Disk 
0 (vdu) Controller 0 (PERC 5/i Integrated)
Aug 24 10:33:28 box1 Server Administrator: Storage Service EventID: 
2251  The physical disk blink has initiated.:  Physical Disk 0:0:0 
Controller 0, Connector 0
Aug 24 10:33:35 box1 Server Administrator: Storage Service EventID: 
2252  The physical disk blink has ceased.:  Physical Disk 0:0:0 
Controller 0, Connector 0

Here is an omreport on the vdisk:

ID                        : 0:0:0
Status                    : Critical
Name                      : Physical Disk 0:0:0
State                     : Failed
Failure Predicted         : No
Progress                  : Not Applicable
Type                      : SATA
Capacity                  : 465.25 GB (499558383616 bytes)
Used RAID Disk Space      : 0.00 GB (0 bytes)
Available RAID Disk Space : 465.25 GB (499558383616 bytes)
Hot Spare                 : No
Vendor ID                 : DELL
Product ID                : WDC WD5000ABYS-01TNA0
Revision                  : 12.01C01
Serial No.                : WD-WCAPW2370103
Negotiated Speed          : Not Available
Capable Speed             : Not Available
Manufacture Day           : Not Available
Manufacture Week          : Not Available
Manufacture Year          : Not Available
SAS Address               : 1221000000000000

<snip 1-4>  Going to hotspare:

ID                        : 1:0:5
Status                    : Ok
Name                      : Physical Disk 1:0:5
State                     : Rebuilding
Failure Predicted         : No
Progress                  : 16% complete
Type                      : SATA
Capacity                  : 465.25 GB (499558383616 bytes)
Used RAID Disk Space      : 465.25 GB (499558383616 bytes)
Available RAID Disk Space : 0.00 GB (0 bytes)
Hot Spare                 : No
Vendor ID                 : DELL
Product ID                : WDC WD5000ABYS-01TNA0
Revision                  : 12.01C01
Serial No.                : WD-WCAPW2062958
Negotiated Speed          : Not Available
Capable Speed             : Not Available
Manufacture Day           : Not Available
Manufacture Week          : Not Available
Manufacture Year          : Not Available
SAS Address               : 1221000005000000


So does this mean that drive 0 is actually dead, or is this part of the 
process?  If it has really failed I can replace it, I just need to know 
that what I'm seeing isn't just a test on the drives themselves and the 
raid recovery process.

Thanks,  Frank



More information about the Linux-PowerEdge mailing list