Filter
Top Products
Error and Notification Messages
www.3ware.com 123
0027 DCB checksum error detected
The 3ware RAID controller stores certain configuration parameters on a
reserved area of each disk drive called the Drive Configuration Block (DCB).
As part of power-on initialization, the 3ware RAID controller performs a
checksum of the DCB area to ensure consistency. If this error occurs, please
contact 3ware technical support. The drive’s DCB has been corrupted.
0028 DCB version unsupported
During the evolution of the 3ware product line, the format of the DCB has
been changed to accommodate new features. The DCB format expected by
the 3ware RAID controller and the DCB that is written on the drive must be
compatible. If a unit that was created on a very old 3ware product is
connected to a newer 3ware RAID controller, this message is posted and the
3ware RAID controller rejects the drive. Please contact 3ware technical
support if this event occurs.
0029 Verify started
The 3ware RAID controller allows you to verify data integrity on a unit.The
verification functions for different RAID levels are as follows:
• Single and Spare. Verify = Media Scan
• RAID 0. Verify = Media Scan
• RAID 1. Verify = Compare of Mirror Sides
• RAID 10. Verify = Compare of Mirror Sides
• RAID 5. Verify = Compare of Parity Data with User Data
For information on scheduling verifications, see “Scheduling Background
Tasks” on page 76
002A Verify failed
This message indicates that the data integrity verification function (see
message 0029) 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. One side of the mirror does not equal the other side.
• RAID 10. One side of the mirror does not equal the other side.
• RAID 5. 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