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
Chapter 10. Maintaining Your Controller
164 3ware Serial ATA RAID Controller User Guide
If you have a 2.6 kernel without sysfs, type the following command:
dmesg | grep 3w
(dmesg can also be used with earlier kernel versions.)
• Under Windows, you can follow the first 5 steps under “Updating the
3ware Driver Under Windows XP” on page 172.
Updating the Firmware and Driver
This chapter details several ways to update the firmware and driver for the
3ware RAID controller, depending upon operating system.
Before starting the update of either driver or firmware, you will want to make
sure you have the latest files. For details, see “Downloading the Driver and
Firmware” on page 165.
To update the firmware
• All operating systems can do so through 3DM. For details, see “Updating
the Firmware Through 3DM 2” on page 166.
• All operating systems can do so through CLI. For details, see 3ware
Serial ATA RAID Controller CLI Guide.
• Windows users can update the firmware along with the driver by using the
Update Utility. For more information, see “Updating the 3ware Driver
and Firmware Under Windows” on page 167.
• Linux and FreeBSD users can use a command-line utility. For details, see
“Updating the Firmware Under Linux and FreeBSD” on page 182.
To update the driver
• Windows users can update the driver along with the firmware by using the
3ware Update Utility. For more information, see “Updating the 3ware
Driver and Firmware Under Windows” on page 167.
• Windows users can also update only the driver through Windows Device
Manager. For details, see “Updating the 3ware Driver Under Windows
XP” on page 172.
• Linux and FreeBSD users can update the driver at the command line. For
details see:
• Updating the 3ware Driver Under Red Hat or Fedora Core
• Updating the 3ware Driver Under SuSE
• Updating the 3ware Driver Under FreeBSD
Note: It is a good idea to back up your data before updating the firmware. Updating
the firmware can render the device driver and/or management tools incompatible. It
is also recommended to have a copy of the current firmware image for rollbacks.