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
3ware Tools for Configuration and Management
www.3ware.com 13
Support for Over 2 Terabytes
Windows 2000, Windows XP (32-bit), Linux 2.4, and FreeBSD 4.x, do not
currently recognize unit capacity in excess of 2 TB.
If the combined capacity of the drives to be connected to a unit exceeds 2
Terabytes (TB), you can enable auto-carving when you configure your units.
Auto-carving divides the available unit capacity into multiple chunks of 2 TB
or smaller that can be addressed by the operating systems as separate
volumes. The carve size is adjustable from 1024 MB to 2048 MB (default)
prior to unit creation.
If a unit over 2 TB was created prior to enabling the auto-carve option, its
capacity visible to the operating system will still be 2TB; no additional
capacity will be registered. To change this, the unit has to be recreated.
For more information, see “Using Auto-Carving for Multi LUN Support” on
page 86.
3ware Tools for Configuration and
Management
3ware software tools let you easily configure the drives attached to your
3ware RAID controller, specifying which drives should be used together as a
RAID unit and the type of RAID configuration you want, and designating hot
spares for use if a drive degrades.
3ware provides the following tools for use in configuring and managing units
attached to the 3ware controller:
• 3BM (3ware BIOS Manager)
3BM is a BIOS level tool for creating, deleting, and maintaining disk
arrays, rebuilding arrays, designating hot spares, and setting controller
policies. 3BM is the tool most frequently used to configure units
immediately after installation of the controller, but can also be used after
installation to maintain the controller and associated drives.
For general information about working with 3BM, seeChapter 5, “3ware
BIOS Manager 2 (3BM 2) Introduction.”
• 3DM 2 (3ware Disk Manager)
3DM is a daemon (under Linux and FreeBSD) and a service (under
Windows) which runs in the background on the controller’s host system,
and can be accessed through a web browser to provide ongoing
monitoring and administration of the controller and associated drives. It
can be used locally (on the system that contains the 9000) or remotely (on
a system connected via a network to the system containing the 9000).