User guide
Table Of Contents
- Title Page
- Table of Contents
- About this User Guide
- Introducing the 3ware® SATA RAID Controller
- Getting Started with Your 3ware RAID Controller
- First-Time RAID Configuration Using 3BM
- Driver Installation
- Driver Installation Under Windows
- Driver Installation Under Linux
- Obtaining 3ware Linux Drivers
- Driver Installation Under Red Hat Linux or Fedora Core 5
- Materials required
- Creating a Red Hat Linux Driver Diskette
- Installing the 3ware Kernel Driver Module while Installing Red Hat Linux on a New Unit
- Installing the 3ware Kernel Driver Module on a Red Hat or Fedora Core Linux System that Boots From a Different Device
- About Variables In the Kernel Driver Module Installation Instructions
- Driver Installation Under SuSE Linux
- Compiling a 3ware Driver for Linux
- Driver Installation Under FreeBSD
- 3ware BIOS Manager 2 (3BM 2) Introduction
- 3DM 2 (3ware Disk Manager) Introduction
- Configuring Your Controller
- Configuring Units
- Configuring a New Unit
- Creating a Hot Spare
- Naming a Unit
- Setting Unit Policies
- Changing An Existing Configuration by Migrating
- Deleting a Unit
- Removing a Unit
- Moving a Unit from One Controller to Another
- Adding a Drive
- Removing a Drive
- Rescanning the Controller
- Maintaining Units
- Checking Unit and Drive Status through 3DM
- About Degraded Units
- About Inoperable Units
- Alarms, Errors, and Other Events
- Background Tasks
- Scheduling Background Tasks
- Locating a Drive by Blinking Its LED
- Maintaining Your Controller
- Determining the Current Version of Your 3ware Driver
- Updating the Firmware and Driver
- Downloading the Driver and Firmware
- Updating the Firmware Through 3DM 2
- Updating the 3ware Driver and Firmware Under Windows
- Using the Update Utility With Multiple Controllers
- Updating the 3ware Driver Under Windows XP
- Updating the 3ware Driver Under Red Hat or Fedora Core
- Updating the 3ware Driver Under SuSE
- Updating the 3ware Driver Under FreeBSD
- Updating the Firmware Under Linux and FreeBSD
- Viewing Battery Information
- Testing Battery Capacity
- 3DM 2 Reference
- Troubleshooting
- Appendices
- Index
Error and Notification Messages
www.3ware.com 241
0029 Verify started
Event Type
Information
Cause
The 3ware RAID controller has started verifying the data integrity of a unit.
The verification functions for different RAID levels are as follows:
•
Single, JBOD, and Spare. Verify = Media scan
•
RAID 0. Verify = Media scan
•
RAID 1 and 10. Verify = Comparison of mirror sides
•
RAID 5, 6, and 50. Verify = Comparison of parity data with user data
Action
Allow verify to complete to identify any possible data integrity issues.
See Also
For information on scheduling a verify process, see “Scheduling Background
Tasks” on page 156. For information on verification of a unit, see “About
Verification” on page 146.
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, JBOD, 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.