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

Maintenance page
www.3ware.com 207
When you click Remove Unit, you will be asked to confirm that you want to
proceed. When you confirm the removal, the unit number and information
will be removed from 3DM. (Units created in the future can reclaim this unit
number.)
The operating system is notified that the unit was removed. In Linux the
device node associated with this unit is removed. In Windows the Device
Manager will reflect the changes under the disk drives icon.
Information about the unit remains intact on the drives. This allows the drive
or drives to be reassembled into a unit again on this controller, or if moved to
another controller.
Delete Unit. Deletes the selected unit and allows you to use the drives to
create another unit. The drives appear in the list of Available Drives.
Caution: Before you click Remove Unit, make sure the unit you are removing is
unmounted and the system is not accessing it. (For example, make sure you are
not copying files to the unit, and make sure that there are no applications with open
files on that unit.)
If a unit is not unmounted and you remove it, it is the equivalent of physically
yanking a hard drive out from under the operating system. You could lose data, the
system could hang, or the controller could reset.
To unmount a unit under windows, use Administrative Tools > Computer
Management > Disk Management. In the Computer Management window, right-
click on the partition and Remove the logical drive letter associated with the unit.
To unmount a unit under Linux, unmount the mount point to where the RAID unit is
mounted. For example, if you want to remove unit 0 and you know that 0
corresponds to /dev/sdb, you should unmount all partitions for sdbx (where x is the
number of the partition).
umount /dev/sdbx
For FreeBSD, the command would be
umount /dev/twedx
Warning: Physically removing drives which are not in hotswap carriers can result
in a system hang or may even damage the system and the drive.










