User Guide 3ware® Serial ATA RAID Controller Supports the 9650SE, 9590SE, and 9550SX Models PN 720-0159-00 March 2007
Copyright ©2004-2007 Applied Micro Circuits Corporation (AMCC). All rights reserved. This publication may be copied or reproduced for reference purposes only. All other purposes require the express written consent of AMCC, 215 Moffett Park Drive, Sunnyvale, CA 94089. AMCC shall not be responsible or liable for, and shall be held harmless against, any and all damages, claims, and/or disputes that arise from the copying or reproduction of this publication.
Table of Contents About this User Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii How this User Guide is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Screenshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting 3DM and Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging In to the 3DM Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the 3DM Daemon under Linux and FreeBSD . . . . . . . . . . . . . . . . . . . . . Starting the 3DM Process under Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . Viewing 3DM Remotely Using a Web Browser . . . . . . . . . . . . . . . . . . . . . . . . . . .
Moving Units from an 8000 Controller to a 9000 Controller . . . . . . . . . . . . . . . . Moving Legacy JBOD Units to a 9000 Controller . . . . . . . . . . . . . . . . . . . . . . . . Moving Units from a 9500S to a 9550SX, 9590SE, or 9650SE Controller . . . . . Adding a Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing a Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Drive Details window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Controller Settings page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarms page . . . . . . . . . . . . . . . . . .
About this User Guide This document, 3ware Serial ATA RAID Controller User Guide, provides instructions for configuring and maintaining RAID units on 3ware 9650SE, 9590SE, and 9550SX series RAID controllers. This guide assumes that you have already installed your controller and drives in your system, and set up your 3ware Sidecar, if you have one. If you have not yet done so, see the installation guide that came with your controller.
Table 1: Chapters and Appendices in this Guide viii Chapter/Appendix Description 2. Getting Started Provides a summary of the process you should follow to get started using your 3ware RAID controller. 3. First-Time RAID Configuration Using 3BM Provides step-by-step instructions for configuring RAID units if you have just installed the controller. 4. Driver Installation Describes how to install drivers for the 3ware controller if you have just installed and configured it.
Conventions Table 1: Chapters and Appendices in this Guide Chapter/Appendix Description D. Warranty, Technical Support, and Service Provides warranty information and tells you how to contact technical support. Conventions The following conventions are used through this guide: • 3BM and 3BM 2 both refer to the 3ware BIOS Manager, version 2. • 3DM and 3DM 2 both refer to the 3ware Disk Manager, version 2.
2 To launch the bookshelf at the opening page, open the 3wareHTMLBookshelf folder and double click the file index.html. Opening the file from “index.html” automatically displays a navigation panel at the left that includes a Table of Contents, Index, and Search. You can also open the bookshelf by double-clicking any other html file in the 3wareHTMLBookshelf folder. When you open an individual file, the navigation pane does not automatically open.
1 Introducing the 3ware® SATA RAID Controller AMCC 3ware RAID controllers deliver full-featured, true hardware RAID to servers and workstations. AMCC's RAID controllers offer Serial ATA (SATA) and SATA II interfaces in both low profile and full-height footprints.
Chapter 1.
System Requirements Drive Requirements Depending on the particular model, the 3ware RAID controller may be connected to two, four, eight, twelve, sixteen, or twenty-four SATA drives using the supplied interface cables. Drives must meet SATA-1 (1.5 GB/s) or SATA-2 (3.0 Gb/s) standards. A list of drives that have been tested is available at http://www.3ware.com/products/compatibility_sata2.asp Drives may be of any capacity or physical form factor.
Chapter 1. Introducing the 3ware® SATA RAID Controller • For best viewing, screen resolution should be 1024 x 768 or greater, with 16-bit color or greater. For a complete listing of features and system requirements, refer to the 3ware SATA RAID Controller datasheets, available from the website at http:// www.3ware.com/products.
Understanding RAID Concepts and Levels drives, in rotation. Should a failure occur, the data on the failed drive can be reconstructed from the data on the other drives. • Hot Swap. The process of exchanging a drive without having to shut down the system. This is useful when you need to exchange a defective drive in a redundant unit. • Array Roaming.
Chapter 1. Introducing the 3ware® SATA RAID Controller Figure 2. RAID 0 Configuration Example RAID 1 RAID 1 provides fault tolerance and a speed advantage over non-RAID disks. RAID 1 is also known as a mirrored array. Mirroring is done on pairs of drives. Mirrored disk arrays write the same data to two different drives using RAID 1 algorithms (see Figure 3). This gives your system fault tolerance by preserving the data on one drive if the other drive fails.
Understanding RAID Concepts and Levels RAID 5 is able to tolerate 1 drive failure in the unit. Figure 4. RAID 5 Configuration Example RAID 6 RAID 6 requires a 3ware 9650SE RAID controller. RAID 6 provides greater redundancy and fault tolerance than RAID 5. It is similar to RAID 5, but has two blocks of parity information (P+Q) distributed across all the drives of a unit, instead of the single block of RAID 5. Due to the two parities, a RAID 6 unit can tolerate two hard drives failing simultaneously.
Chapter 1. Introducing the 3ware® SATA RAID Controller Figure 5. RAID 6 Configuration Example RAID 10 RAID 10 is a combination of striped and mirrored arrays for fault tolerance and high performance. When drives are configured as a striped mirrored array, the disks are configured using both RAID 0 and RAID 1 techniques, thus the name RAID 10 (see Figure 6). A minimum of four drives are required to use this technique. The first two drives are mirrored as a fault tolerant array using RAID 1.
Understanding RAID Concepts and Levels Figure 6. RAID 10 Configuration Example RAID 50 RAID 50 is a combination of RAID 5 with RAID 0. This array type provides fault tolerance and high performance. RAID 50 requires a minimum of six drives. Several combinations are available with RAID 50. For example, on a 12-port controller, you can have a grouping of 3, 4, or 6 drives.
Chapter 1. Introducing the 3ware® SATA RAID Controller Figure 7. RAID 50 Configuration Example Single Disk A single drive can be configured as a unit through 3ware software. (3BM, 3DM 2, or CLI). Like disks in other RAID configurations, single disks contain 3ware Disk Control Block (DCB) information and are seen by the OS as available units.
Understanding RAID Concepts and Levels Determining What RAID Level to Use Your choice of which type of RAID unit (array) to create will depend on your needs. You may wish to maximize speed of access, total amount of storage, or redundant protection of data. Each type of RAID unit offers a different blend of these characteristics. The following table provides a brief summary of RAID type characteristics.
Chapter 1.
3ware Tools for Configuration and Management 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.
Chapter 1. Introducing the 3ware® SATA RAID Controller For details about working with 3DM, see “3DM 2 (3ware Disk Manager) Introduction” on page 66. 3DM 2 is the current version of the 3ware Disk Manager. Throughout this documentation, it is referred to interchangeably as 3DM and 3DM 2.
Monitoring, Maintenance, and Troubleshooting Features RAID 0 unit members. If the disk drive is part of a redundant unit, error locations that are found and are deemed repairable are rewritten with the redundant data. This forces the drive firmware to reallocate the error sectors accordingly. (For more information, see “About Verification” on page 146.) • Error Correction. Bad sectors can be dynamically repaired through error correction (Dynamic Sector Repair).
2 Getting Started with Your 3ware RAID Controller Setting up your 3ware RAID controller involves these main steps: • Physically Install the RAID Controller and Drives • Configure a RAID Unit • Install the Driver and Make the Operating System Aware of the New Drives • Set Up Management and Maintenance Features Once the controller and drives have been physically installed, the order in which you perform these steps depends in part on whether one of the units you configure will act as your boot drive.
installation in. Chapter 3, “First-Time RAID Configuration Using 3BM.” Additional information about configuration is also included in the later chapters of this user guide. If the operating system is already installed on another drive in your system, you can configure units through 3BM, through 3ware Disk Manager (3DM), or through the Command Line Interface (CLI).
Chapter 2. Getting Started with Your 3ware RAID Controller • “Configuring Your Controller” on page 80 • “Setting Unit Policies” on page 106 • “Setting Background Task Rate” on page 155 Initial Settings for Policies and Background Tasks The table below lists the default settings for policies and background tasks. These settings are used if you do not explicitly change the policy settings.
Table 6: Default Settings for Policies and Background Tasks Policy Default Value Where to Change Verify Task Schedules Daily, starting at 12:00 am and running for 24 hours 3DM, CLI Follow Verify Task Schedule No 3DM, CLI Rebuild Task Schedules Daily, starting at 12:00 am and running for 24 hours 3DM, CLI Follow Rebuild Task Schedule No 3DM, CLI Self-test Task Schedulesa Daily, starting at 12:00 am and running for 24 hours 3DM, CLI Follow Self-test Task Schedule Yes 3DM, CLI a.
3 First-Time RAID Configuration Using 3BM If you will install the operating system on and boot from a unit managed through the new 3ware RAID controller, follow the steps in this chapter to use the 3ware BIOS Manager (3BM) to configure the unit and install the driver. If the operating system is already installed on another drive in your system, you can use the steps below or you can configure units through 3DM or the CLI.
Basic Steps for Creating a Unit To launch 3BM 1 Power up or reboot your system. While the system is starting, watch for a screen similar to Figure 8. Figure 8. 3ware BIOS Screen ----Press to access 3ware BIOS Manager ---3ware ATA RAID Controller: 9590SE-12 BIOS: BE9X X.XX.XX.XXX Firmware: FE9X X.XX.XX.XXX BBU Status: Not Present Number of online units: 1, available drives: 0, hot spare: 0, offline units:0 Exportable Units:Π3drive 64K RAID5 SATA - Maxtor SATA - Maxtor SATA - Maxtor 2 558.
Chapter 3. First-Time RAID Configuration Using 3BM 4 If you plan to make changes to your configuration and need to backup data before continuing, press ESC and do so now. Otherwise, press any key to continue. Figure 10. Warning Message When you Start 3BM To select the drives and create a unit 1 Select the drives to be included by highlighting each one and pressing Enter to select it. When you select a drive, an asterisk appears next to it in the left-most column (see Figure 11).
Basic Steps for Creating a Unit 3 Make sure that the proper drives are listed. Figure 12. Create Disk Array Display, RAID 0 Example To name the unit and select the desired RAID configuration 1 (Optional) Press Enter in the Array Name field and type a name for the unit. Then press Enter again to accept the name. 2 Use the arrow keys or press Tab to move to the RAID Configuration field and press Enter to display the available RAID levels for the number of drives you selected. Figure 13.
Chapter 3. First-Time RAID Configuration Using 3BM Figure 14. Stripe Sizes for a RAID 5 To set other policies for the unit While creating a unit through 3BM, you can set several policies that effect the unit (Write Cache, Drive Queuing Mode, and Continue on Error When Rebuild), and you can select a StorSave profile. Each of these policies is already set to a default value, so you do not have to change them. In addition, you can change each of these policies later without affecting the configuration.
Basic Steps for Creating a Unit Note: Setting a Boot Volume Size is optional. In addition, if you specify a boot volume, you do not have to install your operating system onto it. For more information about creating a boot volume, see “Boot volume size” on page 94. If the size your array is 2TB or greater, you may also want to review the information about carving the unit into multiple volumes. For details, see “Using Auto-Carving for Multi LUN Support” on page 86.
Chapter 3. First-Time RAID Configuration Using 3BM Figure 15. Summary of Volumes to be Created To finish up and save your changes 1 If you have additional drives, you can go ahead and configure an additional RAID unit or designate a hot spare. Then continue on with these steps. (For details about hot spares, see page 28.) 2 If you configured more than one unit, and you plan to install the operating system on one of them, make that unit be the first unit (Unit 0) in the list of Exportable Units.
Basic Steps for Creating a Unit 4 Type Y to continue, delete any existing data on the drives, and create the unit. Depending on the RAID configuration you are creating, initialization of the unit may begin immediately. (RAID 6 units and some RAID 5 and RAID 50 units begin immediate initialization.) The initialization process can take several hours, depending on the size of your drives. 5 If you want to use a RAID configuration which has started initializing, you can press Esc to cancel the progress box.
Chapter 3. First-Time RAID Configuration Using 3BM Specifying a Hot Spare You can designate one of the Available Drives as a hot spare in 3BM. If a hot spare is specified and a redundant unit degrades, an event notification will be generated. The hot spare will automatically replace the failed drive without user intervention. To specify a hot spare 1 In the list of Available Drives, highlight the drive to use. 2 Type s to specify that the selected drive will be the hot spare.
Checking the Motherboard Boot Sequence Checking the Motherboard Boot Sequence Using your computer’s Setup utility, ensure that it shows the appropriate boot device. After installing the 3ware 9000 controller in your system, go into the BIOS for your computer system to check and change the boot order. This is necessary because most systems automatically change the boot order when they detect a newly installed controller and device.
4 Driver Installation This chapter provides details about how to install the driver for your 3ware RAID controller and make the units available to your operating system. This section is for PCs only, for Mac OS X, see 3ware Serial ATA RAID Controller User Guide for Mac OS X. • If the unit you have created will be your system's boot device, you install the driver for the controller as you install the operating system.
Driver Installation Under Windows Driver Installation Under Windows Note: Before installing the 3ware driver, you must have already physically installed your 3ware RAID controller in the system. Consult the installation guide that came with your controller for how to do this. You can download that guide from: http://www.3ware.com/support/userdocs.asp. The 3ware RAID controller can be used with Microsoft Windows 2000 (SP3 or newer), Windows XP (SP1 or newer), and Windows Server 2003.
Chapter 4. Driver Installation Creating a 3ware Driver Diskette If you are installing Windows on a new unit or drive managed by the 3ware RAID controller, you must create a 3ware driver diskette. To create a driver diskette 1 Insert the 3ware software CD into your system. 2 When the 3ware Menu appears, click Driver and Firmware Disks. 3 In the 3ware Driver & Firmware Images menu, click the appropriate button to create the driver diskette that you need.
Driver Installation Under Windows 6 If the “Digital Signature Not Found” message appears, click Yes to continue the installation. (If there are multiple controllers in the system, you will see this message once for each controller.) 7 Continue with the normal Windows installation at this point. There are no instructions after installing the driver that are specific to 3ware.
Chapter 4. Driver Installation Figure 18. Found New Hardware Wizard, Windows 2000 1 Click the Next button and respond to the questions the Wizard displays using the default selections. 2 When the Wizard prompts you to select a device driver, click Have Disk, and then indicate that it is on the CD or floppy. 3 If the “Digital Signature Not Found” message appears, click Yes to continue the installation. 4 When the Completing the Found New Hardware Wizard screen appears (Figure 19), click Finish.
Driver Installation Under Windows 6 When the Install Hardware Device Drivers screen appears (Figure 20), click Next and follow the prompts on the screen to install the second driver. Figure 20. Install Hardware Device Drivers 7 When the second Completing the Found New Hardware screen appears, click Finish. Figure 21. Completing Found New Hardware Wizard After the driver has been installed, continue with the instructions under “Making Units Managed by a 3ware Controller Available to Windows” on page 38.
Chapter 4. Driver Installation Figure 22. Found New Hardware Wizard, Windows XP and 2003 1 Click the Next button and respond to the questions the Wizard displays. 2 When the Wizard prompts you to select a device driver, click Have Disk, and then indicate that it is on the CD or floppy. 3 If the “Digital Signature Not Found” message appears, click Yes to continue the installation. 4 When the Completing the Found New Hardware Wizard screen appears (Figure 23), click Finish. Figure 23.
Driver Installation Under Windows Figure 24. Welcome to the Found New Hardware Wizard 7 When the second Completing the Found New Hardware screen appears, click Finish. Figure 25. Completing Found New Hardware Wizard After the driver has been installed, continue with the instructions below under “Making Units Managed by a 3ware Controller Available to Windows” on page 38. www.3ware.
Chapter 4. Driver Installation Making Units Managed by a 3ware Controller Available to Windows After the 3ware driver has been installed, you need to partition and format the new units or disks. 1 Remove the driver diskette or CD, reboot the system, and log in as the system administrator. 2 Use Disk Administrator to partition and format the new units or disks: From the Start menu, choose Administrative Tools > Computer Management. In the Computer Management window, under Storage, select Disk Management.
Driver Installation Under Linux Driver Installation Under Linux Note: Before installing the 3ware driver, you must have already installed your 3ware RAID controller in the system. Consult the installation guide that came with your controller for how to do this. You can download that guide from: http:// www.3ware.com/support/userdocs.asp A drive or unit managed by the 3ware RAID controller may be configured to be your system's boot device.
Chapter 4. Driver Installation 3ware Technical Support, or email your driver request to support1@amcc.com. For information about how to compile a driver from the 3ware driver source, see the links appended to knowledgebase article 14546 (http:// www.3ware.com/kb/article.aspx?id=14546). Obtaining 3ware Linux Drivers Obtain the 3ware driver for Linux from one of these two sources: • 3ware software CD-ROM. Compiled and tested drivers for Red Hat and SuSE Linux are included on this CD. 3ware web site.
Driver Installation Under Linux Determining the Current Version of your 3ware Driver If you already have a 3ware controller installed, you can check the current driver version, using either 3DM 2 or the CLI. (For details, see “Viewing Information About a Controller” on page 80.) You can also check it using the following method: If you have a 2.
Chapter 4. Driver Installation 3 In the 3ware Driver & Firmware Disk Images menu, click the button for the driver disk you want to create. A confirmation window opens. 4 Insert a blank diskette into a drive and click the Yes button to begin creating the driver floppy diskette. Note: If you need to create a Linux driver diskette for a Linux distribution other that what is available on the menu, see 3ware knowledgebase article 14546 http:// www.3ware.com/kb/article.
Driver Installation Under Linux c When the Welcome to Red Hat display appears, type: linux dd A number of files will load and then a message will prompt you to insert your driver install disk. 4 Install the 3ware kernel driver module, using the driver install diskette: Insert the driver install diskette containing the 3ware driver for Red Hat and press Enter. The system automatically reports: Loading 3w-9xxx 5 When prompted, select the proper language and keyboard types for your locality.
Chapter 4. Driver Installation Installing the 3ware Kernel Driver Module on a Red Hat or Fedora Core Linux System that Boots From a Different Device The steps for installing the 3ware kernel driver module vary slightly, depending on your specific installation requirements.
Driver Installation Under Linux • • • For Bigmem kernels: 3w-9xxx.big For Hugemem kernels: 3w-9xxx.hug For IA32E kernels: 3w-9xxx.i32 To install the 3ware driver and update the RAM disk 1 Log in as root and open a console window. 2 Mount the CD which contains the 3ware kernel driver module. To mount the CD, type: mount /dev/cdrom 3 and press Enter. Copy the kernel driver module: For Redhat WS4 Intel x86 and AMD, type: cp /mnt/cdrom/packages/drivers/linux/redhat/ws4_u4/x86/ 3w-9xxx.
Chapter 4. Driver Installation 7 If you are using the GRUB boot loader, skip to Step 8. If you are using the LILO boot loader, run LILO to update the boot record on disk by typing the following: /sbin/lilo The output should be similar to: Added linux * 8 Reboot. The 3ware kernel driver module will be loaded from the ram disk automatically at boot time. To install the 3ware kernel driver module and load the module manually instead of using a RAM disk 1 Log in as root and open a console window.
Driver Installation Under Linux 6 Load the kernel driver module manually. Type: modprobe sd_mod insmod 3w-9xxx You can also incorporate the insmod command into a startup script. Driver Installation Under SuSE Linux Materials required • 3ware software CD-ROM • Floppy diskette, if you need to make a driver install diskette. • SuSE Linux Installation CD-ROM/DVD (Not required if SuSE Linux is already installed on another drive.
Chapter 4. Driver Installation To get the kernel driver module If you only need the kernel driver module, you can get it in one of two ways: • Browse the 3ware CD to /packages/drivers/linux and copy the appropriate kernel driver modules for your distribution release. Or • Follow the steps above to create a driver install diskette from the menu. Extract the kernel driver module from the update.tar.gz file, using this command: tar -xzf update.tar.
Driver Installation Under Linux Note: Other modules may be listed before or after 3w-9xxx, depending on the installation. You may see entries like reiserfs, ext3 or scsi_mod. If present, leave them (ensuring there is a space between each module name), since the system needs them to boot properly. Note about variables: In the instruction below, replace with the kernel version you are using (i.e. 2.6, etc.). In addition, replace 3w-9xxx.* with the appropriate module file for your kernel.
Chapter 4. Driver Installation 5 To load the kernel driver module, type: /sbin/insmod /lib/modules//kernel/drivers/scsi/ 3w-9xxx.ko Note: If the kernel driver module installation fails, confirm that the correct driver was installed from the CD-ROM. If a driver is not available for your system, you will need to compile your own driver. For more information, see 3ware knowledgebase article 14546 http:// www.3ware.com/kb/article.aspx?id=14546.
Driver Installation Under FreeBSD Obtaining 3ware FreeBSD Drivers The 3ware software CD-ROM that came with the 3ware RAID controller includes compiled and tested kernel driver modules for FreeBSD 6.1 only, and source files for 5.x and 6.x series. To see if a more recent driver is available, please see the 3ware web site at http://www.3ware.com/support/index.asp.
Chapter 4. Driver Installation Note: The 3ware kernel driver module integrated into the FreeBSD installation CD supports 9500S controllers, but not 9550SX/9590SE/9650SE controllers. Since this driver is statically compiled with the kernel, newer drivers with the same name (twa.ko) cannot exist. A temporary driver is provided, named twa_96se.ko, which can be used to accomplish the FreeBSD installation and enable boot device support.
Driver Installation Under FreeBSD 8 At the FreeBSD boot menu, select "Escape to loader prompt.” 9 At the loader prompt, load the kernel driver module by typing load disk0:twa_96se.ko (assuming disk0 is the floppy drive) Then boot, by typing boot Now that you have installed the twa_96se.ko kernel driver module and you are up and booted into FreeBSD, the next step is to upgrade the kernel with the latest 3ware kernel driver sources.
Chapter 4. Driver Installation 3 Go to /usr/src/sys/conf/ and edit kern.pre.mk (use vi or any other editor). Below this line: INCLUDES+= -I$S/contrib/ngatm Add this line: INCLUDES+= -I$S/dev/twa Save changes. 4 Go to usr/src/sys/i386/conf or /usr/src/sys/amd64/conf, depending on whether you have a 32-bit or 64-bit version of FreeBSD 5.4 (respectively). a Edit the GENERIC file (use vi or any other editor). b Make sure Device twa # 3ware 9000 series is not commented out. c Save changes.
Driver Installation Under FreeBSD To install the 3ware kernel driver module when FreeBSD is installed on a device on the motherboard 1 Make sure the 3ware RAID controller is not installed in the system yet. 2 Install FreeBSD to a disk attached to the motherboard ATA controller. Be sure to install the full FreeBSD source. 3 Once FreeBSD is installed, power down the system and install the 3ware RAID controller. For assistance, see the installation guide that came with the controller.
Chapter 4. Driver Installation 4 cd /sys/modules/twa make 5 Comment out the entry Device twa # 3ware 9000 series in usr/src/sys/i386/conf or /usr/src/sys/amd64/conf 6 Rebuild the kernel and reboot your system. 7 Load the kernel driver module from /sys/modules/twa kldload twa.
5 3ware BIOS Manager 2 (3BM 2) Introduction This section describes the basics of using 3ware BIOS Manager 2 (3BM 2), one of the tools you can use to configure and maintain the units connected to your 3ware RAID controller.
Chapter 5. 3ware BIOS Manager 2 (3BM 2) Introduction 3 Press Alt-3 immediately to bring up the 3ware BIOS Manager (3BM). Normally your 3ware configuration remains on-screen for just a few seconds. However, if a unit has degraded, the screen indicates the problem and remains on your screen longer. 4 If you have more than one 9000-series controller in your system, a screen lists the available boards (see Figure 28). In this case, highlight the board with which you want to work and press Enter. Figure 28.
Exiting the 3BM Configuration Utility Note: If you have a combination of 7000/8000-series and 9000-series controllers in your system, the 7000/8000-series controllers are not listed on the selection screen shown in Figure 28. Instead, an additional BIOS summary will appear for the 7000/ 8000-series controller, similar to Figure 27. To access the BIOS utility for the 7000/ 8000-series board, press Alt-3 when the information for that controller appears.
Chapter 5. 3ware BIOS Manager 2 (3BM 2) Introduction Working in the 3BM Screens The main 3BM screen (Figure 30) shows the current configuration for the drives attached to your controller, and a list of any available drives. Unusable and incomplete drives are also shown. Figure 30. 3BM Main Display You will see one or more of the following sections in the main 3BM screen: • Available Drives lists any unconfigured, independent drives (JBODs) that are not associated with an array, and hot spares.
Working in the 3BM Screens listed here in other units, you must first delete them. For more information, see “Deleting a Unit” on page 120. If any of the sections are not shown, it means that there are no items of that type connected to the controller. Table 7 lists how to move around and select information in the 3BM screens. When these commands are available in 3BM, they appear at the bottom of the 3BM screen.
Chapter 5. 3ware BIOS Manager 2 (3BM 2) Introduction Table 7: Working in 3BM 2 To do this Use these keys Specify (or unspecify) a drive as a hot spare S Return to starting values for this session in the 3ware BIOS Manager F6 Note: F6 cannot bring back previous policy settings; they are saved when you exit the Policy screen.
Adjusting BIOS Loading Settings Adjusting BIOS Loading Settings 3BM 2 includes the following settings that let you customize the behavior of the BIOS for the selected controller. You can access these settings by selecting Settings > BIOS Settings from the main 3BM screen. • Power-On Self Test (POST) Display Options • BIOS Loading Options • To change BIOS settings Power-On Self Test (POST) Display Options Display Control. Specifies what level of detail to display on the start-up screen.
Chapter 5. 3ware BIOS Manager 2 (3BM 2) Introduction Note: During the boot process, you can also bypass loading of the BIOS for all controllers for one time only by pressing Alt-B. This is useful to temporarily boot from a non-3ware device without having to change the system’s boot order. To change BIOS settings 1 On the main 3BM screen, Tab to Settings and press Enter. 2 On the pop-up menu, select BIOS and press Enter. The BIOS Options Settings screen appears. Figure 31.
Displaying Controller Information Displaying Controller Information The Controller Information screen shows you details about your controller, and about the version of associated software installed on your system. To see the controller information 1 On the main 3BM screen, Tab to Information and press Enter. 2 On the pop-up menu, select Controller and press Enter. (Note that the particular versions shown in the screen shot below may not be current.) Figure 32.
6 3DM 2 (3ware Disk Manager) Introduction Note: 3DM 2 includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). 3ware Disk Manager 2 (3DM 2) allows you to manage and view the status of your 3ware RAID controllers and associated drives. There are two parts to 3DM: a process, that runs in the background on the computer where you have installed your 3ware controller, and a web application that can be used to access it.
Browser Requirements for 3DM Browser Requirements for 3DM 3DM runs in most current web browsers. Tested and supported browsers include: • Internet Explorer 5.5 and above • Mozilla Firefox • Netscape 7 and above Additional requirements: • JavaScript must be enabled • Cookies must be enabled • For best viewing, use a screen resolution of 1024 X 768 or greater, and set colors to 16 bit color or greater.
Chapter 6. 3DM 2 (3ware Disk Manager) Introduction Installing 3DM 3DM 2 can be installed from the 3ware CD that came with your 3ware RAID controller. You can also download the current version from the website at http://www.3ware.com/support/download.asp. Details about the installation are described in Appendix B, “Software Installation” on page 271. 3DM must be installed on the system in which the controller is installed.
Starting 3DM and Logging In To log in to the 3DM web application 1 Open your browser and enter the URL for your system. The default URL is http://localhost:888/ You can also replace “localhost” with the IP address of the computer that contains the 3ware controller. For example: http://:888/ Note: If you receive a page not found message, make sure you entered the URL correctly. If you did, 3DM may not be running in the background. You can start it manually.
Chapter 6. 3DM 2 (3ware Disk Manager) Introduction Note: If you close your browser, 3DM continues to run in the background on the system. Starting the 3DM Daemon under Linux and FreeBSD 3DM should start automatically after installation and upon bootup. If it does not, use the steps below to start it. To start the 3DM daemon manually 1 Login as root on the machine on which 3DM is installed. 2 Afterwards, type: /etc/init.
Working with the 3DM Screens Viewing 3DM Remotely Using a Web Browser When remote administration is enabled on the 3DM 2 Settings page, you can use 3DM to check status and administer your 3ware RAID controller from a browser on any computer, over an internet connection. You do not need to install the 3DM software on the remote computer. To connect to 3DM2 through your web browser • In the address line of your browser, enter the URL or IP of the system containing the 3ware RAID controller.
Chapter 6. 3DM 2 (3ware Disk Manager) Introduction Figure 34. 3DM Main Screen System name and operating system. Online Help Address of the system to which you are connected. Menu bar Message bar List of controllers on the system Time of last page refresh Version of 3DM The menu bar across the top of the screen gives you access to other pages in 3DM. You can move between pages by using the menu bar, or by clicking a link on the page.
Working with the 3DM Screens of unit write cache, and controller settings that affect all units managed by the controller), tasks that can be scheduled (rebuild, verify, and self-test), and maintenance of individual units. Unit configuration can also be done through the Management > Maintenance page. The Monitor menu gives you access to the Alarms page, the BBU page, and the Enclosure Summary page.
Chapter 6. 3DM 2 (3ware Disk Manager) Introduction Viewing Information About Different Controllers If you have more than one 3ware RAID controller in the system, you select the one you want to see details about from the drop-down list at the right of the menu bar. This drop-down is available on all pages that provide controller-specific features. Figure 36.
Working with the 3DM Screens Table 8: List of 3DM Pages 3DM Page Description Controller Summary page Provides basic information about each 3ware RAID controller in your system. To see this page, click Summary in the menu bar. Controller Details page Unit Information page Provides detailed information about the current controller. To see this page, choose Information > Controller Details from the menu bar.
Chapter 6. 3DM 2 (3ware Disk Manager) Introduction Table 8: List of 3DM Pages 3DM Page Description Maintenance page Lets you configure new units and make changes to existing units. To view this page, choose Management > Maintenance from the menu bar. Alarms page Shows a list of alarms, including the specific alarm message, and the exact date and time it occurred. To view this page, choose Monitor > Alarms on the menu bar.
Setting Up 3DM Preferences Setting and Changing 3DM Passwords 3DM provides different access levels for users and administrators. The Administrator access level allows the user to fully configure 3DM. The User access level allows the user to view pages within 3DM. These passwords work independently of each other. The default password for both the User and Administrator is “3ware”. Passwords are case sensitive. You can only change passwords if you are logged in as Administrator.
Chapter 6. 3DM 2 (3ware Disk Manager) Introduction • Information will send e-mails for all events • Warning will send e-mail for events with severity of Warning and Error. • Error will send e-mail for events with severity of Error only. Events are listed on the 3DM Alarms page. Event notification can be set up during 3DM installation, and can be changed on the 3DM 2 Settings page. To set up event notification 1 Click 3DM 2 Settings on the menu bar.
Setting Up 3DM Preferences To enable or disable remote access 1 Click 3DM 2 Settings on the menu bar. 2 In the Remote Access section of the 3DM 2 Settings page, select either Enabled or Disabled in the Allow Remote Connections field. The page refreshes, and a message at the top of the screen confirms that remote access has been enabled or disabled. Setting the Incoming Port # You can set the port which 3DM uses to listen for incoming messages.
7 Configuring Your Controller This section describes how to view details about the controller, check its status, and change configuration settings that affect the controller and all of the drives connected to it.
Viewing Information About a Controller Figure 37. Controller Summary Page Tip: If you are managing controllers remotely, the list of controllers is for the machine with the IP or URL you entered in the browser address bar. 2 To see more details about a particular controller, click the ID link for that controller to display the Controller Details page. Figure 38.
Chapter 7. Configuring Your Controller To see information about a controller in 3BM (BIOS) 1 Power up or reboot your system. 2 While the system is starting, watch for a screen showing information about the controller and units you want to work with. When you have more than one controller installed, information about each one will be shown, sequentially. 3 Press Alt-3 to bring up the 3ware BIOS Manager (3BM).
Viewing Controller Policies and to allow the controller to sequence the spin-up of drives. Compatible drives are sent a spin up command based on the settings specified with the policies Number of drives per spin-up and Delay between spin-up settings. These policies can only be set using 3BM or the CLI. • Number of drives per spin-up. Number of drives that will spin up at the same time when the controller is powered up, if staggered spin-up is enabled.
Chapter 7. Configuring Your Controller To view controller policies in 3DM • Choose Management > Controller Settings from the menu bar. The policies that appear under Other Controller Settings vary, depending on the controller model you are using. Figure 39.
Setting the Auto Rebuild Policy To view controller polices in 3BM You can also view and change these controller polices in 3BM, as shown in Figure 40. 1 On the main 3BM screen, Tab to Settings and press Enter. 2 On the pop-up menu, select Controller Policies and press Enter. The Policy Control screen displays. Figure 40. 3BM Policy Control Screen Setting the Auto Rebuild Policy The Auto Rebuild policy determines how the controller firmware will attempt to rebuild degraded units.
Chapter 7. Configuring Your Controller To enable Auto-Rebuild through 3BM 1 On the main 3BM screen, Tab to Settings and press Enter. 2 On the pop-up menu, select Controller Policies and press Enter. 3 On the Policy Settings page, Tab to the Auto-Rebuild field, press Enter to display the options, select Enable and press Enter again to select it. 4 Tab to OK and press Enter to select it. The policy is enabled immediately.
Using Auto-Carving for Multi LUN Support Note: Using auto-carving can have an impact on performance. The main use of auto-carving is to gain use of the full capacity in units greater than 2 TB. This is because Windows 2000, Windows 2003 (32-bit and 64-bit without SP1), Windows XP (32-bit), and FreeBSD 4.x, do not currently recognize unit capacity in excess of 2 TB. Note: Operating systems without this limitation include Linux 2.6, FreeBSD 5.
Chapter 7. Configuring Your Controller If the combined capacity of the drives exceeds the carve size, a number of volumes will be created. 3 Verify the creation of the volumes. In 3DM 2, the number of volumes is shown on the Unit Details page. 4 Verify that the volumes appear in the operating system. They will appear as additional drives. Notes: • • • • If you are configuring a unit for primary storage and it will be greater than 2 TB, be sure to enable the auto-carve policy before creating the unit.
Enabling and Setting Up Staggered Spin-up 3 On the Policy Settings page, Tab to the Carving Factor field, press Enter to display the text entry box, enter the size you want (between 1024 GB and 2048 GB) and press Enter again to accept it. 4 Tab to OK and press Enter to select it. The policy is enabled immediately. Enabling and Setting Up Staggered Spin-up You can set the number of drives that will spin up at the same time and the delay time between drive group spinups.
Chapter 7. Configuring Your Controller Exporting JBOD Disks By default, JBOD disks (unconfigured disks) connected to the 3ware RAID controller are not exported to the operating system. This means that any drives you leave unconfigured are not seen by the operating system, and cannot be used for storage. When Export JBOD Disks is set to No, you make individual disks available for use by configuring them as Single Disks.
8 Configuring Units This section includes information and procedures on configuring units attached to your 3ware RAID controller.
Chapter 8. Configuring Units Configuration Options When Creating a Unit This section provides an overview of the choices you have when configuring a new unit. For step-by-step instructions, see “Creating a Unit through 3DM” on page 94 and “Creating a Unit through 3BM” on page 97.
Configuring a New Unit Note: Creating a unit erases all data on all drives. Although creating a RAID 1 (mirror) creates a unit that will have a duplicate of data on both drives after it is put in use, creating a RAID 1 cannot be used to make a backup copy of data that currently exists on a single drive unless you migrate from a RAID 1 to two individual single disks. Name of the unit (optional) Units can be given names. These names will be visible in 3DM and, 3BM.
Chapter 8. Configuring Units Boot volume size When you create a unit through 3BM, you can create a special volume to function as the boot volume. You specify the size you want this volume to be. This is useful if you will be installing an operating system onto the unit, and want it to be installed in one volume and have a separate volume for data. This is an optional feature. You do not have to create a boot volume if you plan to install the operating system on the unit.
Configuring a New Unit 3 Click Create Unit. A window similar to the one below shows the drives you selected, and lets you specify configuration settings. Figure 43. Configuring a Unit in 3DM 4 In the Type field, select the RAID configuration you want. 5 If stripe size applies to the RAID type you select, select a Stripe Size. (Stripe size does not apply to RAID 1.) 6 Optional: In the Name box, enter a name for the unit (up to 21 characters, including dashes and underscores).
Chapter 8. Configuring Units 8 Make changes to the unit policies, as desired. You can enable or disable the Write Cache, Auto Verify, and Continue on Source Error During Rebuild. You can also set the StorSave policy. For details about these settings, see “Setting Unit Policies” on page 106. 9 Click OK. The new unit appears in the Unit Maintenance list at the top of the page and the operating system is notified of the new unit.
Configuring a New Unit Creating a Unit through 3BM In 3BM, configuration tasks start from the main 3ware BIOS Manager screen shown in Figure 45. Figure 45. 3BM Main Display To create a unit through 3BM 1 At the main 3BM screen, select the drives to be included by highlighting each one and pressing Enter or Space to select it. When you select a drive, an asterisk appears next to it in the left most column (see Figure 46). Tip: If you want to use all available drives, press Alt-A to select them all.
Chapter 8. Configuring Units 2 After all drives for the unit are selected, Tab to the Create Unit button and press Enter. Tip: You can also press Alt-C to choose Create Unit. 3 On the 3ware Disk Array screen, make sure that the proper drives are listed. Figure 47. Create Disk Array Display 4 (Optional) Press Enter and type a name for the unit; then press Enter again to set the name.
Configuring a New Unit 8 (Optional) Tab through the policy fields and make any appropriate changes to the settings for: • • • • Write Cache Setting Drive Queuing Mode Continue on Error During Rebuild StorSave Policy For details about these settings, see “Configuration Options When Creating a Unit” on page 92. 9 (Optional) Tab to the field Boot Volume Size, press Enter and type the size for the boot volume (volume 0) in gigabytes; then press Enter again to set the size.
Chapter 8. Configuring Units 12 When you are finished making configuration changes, press F8 to save the changes and exit 3BM. A warning message tells you that all existing data on the drives will be deleted, and asks you to confirm that you want to proceed. Figure 50. Confirmation Message when Saving and Exiting If you made changes to units on more than one controller, the details about changes about to be made may extend beyond one screen.
Configuring a New Unit 2 Press the Page Up key to move the unit up the list; press the Page Down key to move the unit down the list. Position the unit you want to be bootable at the top of the list of exportable units. 3 When you are finished working in 3BM, press F8 to save your changes and exit. Partitioning, Formatting, and Mounting Units After you create a unit, whether through 3BM or 3DM, it needs to be formatted, partitioned, and mounted by the operating system before it can be used.
Chapter 8. Configuring Units To partition, format, and mount under Linux 1 Boot the system and log in as root. 2 Open a terminal window.
Creating a Hot Spare To partition, format, and mount under FreeBSD 1 Boot the system and log in as root. 2 Open a terminal window. 3 Partition the unit: fdisk -BI /dev/da0; disklabel /dev/da0 | disklabel -B -R -r da0 4 Create or make the file system: newfs /dev/da0c 5 Mount the volume: mount /dev/da0c /mnt You can also use sysinstall to format and partition the unit. Creating a Hot Spare You can designate an available drive as a hot spare.
Chapter 8. Configuring Units Note: 3ware’s 9000 series RAID controllers use drive coercion so that drives from differing manufacturers and with slightly different capacities are more likely to be able to be used as spares for each other. Drive coercion slightly decreases the usable capacity of a drive that is used in redundant units.
Naming a Unit Figure 51. Hot Spare Indicated If a hot spare is already enabled, you can disable it by pressing s again. 3 If you are finished making changes in 3BM, press F8 to save the changes and exit. Note: If the drive you designated as a spare is not large enough to replace a failed drive in a fault-tolerant unit, or if there is not a fault-tolerant unit for the spare to support, 3BM will notify you.
Chapter 8. Configuring Units To name or rename a unit through 3BM 1 At the main 3BM screen, select the unit by highlighting it and pressing Enter. An asterisk appears in the left-most column to indicate that it is selected. 2 Tab to the Maintain Unit button and press Enter. 3 On the pop-up menu, select Configure and press Enter. On the Configure Disk Array screen, the Array Name field is already selected. 4 Press Enter to open a text box. 5 Type a name for the unit and press Enter.
Setting Unit Policies • Continue on Source Error During Rebuild. Determines whether ECC errors are ignored when they are encountered during a rebuild. (ECC errors are an indication of errors that have occurred on a particular drive since it was last read.) When not enabled, a rebuild will abort upon encountering an ECC error and the unit will be set to Degraded. For details, see “Setting Continue on Source Error During Rebuild” on page 110. • Queuing.
Chapter 8. Configuring Units Enabling and Disabling the Unit Write Cache Write cache is used to store data locally in memory on the drive before it is written to the disk drive media, allowing the computer to continue with its next task. This improves performance. However, there may be instances when you want the computer to wait for the drive to write all the data to disk before going on to its next task. In this case, you must disable the write cache.
Setting Unit Policies To enable or disable unit write cache through 3BM 1 At the main 3BM screen, select the unit by highlighting it and pressing Enter. An asterisk appears in the left-most column to indicate that it is selected. 2 Tab to the Maintain Unit button and press Enter. 3 On the pop-up menu, select Configure and press Enter. 4 In the Configure Disk Array screen, Tab to the field Write Cache Settings. Figure 53.
Chapter 8. Configuring Units verify task during the scheduled time windows. (For information about schedules, see “Scheduling Background Tasks” on page 156.) If Auto Verify is not set, you must manually specify when you want to run a verify, on the 3DM Controller Settings page. If a schedule is set for verify, then the verify that you manually start will only run during the scheduled time.
Setting Unit Policies The page refreshes, and a message at the top confirms the change you have made. To set the Continue on Source Error During Rebuild policy in 3BM 1 At the main 3BM screen, select the unit by highlighting it and pressing Enter. An asterisk appears in the left-most column to indicate that it is selected. 2 Tab to the Maintain Unit button and press Enter. 3 On the pop-up menu, select Configure and press Enter.
Chapter 8. Configuring Units To enable or disable queuing for a unit through 3DM 1 Choose Management > Controller Settings from the menu bar in 3DM. 2 In the Unit Policies section of the Controller Settings page, enable queuing by checking the box under “Queuing” for the designated unit; disable it by unchecking the box. The page refreshes, and a message at the top confirms the change that you have made.
Setting Unit Policies Table 9: StorSave Profile Definitions Definition FUA (Force Unit Access) Protection (Default) Balanced Performance Maximum data protection, but slower performance. More data protection than Performance but less data protection than Protection. Maximum performance for the unit, but less data protection.
Chapter 8. Configuring Units The Protection profile enables write journaling; the Performance and Balanced Profile disables it. The Balanced profile disables it only if no BBU is present. If write journaling is disabled and a BBU is present, then it is as if the BBU was disabled for that unit. • Write cache disabled on degrade. In the event that a unit degrades, the use of write cache can be disabled until the unit is rebuilt. Once the unit is rebuilt, you must enable the write cache manually.
Changing An Existing Configuration by Migrating 5 Press Enter to display the choices, use the arrow keys to select the setting you want, and press Enter again to choose it. 6 Tab to the OK button and press Enter to select it. You return to the main 3BM screen. 7 When you are finished making changes, press F8 to save them and exit 3BM. Changing An Existing Configuration by Migrating You can convert one RAID configuration into another while the unit is online.
Chapter 8. Configuring Units RAID Level Migration (RLM) Overview RAID level migration is the process of converting one RAID configuration to another. When you migrate a unit to a different configuration, the user data on it is redistributed to the format of the new configuration. This data redistribution process is a background task, similar to the rebuild or verify processes. Figure 54 shows an example of how data is reconfigured during a migration.
Changing An Existing Configuration by Migrating Table 10: Valid Migration Paths Destination Source R0 R1 R5 R6 R10 R50 Single JBOD Spare Single Yes Yes Yes Yes Yes Yes No No No JBOD No No No No No No No No No Spare No No No No No No No No No Warning: If you are booted from a mirror (RAID 1 unit), never split it into 2 single (identical) drives. Once the unit is split, any pending writes cannot be written to the second drive.
Chapter 8. Configuring Units To change the RAID level of a unit 1 In 3DM 2, choose Management > Maintenance. 2 In the Unit Maintenance table on the Maintenance Page, select the unit for which you wish to change the RAID level, by checking the box next to the Unit ID. The unit to be migrated must be in a normal state (not degraded, initializing, or rebuilding) before starting the migration. 3 Click the Migrate Unit button. The Migrate dialog box appears. 4 Select any drives to be added to the unit.
Changing An Existing Configuration by Migrating 3 Click the Migrate Unit button. The Migrate dialog box appears, listing the drives which can be added to the unit. 4 Select the drives(s) you wish to add to the unit by checking the Port ID box next to each one. 5 If desired or necessary, select the appropriate RAID level. 6 Click OK. The Maintenance page updates to show the newly reconfigured unit. The Status column title indicates that Migration is in progress.
Chapter 8. Configuring Units 2 3 In the software, remove and rescan the controller, in order to update unit information. a In 3DM2 choose Management > Maintenance and select the appropriate unit. a Click the Remove Unit button. b After the unit has been removed, click the Rescan button. The new unit capacity displays. Resize the partition and file system or create a new partition. In Windows, use the disk management utility to determine whether the disk is a basic disk or a dynamic disk.
Deleting a Unit Warning: When a unit is deleted, all of the data on that unit will be lost. The drives cannot be reassembled into the same unit because the data on it is erased. If you want to reassemble the drives into the same unit on another controller, use the Remove Unit button in 3DM instead of the Delete Unit button. Or, if you’re at the BIOS level already, you can shut down the computer and physically move the drives to another 3ware 9000 series RAID controller.
Chapter 8. Configuring Units 5 In the Unit Maintenance section of the Maintenance page, select the unit you want to remove and click Delete Unit. 6 When a message asks you to confirm, click OK. Configuration information associating the drives with the unit is deleted, and the individual drives appear in the Available Drives list (Figure 55). You can now use them as part of another unit, or designate them as Spares, for use in a rebuild. Figure 55.
Removing a Unit 3 On the Delete Disk Array screen, review the information about the unit to make sure it is the one you want to delete. Figure 56. Deleting a Unit in 3BM 4 Tab to the OK button and press Enter. You return to the main 3BM screen, and the drives associated with the unit now appear in the list of Available Drives. Remember: The unit is not actually deleted and no data is overwritten until you press the F8 key to save your changes, or press Esc and select Yes when asked if you want to save.
Chapter 8. Configuring Units Note: You can also remove a drive, if you want to force a degrade on a redundant unit, or if you want to remove a drive from the “Available Drives” list so that you can then remove it from the system. For more information, see “Removing a Drive” on page 130. Removing a Unit Through 3DM In 3DM, the command for deleting a unit is on the Maintenance page. Be sure to follow steps 1 and 2 in the instructions before using the Remove command.
Removing a Unit 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. You can now physically remove the drives and move them to another controller. If you have a hotswap carrier, you can do this without shutting down the system. If you do not have a hot-swap carrier, power-down the system and ground yourself before making changes to the hardware.
Chapter 8. Configuring Units Moving a Unit from One Controller to Another After you have configured a unit on a 3ware 9000 series controller, you can move it to a different 3ware 9000 series controller, and retain the configuration on the new controller. This is referred to as “array roaming.” When connecting the unit to the new controller, you do not have to physically connect the drives to the same ports to which they were connected on the previous controller. The firmware will still recognize the unit.
Moving a Unit from One Controller to Another below. For units using JBOD, see “Moving Legacy JBOD Units to a 9000 Controller” on page 127. Note: In order to preserve the data that is on the units attached to the 8000, you will need to run a special utility to convert the units to a format that the 9000 controller can use. Contact Technical Support to obtain the utility. (This utility is not required for legacy JBOD units.) Do not remove the 8000 board from your system until you have converted the units.
Chapter 8. Configuring Units 3 Power down the system, disconnect the drives from the 8000 controller and remove that controller from the system. 4 Attach the drives to the 9000 board. 5 Reboot the system and enter the 3ware 9000 series BIOS (3BM) by pressing Alt-3. Enable the Export JBOD policy on the Policy screen. 6 Press the F8 or Esc key to save and exit. To move legacy JBOD units under Linux or FreeBSD 1 Upgrade your driver to the 9000 series driver.
Adding a Drive 4 Remove the 9500S controller. 5 If you are working with a Linux system, install the 9550SX, 9590SE, or 9650SE controller. 6 Attach the drives that were on the to the 9500S to the 9550SX, 9590SE, or 9650SE controller. 7 Power up the computer and verify that the upgrade is complete. (The existing units should be available for use.) To move a secondary storage unit from a 9500S to a 9550SX, 9590SE, or 9650SE controller 1 Power down the computer. 2 Remove the 9500S controller.
Chapter 8. Configuring Units Note: When you add a drive to your system and connect it to the controller, it is automatically detected and listed in 3DM. If it does not immediately display, or if it is part of a unit, you can use the rescan feature, as described below. To add a drive 1 Insert the drive into the hot-swap carrier or into your 3ware Sidecar. 2 In 3DM, choose Management > Maintenance. 3 On the Maintenance page, click Rescan Controller.
Rescanning the Controller To remove a drive 1 In 3DM, choose Management > Maintenance. On the Maintenance page, Remove Drive links appear next to all drives that can be removed from units, and next to drives in the Available Drives list. 2 3 Locate the drive you want to remove and click the Remove Drive link (Figure ). When 3DM asks you to confirm that you want to remove the drive, click OK. You can now remove the drive from your system.
Chapter 8. Configuring Units To rescan the controller through 3DM 1 In 3DM, choose Management > Maintenance. 2 On the Maintenance page, click Rescan Controller. 3DM scans the controller for information about units and drives, and updates the information shown on the Maintenance page. To rescan the controller through 3BM 132 1 From the main 3BM screen, press Alt-r. You are warned that any configuration changes you have made in 3BM will be lost. 2 Type Y for Yes to rescan the controller.
9 Maintaining Units 3ware RAID controllers include a number of features in the firmware that help maintain the integrity of your drives, check for errors, repair bad sectors, and rebuild units when drives degrade. In addition, 3ware BIOS Manager (3BM) and 3ware Disk Manager (3DM) provide tools to let you check unit and drive status, and manually start background maintenance tasks. 3DM also lets you review alarms and errors and schedule background maintenance tasks.
Chapter 9. Maintaining Units The next figure illustrates how you can drill down to get additional detail about units and drives in your system. Figure 58. Drilling Down to Check Status Information For some RAID levels (RAID 6, RAID 10, and RAID 50), a single RAID unit may have more than one status. For example, part of the unit could be rebuilding, while another part is degraded or initializing. When this is the case, you will see both statuses listed at the top unit level.
Checking Unit and Drive Status through 3DM Enclosure LED Status Indicators If you use a 3ware Sidecar or an enclosure that has an integrated AMCC/ 3ware CCU (chassis control unit), the LEDs on your enclosure also provide some status information. The chassis should come with a cable which attaches to the I2C port on the controller. Note: The following table is an example only. Check with your chassis documentation for more details. Not all features may be supported or implemented in the same way.
Chapter 9. Maintaining Units The unit is not fully fault tolerant until the rebuilding is complete. For more information, see “To verify a unit through 3BM” on page 149. • Rebuild-Paused. The unit is set to rebuild, however scheduling is enabled, and the present time is not during a scheduled timeslot. Rebuilding will start at the next scheduled time slot. Rebuilds are also paused for up to ten minutes after a reboot, even during a scheduled timeslot. • Initializing.
About Degraded Units Drive Statuses The following is a list of drive statuses you may see in 3DM: • OK. The drive is fine and is functioning normally. • Not Present. No drive is present in this slot. • Drive Removed. The drive has been removed. • Other. A number of other drive statuses may appear in the event of a problem. If you have a question about a status shown, contact AMCC customer support. knowing the exact drive status can help trouble-shoot the problem.
Chapter 9. Maintaining Units About Inoperable Units Units become inoperable when there are no longer enough drives in the unit for it to function. For example, a RAID 5 unit created from four drives becomes degraded if one drive fails or is removed, but becomes inoperable if two drives fail or are removed. A RAID 6 unit created from five drives becomes degraded if one or two drives is removed, but becomes inoperable if three drives fail or are removed.
Alarms, Errors, and Other Events Event messages are categorized into the following levels of severity: • Errors (high severity events), shown next to a red box • Warnings, shown next to a yellow box • Information, shown next to a blue box Examples of event messages: • Error: Unclean shutdown • Warning: Degraded unit • Information: Start and completion of rebuilding, verifying, initializing, migrating, and so forth. 3DM can e-mail notifications of these events to one or more recipients.
Chapter 9. Maintaining Units WinAVAlarm is a stand-alone utility and does not require 3DM to be running, unlike e-mail notification. After it is installed, an icon for it appears in your System tray. To change the alert utility settings 1 Double-click on the WinAVAlarm icon in the system tray. Figure 59. WinAVAlarm in the Windows System Tray 2 In the Windows Audible Visual Alarm window, select the types of alerts you want to be notified of.
Alarms, Errors, and Other Events Downloading an Error Log You can download an error log containing information from the firmware log. This can be useful when troubleshooting certain types of problems. For example, you might want to send the saved file to 3ware Customer Support for assistance when troubleshooting. To download the error log 1 In 3DM, choose Information > Controller Details from the menu bar. 2 Make sure the correct controller is displayed in the Select Controller field in the menu bar.
Chapter 9. Maintaining Units Background Tasks Background tasks are maintenance tasks that help maintain the integrity of your drives and data. These tasks include • Initialization of units • Verification of units • Rebuilds when units have become degraded • Migration of an on-line RAID from one RAID configuration to another • Self-tests You can set up your system so that these tasks occur as they are needed, or you can create schedules so that they occur during non-peak times.
Background Tasks About Initialization For 3ware SATA RAID controllers, initialize means to put the redundant data on the drives of redundant units into a known state so that data can be recovered in the event of a disk drive failure. For RAID 1 and RAID 10, initialization copies the data from the lower port to the higher port. For RAID 5, RAID 6, and RAID 50, initialization calculates the RAID 5 parity and writes it to disk (background initialization).
Chapter 9. Maintaining Units postpone initialization until a scheduled time. (See “Scheduling Background Tasks” on page 156). Note: Units that do not need to be immediately initialized for full performance will be automatically initialized using background initialization when they are verified for the first time. (Verification requires that the units have been previously initialized.
Background Tasks Notes: For RAID 5 with more 5 or more drives, it is strongly recommended that you initialize the unit before using it. Initializing such a unit is critical to insuring data integrity on the unit. For RAID 5 with 3 or 4 drives, initialization before use is not required. However, initialization is required before a unit can be verified.
Chapter 9. Maintaining Units Table 12: Initialization Requirements for Different RAID Configurations Initialization Required for Highest Performance? Yes RAID Configurations RAID 5 with 5 or more disks RAID 6 RAID 50 with subunits of 5 or more disks Background Initialization After Power Failure The 3ware controller detects and handles power failures, using a mechanism that ensures that redundant units have consistent data and parity.
Background Tasks What Verification Does For a RAID 1 or RAID 10 unit, a verify compares the data of one mirror with the other. For RAID 5, RAID 6, and RAID 50, a verify calculates parity and compares it to what is written on the disk drive. Verification checks each sector on a drive. This is important, because day-today use of the media may leave many sectors on a drive unused or unchecked for long periods of time. This can result in errors occurring during user operation.
Chapter 9. Maintaining Units How Errors Are Handled Verification makes use of the same error checking and error repair techniques used during ordinary use of drives configured through 3ware RAID controllers. When verification encounters an error, the controller typically retries the command. If there are cable CRC errors, there may be multiple retries including downgrade of the UDMA mode. If the error persists and is unrepairable (e.g., ECC errors), an error notification is issued to indicate the problem.
Background Tasks To verify a unit through 3DM 1 In 3DM, choose Management > Maintenance. 2 In the Unit Maintenance section of the Maintenance page, select the unit you want to verify and click Verify Unit. 3DM puts the selected unit in verifying mode. If verify scheduling is not enabled on the Scheduling page, the verification process begins almost immediately. If verify scheduling is enabled, the unit will not start actively verifying until the next scheduled time.
Chapter 9. Maintaining Units Notes: If a unit that requires initialization has not previously been initialized, selecting Verify Unit starts initialization. This is because fault-tolerant units cannot be verified until after they are initialized. If the unit is already in a state of rebuild, initialization, or verification, the unit cannot be verified in 3BM. You must boot the system and let the task finish in the background.
Background Tasks A RAID 6 unit can have two simultaneous drive failures, before becoming inoperable. When a RAID 5 or RAID 6 is running in Degraded mode and you rebuild it, the missing data is reconstructed from all functioning drives. Note: If a rebuild fails, check the Alarms page for the reason. If there was an ECC error on the source disk, you can force the rebuild to continue by checking the Overwrite ECC Error policy on the Controller Settings page in 3DM and then running Rebuild again.
Chapter 9. Maintaining Units scheduling is enabled, the unit will not start actively rebuilding until the next scheduled time. Note: If you need to cancel a rebuild, you can do so by using the Remove Drive link on the Maintenance page to remove the drive from the unit. Rebuilding Units through 3BM When a RAID unit becomes degraded, it is marked as such, and the drive(s) that failed are marked as Not In Use in the 3BM screens. Figure 63, shows an example of how a degraded RAID 5 unit appears in 3BM.
Background Tasks Figure 64. Degraded Disk Array Warning Message 2 Press a key to continue. 3 If your degraded unit has a drive indicated as Not in Use, the drive may still be usable. Try rebuilding with the Not in Use drive intact. Simply select the unit (highlight it and press Enter) and then select the Rebuild Unit button. 4 When the Rebuild confirmation screen appears, confirm that you selected the correct unit by selecting OK. 5 Press F8 to save your changes and exit 3BM.
Chapter 9. Maintaining Units Figure 65. Rebuild Option on the Maintain Menu The Rebuild Disk Array screen displays. Figure 66. Rebuild Disk Array Screen 5 Press Enter to select the OK button to continue. You are returned to the main screen; “Rebuilding” appears next to the unit you selected. 6 Press F8 to save your changes and exit 3BM. The unit will begin rebuilding about ten minutes after the operating system finishes loading and the 3ware driver has loaded.
Background Tasks and cancel a rebuild by using the Remove Drive link on the Maintenance page. If you do not have hot-swap carriers and do not want to boot the operating system and launch 3DM, you can also cancel a rebuild by powering down the system, physically removing a drive, and installing another one that you want to use. Then when you start 3BM, the unit will appear as degraded and you can rebuild it, using the steps described under “Rebuilding Units through 3BM” on page 152.
Chapter 9. Maintaining Units Background Task Prioritization Although migration tasks follow the same schedule as rebuild and initialization tasks, they are always given the highest priority because of the controller and disk resources required during migration. Once a unit is put into the migration state, it must be allowed to complete the process. While migrating, rebuilds or verifies to the unit are not permitted. Rebuilding preempts verify operations.
Scheduling Background Tasks Tip: If you want to change a task schedule window, you first remove the schedule item and then add it back with the desired day, time, and duration. Note: Setting up the scheduling window does not actually request background tasks. It simply specifies when they can run. For more information about the background tasks themselves, see “Background Tasks” on page 142. You can also set the rate at which background tasks are performed compared to I/O tasks.
Chapter 9. Maintaining Units Figure 67. Selecting Task Schedules to View Turning On or Off Use of a Task Schedule Turning on the schedule for Rebuild/Migrate and Verify tasks forces rebuilds, migrates, and verifies to be performed only during the time specified by the schedule. If the schedule is not turned on, rebuilds, migration, initialization, and verify can happen whenever they are required or are manually started.
Scheduling Background Tasks 3 In the Schedule Rebuild Tasks section, select the appropriate setting: Follow Schedule or Ignore Schedule. The illustration below shows this setting for the rebuild task schedule. Note: Self-test schedules cannot be turned off in this way. To disable self-tests you must either remove all schedule times, or uncheck the tests listed in the Tasks column. For more information, see “Selecting Self-tests to be Performed” on page 160.
Chapter 9. Maintaining Units To add a task schedule slot 1 Choose Management > Schedule from the menu bar. The Scheduling page appears, showing the schedule for Rebuild/Migrate Tasks. 2 To view Verify Tasks or Self-test Tasks, select it from the drop-down list at the top of the page. 3 Scroll to the section of the Scheduling page that shows the task you want to add. 4 In the fields at the bottom of the section, select the Day, Time, and Duration for the task. 5 Click the Add New Slot button.
Locating a Drive by Blinking Its LED 3 Check the boxes next to the self-tests you want to be performed. To disable self-tests Unlike scheduling of rebuilds and verifies, scheduling of self-tests is always enabled. To disable self-tests you must either remove all schedule times, or uncheck the tests listed in the Tasks column. Locating a Drive by Blinking Its LED You can easily identify the drives in a unit, or an individual drive, by causing the LEDs associated with the drives to blink.
Chapter 9. Maintaining Units The LED on the enclosure begins blinking. 3 When you are finished working with the drive and no longer need to see the LED, return to this page and uncheck the Identify box. To blink the LEDs for all drives in a unit 1 Choose from the main menu in 3DM. 2 On the list of units, locate the unit you want to identify. 3 Check the box in the Identify column. The LEDs associated with each drive in the unit begin blinking on the enclosure.
10 Maintaining Your Controller This section contains instructions for how to perform tasks that help you maintain your controller, including: • Determining the Current Version of Your 3ware Driver • Updating the Firmware and Driver • Downloading the Driver and Firmware • Updating the Firmware Through 3DM 2 • Viewing Battery Information • Testing Battery Capacity Determining the Current Version of Your 3ware Driver You can view controller and driver information in several different ways: • Using
Chapter 10. Maintaining Your Controller 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 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.
Updating the Firmware and Driver Downloading the Driver and Firmware You can download the latest drivers and firmware from the 3ware website, at http://www.3ware.com/support. Note: Information in this section applies to updating drivers and firmware for the 9550SX, 9590SE, and 9650SE controllers. The 3ware website also allows you to download drivers for other 3ware controller models and associated release notes. For Windows, the firmware and driver can be installed from the same download (3wUpdate.exe).
Chapter 10. Maintaining Your Controller 10 Uncompress the file to extract the driver or firmware files to a local directory or a diskette. (Make note of the absolute path to the local directory.
Updating the Firmware and Driver Updating the 3ware Driver and Firmware Under Windows You can update both the driver and the firmware under Windows, using the utility 3wUpdate.exe. This utility is included with the driver and firmware files when you download them. If you only need to update the driver, you can either use the update utility as described below, or you can update it through the Windows Device Manager, as described under “Updating the 3ware Driver Under Windows XP” on page 172.
Chapter 10. Maintaining Your Controller When the 3ware Driver/Firmware Update dialog box appears, it shows available updates for the device driver and for the firmware. Figure 69. Update Utility Showing Available Drivers . The updater tells you whether newer updates are available, and makes recommendations for whether you should update. If either your driver or firmware is current, the screen reflects that. Figure 70.
Updating the Firmware and Driver If the firmware image is not found with the driver files, the 3ware Driver/ Firmware Update dialog box will show only the driver as available. Figure 71. Update Utility Showing Only Driver Available Only the driver is available, because the firmware image was not found. If the driver is not found, the 3ware Driver/Firmware Update dialog box will show only the firmware as available. Figure 72.
Chapter 10. Maintaining Your Controller Note: If you have multiple controllers in your system, your screen will look slightly different, so that you can update the firmware for one or all controllers. For details, see “Using the Update Utility With Multiple Controllers” on page 171 6 In the Action section of the dialog, make any changes to what will be updated and click Continue to install your selections. During the update, the driver installs on your local drive.
Updating the Firmware and Driver (This message appears if you do not need to restart your computer.) Figure 74. Dialog Indicating Update Complete Using the Update Utility With Multiple Controllers When your system has multiple 3ware RAID controllers installed, the update utility lets you update the firmware on any or all of the installed controllers. To update the firmware on multiple controllers 1 Follow steps 1 through 5 above, under “Updating the 3ware Driver and Firmware Under Windows” on page 167.
Chapter 10. Maintaining Your Controller 2 Use the scroll arrows under “Current” Controller to see firmware recommendations for each controller on your system. 3 For each controller, review the option for whether the firmware should be updated, and change it if appropriate. 4 Continue with step 6 above, in the procedure “Updating the 3ware Driver and Firmware Under Windows.
Updating the Firmware and Driver Figure 76. 3ware Serial ATA RAID Controller Properties Dialog 10 Click the Update Driver… button. 11 If your system has Windows XP Service Pack 2, the first screen asks whether you want to connect to Windows Update. Select “No, not this time” and click Next. Figure 77. Windows XP Service Pack 2 Windows Update Query 12 When you reach the Hardware Update Wizard screen shown below, select “Install from a list or specific location (Advanced)” and then click Next. www.3ware.
Chapter 10. Maintaining Your Controller Figure 78. Upgrade/Install Device Driver Wizard 13 At the next screen (Figure 79) choose “Don’t search. I will choose the driver to install” and click Next. Figure 79. Search for Driver Screen 14 When the Select the Device Driver screen appears (Figure 80), click the Have Disk… button.
Updating the Firmware and Driver Figure 80. Select the Device Driver Screen 15 When the Install from Disk dialog box appears (Figure 81), enter the correct path name to the driver. If you created a driver diskette, insert it now. (The path will be A: if you are using a diskette in the A drive.) Figure 81. Install From Disk Dialog Box 16 When the Select the Device Driver dialog box reappears, select the appropriate driver (Figure 82) and click Next.
Chapter 10. Maintaining Your Controller Figure 82. Select a Device Driver The wizard begins installing the driver. You will see a progress box during installation. 17 If the Digital Signature Not Found screen appears, click Yes to continue and follow the instructions to complete the driver installation. 18 When the Completing the Hardware Update Wizard screen appears, click Finish. 19 If you are prompted to restart the system, do so.
Updating the Firmware and Driver Figure 83. Found New Hardware Screen 20 Choose “No, not this time” and click Next. At the next screen, leave the selection as “Install the software automatically.” Click Next and follow the prompts on the screen. 21 When the second Completing the Found New Hardware screen appears, click Finish. Figure 84. Completing Found New Hardware Wizard www.3ware.
Chapter 10. Maintaining Your Controller Updating the 3ware Driver Under Red Hat or Fedora Core The following steps describe how to update the 3ware driver under Red Hat. Note: Pre-compiled, tested, and supported drivers are no longer available for older RedHat or Fedora Core releases using the 2.4 kernel. The source code is still available (for a limited time) if a newer driver is still needed.
Updating the Firmware and Driver 5 For 2.4 Kernels, add the following line to /etc/modules.conf: alias scsi_hostadapter 3w-9xxx.o For 2.6 Kernels, add the following line to /etc/modprobe.conf. alias scsi_hostadapter 3w-9xxx.ko 6 Complete the upgrade by upgrading the initial ramdisk. Change the directory to the boot directory: cd /boot Run mkinitrd by entering the following: (In the commands below, replace with the applicable kernel, for example 2.4.
Chapter 10. Maintaining Your Controller To update the 3ware driver under SuSE 1 Download and extract the driver, as described under “Downloading the Driver and Firmware” on page 165. 2 Backup any critical data prior to updating the 3ware driver. 3 Change the directory to the location with the extracted driver. 4 Copy the files to the appropriate directory. (In the commands below, replace with applicable SuSE version, such as su10) Replace with applicable kernel (i.e.: 2.6.16.
Updating the Firmware and Driver 11 Stop the current driver module, if loaded: rmmod 3w-9xxx 12 Load the new driver module: modprobe 3w-9xxx If the new driver fails to load properly, confirm that you used correct driver. If your kernel or SuSE version is not supported, you will need to compile your own driver. For more information, see knowledgebase article 14546 (http:// www.3ware.com/KB/article.aspx?id=14546).
Chapter 10. Maintaining Your Controller Updating the Firmware Under Linux and FreeBSD The following steps describe how to update the firmware under Linux and FreeBSD using the utility tw_update. (You can also update the firmware through 3DM. For details, see “Updating the Firmware Through 3DM 2” on page 166.) The PROM images that are installed when you update the firmware include any 3BM and BBU firmware updates.
Viewing Battery Information Viewing Battery Information The Battery Backup Unit (BBU) is an add-on card that can be attached to most 3ware 9000 RAID controllers to supply power from a battery pack in the event of a system power loss. (The BBU is not supported on the 9590SE4ME.) This allows the controller to use write-caching for optimal performance and to preserve data in the event of a system power failure. When fully charged, the battery preserves the contents of the cache memory for up to 72 hours.
Chapter 10. Maintaining Your Controller automatically charged again after the test completes. The whole process usually takes between 8 and 12 hours. While running the battery test and until charging is completed, write cache is temporarily disabled. For how to replace the battery, see the installation guide that came with your controller. To test the battery in a BBU in 3DM 2 1 On the menu bar, choose Monitor > Battery Backup. 2 On the Battery Backup page, click the Test Battery Capacity link.
Testing Battery Capacity Figure 86. BBU Information Screen While Battery is Testing To test the battery in a BBU in 3BM 1 At the main 3BM screen, tab to the BBU button and press Enter. 2 Tab to Test Battery Capacity and press Enter. Figure 87. Battery Backup Information Screen in 3BM www.3ware.
11 3DM 2 Reference This section includes details about the fields and features available on the pages you work with throughout 3DM 2. It is organized by 3DM page, as the pages are organized on the 3DM menu bar.
Controller Summary page Controller Summary page Figure 88. Controller Summary Page The Summary page appears after you first logon to 3DM, and when you click the Summary link in the menu bar. This page provides basic information about each 3ware RAID controller in your system. To see details about the units in a controller, click the link in the ID column. ID. The ID that the operating system assigns to the controller.
Chapter 11. 3DM 2 Reference Controller Details page Figure 89. Controller Details Page The Controller Details page appears when you choose Information > Controller Details from the menu bar. This page provides detailed information about the controller specified in the drop-down list on the menu bar. You can also open or download an error log from this screen. Model. The model name of the controller. Serial #. The serial number of the controller. Firmware. The firmware version running on the controller.
Unit Information page # of Drives. The number of drives connected to the controller. Download Error Log: Click on this link to download the firmware error log to your computer. This feature is important when contacting AMCC for support with your controller. It will help AMCC identify the problem you encountered. Unit Information page Figure 90.
Chapter 11. 3DM 2 Reference Status. The operational status of the unit: OK, Rebuilding, Initializing, Migrating, Verifying, Degraded, or Inoperable (missing drives). When a unit is Rebuilding, Initializing, Migrating, or Verifying, the percentage (%) complete is also shown. For an explanation of the statuses, see “Unit Statuses” on page 135. Note: If an asterisk (*) appears next to the status of a unit, there is an error on one of the drives in the unit.
Unit Details page 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.
Chapter 11. 3DM 2 Reference Drive Information page Figure 92. Drive Information Page The Drive Information page appears when you choose Information > Drive Information from the menu bar, or when you click a port # on the Unit Details page. If you arrive at this page from the port # hyperlink on the Unit Information page, the line showing the port # you clicked on is highlighted. This page shows a list of drives on the current controller and a summary of each one.
Drive Details window Note: In most cases, the status of the drive will not correspond to the status of the unit, shown on the Unit Information page. Different status information is provided for drives and for units. Identify. Check this box to cause the LED for this drive to blink in the enclosure.
Chapter 11. 3DM 2 Reference applications, usually server-type applications. In order to make use of Native Command Queuing, the feature must be enabled at both the drive and the controller. Not all drives support NCQ. . The NCQ values in this window indicate whether the feature is supported and enabled at the drive. At the controller level, queuing is enabled or disabled for all drives in a unit on the Controller Settings page. SATA Link Supported and SATA Link Enabled.
Controller Settings page Controller Settings page Figure 94. Controller Settings Page The Controller Settings page appears when you choose Management > Controller Settings from the menu bar. This page lets you view and change settings that affect the units on the controller specified in the drop-down list on the menu bar.
Chapter 11. 3DM 2 Reference The five radio buttons let you set the ratio at which background tasks are performed in comparison to I/O. For additional information, see “Setting Background Task Rate” on page 155. Unit Policies You can enable or disable these policies: Write Cache, Auto-verify, Continue on Source Error During Rebuild, Queuing, and you can select a StorSave Profile.
Controller Settings page Note: The policy Continue on Source Error During Rebuild is equivalent to the “Force continue on source errors” option in 3DM v 1.x and the “ignoreEcc” option in the CLI. Queuing. This policy enables or disables Native Command Queuing (NCQ) for drives in the unit. By default, queuing is disabled. You can enable it, if desired. NCQ only operates when the feature is enabled at both the drive and the controller.
Chapter 11. 3DM 2 Reference • Smallest usable spare. • Smallest usable unconfigured (available) drive. • Smallest usable failed drive. For additional information, see “Setting the Auto Rebuild Policy” on page 85. Auto-Carving. Auto-carving can be enabled or disabled by selecting the appropriate radio button. When this feature is enabled, any unit that is over a specified size (known as the carve size) will be broken down into multiple volumes of that size, plus a remainder volume.
Scheduling page Scheduling page Figure 95. Scheduling Page The Scheduling page appears when you choose Management > Scheduling from the menu bar. The Scheduling page lets you set up a schedule for when background tasks (rebuild, migrate, initialize, verify, and self-test) should occur. Background tasks can have impact on the performance of your system, so you may prefer to schedule them at times when they will be least disruptive, such as in the middle of the night or on a weekend.
Chapter 11. 3DM 2 Reference Follow Schedule/Ignore Schedule. You can enable or disable the schedule for the Rebuild/Migrate and Verify tasks by selecting either Follow Schedule or Ignore Schedule. When schedules are set to be ignored, these tasks can be performed at any time, and are not restricted to the scheduled times. Note: Scheduling of these tasks is only available on the 9000-series controllers. For details about the different background tasks, see “Background Tasks” on page 142.
Scheduling page The UDMA mode can become downgraded in the event that cable CRC errors are encountered, requiring multiple retries to read sectors. In severe cases, the UDMA mode may be downgraded from ATA 150 to ATA 133, to ATA 100, to 66, to 33. This check is also done every time the system is booted. Check SMART Thresholds. This test checks to see whether SMART thresholds have been exceeded.
Chapter 11. 3DM 2 Reference Maintenance page Figure 96. Maintenance Page The Maintenance page appears when you choose Management > Maintenance from the menu bar. The Maintenance page lets you perform maintenance tasks on existing units on the current controller and lets you create new units by configuring available drives.
Maintenance page Rescan Controller The Rescan Controller button scans the ports on the controller. Rescanning updates the list of available drives shown and updates the status of all ports. If error conditions have been fixed, the status is updated to reflect that. Rescanning is useful in variety of maintenance tasks. For example, if you physically plug in a drive and want the controller to recognize the newly plugged in drive, Rescan will find it.
Chapter 11. 3DM 2 Reference Unit Information Unit Number. The unit number assigned to the unit by the firmware. Use the checkbox next to the unit to select a unit before clicking one of the task buttons. # Drives. Number of drives in the unit. Type of Unit. Type of unit: RAID 0, RAID 1, RAID 5, RAID 6, RAID 10, RAID 50, Single Disk, JBOD, or Spare. If the unit has been given a unique name, it shows beneath the RAID type. Name of Unit. User-assigned unique name of the unit. The default setting is blank.
Maintenance page 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. Maintenance Task Buttons Below the list of units, a row of task buttons lets you perform maintenance and configuration tasks related to the unit. Before clicking one of these buttons, select the appropriate unit. Verify Unit. Puts the selected unit in verifying mode.
Chapter 11. 3DM 2 Reference If rebuild scheduling is enabled on the Scheduling page, the unit will not start actively rebuilding until the scheduled time, and the status will change to say “Rebuild-Paused.” (The Unit Details page indicates whether a unit is actively rebuilding.) If rebuild scheduling is not enabled, the rebuild process will begin right away. For more information about rebuilds, see “To verify a unit through 3BM” on page 149. Migrate Unit. Reconfigures a unit while it is on-line.
Maintenance page 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.
Chapter 11. 3DM 2 Reference Caution: Before you click Delete 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.
Maintenance page Figure 97. Configuration Window in 3DM For more detailed instructions, see “Configuring a New Unit” on page 91. Type. The drop-down list lists the possible RAID configurations for the drives selected in the list of Available Drives. Available configurations may include RAID 0, RAID 1, RAID 5, RAID 6, RAID 10, RAID 50, Single Disk, and Spare Disk. For information about these configurations, see “Available RAID Configurations” on page 5.
Chapter 11. 3DM 2 Reference and the worse the random I/O. The larger the stripe size, the worse the sequential I/O and the better the random I/O. Write Cache, Auto Verify, and Continue on Source Error during Rebuild. These check boxes let you set the policies for the unit. These policies can also be set and changed on the Controller Settings page. For details about these policies, see “Unit Policies” on page 196.
Battery Backup page You can sort the events by severity or time. To do so, just click the column header. For information about a particular event, click it on the Alarms page; the 3DM Help will open with information about the event. For a complete listing of the alarms that appear on the Alarms page, see “Error and Notification Messages” on page 224. Clear Alarms. The Clear Alarms button removes all alarms shown in the list. Sev. Shows the severity of the event.
Chapter 11. 3DM 2 Reference Serial Number. Indicates the BBU serial number. BBU Ready. Indicates if the BBU is able to backup the 3ware RAID controller or not. If the BBU is “Ready”, write cache can be enabled on the 3ware RAID controller. When the status is not “Ready,” write caching is automatically disabled on all units attached to the controller. BBU Status. Indicates the status of the BBU. Possibly BBU statuses include the following: • OK. The BBU is functioning normally. • Not Present.
Enclosure Summary page generated based on the measured temperature. In the case of a temperature error, the BBU status will change to “Fault” and the battery will be disconnected electronically. Estimated Backup Capacity. Indicates the estimated backup capacity in hours. This is the amount of time that the battery backup unit can protect the data in the 3ware RAID controller's cache memory. This field is set to zero at the start of a new test and is updated after the test completes.
Chapter 11. 3DM 2 Reference Enclosure Details page Figure 102. Enclosure Details Page The Enclosure Details page appears when you click the ID of the enclosure on the Enclosure Summary page. Enclosure ID. The ID of the controller to which the enclosure is attached. Fan Summary. Shows the ID of the enclosure and the status of the fan— either OK or Unknown. Temp Sensor Summary. Shows the ID of the enclosure and the temperature in the enclosure.
3DM 2 Settings page 3DM 2 Settings page Figure 103. 3DM 2 Settings Page The 3DM 2 Settings page appears when you click 3DM 2 Settings on the menu bar. Use this page to set preferences, including email notification for alarms, passwords, page refresh frequency, whether remote access is permitted, and the incoming port for 3DM to listen for requests. The initial settings for most of these preferences are specified during installation of 3DM.
Chapter 11. 3DM 2 Reference E-mail Notification Use the fields in this section to set up and manage notifications of events by email. Send E-mail. This field determines whether e-mail notification is Enabled or Disabled. It is a good idea to enable this feature, so that you receive email when your units or drives have problems. Notify On. Specifies the type of events for which notifications should be sent.
3DM 2 Settings page Page Refresh Minutes Between Refresh. Displays how frequently pages in 3DM will be refreshed with new data from the controller. To change this setting, select another option from the drop-down. If you prefer 3DM to only refresh when you click Refresh Page, select Never. The Login, Help and Drive SMART data pages do not automatically refresh. All other 3DM pages do. Remote Access Allow Remote Access.
12 Troubleshooting This troubleshooting section includes the following sections: • Web Resources • Before Contacting Customer Support • Basic Troubleshooting: Check This First • Command Logging • Problems and Solutions • Error and Notification Messages Web Resources For support, troubleshooting tips, frequently asked questions, software releases, and compatibility information related to 3ware RAID controllers, refer to: • 3ware support page at: http://www.3ware.
Before Contacting Customer Support Before Contacting Customer Support Three screens in 3DM 2 provide controller version and status information that can be helpful when contacting 3ware Customer Support with questions or for troubleshooting: Controller Summary, Unit Details, and Unit Information. You can copy and paste the information from these screens into an email using the system clipboard.
Chapter 12. Troubleshooting Command Logging All changes that are made to RAID configurations using 3DM or CLI are automatically stored in a special log file, tw_mgmt.log. This log can be helpful to AMCC technical support for troubleshooting problems with your RAID controller and units. In Linux, FreeBSD and Mac OS X, tw_mgmt.log is in the /var/log directory. In Windows, tw_mgmt.log is in the 3DM2 installation directory if 3DM2 is installed on your system.
Problems and Solutions Enclosure-Related Problems An LED is blinking red on the 3ware Sidecar. A blinking red LED on the 3ware Sidecar indicates that there is a “predicted fault” on the drive in that slot. This can result from a number of different factors, include a SMART error, read error, or cable error. The drive has not failed yet, but may fail soon. For additional information about the LED indicators on the 3ware Sidecar, see “Enclosure LED Status Indicators” on page 135.
Chapter 12. Troubleshooting Software Installation Problems The 3ware RAID controller was configured without problems, but the system does not boot The problem could be one or more of the following: • The BIOS may have changed the order of the boot devices. Check your system BIOS boot sequence. • The 3ware BIOS will only boot from the first unit listed in 3BM.
Problems and Solutions Problems in 3DM and 3BM A 3ware RAID controller does not show in the list of controllers You may not have the most recent driver for your controller. To find out the driver version currently installed, see “Determining the Current Version of Your 3ware Driver” on page 163 Current drivers are available for download on the 3ware website at http://www.3ware.com/support/download.asp.
Chapter 12. Troubleshooting Error and Notification Messages Error and notification messages are issued by the 3ware RAID controller when an error is detected or when an action is completed. These messages are sometimes referred to as AENs (asynchronous event notifications). AEN messages are displayed on the 3DM 2 Alarms page and CLI Show Alarms page. On the 3DM 2 Alarms page, you can click on the message to jump to help text about that message. You can also look the message up in the list below.
Error and Notification Messages Table 13: Error and Notification Message List Value Message 000C Initialize started 000E Initialize failed 000F SMART threshold exceeded 0019 Drive removed 001A Drive inserted 001E Unit inoperable 001F Unit Operational 0021 Downgrade UDMA mode 0022 Upgrade UDMA mode 0023 Sector repair completed 0024 Buffer integrity test failed 0025 Cache flush failed; some data lost 0026 Drive ECC error reported 0027 DCB checksum error detected 0028 DCB version unsupported 0029 Verify start
Chapter 12.
Error and Notification Messages Table 13: Error and Notification Message List Value Message 0058 Battery capacity is below warning level 0059 Battery capacity is below error level 005A Battery is present 005B Battery is not present 005C Battery is weak 005D Battery health check failed 005E Cache synchronization completed 005F Cache synchronization failed; some data lost Error and Notification Message Details 0001 Controller reset occurred Event Type Information Cause The device driver has sent a soft rese
Chapter 12. Troubleshooting See Also For how to collect the system logs, see http://www.3ware.com/kb/ article.aspx?id=12278 For more information regarding FreeBSD installation, see KB articles 14850: http://www.3ware.com/kb/article.aspx?id=14850 0002 Degraded unit Event Type Error Cause An error was encountered and the unit is now operating in degraded (nonredundant) mode. This is usually due to a drive failure or the physical removal of a drive from a redundant unit.
Error and Notification Messages 0004 Rebuild failed Event Type Error Cause The 3ware RAID controller was unable to complete a rebuild operation. This error can be caused by drive errors on either the source or the destination of the rebuild. However, because ATA drives can reallocate sectors on write errors, the rebuild failure is most likely caused by the source drive of the rebuild detecting a read error.
Chapter 12. Troubleshooting 0006 Incomplete unit detected Event Type Warning Cause The 3ware RAID controller has detected an incomplete unit. An incomplete unit is a unit in which the 3ware RAID controller is unable to detect one or more drives. The drives may be missing, dead, or improperly connected. A unit that is incomplete is also degraded (although a degraded unit can be complete if all drives are still detected, including the failed drive). Action Check hardware connections and reseat the drives.
Error and Notification Messages 0008 Unclean shutdown detected Event Type Warning Cause The 3ware RAID controller detected an unclean shutdown of the operating system, either from a power failure or improper shutdown procedure. The controller will force the unit to begin verifying, due to the possibility that data on a redundant unit could be out of synchronization. Action Allow the verification to complete.
Chapter 12. Troubleshooting See Also For links to drive manufacturer diagnostic utilities and troubleshooting advice, see http://www.3ware.com/KB/article.aspx?id=14924. “Basic Troubleshooting: Check This First” on page 219 000A Drive error detected Event Type Error Cause A drive has returned an error to the 3ware RAID controller that it is unable to complete a command. The error type is not a time-out (000A) or uncorrected ECC (0026).
Error and Notification Messages Action Allow the rebuild to complete. This will return the unit to its normal redundant state. See Also “Scheduling Background Tasks” on page 156. “Rebuilding Units” on page 150. “Background Task Prioritization” on page 156. 000C Initialize started Event Type Information Cause The 3ware RAID controller started an initialization. This is always a “synching” background initialization and does not erase user data.
Chapter 12. Troubleshooting Check physical cable and power connections. You can also run the drive manufacturer’s diagnostic and repair utilities on the drive. See Also For links to drive manufacturer diagnostic utilities and troubleshooting advice, see http://www.3ware.com/KB/article.aspx?id=10894. “Basic Troubleshooting: Check This First” on page 219 000F SMART threshold exceeded Event Type Warning Cause SMART monitoring is predicting a potential drive failure.
Error and Notification Messages 0019 Drive removed Event Type Warning Cause A drive was physically removed from the controller while the controller was powered on. Action If the drive is not part of a redundant unit, return the drive as soon as possible. You may need to rescan the controller to have the drive recognized. If at all possible, do not remove a drive from a non-redundant unit as this may cause data loss or a system hang.
Chapter 12. Troubleshooting • A RAID 10 unit with both drives missing from one of the RAID 1 subunits. • A RAID 6 unit with three or more drives missing. Note: The controller only generates this message if the unit is missing drives for more than 20 seconds. This allows a hot-swap of a drive to be completed without generating this error. Action The unit is no longer available for use. Return all missing drives to the unit. If the drives are physically present, check all data and power connections.
Error and Notification Messages Background Information The 3ware RAID controller communicates to the ATA disk drives through the Ultra DMA (UDMA) protocol. This protocol ensures data integrity across the ATA cable by appending a Cyclical Redundancy Check (CRC) for all ATA data that is transferred. If the data becomes corrupted between the drive and the 3ware RAID controller (because of an intermittent or poor quality cable connection) the 3ware RAID controller detects this as a UDMA CRC or cable error.
Chapter 12. Troubleshooting Background Information The 3ware RAID controller supports a feature called dynamic sector repair that allows the unit to recover from certain drive errors that would normally result in a degraded unit situation. For redundant units such as RAID 1, 5, 6, 10, and 50, the 3ware RAID controller essentially has two copies of your data available. If a read command to a sector on a disk drive results in an error, it reverts to the redundant copy in order to satisfy the host’s request.
Error and Notification Messages 0025 Cache flush failed; some data lost Event Type Error Cause The 3ware RAID controller was not able to commit data to the drive(s) during a caching operation.This is due to a serious drive failure, possibly from a power outage. Background Information The 3ware RAID controller uses caching layer firmware to improve performance. For write commands this means that the controller acknowledges it has completed a write operation before the data is committed to disk.
Chapter 12. Troubleshooting Under Linux or FreeBSD use fsck /dev/sda1. If you have more than one SATA device, substitute the correct drive letter and partition number, such as sdb2, for sda1. See Also “Setting Auto Verify for a Unit” on page 109 “Scheduling Background Tasks” on page 156 0027 DCB checksum error detected Event Type Error Cause The drive’s Drive Configuration Block (DCB) has been corrupted.
Error and Notification Messages 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.
Chapter 12. Troubleshooting Action When a verify fails, redundant units will automatically resynchronize user data through a background initialization. The initialize will not erase user data, but will recalculate and rewrite user parity data. If the unit was non-redundant, any data in the error location is lost. (However, the error could be in a part of the drive that did not contain data.) A unit file system check is recommended.
Error and Notification Messages 002C Source drive ECC error overwritten Event Type Error Cause A read error was encountered during a rebuild and the controller is configured to ‘ignore ECC’ or to ‘Force continue on source errors’. The sector in error was reallocated.This will cause uncorrectable blocks to be rewritten, but the data may be incorrect. Action It is recommended that you execute a file system check when the rebuild completes.
Chapter 12. Troubleshooting Under Linux or FreeBSD use fsck /dev/sda1. If you have more than one SATA device, substitute the correct drive letter and partition number, such as sdb2, for sda1.
Error and Notification Messages 0030 Drive not supported Event Type Error Cause 3ware 8000 and 9500S Serial ATA controllers only support UltraDMA-100/ 133 drives when using the parallel-to-serial ATA converter. This message indicates that an unsupported drive was detected during rollcall or a hot swap. This message could also indicate that the parallel-to-serial converter was jumpered incorrectly.
Chapter 12. Troubleshooting 0033 Migration started Event Type Information Cause The 3ware RAID controller has started the migration of a unit. Migration changes can include: • Expanding capacity of a unit by adding drives • Changing RAID levels, for example, from RAID 1 to RAID 5. See Also “RAID Level Migration (RLM) Overview” on page 116. 0034 Migration failed Event Type Error Cause The migration of a unit has failed. Migration changes can include: • Expanding capacity of a unit by adding drives.
Error and Notification Messages 0035 Migration completed Event Type Information Cause The migrated unit is now ready to be used. Migration changes can include: • Expanding capacity of a unit by adding drives • Changing RAID levels, for example, from RAID 1 to RAID 5. Action If the capacity of the unit did not change, then you do not need to do anything else. If the capacity of the migrated unit is larger, you will need to inform the operating system of the change.
Chapter 12. Troubleshooting Note: This message only applies to the 3ware 9500S controller, which has removable memory. Other 3ware controller models do not have memory that can be removed. Action Replace the incompatible SO-DIMM with a compatible one. See Also For a list of SODIMMs compatible with the 9500S, see http://www.3ware.com/KB/article.aspx?id=11748. 0038 SO-DIMM not detected Event Type Error Cause The 3ware 9500S RAID controller is inoperable due to missing SO-DIMM memory.
Error and Notification Messages Action None required. If errors persist, contact technical support at http://www.3ware.com/support/ index.asp. 003A Drive power on reset detected Event Type Error Cause The controller has detected that a drive has lost power and then restarted. The controller may degrade the unit if it is a redundant unit (non-redundant units cannot be degraded). Action If this drive was the only one to lose power, check the cable connections.
Chapter 12. Troubleshooting 003C Initialize paused Event Type Information Cause The initialization is paused. Initializations are normally paused for two (formerly ten) minutes after a system first boots up. Initialization is also paused during non-scheduled times when scheduling is enabled. Initializations follow the rebuild schedule. Action If you want the initialize to resume, you can disable or modify the schedule through 3DM or CLI.
Error and Notification Messages 003E Migration paused Event Type Information Cause Migration is paused. Migration follows the rebuild schedule. Action If you want the migration to resume, you can disable or modify the schedule through 3DM or CLI See Also “RAID Level Migration (RLM) Overview” on page 116 “Scheduling Background Tasks” on page 156 003F Flash file system error detected Event Type Warning Cause A corrupted flash file system was found on the 3ware RAID controller during boot-up.
Chapter 12. Troubleshooting 0040 Flash file system repaired Event Type Information Cause A corrupted flash file system has been successfully repaired. Some of the flash files with insufficient data may have been lost in the operation. The configuration parameters which are lost will then return to their default values. Action We recommend using 3DM, CLI or 3BM to check your settings, in case they were not able to be restored.
Error and Notification Messages Action AMCC recommends verifying the unit. See “Starting a Verify Manually” on page 148. 0043 Backup DCB read error detected Event Type Warning Cause The controller has detected a latent error in the backup Disk Configuration Block (DCB). The 3ware RAID controller checks the backup DCB, even when the primary DCB is OK. If an error is found, the controller will attempt to correct the error by reading the primary copy.
Chapter 12. Troubleshooting Cause The battery pack voltage being monitored by the Battery Backup Unit has fallen below the warning threshold. Action The Battery Backup Unit is presently still able to backup the 3ware RAID controller, but you should replace the battery pack if the warning continues. 0046 Battery voltage is high Event Type Warning Cause The battery pack voltage being monitored by the Battery Backup Unit has risen above the warning threshold.
Error and Notification Messages 0048 Battery voltage is too high Event Type Error Cause The battery pack voltage being monitored by the Battery Backup Unit is too high to backup the 3ware RAID controller. Action The battery pack must be replaced. This may be a fault in the BBU control module. If you get this error, do the following: 1 2 Turn off the computer and remove the 3ware RAID controller. Remove the BBU control module and battery module from the 3ware RAID controller.
Chapter 12. Troubleshooting 004A Battery temperature is low Event Type Warning Cause The battery pack temperature being monitored by the Battery Backup Unit has fallen below the acceptable range. The most likely cause is ambient temperature. Action The Battery backup Unit is presently still able to backup the 3ware RAID controller, but you should replace the battery pack if the temperature warning persists and is not due to environmental reasons.
Error and Notification Messages 004C Battery temperature is too low Event Type Error Cause The battery pack temperature being monitored by the Battery Backup Unit is too low. The BBU is unable to backup the 3ware RAID controller. Action Contact 3ware technical support at http://www.3ware.com/support/index.asp. The battery pack must be replaced if the problem persists and is not due to environmental reasons.
Chapter 12. Troubleshooting Background Information The test estimates how many hours the Battery Backup Unit will be able to back up the 3ware RAID controller in case of a power failure. This test performs a full battery charge/discharge/re-charge cycle and may take up to 20 hours to complete. During this test the Battery Backup Unit cannot backup the 3ware RAID controller. In addition, all units have their write cache disabled until the test completes. Action None required.
Error and Notification Messages 0051 Battery health check started Event Type Information Cause The Battery Backup Unit periodically evaluates the health of the battery and its ability to backup the 3ware RAID controller in case of a power failure. This health check has started. 0052 Battery health check completed Event Type Information Cause The Battery Backup Unit evaluates periodically the health of the battery and its ability to backup the 3ware RAID controller in case of a power failure.
Chapter 12. Troubleshooting Cause The Battery Backup Unit has started a battery charge cycle. Action None required 0056 Battery charging completed Event Type Information Cause The Battery Backup Unit has completed a battery charge cycle. 0057 Battery charging fault Event Type Error Cause The Battery Backup Unit has detected a battery fault during a charge cycle. The Battery Backup Unit is not ready and is unable to backup the 3ware RAID controller. Action Replace the battery pack.
Error and Notification Messages Action Replace the battery pack if the warnings persist. See Also See the Install Guide for your controller. 0059 Battery capacity is below error level Event Type Error Cause The measured capacity of the battery is below the error level. The Battery Backup Unit is not ready and is unable to backup the 3ware RAID controller. Action Replace the battery pack. See Also See the Install Guide for your controller.
Chapter 12. Troubleshooting 005C Battery is weak Event Type Warning Cause The Battery Backup Unit periodically evaluates the health of the battery and its ability to backup the 3ware RAID controller in case of a power failure. This message is posted when the result of the health test is below the warning threshold. Action Replace the battery pack if warnings persist. 005D Battery health check failed Event Type Error Cause The Battery Backup Unit is not able to backup the 3ware RAID controller.
Error and Notification Messages 005F Cache synchronization failed; some data lost Event Type Error Cause The 3ware RAID controller performs cache synchronization when system power is restored following a power failure. The cache synchronization was not successful for some reason. www.3ware.
Appendices The following information is available in the appendices: 264 • Appendix A, “Glossary” on page 265 • Appendix B, “Software Installation” on page 271 • Appendix C, “Compliance and Conformity Statements” on page 280 • Appendix D, “Warranty, Technical Support, and Service” on page 282 3ware Serial ATA RAID Controller User Guide
A Glossary • 3BM 2. The 3ware BIOS Manager, used on PC machines. The 3ware BIOS (Basic Input Output System) manager is a basic interface used to view, maintain, and manage 3ware controllers, disks, and units, without having to boot the operating system. 3BM is included with the controller and is updated when the controller firmware is upgraded. The latest firmware and code set is available for download from the 3ware web site: http://www.3ware.com/support/ • 3DM 2. 3ware Disk Manager.
Appendix A. Glossary • Boot volume size. The size to be assigned to volume 0 when creating a unit through 3BM on a PC machine. Note that the resulting volume does not have to be used as a boot volume. However, if the operating system is installed on the unit, it is installed in volume 0. • Carve size. The size over which a unit will be divided into volumes, if auto-carving is enabled. • Chassis Control Unit (CCU).
• Distributed parity. Parity (error correction code) data is distributed across several drives in RAID 5, RAID 6, and RAID 50 configurations. Distributing parity data across drives provides both protection of data and good performance. • Drive ID. A unique identifier for a specific drive in a system. Also called a port ID. • Drive Number. The SCSI number, or channel number, of a particular drive. • ECC. Error correction code.
Appendix A. Glossary • I²C-(or Inter-IC) bus. A two-wire serial bus solution used as a control, diagnostic, environmental, and power management for EMS (enclosure management services). • Import a unit. Attach a set of disk drives with an existing configuration to a controller and make the controller aware of the unit. Does not affect the data on the drives. • Initialize.
NCQ must be supported by the drive. NCQ must be turned on in both the drive and the RAID controller. By default, the RAID unit’s queue policy is disabled when creating a unit. • Non-redundant units. A disk array (unit) without fault tolerance (RAID 0, single disk, or JBOD.). • OCE (Online Capacity Expansion). The process of increasing the size of an existing RAID unit without having to create a new unit. See also migration. • Parity.
Appendix A. Glossary to delete the original unit. For example, converting a single disk to a mirrored disk or converting a RAID 0 unit to a RAID 5 unit. • Self-test. A test that can be performed on a scheduled basis. Available self-tests include Upgrade UDMA mode and Check SMART Thresholds. • Stagger time. The delay between drive groups that will spin up, at one time, on a particular controller. • Stripe size. The size of the data written to each disk drive in RAID unit levels that support striping.
B Software Installation This appendix provides detailed instructions for installing the 3ware management software for your 3ware RAID controller and the 3ware HTML Bookshelf.
Appendix B. Software Installation 3 From the Welcome screen, click Next to start the installation process. Figure 104. Welcome Installation Screen 4 On the License Agreement page, accept the agreement and click Next. Figure 105.
Installing Software from a Graphical User Interface (GUI) 5 If you want to change where the 3ware Disk Management tools 3DM and CLI will be installed, you can change the path and directory. When you are ready, click Next. Figure 106. Specify Directory Path Screen 6 Select what components you want to install and click Next. 3DM and CLI are applications that let you set up and manage RAID units. 3DM is browser-based; CLI is a command line interface.
Appendix B. Software Installation 7 To configure email notification, check the box and complete the 3DM 2 Email Configuration screen. This features allows you to receive notification of problems with your 3ware RAID controller and units. For details about completing these fields, see “Managing E-mail Event Notification” on page 77. You can select what level of notifications you want to be emailed about. • Errors. You will be notified of Errors only. • Warnings. You will be notified of Warnings and Errors.
Installing Software from a Graphical User Interface (GUI) Figure 109. 3DM2 Command Logging Message 9 [Optional] On the 3DM 2 Security Configuration screen, specify whether you want to restrict access to localhost connections. Enabling this feature prevents people from checking the status and administering the controller from across the Internet or Intranet. If you want to allow people to remotely administer the controller, uncheck this box.
Appendix B. Software Installation 10 [Optional] On the same 3DM 2 Security Configuration screen, you can specify a different listening port than the default (888), if appropriate. For more about this feature, see “Setting the Incoming Port #” on page 79. When you are ready, click Next to continue. Figure 111. 3DM2 Specify Listening Port 11 If you want the Installation Wizard to connect to 3DM 2 after you finish the wizard, check the Connect to 3DM2 box.
Installing Software from a Graphical User Interface (GUI) 12 On the summary screen, review the installation that is about to occur. If you want to make changes, use the Back button to move back through the screens. When you are ready, click Install to continue. Figure 113. Installation Summary Screen 13 When the final installation screen lets you know that installation is complete, click Finish. Figure 114. Final Installation Screen www.3ware.
Appendix B. Software Installation Installing Software on Linux and FreeBSD from the Command Line The following steps describe how to install software on Linux and FreeBSD at a command line, using a console application. To install software on Linux and FreeBSD from the command line 1 Navigate to the folder containing the installer for your operating system and processor type (x86 or x64).
Uninstalling Software Uninstalling Software The steps below tell you how to remove 3ware software from your system. Note: If 3DM is reinstalled or restarted, close any open web browsers before starting 3DM again to close the server socket. Uninstalling 3DM under Microsoft Windows Use the Add or Remove Programs control panel to uninstall 3DM. • From the Startup menu, choose Control Panels > Add or Remove Programs.
C Compliance and Conformity Statements This section is organized into the following topics: • FCC Radio Frequency Interference Statement • Microsoft Windows Hardware Quality Lab • European Community Conformity Statement FCC Radio Frequency Interference Statement This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC (Federal Communications Commission) Rules.
Microsoft Windows Hardware Quality Lab Microsoft Windows Hardware Quality Lab AMCC is committed to Microsoft Windows Hardware Quality Labs (WHQL) certification for all its products. However, a product’s software drivers are typically submitted for certification at nearly the same time as their release to market. Since the certification process may lag behind the release of the drivers, please refer to our WEB site at www.3ware.com for current certification information.
D Warranty, Technical Support, and Service This section is organized into the following topics: • Limited Warranty • Warranty Service and RMA Process • AMCC Technical Support and Services • Sales and ordering information • Feedback on this manual Limited Warranty RAID Controller Hardware. 3-Year Hardware Warranty: AMCC warrants this product against defects in material and workmanship for a period of thirty-six (36) months from the date of original purchase.
Warranty Service and RMA Process parts or replacement products will be provided by AMCC on an exchange basis and will be either new or refurbished to be functionally equivalent to new. Products or parts replaced under this provision shall become the property of AMCC. Software Warranty: AMCC will replace a defective media purchased with this product for a period of up to 30 days from the date of purchase. AMCC warranty service is provided by returning the defective product to AMCC.
Appendix D. Warranty, Technical Support, and Service Serial ATA RAID Controller, including shipping costs. As soon as practicable thereafter, AMCC will ship the advanced replacement to you at the address of your choosing. Upon receipt of the advanced replacement, we ask that you immediately ship the defective AMCC 3ware Serial ATA RAID Controller to AMCC, RAID Products RMA DEPT, 6290 Sequence Drive, San Diego, CA 92121.
Index Numerics 2TB support 86 3BM help 65 main screen 60 navigation 61 screens 60 starting 57 working in 61 3DM 3DM menus 72 Alarms page 210 Battery Backup Information page 211 browser requirements 67 Controller Details page 188 Controller Settings page 195 Controller Summary page 187 Disk Management Utility Overview 66 Drive Details page 193 Drive Information page 192 enabling remote access 78 Enclosure Details page (3DM) 214 Enclosure Summary page (3DM) 213 installation 271 main 3DM screen 72 Maintenance
Flash file system error detected (003F) 251 Flash file system repaired (0040) 252 Incomplete unit detected (0006) 230 Initialize completed (0007) 230 Initialize failed (000E) 233 Initialize paused (003C) 250 Initialize started (000C) 233 Migration completed (0035) 247 Migration failed (0034) 246 Migration paused (003E) 251 Migration started (0033) 246 Primary DCB read error occurred (0042) 252 Rebuild completed (0005) 229 Rebuild failed (0004) 229 Rebuild paused (003B) 249 Rebuild started (000B) 232 Replace
C Cache flush failed, some data lost (0025) 239 Cache synchronization completed (005E) 262 Cache synchronization failed 263 Cache synchronization skipped (004F) 258 cancel rebuild 154 carve size 82 setting 88, 198 certificate message when starting 3DM 69 CLI definition 266 installation 271 Compliance and Conformity 280 configuration changing 115 controller 80 definition 266 exit and save modifications 59 exit without saving 59 unit 91 configuring a controller 80 units 91 configuring units first time, in BIO
Drive timeout detected (0009) 231 driver compiling for Linux 50 current version, determining 163 downloading 165 installation 30 installation under FreeBSD 50 installation under Linux 39 installation under Windows 31 updating FreeBSD 181 Red Hat 178 SuSE 179 Windows 172 driver diskette creating (Linux) 41 creating (Windows) 32 drives per spin-up policy 198 dynamic sector repair 148, 238 E ECC definition 267 ECC error policy (definition) 267 e-mail event notification, managing in 3DM 77, 216 enclosure blinki
inoperable units (about) 138 installation disk management tools (3DM2 and CLI) installation 271 of controller 16 overview 20 troubleshooting hardware 221 software 222 installing formatting 38 making units available 38 partitioning 38 Inter-IC bus, definition 268 J JBOD 10, 28 JBOD disks exporting 90 JBOD policy 83 setting 90 JBOD policy (viewing in 3DM) 198 L LEDs colors and behavior 135 indicators 135 Linux driver compiling 50 installation 39 updating 178, 179 listening port for 3DM 217 logging in to 3DM 6
R RAID concepts and levels 4 configurations 5 determining level to use 11 RAID 0 5 RAID 1 6 RAID 10 8 RAID 5 6 RAID 50 9 RAID 6 7 RAID Level Migration (RLM) changing level 117 definition 269 overview 116 Rebuild completed (0005) 229 Rebuild failed (0004) 229 Rebuild paused (003B) 249 Rebuild started (000B) 232 rebuild task schedule adding (3DM) 159 removing (3DM) 159 viewing (3DM) 157 rebuild task schedule (definition) 269 Rebuilding (unit status) 135 rebuilding a unit 3BM 152 3DM 151, 205 about 150 cancell
definition 270 system requirements 2 T task schedules about, 3DM 200 adding 159 rebuild/migrate 159 removing 159 self-test 159 task duration 157 turning on and off 157, 158 verify 159 viewing 157 technical support 282 contacting 219, 284 troubleshooting 218 3DM 223 hardware installation 221 software installation 222 TwinStor 8 U UDMA mode, definition 270 ultra DMA protocol 237 Unclean shutdown detected (0008) 231 unconfigured disks, exporting 90 uninstalling 3DM on Linux 279 Windows 279 unit checking status
manually 148 stopping (3DM) 149 Verify-Paused (unit status) 136, 205 viewing 3DM remotely 71 volume specifying a boot volume size 94 volumes in a unit 191 multiple from one unit 86 resulting from auto-carvings 191 W Warranty 282 WHQL (Windows Hardware Quality Labs), Microsoft 281 WinAVAlarm 139 Windows alert utility (WinAVAlarm) 139 working in 3BM 61 write cache 15, 196 disable on degrade, part of Storsave profile 114 enabling in 3BM 109 enabling in 3DM 108 write journaling, part of StorSave profile 113 29
