Chapter 9. Maintaining Units
194 3ware Serial ATA RAID Controller User Guide
Cancelling a Rebuild and Restarting It with a
Different Drive
When you start a rebuild from 3BM, you cannot cancel from within the 3BM
interface. However, if you have hot-swap carriers, you can remove and
replace the drive, rescan the controller (Alt-R), and then select a new drive to
be used in the rebuild. You can also boot the operating system, launch 3DM,
and cancel a rebuild by using the
Remove Drive link on the Maintenance
page.
If you do not have hot-swap carriers and do not want to boot the operating
system and launch 3DM, you can also cancel a rebuild by powering down the
system, physically removing a drive, and installing another one that you want
to use. Then when you start 3BM, the unit will appear as degraded and you
can rebuild it, using the steps described under “Rebuilding Units through
3BM” on page 191.
Note: If you want to pause the rebuild process through 3DM, you
can do so by setting or changing the rebuild schedule on the
Scheduling page. If you set a schedule for rebuilds that does not
include the current time, the rebuild process will pause.
Verifying Units
For redundant units, verify checks the redundancy of the unit. For example it
will check parity for a RAID 5 or check data consistency for a RAID 1. If the
unit you checked is not a redundant unit, verify performs a surface scan of the
media. During verification, I/O continues normally, but with a slight
performance loss, depending on your verify rate setting. For more details
about how verification works, see “About Verification” on page 181. For
details about verify rates, see “Setting Background Task Rate” on page 183.
For 9000 series controllers, if the verify unit process determines that the
mirrored drives are not identical or the parity is not correct, the error is
corrected. For RAID 1 and 10, this involves copying the miscompared data
from the lower port(s) to the higher port(s) of the mirror. For RAID 5 this
involves recalculating and rewriting the RAID 5 parity that was incorrect.
AEN 36 (
“Verify detected and fixed data/parity mismatch”) is posted to
the Alarms page.
When this occurs for 7000/8000 series controllers, AEN 36 (
“Verify
detected and fixed data/parity mismatch”
) is logged and the entire unit is
initialized. For RAID 1 and 10, initialization involves copying the data from
the lower port(s) to the higher port(s) of the mirror. For RAID 5 this involves
recalculating and rewriting the RAID 5 parity for the entire unit. If the unit is
To Next Page
Loading...
