Avago Technologies 3ware 9650SE-12ML (Channel) - Manual (Page 290)

Troubleshooting
278 3ware SAS/SATA RAID Software User Guide, Version 9.5.1
See Also
For information on scheduling a verify process, see “Scheduling Background
Tasks” on page 173. For information on verification of a unit, see “About
Verification” on page 162.
002A Verify failed
Event Type
Error
Cause
Verification of a unit has terminated with an error. For each RAID level being
verified, this may mean:
• Single and Spare. A single drive returned an error, possibly because of a
media defect.
• RAID 0. A single drive returned an error, possibly because of a media
defect.
• RAID 1 and 10. One side of the mirror does not equal the other side.
• RAID 5, 6, and 50. The parity data does not equal the user data.
For any RAID type, the most likely cause of the error is a grown defect in the
drive. For out-of-synchronization mirrors or parity, the error could be caused
by improper shutdown of the unit. This possibility applies to RAID 1, 5, 6, 10,
and 50.
Action
When a verify fails, redundant units will automatically resynchronize user
data through a background initialization. The initialize will not erase user
data, but will recalculate and rewrite user parity data.
If the unit was non-redundant, any data in the error location is lost. (However,
the error could be in a part of the drive that did not contain data.) A unit file
system check is recommended.
Under Windows, right-click on your drive icon and choose Properties>
Tools> Check Now .
Under Linux or FreeBSD use fsck /dev/sda1 . If you have more than one
SATA device, substitute the correct drive letter and partition number, such as
sdb2, for sda1.
The resynchronization of data that takes place during a background
initialization can slow down access to the unit. Once initialization has begun,
it cannot be canceled. You can pause it, however, by scheduling it to take