> Frank,
>
> you may want to go to the Virtual Disk and do a "check consistency".
> This compares the data from one physical disk to the other (raid1) and
> corrects any bad blocks.
>
Thanks Paul.
The test is still going on. We've got one failed result - 'The Check
Consistency found inconsistent parity data. Data redundancy may be lost.:
Virtual Disk 0 (web) Controller 0 (PERC 5/i Integrated)'
The related log is as following,
10/18/10 23:45:52: EVT#05238-10/18/10 23:45:52: 66=Consistency Check
started on VD 00/0
...
10/18/10 23:57:55: EVT#05279-10/18/10 23:57:55: 65=Consistency Check
progress on VD 00/0 is 10.19%(723s)
10/18/10 23:58:36: DEV_REC:Medium Error DevId[3] Tgt 3 retires=0
10/18/10 23:58:36: ErrLBAOffset (1b) LBA(17a7e200) BadLba=17a7e21b
10/18/10 23:58:36: DIO with no cache command. returning RDM_STATUS_FAILURE
with CRB set to -3
10/18/10 23:58:36: EVT#05280-10/18/10 23:58:36: 113=Unexpected sense: PD
03(e1/s3), CDB: 28 00 17 a7 e2 00 00 00 6d 00, Sense: f0 00 03 17 a7 e2 1b
0a 00 00 00 00 11 00 00 00 00 0
10/18/10 23:58:37: Retrying cmdId a5
10/18/10 23:58:39: DEV_REC:Medium Error DevId[3] Tgt 3 retires=0
10/18/10 23:58:39: ErrLBAOffset (1b) LBA(17a7e200) BadLba=17a7e21b
10/18/10 23:58:39: EVT#05281-10/18/10 23:58:39: 113=Unexpected sense: PD
03(e1/s3), CDB: 28 00 17 a7 e2 00 00 00 6d 00, Sense: f0 00 03 17 a7 e2 1b
0a 00 00 00 00 11 00 00 00 00 0
10/18/10 23:58:40: Issuing write verify pd=03, arm=3, span=0, blk=17a7e21b
10/18/10 23:58:40: EVT#05282-10/18/10 23:58:40: 110=Corrected medium error
during recovery on PD 03(e1/s3) at 17a7e21b
...
Even the medium error was corrected by the RAID. I guess it's probably
better to replace it. I don't understand why there's no alert email by
OMSA and the VD was marked ready.
_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
