Software User Guide for Windows*

RAID Features
10 Intel
®
RSTe for Microsoft Windows* OS Software User’s Guide
2.5.17 Verify and Repair
Intel
®
RSTe provides support for Verify and Repair.
The RAID volume data verification process identifies any inconsistencies or bad data on a RAID 0, RAID
1, RAID 5, or RAID 10 volume.
The RAID volume data verification and repair process identifies and repairs any inconsistencies or bad data
on a RAID 1, RAID 5, or RAID 10 volume.
The following table describes what occurs for each RAID level.
Table 1. Verify and Repair
RAID Level
Verify
Verify and Repair
RAID 0
Bad blocks are
identified.
N/A
RAID 1
Bad blocks are
identified.
Bad blocks are reassigned.
Data on the mirror
drive is compared to
data on the source
drive.
If the data on the mirror drive does not match the data on the
source drive, the data on the mirror is overwritten with the
data on the source.
RAID 5
Bad blocks are
identified.
Bad blocks are reassigned.
Parity is recalculated
and compared to the
stored parity for that
stripe.
If the newly calculated parity does not match the stored parity,
the stored parity is overwritten with the newly calculated
parity.
RAID 10
Bad blocks are
identified.
Bad blocks are reassigned.
Data on the mirror is
compared to data on
the source.
If the data on the mirror does not match the data on the
source, the data on the mirror is overwritten with the data on
the source.
2.5.18 Check Pointing
Intel
®
RSTe provides the ability to perform Check Pointing to be able to track forward progress on read
patrol, array rebuilds, and volume migration if interrupts occur. After resuming, the operation will restart
from the last valid stage reached.
2.5.19 Bad Block Management
Intel
®
RSTe provides support for Bad Block Management.
In the course of rebuilding a degraded RAID volume, where one of the member disks has failed or been
removed, and is being replaced by a spare drive, the redundant contents of the other drives are read and
then used to reconstruct data to be written to the spare drive. In case a read failure occurs sometime during
this rebuild process, the data to be written to the spare will not be available and therefore lost. In this
scenario, rather than mark the entire RAID volume as failed, we can mark only those sectors on the spare
that are known to have indeterminate data, in a log of such bad sectors. This bad block management log can
be used to reflect error status whenever any attempts are made to access those sectors of the spare.