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
Unit Details page
www.3ware.com 191
about a RAID 5 unit made up of three subunits, each of which contains one
drive, will include details about the unit and each subunit, as shown in
Figure 91. However, if the unit is a Single Disk, only information about one
disk will be shown.
Details on this page may include all or some of the following information
described below.
To see details about a particular drive, click the Port #. You’ll see a list of all
drives, with the drive you selected highlighted.
Status. The operational status of the unit or subunit: OK, Rebuilding,
Migrating, Initializing, Verifying, Degraded, or Inoperable (missing drives).
When a unit is Rebuilding, Initializing, or Verifying, the percentage (%)
complete is also shown. For status definitions, see “Unit Statuses” on
page 135.
Capacity. The total capacity of the unit (capacities of subunits are not shown).
Type. The type of unit or subunit. RAID 0, RAID 1, RAID 5, RAID 6, RAID
10, RAID 50, Single Disk, Spare, JBOD, or Disk
Volumes. Displays the number of volumes in a unit. This is usually 1. If you
created a boot volume on this unit, or if you have a unit on which you have
enabled the auto-carving policy, you will see the number of volumes into
which the unit has been divided. For more information, see “Using Auto-
Carving for Multi LUN Support” on page 86.
Stripe. The stripe size of the unit, if applicable.
Subunits. If the unit has subunits, details of the subunits are shown.
Port #. If the Type is Disk, Single Disk, JBOD, or Spare, the port to which the
drive is connected is shown. For multiple drive units, the port numbers are
shown in the subunits section. The port number is a link to the Drive
Information page.
Note: If an asterisk (*) appears next to the status of a subunit, there is an error on
one of the drives in the subunit. This feature provides a diagnostic capability for
potential problem drives. The error may not be a repeated error, and may be
caused by an ECC error, SMART failure, or a device error. Rescanning the
controller will clear the drive error status if the condition no longer exists.