SAS/SATA RAID Software User Guide Supports the 9650SE and 9690SA Models PN 720-0184-00 August 2008 User Guide 3ware®
Copyright ©2004-2008 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix How this User Guide is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Screenshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the driver when your primary storage will be managed by the 3ware RAID controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Installing the driver when your secondary storage will be managed by the 3ware RAID controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Chapter 5. 3ware BIOS Manager (3BM) Introduction . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Unit Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling and Disabling the Unit Write Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling or Disabling Auto Verify for a Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Overwrite ECC (Continue on Source Error When Rebuilding) . . . . . . . . Enabling and Disabling Queuing for a Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 10. Maintaining Your Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179 Determining the Current Version of Your 3ware Driver . . . . . . . . . . . . . . . . . . . . . . Updating the Firmware and Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading the Driver and Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating the Firmware Through 3DM 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error and Notification Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258 Error and Notification Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314 Software Installation . . .
viii 3ware SAS/SATA RAID Software User Guide, Version 9.5.
About this User Guide This document, 3ware SAS/SATA RAID Software User Guide, Version 9.5.1, provides instructions for configuring and maintaining RAID units on 3ware 9690SA and 9650SE series RAID controllers, using software and firmware version 9.5.1. This guide assumes that you have already installed your 3ware RAID controller and drives in your system and any enclosures, if you have them. If you have not yet done so, see the installation guide that came with your controller.
Table 1: Chapters and Appendices in this Guide x 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 in the BIOS (3BM) 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 throughout this guide: • 3BM refers to the 3ware BIOS Manager. • 3DM and 3DM 2 both refer to the 3ware Disk Manager, version 2.
To make use of the 3ware HTML Bookshelf 1 To launch the bookshelf at the opening page, do one of the following: • For Windows, from the Start menu, choose Programs > AMCC > Bookshelf shortcut. • Navigate to the 3wareHTMLBookshelf folder on the 3ware CD and double click the file index.html. • For Linux, open a browser window to the following location: /opt/AMCC/Documentation/index.html When you use either of these methods, a navigation panel at the left automatically opens.
1 Introducing the 3ware® SAS/ SATA RAID Controller AMCC 3ware RAID controllers deliver full-featured, true hardware RAID to servers and workstations. AMCC's RAID controllers offer Serial Attached SCSI (SAS) and Serial ATA (SATA) interfaces. Combined with an advanced RAID management feature-set that includes web-based, command-based, and API (application programming interface) software components, AMCC 3ware controllers provide compelling RAID solutions.
Introducing the 3ware® SAS/SATA RAID Controller • Support for the I2C-MUX-SM1 on the 9690SA • 8th-generation StorSwitch™ non-blocking switch fabric for maximum controller output • Simultaneous RAID 6 parity generation to maximize RAID 6 performance • StreamFusion™ optimizes RAID 5 and RAID 6 disk accesses to maximize application performance under heavy loads • StorSave™ BBU with write journaling optimizes data protection and performance • RAID levels 0, 1, 5, 6, 10, 50, and Single Disk (RAID 6 a
System Requirements Table 2: Required Slots for 3ware RAID Controller Models Controller Model PCI-E X1 PCI-E X4 PCI-E X8 PCI-E x16 PCI-X (64-bit) 9690SA (all models) NO NO YES Yes No 9650SE-2LPML YES YES YES Yes No 9650SE-4LPML NO YES YES Yes No 9650SE-4LPME NO YES YES Yes No 9650SE-8LPML NO YES YES Yes No 9650SE-12ML NO NO YES Yes No 9650SE-16ML NO NO YES Yes No 9650SE-24M8 NO NO YES Yes No 9590SE NO YES YES Yes No Notes: 3ware 9690SA and 9650SE R
Introducing the 3ware® SAS/SATA RAID Controller A list of drives that have been tested is available at http://www.3ware.com/products/sys_compatibility.asp Drives may be of any capacity or physical form factor. The length of internal unshielded interface cables may not exceed 1M (39”) and a maximum of 6M (234”) for external shielded cables.
Understanding RAID Concepts and Levels In addition: • JavaScript must be enabled • Cookies must be enabled • 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.
Introducing the 3ware® SAS/SATA RAID Controller • Distributed Parity. Parity works in combination with striping on RAID 5, RAID 6, and RAID 50. Parity information is written to each of the striped 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.
Understanding RAID Concepts and Levels 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.
Introducing the 3ware® SAS/SATA RAID Controller 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 or 9690SA 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.
Understanding RAID Concepts and Levels 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.
Introducing the 3ware® SAS/SATA RAID Controller 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.
Understanding RAID Concepts and Levels 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. Single drives are not fault tolerant and therefore not recommended for high availability systems unless additional precautions are taken to prevent system hangs and data loss.
Introducing the 3ware® SAS/SATA RAID Controller 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.
Understanding RAID Concepts and Levels Table 4: Possible Configurations Based on Number of Drives # Drives Possible RAID Configurations 5 RAID 6 RAID 5 with hot spare RAID 10 with hot spare Combination of RAID 0, RAID 1, hot spare, single disk 6 or more RAID 6 RAID 6 with hot spare RAID 50 Combination of RAID 0, 1, 5, 6,10, hot spare, single disk Using Drive Capacity Efficiently To make the most efficient use of drive capacity, it is advisable to use drives of the same capacity in a unit.
Introducing the 3ware® SAS/SATA RAID Controller down to 120 GB. For more information, see the discussion of drive coercion under “Creating a Hot Spare” on page 113. Note: All drives in a unit must be of the same type, either SAS or SATA. Support for Over 2 Terabytes Windows 2000, Windows XP (32-bit), Windows 2003 (32-bit and 64-bit without SP1) and Linux 2.4 and FreeBSD 4.x, do not currently recognize unit capacity in excess of 2 TB.
3ware Tools for Configuration and Management 3ware Tools for Configuration and Management 3ware software tools let you easily configure the drives attached to your 3ware RAID controller, specifying which drives should be used together as a RAID unit and the type of RAID configuration you want, and designating hot spares for use if a drive degrades.
Introducing the 3ware® SAS/SATA RAID Controller • 3ware CLI (Command Line Interface) The 3ware CLI provides the functionality available in 3DM through a Command Line Interface. You can view unit status and version information and perform maintenance functions such as adding or removing drives, and reconfiguring RAID units online. You can also use it to remotely administer controllers in a system. The 3ware CLI is described in 3ware SAS/SATA RAID Controller CLI Guide and in the 3ware HTML Bookshelf.
Monitoring, Maintenance, and Troubleshooting Features • Verification and Media Scans. The verify task verifies all redundant units, and checks for media errors on single disks, spares and 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 162.
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).
Getting Started with Your 3ware RAID Controller 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 Background Task Settings (For details, see “Scheduling Background Tasks” on page 173 and “Setting Background Task Rate” on page 172) Verify Task Schedules Basic - Friday 12:00 am 3DM, 3BM, CLI Advanced - Daily, starting 3DM, CLI at 12:00 am and running for 24 hours Follow Verify Task Schedule Enabled - Basic schedule 3DM, 3BM, CLI Rebuild/Migrate Task Schedules Daily, starting at 12:00 am and running
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: 9690SA-4I4E 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 Available drives: SATA - SAMSUNG HD160JJ 149.04 GB Phy 0 298.
First-Time RAID Configuration Using 3BM Figure 10. 3ware Controller Board Selection Screen You will see a screen similar to Figure 9, warning you that changing your disk array configuration may overwrite data on the disks. 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, or select all at once by selecting the heading above them.
Basic Steps for Creating a Unit 3 Make sure that the proper drives are listed. Figure 12. Create Disk Array Display 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.
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 the following unit policies: Write Cache, Drive Queuing Mode, Continue on Error When Rebuild (ECC Overwrite), Initialization Method, and Auto Verify. You can also select a StorSave profile and configure Rapid RAID Recovery. Each of these policies is already set to a default value, so you do not have to change them.
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 103. If the size of 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 92.
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 30.) 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. If you chose foreground initialization, then, depending on the RAID configuration you are creating, initialization of the unit may begin immediately and delay your ability to use your unit for several hours. (RAID 6 units and some RAID 5 and RAID 50 units begin immediate initialization.).
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. If the hot spare is of the same type (SAS or SATA) and of adequate size, it 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.
Making Drives Visible to the Operating System Making Drives Visible to the Operating System By default, if you leave individual drives unconfigured, they will not be available to the operating system. If you want to be able to use individual drives, configure them as single-disk units. If you have JBODs attached to an 8000 controller that you want to move to a 9000 controller, see “Moving Units from an 8000 Controller to a 9000 Controller” on page 141.
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. • 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. • If the operating system is already installed on a unit connected to another controller or to the motherboard, you start the operating system and then install the driver.
Driver Installation Under Windows Driver Installation Under Windows Note: Before installing the 3ware driver, you may 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 Windows XP (SP1 or newer), Windows Server 2003, Windows 2008, and Vista.
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 may need to create a 3ware driver diskette, unless you are installing Windows 2008 or Vista, in which case you can also use a USB drive or the 3ware CD. To create a driver diskette 1 Insert the AMCC 3ware software CD into your Windows system. Autorun should start the 3ware menu program.
Driver Installation Under Windows 4 When a box with AMCC 3ware 9000 Series RAID Controller appears, press Enter to select it. 5 Type S if you have additional devices to add. Otherwise, press Enter. 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.
Driver Installation Installing the 3ware Driver on a Windows System that Boots from a Different Device If you are installing the 3ware RAID controller on a system that already has a Windows operating system boot device, follow the instructions in this section. If you will be using a unit managed by the 3ware RAID controller as your boot device, see “Installing the 3ware Driver and Windows on a New RAID Unit” on page 34. With the 9.5.
Driver Installation Under Windows Figure 18. 3ware Device Driver Installation Wizard 3 Click Next. Depending upon your operating system, you will see one of the two following screens. The green checkmarks indicate successful installation of the driver. If unsuccessful, there will be a red checkmark. Figure 19. Windows Vista, 2003, and 2008 Final Install Screen www.3ware.
Driver Installation Figure 20. Windows XP Final Install Screen 4 Click Finish to exit the installer. Installing the 3ware driver under Windows with the Found New Hardware wizard When you start Windows after installing a 3ware RAID controller, Windows recognizes it as a Plug and Play device, and brings up the Found New Hardware Wizard. This wizard guides you in installing the 3ware driver (see Figure 21). Note that you will see screens for the installation of two drivers during this process. Figure 21.
Driver Installation Under Windows To install the 3ware driver under Windows with the Found New Hardware wizard 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 22), click Finish.
Driver Installation Figure 23. Welcome to the Found New Hardware Wizard 7 When the second Completing the Found New Hardware screen appears, click Finish. Figure 24. 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 41. 40 3ware SAS/SATA RAID Software User Guide, Version 9.5.
Driver Installation Under Windows 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 Programs>Administrative Tools > Computer Management.
Driver Installation Driver Installation Under Linux Note: Before installing the 3ware driver, you may 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.
Driver Installation Under Linux 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, • SuSE, and Fedora Core Linux are included on this CD. • 3ware web site. You can download the latest compiled and tested driver for supported Linux distributions from the 3ware web site at http://www.3ware.com/support/index.asp .
Driver Installation Driver Installation Under Red Hat Linux or Fedora Core Materials required • 3ware software CD-ROM • Floppy diskette, if you need to create a driver install diskette. • Red Hat Linux installation DVD or CD-ROM. (Not required if Red Hat Linux is already installed on another drive.) Creating a Red Hat Linux Driver Diskette If you are installing Linux on the new drive or unit managed by the 3ware RAID controller, you must create a 3ware driver install diskette.
Driver Installation Under Linux Installing the 3ware Kernel Driver Module while Installing Red Hat Linux on a New Unit Note: If Red Hat Linux is already installed and bootable on another drive, turn to “Installing the 3ware Kernel Driver Module on a Red Hat or Fedora Core Linux System that Boots From a Different Device” on page 46. Note: We have tested some older systems where a drive connected to the motherboard interfered with using a drive or unit managed by the 3ware RAID controller as a boot device.
Driver Installation Caution: If installing Fedora Core 8 DO NOT reboot after the installation completes. An update script is required in order for the new driver to be loaded automatically after reboot. - When prompted for Reboot after installation completes switch over to the alternate console. Type: - At the Linux # prompt type the following commands: mkdir /update mount /dev/fd0 /update (use same driver disk from step 4) cd /update .
Driver Installation Under Linux • For a i586 kernel, the kernel string will end in 586. For example: 2.6.16-586 • For a PAE kernel (Physical Address Extension), the kernel string will end in pae. For example: 2.6.16-pae Module Naming Conventions 3w-9xxx.* refers to the specific kernel driver module you will copy in the examples shown in steps 3 and 4. The name of the kernel driver module you will copy (3w-9xxx.*) varies, depending on the kernel; however you will always copy it to a file named 3w-9xxx.
Driver Installation For Fedora Core on AMD Opteron and Intel EM64T, type: cp /mnt/packages/drivers/linux/fedora//x86_64/ 3w-9xxx.ko /lib/modules//kernel/drivers/scsi/ 3w-9xxx.ko If prompted to overwrite, type y. 4 For 2.6 Kernels, add the following line to /etc/modprobe.conf alias scsi_hostadapter 3w-9xxx 5 Update the modules.dep file, by issuing the following command: /sbin/depmod -a 6 Run mkinitrd by entering the following: /sbin/mkinitrd -v -f /boot/initrd-.
Driver Installation Under Linux For Fedora Core on Intel x86 and AMD x86, type: cp /mnt/packages/drivers/linux/fedora//x86/3w-9xxx. /lib/modules//kernel/drivers/ scsi/3w-9xxx.ko If prompted to overwrite, type y. For Redhat Linux on AMD Opteron and Intel EM64T, type: cp /mnt/packages/drivers/linux/redhat//x86_64/ 3w-9xxx.ko /lib/modules//kernel/drivers/scsi/ 3w-9xxx.
Driver Installation You can load the driver from a floppy diskette on which you have installed the driver or from the 3ware CD. If installing SuSE 10.3, you will need to use the 3ware CD. To create a driver install diskette 1 Insert the 3ware software CD into your Linux system. A GUI such as X windows is required to load the 3ware menu. To manually mount the cd, type: mount -t iso9660 /dev/cdrom /mnt To start autorun, type: /mnt/autorun 2 When the 3ware Menu appears, click Driver Disk Images.
Driver Installation Under Linux Installing the 3ware Kernel Driver Module on a SuSE Linux System that Boots from a Different Device 1 Log in as root. 2 Edit /etc/sysconfig/kernel and make sure the file contains the following line: INITRD_MODULES="reiserfs 3w-9xxx" 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.
Driver Installation For openSuSE and SuSE Linux Enterprise Server 64-bit (x86_64), type: cp /mnt/packages/drivers/linux/suse//x86_64/ 3w-9xxx.ko /lib/modules//kernel/drivers/scsi/3w-9xxx.ko If prompted to overwrite, type y. 5 To load the kernel driver module, type: modprobe sd_mod insmod /lib/modules//kernel/drivers/scsi/3w9xxxx.ko Note: If the kernel driver module installation fails, confirm that the correct driver was installed from the CD-ROM.
Driver Installation Under FreeBSD Driver Installation Under FreeBSD 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 the installation guide from: http://www.3ware.com/support/userdocs.
Driver Installation Driver source files for FreeBSD 5.x, 6.x, and 7.x, located at: • • • • FreeBSD 5.x: packages/drivers/freebsd/src/5.x FreeBSD 6.x: packages/drivers/freebsd/src/6.x FreeBSD 7.x: packages/drivers/freebsd/src/7.x 3ware web site. You can download the latest compiled and tested driver modules and driver source files for FreeBSD from the 3ware web site at http://www.3ware.com/support/index.asp.
Driver Installation Under FreeBSD Installing the Kernel Driver Module while Installing FreeBSD on a Unit Managed by a 3ware RAID Controller Use this procedure if your boot unit is going to be managed by the 3ware RAID controller. It describes how to load the FreeBSD 6.3 or FreeBSD 7.0 kernel driver module to enable boot device support and how to then compile the current drivers into the kernel from source files. Note: This procedure is specific to FreeBSD 6.3 and FreeBSD 7.
Driver Installation 11 At the loader prompt, load twa.ko from the floppy using "load disk0:twa.ko" (assuming disk0 is the floppy drive). 12 Remove the floppy and then boot by typing "boot". 13 Once the system boots up, replace the twa driver sources at /sys/dev/twa and /sys/modules/twa with the new sources and build the kernel with the new driver sources. See “Updating the Kernel with the New Driver Source” on page 199 for more details. 14 Reboot your system.
Driver Installation Under VMware ESX 3.x Server Driver Installation Under VMware ESX 3.x Server This section provides details about how to install the driver for your 3ware RAID controller under VMware ESX Server 3.x and make the RAID units available to the operating system.
Driver Installation 6 When prompted, choose your keyboard type and press Enter. 7 At the “Update CD successfully loaded” screen, insert the applicable VMware ESX Server 3.x installation CD and press Enter to continue the installation. 8 After you have finished your VMware ESX Server 3.x installation, reboot the server and install 3DM 2 and CLI. See “Installing Software on FreeBSD” on page 330.
Driver Installation Under VMware ESX 3.x Server 8 Unmount the CD. cd / umount /mnt/cdrom and remove the CD from the drive. 9 Reboot the server. You can now create one or more RAID units. Instructions are available in the 3ware SAS/SATA RAID Software User Guide, Version 9.5, under “Configuring Units” on page 85. Note: If you wish to verify successful installation of the driver, you can use one of the following commands: esxupdate -l query The driver package should be mentioned in the resulting message.
5 3ware BIOS Manager (3BM) Introduction This section describes the basics of using 3ware BIOS Manager (3BM), one of the tools you can use to configure and maintain the units connected to your 3ware RAID controller.
Starting 3BM 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 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. If 3BM detects a degraded array, a red message box appears, to alert you to the problem.
3ware BIOS Manager (3BM) Introduction You see a screen similar to the warning message below, warning you that changing your disk array configuration may overwrite data on the disks. Figure 28. 6 Warning Message When you Start 3BM Press any key to continue to the 3BM BIOS Manager screen. Exiting the 3BM Configuration Utility When you are ready to exit the 3BM configuration utility, you have the option to save the configuration changes you have made, or to discard the changes.
Working in the 3BM Screens Exception: Changes made to controller policies are saved when you leave the Policy screen. Pressing F8 is not required to save those changes. For more about changing policies, see “Setting the Auto Rebuild Policy” on page 91. Working in the 3BM Screens The main 3BM screen (Figure 29) 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 29.
3ware BIOS Manager (3BM) Introduction • Incomplete Drives and Others lists drives that are remaining from a unit with missing or failed drives and drives that are not usable. When some of the drives are remaining from a unit, you can power down and add the missing drives to complete the unit. To use drives that are listed here in other units, you must first delete them. For more information, see “Deleting a Unit” on page 133.
Working in the 3BM Screens Table 7: Working in 3BM To do this Use these keys Highlight one of the primary buttons on the main screen: • • • • • Create Unit Delete Unit Maintain Unit Settings Information Alt+C Alt+D Alt+M Alt+S Alt+I Specify (or unspecify) a drive as a hot spare S Blink the LED associated with a drive F4, from the Drive Information screen (requires use of a supported enclosure) Return to starting values for this session in the 3ware BIOS Manager F6 Note: F6 cannot bring back prev
3ware BIOS Manager (3BM) Introduction Adjusting BIOS Option Settings 3BM includes a few 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 3BM BIOS Manager screen. Figure 30. 3BM BIOS Option Settings Power-On Self Test (POST) Display Options Display Control. Specifies what level of detail to display on the start-up screen.
Adjusting BIOS Option Settings BIOS Loading Options Load Control. This setting is enabled by default. It allows you to boot from RAID units or drives managed by the controller. If this setting is disabled, you will only be able to boot from hard drives or peripheral devices (such as CDROM or floppy) that are not managed by the controller. You may wish to disable this setting if you have multiple controllers in a "headless" system with no monitor or keyboard. Options for Entering BIOS Hot Key.
3ware BIOS Manager (3BM) Introduction Displaying Information About the Controller and Related Devices The 3BM Information menu gives you access to detailed information about the controller, BBU, drives, enclosures, and phys. To see information about the controller or a related device 1 On the 3BM BIOS Manager screen, Tab to Information and press Enter. A pop-up menu appears, listing the available information screens.
Getting Help While Using 3BM Getting Help While Using 3BM You can get help with using 3BM while you are in the BIOS manager. • Press F1 or Alt-F1 at any time. A description of the basic 3BM tasks appears. When you’re finished using help, press Esc to close the help window. www.3ware.
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.
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 322. 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 https://localhost:888/ If remote access is enabled, you can also replace “localhost” with the IP address of the computer that contains the 3ware controller. For example: https://:888/ Note: If you receive a page not found message, make sure you entered the URL correctly by specifying https, not http. If you did, 3DM may not be running in the background.
3DM 2 (3ware Disk Manager) Introduction Note: If you close your browser, 3DM continues to run in the background on the system. Managing the 3DM 2 Daemon under Linux, VMware, and FreeBSD 3DM should start automatically after installation and upon bootup. If it does not, use the steps below to manage it. To manage the 3DM daemon manually 1 Login as root on the machine on which 3DM is installed. 2 For Linux: /etc/init.d/3dm2 start|stop|restart For FreeBSD: /etc/rc.
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 3DM 2 through your web browser • In the address line of your browser, enter the URL or IP address of the system containing the 3ware RAID controller.
3DM 2 (3ware Disk Manager) Introduction Figure 33. 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 The Management menu gives you access to tasks used for managing controller-level settings (background task rate, unit polices such as enabling 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.
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 35.
Working with the 3DM Screens 3DM Screens and What They're Used For The table below shows a list of the pages you work with in 3DM and describes what they are used for. Details about each page and the fields and features on it are provided in Chapter 12, “3DM 2 Reference”. The page names in the table provide links to details about that page.
3DM 2 (3ware Disk Manager) Introduction Table 8: List of 3DM Pages 3DM Page Description Controller Phy Summary page Shows the properties of controller phys for 9690SA RAID controllers. There are two ways to access this page. If you have a directattached drive you can access this page from the Information > Drive Information page by clicking the phy ID for the drive. If all drives are connected via expanders, navigate to the Management > Controller Settings page.
Setting Up 3DM Preferences Table 8: List of 3DM Pages 3DM Page Description Enclosure Details page Shows details about a particular enclosure, including status information. You can also use this page to blink the LED for a particular drive. To view this page, click the ID number of the Enclosure on the Enclosure Summary page.
3DM 2 (3ware Disk Manager) Introduction To set or change the password 1 Click 3DM 2 Settings on the 3DM menu bar. 2 On the 3DM 2 Settings page, in the Password section, select the type of password you want to change: User or Administrator. 3 Type the current password in the Current Password field. If you are changing the password for the first time, the factory-set default password is 3ware. 4 Enter the new password in the New Password field and again in the Confirm New Password field.
Setting Up 3DM Preferences To set up event notification 1 Click 3DM 2 Settings on the menu bar. 2 In the E-mail Notification section of the 3DM 2 Settings page, enter or change the settings you want. • Enable or Disable all notifications. • Set the severity level of events for which e-mail notifications are sent. • Specify the email address of the sender. This will appear in the “From” field of the e-mail. • Enter the e-mail address(es) to which notifications are sent.
3DM 2 (3ware Disk Manager) Introduction Enabling and Disabling Remote Access When remote access is enabled, a user can connect to 3DM over the internet or an intranet, to check status or administer the controller and associated drives. (See “Viewing 3DM Remotely Using a Web Browser” on page 75.) If remote access is disabled and a user attempts to connect to 3DM remotely, they will see the following error message: “Remote Access to 3DM has been disabled.
Setting Up 3DM Preferences Setting the Frequency of Page Refreshes Since the status of the drives attached to your 3ware RAID controller can change while you are viewing information about them in 3DM, it is important to refresh the page information regularly. That way you can be assured that the information you see in 3DM is current. You can manually refresh the information on a page by clicking Refresh Page in the menu bar. But you can also have 3DM refresh the information on a regular basis.
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 36. 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 Unit Information page.
Configuring Your Controller 5 On the pop-up menu, select Controller and press Enter. The Controller Information page displays. Figure 37. Controller Information page About Controller Policies The following policies affect all units and drives on a controller and can be adjusted as appropriate for your equipment. Controller policies are shown at the bottom of the Controller Settings page in 3DM (Figure 38) and on the Policy Control screen in 3BM (Figure 39). • Auto Rebuild.
About Controller Policies policies Number of drives per spin-up and Delay between spin-up settings. These policies can only be set using 3BM or the CLI. Note: This policy does not apply to drives attached to an expander. • • • 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. From 1 to x, depending on the number of ports on the controller. Delay between spin-up.
Configuring Your Controller Viewing Controller Policies You can view the current state of controller policies in 3DM, in the Other Controller Settings section at the bottom of the Controller Settings page (See Figure 38). Only the Auto Rebuild, Auto-Carving, and Carve Size policies can be changed on this page. The other policies can be changed in 3BM or through the CLI. For a summary of the initial default settings, see Table 6, “Default Settings for Policies and Background Tasks,” on page 20.
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 39. 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 39. 3BM Policy Control Screen Setting the Auto Rebuild Policy The Auto Rebuild policy determines how the controller firmware will attempt to rebuild degraded units.
Configuring Your Controller To enable Auto Rebuild through 3DM 1 Choose Management > Controller Settings from the menu bar in 3DM. 2 In the Other Controller Settings section at the bottom of the screen, select the Enabled option for Auto Rebuild. The page refreshes, and a message at the top confirms the change you have made. 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.
Using Auto-Carving for Multi LUN Support Each volume can be treated as an individual disk with its own file system. The default carve size is 2 TB; you can change this to a setting in the range of 1 TB to 32 TB (1024 GB to 32768 GB). 3ware firmware supports a maximum of 32 volumes per controller, up to a total of 32TB. Note: CLI now provides the ability to specify variable sizes for the first 4 volumes of a unit when autocarving.
Configuring Your Controller Figure 40. Auto-Carve policy in 3BM 2 Create a new unit or migrate an existing unit to include the drives you want to use. 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.
Setting the Size of Volumes Created with Auto-Carving Setting the Size of Volumes Created with Auto-Carving You can use auto-carving to divide units larger than 1 TB into multiple volumes. You control the size of the volumes to be created by setting the carve size (referred to as carving factor in 3BM). The carve size can be between 1 TB (1024 GB) and 32 TB (32768 GB); the default is 2 TB. When you change this policy, it applies to units you create in the future. Existing units will not be affected.
Configuring Your Controller It is possible to enable or disable automatic detection of drives on the controller’s ports for staggered spinup during hot swapping of drives. This feature is only available in the CLI using the autodetect=on|off command. For more information, see /cx set autodetect=on|off disk=|all 3ware SAS/SATA RAID Controller CLI Guide. Note: Some hard drives require that the power management jumper (PM2) be set to enable staggered spinup, in order for the SATA OOB option to be used.
Viewing Information About a Phy If JBOD disks are not exported to the operating system, they will appear as available drives in 3DM, and can be configured as single disks or spares, and included in other RAID configurations. If you change the policy to allow JBOD disks to be exported to the operating system, they will appear as units in 3DM if those drives were previously used as JBODs on another controller. AMCC recommends that new drives be configured as Singles and not JBODs.
Configuring Your Controller Figure 41. Phy Summary Page For details about the columns on this page, see “Controller Phy Summary page” on page 223. To see information for a phy in 3BM 1 On the main 3BM screen, Tab to Information and press Enter. 2 On the pop-up menu, select Phys and press Enter. 3 On the Controller Phy Information page, use the arrow keys to select the Phy you want to see details about. The information displays on the right. Figure 42.
Changing the Phy Link Speed Changing the Phy Link Speed You can change the link speed between the controller and an expander or between the controller and a drive that is directly connected to the controller. Typically, the phy link speed is set to Auto. If desired for compatibility, troubleshooting or performance analysis, you can specify a specific link speed (1.5 or 3.0 Gbps).
Configuring Your Controller To change the phy link speed in 3BM 1 On the main 3BM screen, Tab to Settings and press Enter. 2 On the pop-up menu, select Phy Policies and press Enter. 3 On the Controller Phy Policies page, use the arrow keys to select the Phy for which you want to set the link speed. 4 Press Enter to display a popup of the possible settings, select the one you want, and press Enter again. Figure 44. Controller Phy Policies page 100 3ware SAS/SATA RAID Software User Guide, Version 9.
8 Configuring Units This section includes information and procedures on configuring units attached to your 3ware RAID controller.
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 105 and “Creating a Unit through 3BM” on page 107.
Configuring a New Unit Name of the unit (optional) Units can be given names for easier identification. These names will be visible in 3DM, CLI, and 3BM. Type of configuration (RAID Level) Available configuration types include RAID 0, RAID 1, RAID 5, RAID 6, RAID 10, RAID 50, and Single Disk. For information about the different RAID levels, see “Understanding RAID Concepts and Levels” on page 5 Warning: Creating a unit writes the DCB and makes any earlier data on the drives inaccessible.
Configuring Units Multiple Volumes When you create a unit through CLI, you have the option of creating up to four volumes with variable, defined sizes. If you have enabled the AutoCarving policy, these units will be created first, and then the carve size will be used to segment the remaining drive space into additional volumes. For details, see the /cx add command in the 3ware SAS/SATA RAID Controller CLI Guide.
Configuring a New Unit Creating a Unit through 3DM In 3DM, creating a unit starts from the Management > Maintenance page (Figure 45). Figure 45. 3DM Maintenance Page To create a unit 1 In 3DM, choose Management > Maintenance. 2 In the Available Drives list, select the drives you want to include in the unit by marking the checkbox in front of the VPort number for each one.
Configuring Units Figure 46. 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).
Configuring a New Unit 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. If you have auto-carving enabled and the size of your unit exceeds the carve size, you may see multiple unit volumes in your operating system. For details, see “Using Auto-Carving for Multi LUN Support” on page 92. In Linux, a device node will now be associated with each unit created.
Configuring Units Tip: If you want to use all available drives, press Alt-A to select them all. Figure 49. Asterisks Next to Selected Drives 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 50. Create Disk Array Display 4 108 (Optional) Press Enter and type a name for the unit; then press Enter again to set the name.
Configuring a New Unit 5 Tab to the RAID Configuration field and press Enter to display a list of available configurations for the number of drives you selected. Figure 51. Configuration Choices for Four Drives 6 Use the arrow keys to select the configuration you want and press Enter. 7 Tab to the field Stripe Size and select the desired striping size (16, 64, or 256 KB). Figure 52.
Configuring Units You are returned to the main 3BM screen. Note: The unit is not actually created and no data is overwritten until you have finished making all your changes and press F8. 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 53.
Configuring a New Unit Ordering Units in 3BM If you configure multiple units in 3BM and you want to install the OS on one of them so that you can boot from that unit, that unit must be the first unit. You can change the order of the units in 3BM. To change the order of units in 3BM 1 At the main 3BM screen, in the list of exportable units, highlight the unit you want to move. 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.
Configuring Units Note: If you plan on migrating your unit to a larger array or another RAID type in the future remember to select the dynamic disk option. Only dynamic disks can be resized into larger partitions. Older Windows systems cannot convert basic disks into dynamic disks after the file system has been created. 6 Follow the steps that appear on-screen to create a volume and to assign a drive letter. The volume is automatically mounted after formatting completes.
Creating a Hot Spare Use of the -j option to turn on journaling is recommended for large partitions. For example: mkfs -j /dev/sda1 If the partition is over 2TB, use parted to also make the file system: parted /dev/sda1 (parted) mkfs Partition number? 1 File system? [ext2]? writing per-group metadata (begins)...0% to 100% is displayed) (parted) quit (when completed) 5 Mount the volume: mount /dev/sda1 /mnt To partition, format, and mount under FreeBSD 1 Boot the system and log in as root.
Configuring Units In order to replace a failed drive, a hot spare must have the same or larger storage capacity than the drive it is replacing, and must be of the same type (SAS or SATA). The Auto Rebuild policy allows automatic rebuilding to occur with available drives that are not designated as spares. For more information, see “Setting the Auto Rebuild Policy” on page 91.
Naming a Unit Specifying a Hot Spare through 3BM 1 On the main 3BM screen, in the list of Available Drives, highlight the drive you want to use. 2 Type s to specify that the selected drive will be the hot spare. You’ll see the words “Hot Spare” appear next to the drive in the Available Drives list. Figure 54. 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.
Configuring Units 4 In the text box, enter or type over the name shown. A name can be up to 21 characters, and can include dashes and underscores. 5 Click the Save Names button. Note: If you want to cancel your change before saving it, click the Reset Names button. 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.
Setting Unit Policies • Auto Verify. Determines whether the unit will be automatically verified at a time determined by the Verify Schedule. Enabling this feature helps insure that the unit is verified on a regular basis. For details, see “Enabling or Disabling Auto Verify for a Unit” on page 120. • Override ECC (Continue on Source Error When Rebuilding). Determines whether ECC errors are ignored when they are encountered during a rebuild.
Configuring Units Figure 55. Unit Policies on Controller Settings Page in 3DM Enabling and Disabling the Unit Write Cache Write cache is used to store data locally in memory on the controller 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.
Setting Unit Policies If you have a BBU (Battery Backup Unit) installed on the controller, the battery preserves the contents of the controller cache memory for a limited period of time (up to 72 hours) in the event of a system power loss. When a BBU is installed, if the battery is not “Ready,” write cache is disabled and cannot be enabled. The unit's StorSave profile can also determine whether the write cache can be enabled or disabled.
Configuring Units Figure 56. Unit Write Cache State in 3BM The current setting—Enabled or Disabled—is shown. (The initial default setting is for write cache to be enabled.) 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.
Setting Unit Policies To enable or disable the Auto Verify policy for an existing unit through 3DM 1 Choose Management > Controller Settings from the menu bar. 2 In the Unit Policies section of the Controller Settings page check the Auto Verify box for the appropriate unit. (To disable this policy, uncheck the box.) The page refreshes, and a message at the top confirms the change you have made.
Configuring Units To set the Overwrite ECC policy in 3DM 1 Choose Management > Controller Settings from the menu bar in 3DM. 2 In the Unit Policies section of the Controller Settings page, check the boxes to select the policies you want to be in effect for each unit The page refreshes, and a message at the top confirms the change you have made. To set the Continue on Source Error When Rebuilding policy in 3BM 1 At the main 3BM screen, select the unit by highlighting it and pressing Enter.
Setting Unit Policies Note: Not all drives support command queuing. If a drive does not support command queuing, the policy setting for the controller is ignored. Queuing information for SAS is not available. 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.
Configuring Units About StorSave Profile Levels The three profiles automatically adjust several different factors that affect protection and performance on a per unit basis. These are summarized in the table below and further explained after the table. 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.
Setting Unit Policies Using write journaling helps protect your data, however it can have an impact on performance. The Protection profile enables write journaling; the Performance and Balanced Profile disables it. The Balanced profile disables write journaling 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.
Configuring Units 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. Rapid RAID Recovery The Rapid Raid Recovery feature increases the speed with which a redundant unit can be made redundant again when a rebuild is required.
Setting Unit Policies • Units with Rapid RAID Recovery enabled will not be readable if moved to controllers using pre-9.5.1 firmware. If you wish to move the unit to a controller with pre-9.5.1 firmware, you must first disable Rapid RAID Recovery. • Units created on controllers with pre-9.5.1 firmware will not be able to take advantage of Rapid RAID Recovery when the controller is updated to 9.5.1 or later. These units will show Rapid RAID Recovery as disabled.
Configuring Units Changing An Existing Configuration by Migrating You can convert one RAID configuration into another while the unit is online. This process is known as RAID Level Migration (RLM). You can use RAID Level Migration to make two main types of configuration changes: • RAID Level (for example, a RAID 1 to a RAID 5) • Unit Capacity Expansion (for example, adding a 4th drive to a 3-drive RAID 5) You can also use RLM to change the stripe size of a unit.
Changing An Existing Configuration by Migrating Figure 57. RAID Level Migration Example Typically, a unit is reconfigured with the same or more storage capacity. Sometimes additional drives are added. The following table shows valid reconfigurations, some of which will require the addition of more drives.
Configuring Units 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. In addition, the file system on the drive will not be clean. Instead, shut down the system, replace one of the drives, and start the rebuild from 3BM. Note: You can only migrate a unit to a RAID level that has the same or more capacity as the existing one.
Changing An Existing Configuration by Migrating 4 Select any drives to be added to the unit. 5 Select the new RAID level. 6 Optionally, select a new Stripe size. 7 Click OK. The Maintenance page updates to show the new unit and the Migration progress. 8 Inform the operating system of the change, as described below under “Informing the Operating System of Changed Configuration”.
Configuring Units 7 If you booted from the unit that is being migrated, when migration is complete, reboot your system. Then turn to Step 4 under “Informing the Operating System of Changed Configuration” on page 132. 8 After the migration is complete, inform the operating system of the change, as described below. You can check the status of the migration on the Maintenance page.
Deleting a Unit • Go to Administrative Tools > Computer Management, and then select Disk Management in the list on the left. Only dynamic disks can be expanded with Windows Disk Management. If the unit is shown as a basic disk, right-click on the disk icon and change it to a dynamic disk. • Older Windows systems cannot convert basic disks into dynamic disks after the file system has been created.
Configuring Units Deleting a Unit through 3DM In 3DM, the command for deleting a unit is on the Maintenance page. Be sure to follow steps 1 through 3 in the instructions before using the Delete command. To delete a unit through 3DM 1 Make sure the operating system is not accessing the unit you want to delete. 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. 2 Backup any data you want to keep. 3 Unmount the unit.
Deleting a Unit Figure 58. Unit Successfully Deleted through 3DM Deleting a Unit through 3BM In 3BM, the command for deleting a unit is on the main 3BM screen. To delete a unit through 3BM 1 At the main 3BM screen, select the unit in the list of Exportable Units by highlighting it and pressing Enter or Space. An asterisk appears in the left-most column to indicate that it is selected. 2 Tab to the Delete Unit button and press Enter.
Configuring Units Figure 59. 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. 5 Press F8 to save your changes, or press Esc and then Yes.
Removing a Unit 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. To remove a unit through 3DM Note: If your drives are not in hot swap bays, you do not need to remove a unit via 3DM. Simply power down the system and remove the applicable drives. Refer to your system’s user guide for details on removing fixed disks. If your drives are in hot swap bays, follow the steps below.
Configuring Units If you change your mind before physically removing the drives and want to reuse the drives and unit on the current controller, just click Rescan Controller. Removing a Unit Through 3BM Note: Even though removing a unit is supported in 3BM, you can also simply power down to remove the applicable drives since you are not booted yet. To remove a unit through 3BM 1 If your drives are not in hot swap bays, you do not need to remove a unit via 3BM.
Moving a Unit from One Controller to Another 3DM includes two features that help you move a unit without powering down the system, allowing you to hot swap the unit. The Remove Unit feature lets you prepare a unit to be disconnected from the controller, and the Rescan feature checks the controller for drives that are now connected, and updates the 3DM screens with current information. For details, see “Removing a Unit” on page 136 and “Rescanning the Controller” on page 145.
Configuring Units 2 Update the driver for the 9650SE or 9690SA RAID controller. If you are using Linux, you will also need to update the initial RAM disk with the mkinitrd command. 3 Power down the computer. 4 Remove the original controller. 5 If you are working with a Linux system, install the 9650SE or 9690SA controller. 6 Attach the drives that were on the original controller to the 9650SE or 9690SA controller. 7 Power up the computer and verify that the upgrade is complete.
Moving a Unit from One Controller to Another Moving Units from an 8000 Controller to a 9000 Controller It is possible to move your RAID units from a 3ware 8000 series RAID controller to a 3ware 9000 series controller. You will then have the advantages of the 9000 series controller. The drive units must be in normal mode before moving the units. Incomplete, degraded, rebuilding, or initializing units cannot be converted. In addition, RAID 0, 10, and 5 units must use a standard 64 KB stripe size.
Configuring Units Moving Legacy JBOD Units to a 9000 Controller The steps for moving legacy JBOD units vary, depending on the operating system you are using. To move legacy JBOD units under Windows 1 Install the 9000 controller in your system, while leaving the 8000 controller installed. 2 Install the Windows driver. (For details, see “Driver Installation Under Windows” on page 33.) 3 Power down the system, disconnect the drives from the 8000 controller and remove that controller from the system.
Removing a Drive 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 bay or into your enclosure. 2 In 3DM, choose Management > Maintenance. 3 On the Maintenance page, click Rescan Controller. The drive will appear in the list of available drives.
Configuring Units 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 Locate the drive you want to remove and click the Remove Drive link (Figure ). 3 When 3DM asks you to confirm that you want to remove the drive, click OK. You can now remove the drive from your system.
Rescanning the Controller Rescanning the Controller When you make a change by physically adding or removing drives or units, you can have 3DM rescan the controller to update the list of units and available drives shown on the Maintenance page. This is useful in a variety of circumstances. For example, if you add new drives to the controller, you can make them available by rescanning 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.
Checking Unit and Drive Status through 3DM The next figure illustrates how you can drill down to get additional detail about units and drives in your system. Figure 61. 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.
Maintaining Units Viewing a List of Drives You can see a list of drives connected to your 3ware RAID controller, and see additional detail about each of those drives. To view a list of drives in 3DM • Choose Information > Drive Information from the main menu in 3DM. On the Drive Information page, you can access details about any of the drives listed by clicking the link for that drive in the VPort column. For more information about the Drive Information page, see page 219. Figure 62.
Checking Unit and Drive Status through 3DM Tip: You can scroll both sections of the Drive Information page to bring additional drive information or drives into view. Press Tab to move between the two sections. Figure 63. Drive Information page (3BM) Enclosure Drive LED Status Indicators If you have a supported enclosure, the LEDs on your enclosure may be able to provide some status information about your drives and units. Note: The following table is an example of how LEDs may be used.
Maintaining Units Table 11: Meaning of LED Colors and Behavior Color Drive Status Solid red Drive fault This drive has failed. You should replace it and rebuild the unit. Blinking red Predicted drive fault 3ware software predicts that this drive will fail soon. You may want to replace it. Unit Statuses The following is a list of unit statuses you may see in 3DM: • OK. The unit is optimal and is functioning normally. • Rebuilding.
About Degraded Units • Migrate-Paused. The unit is in the process of migrating, however scheduling is enabled, and the present time is not during a scheduled timeslot. Migrating will start at the next scheduled time slot. Migration is also paused for up to ten minutes after a reboot, even during a scheduled timeslot. • Degraded. One or more drives in the redundant unit is no longer being used by the controller. For more information, see “About Degraded Units” on page 151. • Inoperable.
Maintaining Units You can still read and write data from a degraded unit, but the unit will not be fault tolerant until it is rebuilt using the Rebuild feature. 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 and Degraded in the 3DM pages. If supported by your enclosure, the LED for failed drives may turn red. You should replace the failed drive and rebuild the unit as soon as it is convenient to do so.
Locating a Drive by Blinking Its LED • 2 Choose Monitor > Enclosure from the main menu in 3DM. On the list of enclosures, click the ID number of the enclosure. On the Enclosure Detail page, identify the drive you want to physically locate. Check the box in the Identify column. 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.
Maintaining Units Alarms, Errors, and Other Events 3ware provides several levels of detail about alarms, errors, and other events. This information is available through the 3DM web application and the CLI. On Windows systems, the WinAVAlarm alert utility can also be used to notify you of events. The next few pages describe these capabilities.
Alarms, Errors, and Other Events If your 3ware RAID controller is installed in a Windows system, the WinAVAlarm alert utility can notify you of events immediately with an audible alarm and a popup message. For details, see “Using the Alert Utility Under Windows” on page 155. A list of the possible error and other event messages is provided under “Error and Notification Messages” on page 258. To view alarms, errors and other events in 3DM 1 Choose Monitor > Alarms.
Maintaining Units To change the alert utility settings 1 Double-click on the WinAVAlarm icon in the system tray. Figure 64. 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. If you want to turn off the sound alarm and only have a pop-up message appear, check the Audio Off button. Figure 65. WinAVAlarm Popup Window If you wish, you can open 3DM from this window by clicking Open Browser.
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.
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 Some RAID levels must be initialized for best performance. (For specifics, see “Initialization of Different RAID Types” on page 160.) When these units are created in the BIOS (through 3BM), you can choose to do a foreground initialization, which will take place before the operating system has loaded, or a background initialization, which allows you to put the unit in service immediately, but will slow down the unit performance until it completes.
Maintaining Units 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.) This will not affect the data on the drives, and the units will perform normally, although performance will be slowed until the initialization and verification are completed.
Background Tasks Notes: For RAID 5 and RAID 6 with more 5 or more drives, it is strongly required that you initialize the unit. Initialization is critical to insuring data integrity on the unit. The initialization can be a background or foreground initialization. For RAID 5 with 3 or 4 drives, initialization before use is not required. However, initialization is required before a unit can be verified.
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 Note: Not verifying the unit periodically can lead to an unstable unit and may cause data loss. It is strongly recommended that you schedule a verify at least 1 time per week. You can take advantage of the the Auto Verify and Basic Verify Schedule to accomplish this. 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.
Maintaining Units For RAID 1 and 10, verification involves copying the data from the lower port(s) to the higher port(s) of the mirror. For RAID 5 and RAID 50, this involves recalculating and rewriting the parity for the entire unit. If the unit is not redundant, a file-system check is recommended to correct the issue. If the errors persist and cannot be overwritten from a backup copy, perform a final incremental backup.
Background Tasks For users who need more control over when Verify tasks run, an Advanced Verify schedule is also available, which gives you the ability to define seven times during the week when verifications can occur, and allows you to specify the duration of each, effectively creating a series of "schedule windows". This is useful if you want to insure that background tasks such as verification occur during times of low system usage.
Maintaining Units 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 Basic Verify is selected on the Scheduling page, the verification process begins almost immediately. If Advanced Verify is selected, the unit will not start actively verifying until the next scheduled time.
Background Tasks 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.
Maintaining Units A RAID 50 unit can sustain multiple drive failures, as long there is only one failed drive in each RAID 5 set. 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.
Background Tasks If rebuild scheduling is not enabled on the Scheduling page, the rebuild process begins almost immediately in the background. If rebuild 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.
Maintaining Units Figure 69. 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.
Background Tasks Figure 70. Rebuild Option on the Maintain Menu The Rebuild Disk Array screen displays. Figure 71. 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. www.3ware.
Maintaining Units Cancelling a Rebuild and Restarting It with a Different Drive When you start a rebuild from 3BM, you cannot cancel it in 3BM interface. However, if you have drives in hot swap bays, you can remove and replace the drive, rescan the controller (Alt-R), and then select a new drive to be used in the rebuild. You can also boot the operating system, launch 3DM, and cancel a rebuild by using the Remove Drive link on the Maintenance page.
Scheduling Background Tasks 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.
Maintaining Units 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 158. You can also set the rate at which background tasks are performed compared to I/O tasks. For more information, see “Setting Background Task Rate” on page 172.
Scheduling Background Tasks Figure 72. Selecting Task Schedules to View Turning On or Off Use of a Rebuild/Migrate Task Schedule Turning on the schedule for Rebuild/Migrate tasks forces initializations, rebuilds and migrates to be performed only during the time specified by the schedule. If the schedule is not turned on, rebuilds, migration, and initialization can happen whenever they are required or are manually started.
Maintaining Units 2 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 178.
Scheduling Background Tasks To remove a task slot from a schedule 1 Choose Management > Schedule from the menu bar. The Scheduling page appears, showing the schedule for Rebuild/Migrate Tasks. To view Verify Tasks or Self-test Tasks, select one from the drop-down list at the top of the page. To view the seven verify schedule slots, select Advanced. 2 Select the checkbox next to the schedule(s) you want to remove. 3 Click the Remove Checked button.
Maintaining Units Selecting Self-tests to be Performed For 3ware RAID controllers older than the 9690SA, two self-tests can be set: one to check whether UDMA Mode can be upgraded (PATA drives only), and another to check whether SMART thresholds have been exceeded. For the 9690SA, you can only check the SMART thresholds for drives. (For more information about these self-tests, see the 3DM Reference section, “Scheduling page” on page 228.) Initially, these tests are set to run every 24 hours.
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
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” on page 189. Updating the Firmware and Driver Important: Updating the firmware can render the device driver and/or management tools incompatible.
Updating the Firmware and Driver • Windows users can also update the driver through Windows Device Manager. For details, see “Updating the 3ware Driver Under Windows” on page 189. • Linux or FreeBSD users can update the driver at the command line. For details see: • Updating the 3ware Driver Under Red Hat or Fedora Core • Updating the 3ware Driver Under SuSE • Updating 3ware Drivers under FreeBSD • VMware 3.x must be updated at the command line, as it doesn’t have a GUI in it’s default installation.
Maintaining Your Controller 6 Click Next. 7 When details about the download you requested appear, click the link for the item you want to download. Depending on the item you selected, you may see either .zip (for Windows) or .tgz (for Linux or FreeBSD) files to download. Note: If using Winzip or another Windows utility to extract the Linux file, use the .zip version instead of the .tgz version. Otherwise the files will not be compatible with Linux.
Updating the Firmware and Driver 3 In the Update Firmware section of Controller Settings page, browse to the location where you have saved the downloaded firmware update. The update name will be something like promxxx.img. 4 Click Begin Update. The Compatibility Information window appears. 5 Click Proceed Update. The 3ware RAID controller firmware is updated.
Maintaining Your Controller 6 To continue, type: y The program checks that the update program version of the firmware is compatible. If it is, it begins installing the firmware. This will take 1 to 3 minutes. Do not power off your computer until the firmware finishes updating. 7 If multiple controllers are being installed, repeat steps 3-5 for the next controller. 8 Type q to quit, remove the bootable CD and reboot your system.
Updating the Firmware and Driver Figure 73. Update Utility Progress Dialog (System Check) When the 3ware Driver/Firmware Update dialog box appears, it shows available updates for the device driver and for the firmware. Figure 74. 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. www.3ware.
Maintaining Your Controller Figure 75. Update Utility Showing Drivers Already Current In this example, both the driver and firmware are already current on the system, so the recommendation is not to update either one. . 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 76. Update Utility Showing Only Driver Available Only the driver is available, because the firmware image was not found.
Updating the Firmware and Driver Figure 77. Update Utility Showing Only Firmware Available Only the firmware is available, because the driver image was not found. 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.
Maintaining Your Controller Figure 78. Dialog Prompting for Restart 8 If the driver you are installing is unsigned, you will receive a message to that effect. To complete the installation with an unsigned driver, click OK. 9 If a final message box confirms that the process is complete, click OK. (This message appears if you do not need to restart your computer.) Figure 79.
Updating the Firmware and Driver When the 3ware Driver/Firmware Update dialog box appears, it lists the number of controllers in your system, shows available updates for the device driver, and available firmware updates for the first controller. Figure 80. Update Utility Showing Available Drivers . Type of controller Number of controllers Current controller Number of controllers that will be updated.
Maintaining Your Controller 2 Backup any critical data prior to updating the 3ware driver. 3 Log in to your system as system administrator. 4 From the Start menu, open the Control Panel window. 5 In the Control Panel window, double-click on the System icon. 6 Click on the Hardware tab and then click on the Device Manager tab. 7 Open the SCSI and RAID Controllers selection. 8 Locate and double-click on the applicable 3ware Serial ATA RAID Controller.
Updating the Firmware and Driver Select “No, not this time” and click Next. Figure 82. 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. Figure 83. Upgrade/Install Device Driver Wizard 13 At the next screen (Figure 84) choose “Don’t search. I will choose the driver to install” and click Next. www.3ware.
Maintaining Your Controller Figure 84. Search for Driver Screen 14 When the Select the Device Driver screen appears (Figure 85), click the Have Disk… button. Figure 85. Select the Device Driver Screen 15 When the Install from Disk dialog box appears (Figure 86), 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.) 192 3ware SAS/SATA RAID Software User Guide, Version 9.5.
Updating the Firmware and Driver Figure 86. Install From Disk Dialog Box 16 When the Select the Device Driver dialog box reappears, select the appropriate driver (Figure 87) and click Next. Be sure to select the correct driver name, otherwise the driver upgrade will not be successful. Figure 87. Select a Device Driver The wizard begins installing the driver. You will see a progress box during installation.
Maintaining Your Controller 19 If you are prompted to restart the system, do so. Shortly after clicking Finish, or after the machine reboots, the first screen of the Hardware Update Wizard appears again, informing you that Windows has found new hardware. If you are using Windows XP Service Pack 2, the screen asks whether you want to connect to Windows Update (Figure 88). Figure 88. Found New Hardware Screen 20 Choose “No, not this time” and click Next.
Updating the Firmware and Driver 21 When the second Completing the Found New Hardware screen appears, click Finish. Figure 89. Completing Found New Hardware Wizard 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 Linux releases using the 2.4 kernel. The source code is still available (for a limited time) if a newer 2.
Maintaining Your Controller 4 Copy the files to the appropriate directory. (In the commands below, replace with the applicable Red Hat or Fedora Core version, such as ws4_u4 or fc5, and replace with the applicable kernel, for example 2.6.15-x) Note: The name of the module you will copy (3w-9xxx.*) varies, depending on the kernel; however you will always copy it to a file named 3w-9xxx.ko for 2.6 kernels For Red Hat or Fedora Core Uniprocessor cp /3w-9xxx.
Updating the Firmware and Driver For Red Hat Hugemem mkinitrd –v –f initrd-hugmem 7 string>hugmem.img
Maintaining Your Controller 5 Run /sbin/depmod -a 6 Make sure the file /lib/modules//modules.dep contains an entry for 3w-9xxx. If not, add it after the 3w-xxxx entry. 7 Complete the upgrade by upgrading the initial ramdisk. (Skip to step 10 if you prefer to use insmod 3w-9xxx.ko, instead.) Make sure the file /etc/sysconfig/kernel contains the following line: INITRD_MODULES=”3w-9xxx” Note: Other modules may be listed before or after 3w-9xxx depending on the installation.
Updating the Firmware and Driver Updating 3ware Drivers under FreeBSD Drivers can be updated either from source files or with driver modules. Using source files, you can compile drivers into the kernel or you can create modules for versions of FreeBSD for which 3ware does not supply modules. In addition, there may be new modules included with future updates from 3ware. See http://www.3ware.com/support/index.asp.
Maintaining Your Controller Updating the 3ware Kernel Driver Module Under FreeBSD The following steps describe how to update the 3ware driver with a kernel driver module under FreeBSD. Backup your original driver before updating in case you need to revert back to it. However, you will not be able to revert back to the original driver if you are booting from that unit.
Updating the Firmware and Driver To compile the driver as a module 1 Boot to FreeBSD. 2 Download and extract the driver, as described under “Downloading the Driver and Firmware” on page 181. 3 Unpack twa.tgz. Then copy the *.c and *.h files to /sys/dev/twa and the Makefile to /sys/modules/twa. 4 Build the twa.ko module cd /sys/modules/twa make The twa.
Maintaining Your Controller Updating 3ware Drivers under VMware Driver updates for the 3ware RAID controller will be available from 3ware as RPMs. The following steps describe how to update the 3ware driver under VMware. Warning: Backup your original driver before updating in case you need to revert back to it. However, you will not be able to revert back to the original driver if you are booting from that unit.
Testing Battery Capacity Note: When the BBU status is not “Ready,” write caching is automatically disabled on all units attached to the controller To view information about a BBU in 3DM 2 • On the menu bar, choose Monitor > Battery Backup. The Battery Backup page appears, on which you can see details and status about the unit. This page is refreshed every 30 seconds. For details about the fields on this page, see “Battery Backup page” on page 241.
Maintaining 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. Figure 90. Battery Backup Information Screen in 3DM 3 When a message cautions you that testing the battery will disable the BBU for up to 24 hours, click OK to continue. After the battery test starts, you will see the voltage start dropping; eventually the battery voltage will say "LOW".
Testing Battery Capacity 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 92. Battery Backup Information Screen in 3BM www.3ware.
11 Managing an Enclosure 3ware enclosure management features let you view the status of enclosure hardware, such as fans, power supplies, and temperature sensors through 3DM, and locate individual hardware components by blinking LEDs associated with them. Enclosure management features in 3ware software are available for enclosures with expanders that support SCSI Enclosure Services 2 (SES-2). Note: The SAFTE (SCSI Accessed Fault Tolerant Enclosure) specification is not supported at this time.
Viewing a List of Enclosures Viewing a List of Enclosures If you have multiple enclosures attached to your 3ware RAID controller, you can see a list of them. To see a list of enclosures in 3DM • Choose Monitor > Enclosure Support from the menu. The Enclosure Summary screen appears. Figure 93. Enclosure Summary page To see details about a particular enclosure, click the link in the ID column.
Managing an Enclosure Figure 94. Enclosure Information page (3BM) Checking Enclosure Component Status If your enclosure supports enclosure services, you may be able to check the status of enclosure components such as power supplies, fans, slots, drives, and temperature sensors. To check the status of components in your enclosure in 3DM 1 Choose Monitor > Enclosure Support from the menu.
Checking Enclosure Component Status Figure 95. Enclosure Details page To check the status of components in your enclosure in 3BM When you view the list of enclosures in 3BM, the status information is available on the same screen. For details, see “To see a list of enclosures in 3BM” on page 207. Fan Status The following is a list of possible fan statuses: www.3ware.com • OK. The fan is optimal and is functioning normally. • Off. The fan is off. • Failure. The fan is present, but is malfunctioning.
Managing an Enclosure Temp Sensor Status Below is a list of possible temperature sensor statuses. Note that the temp sensor status indicates the temperature of the enclosure or backplane. Drive temperature, if supported, is available on the Drive Details page. • OK. The temperature sensor is functioning normally. • Failure. The temperature sensor is present, but is malfunctioning. • Not Installed. There is no temperature sensor installed. • Unknown.
Locating a Specific Enclosure Component Locating a Specific Enclosure Component If you have a supported enclosure and the identify feature is supported by your enclosure manufacturer, you can locate power supplies, fans, and temperature sensors by blinking the leds associated with them. This can help you quickly identify which component needs to be checked or replaced. The specific components that can be located in this way will depend on your enclosure.
12 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 96. Controller Summary Page The Summary page appears after you first logon to 3DM, or 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. Model. The model name of the controller.
3DM 2 Reference Controller Details page Figure 97. 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. Driver.
Unit Information page Bus Width. The bus width detected by the controller. This is 8 lanes for the 9690SA controller. It may be 1, 4, or 8 lanes on the 9650SE. Bus Speed. The speed of the bus used on the controller. Controller Phys. The number of phys on the controller, regardless of whether each currently has a device connected. The 9690SA controller has 8 phys. Connections. The number of connections that are presently being used out of the total number possible on the controller. Drives.
3DM 2 Reference To see details about a particular unit, click the link in the Unit # column. Unit #. The unit number assigned to the unit by the firmware. Name. If a name has been given to this unit, it shows here. If it is empty, no name has been assigned. You can name your unit in the Unit Names section of the Management > Controller Settings page. Type. The type of unit, specified during configuration: RAID 0, RAID 1, RAID 5, RAID 6, RAID 10, RAID 50, Single Disk, or Spare.
Unit Details page Unit Details page Figure 99. Unit Details Page The Unit Details page appears when you click an ID number on the Unit Information page. Because it is a sub-page of Unit Information, the page title in the menu bar continues to display “Unit Information” even when you view details of a unit. The Unit Details page shows details about a particular unit. The specific information shown depends on what type of unit it is.
3DM 2 Reference Serial #. The serial number of the unit. This number is assigned by the firmware when the unit is created. Capacity. The total capacity of the unit (capacities of subunits are not shown). Type. The type of unit or subunit. RAID 0, RAID 1, RAID 5, RAID 6, RAID 10, RAID 50, Single Disk, Spare, or Disk. Stripe. The stripe size of the unit, if applicable. Parities. The number of parity drives in the RAID unit. Volumes. Displays the number of volumes in a unit. This is usually 1.
Drive Information page Drive Information page Figure 100. Drive Information Page The Drive Information page appears when you choose Information > Drive Information from the menu bar, or when you click a VPort # on the Unit Details page. If you arrive at this page from the VPort # hyperlink on the Unit Information page, the line showing the VPort # you clicked on is highlighted. This page shows a list of drives on the current controller and a summary of each one.
3DM 2 Reference Capacity. The physical capacity of the drive. (Note that the capacity as shown on 3DM screen is calculated as 1KB = 1024. This amount may differ from the capacity that is printed on the disk drive, where it typically has been calculated as 1KB = 1000. Consequently, the capacity of the drive may appear smaller in the 3DM screens. No storage capacity is actually lost; the size has simply been calculated differently for consistency.) Type. The type of drive: SATA or SAS. Phy.
Drive Details window Drive Details window Figure 101. Drive Details Page The Drive Details window displays when you click a VPort # on the Drive Information page. This Drive Details window shows some Extra Drive Information, including Queuing and SATA Link Speed support, and the SMART data for SATA drives. SMART data is not displayed for SAS drives. Extra Drive Information Drive Type. The type of drive: SAS or SATA. Serial #. The serial number of the drive. Firmware. The firmware version of the drive.
3DM 2 Reference SAS WWN. The SAS drive’s unique World Wide Number. Reallocated Sectors. The number of sectors that have been re-allocated due to bad sectors on the drive. Power On Hour. The total number of hours the drive has been powered-on. Drive Temperature. The temperature of the drive. Spindle Speed. The drive speed in RPM. Queuing Supported and Queuing Enabled.
Controller Phy Summary page Controller Phy Summary page Figure 102. Controller Phy Summary Page The Controller Phy Summary page shows the properties of controller phys. The Controller Phy Summary page can be accessed in two ways.If you have a direct-attached drive you can access this page from the Information > Drive Information page by clicking the phy ID for the drive. If all drives are connected via expanders, navigate to the Management > Controller Settings page.
3DM 2 Reference Controller Settings page Figure 103. 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.
Controller Settings page Background Task Rate The Background Task Rate fields let you change the balance of background tasks and I/O (reading and writing to disk) performed by the controller. There are separate settings for Rebuild/Migrate Rate and Verify Rate, Figure 103. The Rebuild/Migrate Rate also applies to initialization. Although the same rate is used for rebuilding, migrating, and initializing, migrating has the highest priority.
3DM 2 Reference Drive and choosing Properties; then on the Tools tab, click Check Now. Under Linux or FreeBSD use the fsck utility command. For example, fsck /dev/ sda1. Note: The policy Overwrite ECC is equivalent to the “Continue on Source Error” option in 3BM and the “IgnoreECC” option in the CLI. Queuing. (Not applicable for SAS drives) This policy enables or disables Native Command Queuing (NCQ) for SATA drives in the unit. By default, queuing is disabled. You can enable it, if desired.
Controller Settings page Other Controller Settings The Other Controller settings displays information about additional settings, some of which can only be changed in the BIOS (3BM). Auto Rebuild. The Auto Rebuild policy determines how the controller firmware will attempt to rebuild degraded units. When Auto Rebuild is disabled, only spares will be used to automatically rebuild degraded units.
3DM 2 Reference Update Firmware The Update Firmware function allows you to update the firmware of your 3ware RAID controller to the latest version. This keeps the firmware compatible with updates to your operating system and allows you to take advantage of new features AMCC may have added to your controller’s functionality. For additional information, see “Updating the Firmware Through 3DM 2” on page 182. Scheduling page Figure 104.
Scheduling page 3DM then updates the page to show you schedule details for that type of task. Scheduled Rebuild/Migrates. You can enable or disable the schedule for the Rebuild/Migrate 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. Scheduled Verify Mode. You can select either Basic or Advanced verify mode. Basic verify creates a once a week schedule.
3DM 2 Reference Self-test Schedules Unlike scheduling of rebuilds and verifies, scheduling of self-tests is always followed. To disable self-tests you either remove all schedule times, or uncheck the tests listed in the Tasks column. Note: Only the checked tasks will be run during the scheduled times. If none of the tasks are checked, self-tests will never run, even if you have scheduled time slots set. Two self-tests can be scheduled: Upgrade UDMA mode. (Only applicable to PATA drives.
Maintenance page Maintenance page Figure 105. 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.
3DM 2 Reference Rescanning is useful in a 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. Note: If you unplug a drive without first removing it through 3DM, Rescan may not recognize it as gone unless the drive was in use or until it is required by the system. Always use the Remove link to remove a drive before unplugging it.
Maintenance page 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, 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. Capacity.
3DM 2 Reference 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. If the Advanced Verify schedule is selected on the Scheduling page, the unit will not start actively verifying until the scheduled time, and the status will indicate “VerifyPaused.
Maintenance page 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 166. Migrate Unit. Reconfigures a unit while it is on-line. Migration can be used to change the RAID level, to expand the capacity by adding additional drives, or to change the stripe size. Warning: Once migration of a unit is started, it cannot be cancelled.
3DM 2 Reference Caution: Before you click Remove Unit, make sure the unit you are removing is unmounted from the operating system and that the system is not accessing it. If a unit is not unmounted and you remove it, it is the equivalent of physically yanking a hard drive out from under the operating system. You could lose data, the system could hang, or the controller could reset. To unmount a unit under windows, use Administrative Tools > Computer Management > Disk Management.
Maintenance page Warning: When a unit is deleted, the data will be permanently deleted: the drives cannot be reassembled into the same unit. If you want to reassemble the drives on another controller and access the existing data, use Remove Unit instead of Delete Unit. After deletion, the operating system is notified that the unit was deleted. 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.
3DM 2 Reference Figure 107. Configuration Window in 3DM For more detailed instructions, see “Configuring a New Unit” on page 101. 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 6.
Maintenance page will give better performance with applications that have a lot of random reads and writes. In general, the smaller the stripe size, the better the sequential I/O 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 Overwrite ECC. These check boxes let you set the policies for the unit. These policies can also be set and changed on the Controller Settings page.
3DM 2 Reference Alarms page Figure 109. Alarms Page The Alarms page appears when you click Monitor > Alarms on the menu bar. This page displays a list of AENs (asynchronous event notifications) received from the controller displayed in the drop-down list in the menu bar. Up to 1000 events can be listed. After the 1000-limit is reached, the oldest events are deleted, as new ones occur. You can sort the events by severity or time. To do so, just click the column header.
Battery Backup page Battery Backup page Figure 110. Battery Backup Page The Battery Backup page appears when you choose Monitor > Battery Backup on the menu bar. Use this page to determine whether a backup battery is present, see details about it, and perform a battery test. Battery Backup Unit. Indicates whether the BBU is present. Firmware. Indicates the BBU firmware version. Serial Number. Indicates the BBU serial number. BBU Ready.
3DM 2 Reference If the battery is ever discharged through a backup cycle or if the system power is off for more than two weeks, the battery status changes to “Charging” the next time the system is powered on. This indicates the BBU is not able to backup the 3ware RAID controller. When the BBU is in the charging state, write caching is disabled automatically on all units attached to the controller. • Fault. The BBU detected a fault.
Enclosure Summary page Enclosure Summary page Figure 111. Enclosure Summary Page The Enclosure Summary page appears when you choose Monitor > Enclosure Support from the menu bar. The Enclosure Summary page provides basic information about any enclosures attached to your system. The specific details that display depend upon your enclosure. For a list of supported enclosures, see http:// www.3ware.com/support/sys_compatibility.asp. ID. The ID that the 3ware firmware assigns to the enclosure.
3DM 2 Reference Enclosure Details page Figure 112. Enclosure Details Page The Enclosure Details page appears when you click the ID of an enclosure on the Enclosure Summary page. Use this page to view information about the enclosure, fans, temp sensors, power supplies, and drive slots.
Enclosure Details page Enclosure ID Status. The status of the enclosure. Vendor. The manufacturer of the enclosure. Product ID. The product ID of the enclosure. Revision. The manufacturer’s revision number for the enclosure. Diagnostic. Click the Diagnostic Text link to download a log of enclosure diagnostic information to your computer. If you contact AMCC for support with your controller, they may ask you to use this feature. It may help AMCC identify the problem you encountered. Controller ID.
3DM 2 Reference Power Supply Summary Power Supply. The ID number associated with the specified power supply. Status. Can be OK, Failure, Not Installed, Off, or Unknown. For status definitions, see “Power Supply Status” on page 210. State. Indicates if the power supply is ON or OFF. Voltage.The status of the dc voltage output of the power supply. Can be Normal, Over Voltage, Under Voltage, or Unknown. Current. The status of the dc amperage output of the power supply.
3DM 2 Settings page 3DM 2 Settings page Figure 113. 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.
3DM 2 Reference • Remote Access • HTTP Settings 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 Confirm New Password. Enter the new password a second time, to be sure you have entered it correctly. Change Password button. Saves password changes. 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.
13 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 Four 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, Controller Details, Unit Information and Enclosure Summary (The Controller Details and Unit Information screens are available from the Information tab, Enclosure Summary is available from the Monitor tab.
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. Under Linux and FreeBSD tw_mgmt.log is in the /var/log directory. For Windows Vista and Windows Server 2008, tw_mgmt.log is in \ProgramData\AMCC. For earlier versions of Windows, tw_mgmt.
Drive Performance Monitoring Drive Performance Monitoring When one drive in a RAID unit is responding much slower than others, it reduces the performance of the entire unit. Drive Performance Monitoring (DPM) is now available to measure drive performance, and to help identify when a specific drive is causing problems so that you can have the drive manufacturer repair or replace it. DPM is an advanced trouble-shooting tool.
Troubleshooting • Display a DPM Summary. This shows whether DPM is On or Off, and provides summary statistics for drives attached to a controller. (/cx show dpmstat) Note that if DPM is Off, this summary may still show data, although that data will be static, and not changing over time. Disabling DPM does not clear the existing data. That is done separately, on a per-port basis (see below.
Problems and Solutions Problems and Solutions This section covers some common problems and solutions. It is organized into the following sections: • Enclosure-Related Problems • An LED is blinking red on an enclosure.
Troubleshooting • The motherboard may be functional, but may not be compatible. Please check the Motherboard Compatibility List on the 3ware website at http:// www.3ware.com/products/compatibility.asp to see if you motherboard has been tested by 3ware. If you have a different type of motherboard available, you may want to test the controller in it to see if the 3ware BIOS screen appears. • The motherboard's BIOS may need to be upgraded.
Problems and Solutions A unit shows up as unusable, because of missing drives: Unusable Arrays: 3 drive 64K RAID 5 558.77 GB (Unit 1) SATA - Maxtor 6B300S0 279.86 GB (Port 6) The unit has some but not all of its members available. The unit will be unusable. If this unit is your boot device, your system will not boot. You must either return the missing disks to complete the unit, or release the member disks by deleting the incomplete unit(s) listed in the display.
Troubleshooting If a drive that previously showed up in 3DM or 3BM does not show up, try the following: 1 Power the system down, then reseat the drive in the slot, reseat the data cable, and reseat the power cable. 2 Power the system back up. 3 If the drive still does not show up in 3DM or 3BM, then swap that drive with a drive that is showing up. 4 If the drive now shows up, and drive you swapped it with does not, then the drive is OK.
Error and Notification Messages Table 13: Error and Notification Message List Value Message 0001 Controller reset occurred 0002 Degraded unit 0003 Controller error occurred 0004 Rebuild failed 0005 Rebuild completed 0006 Incomplete unit detected 0007 Initialize completed 0008 Unclean shutdown detected 0009 Drive timeout detected 000A Drive error detected 000B Rebuild started 000C Initialize started 000E Initialize failed 000F SMART threshold exceeded 0019 Drive removed 001A Drive inserted 001E Unit inopera
Troubleshooting Table 13: Error and Notification Message List Value Message 0028 DCB version unsupported 0029 Verify started 002A Verify failed 002B Verify completed 002C Source drive ECC error overwritten 002D Source drive error occurred 002E Replacement drive capacity too small 002F Verify not started; unit never initialized 0030 Drive not supported 0032 Spare capacity too small 0033 Migration started 0034 Migration failed 0035 Migration completed 0036 Verify fixed data/parity mismatch 0037 SO-DIMM not c
Error and Notification Messages Table 13: Error and Notification Message List Value Message 0047 Battery voltage is too low 0048 Battery voltage is too high 0049 Battery temperature is normal 004A Battery temperature is low 004B Battery temperature is high 004C Battery temperature is too low 004D Battery temperature is too high 004E Battery capacity test started 004F Cache synchronization skipped 0050 Battery capacity test completed 0051 Battery health check started 0052 Battery health check completed 0053
Troubleshooting Table 13: Error and Notification Message List Value Message 8002 Enclosure fan removed 8003 Enclosure fan added 8004 Enclosure fan unknown 8005 Enclosure fan off 8020 Enclosure temp normal 8021 Enclosure temp low 8022 Enclosure temp high 8023 Enclosure temp below operating 8024 Enclosure temp above operating 8025 Enclosure temp removed 8026 Enclosure temp added 8027 Enclosure temp critical 8028 Enclosure temp unknown 8030 Enclosure power normal 8031 Enclosure power fail 8032 Enclosure power
Error and Notification Messages Table 13: Error and Notification Message List Value Message 8004 Enclosure fan unknown 8005 Enclosure fan off 8020 Enclosure temp normal 8021 Enclosure temp low 8022 Enclosure temp high 8023 Enclosure temp below operating 8024 Enclosure temp above operating 8025 Enclosure temp removed 8026 Enclosure temp added 8027 Enclosure temp critical 8028 Enclosure temp unknown 8030 Enclosure power normal 8031 Enclosure power fail 8032 Enclosure power removed 8033 Enclosure power added
Troubleshooting Error and Notification Message Details 0001 Controller reset occurred Event Type Information Cause The device driver has sent a soft reset to the 3ware RAID controller. The driver does this when the controller has not responded to a command within the allowed time limit (30 sec.). After the soft reset command has been sent, the driver will resend the command. Action If this message occurs more than three times a day, collect the system logs and contact Technical Support.
Error and Notification Messages See Also “About Degraded Units” on page 151 “Rebuilding Units” on page 167 0003 Controller error occurred Event Type Error Cause The 3ware RAID controller has encountered an internal error. Action Please collect log files and contact AMCC Customer Support, as a replacement board may be required. Technical support is at http://www.3ware.com/support/index.asp. Information on collecting logs is at http://www.3ware.com/KB/article.aspx?id=12278.
Troubleshooting To lower the likelihood of getting this error, schedule regular verifications. See Also “Setting Overwrite ECC (Continue on Source Error When Rebuilding)” on page 121. “Scheduling Background Tasks” on page 173 0005 Rebuild completed Event Type Information Cause The 3ware RAID controller has successfully completed a rebuild. The data is now redundant. Action None required. 0006 Incomplete unit detected Event Type Warning Cause The 3ware RAID controller has detected an incomplete unit.
Error and Notification Messages 0007 Initialize completed Event Type Information Cause The 3ware RAID controller completed the “synching” background initialization sequence of RAID levels 1, 6, 10, 50, or 5. For RAID 5, RAID 6, and RAID 50, the data on the unit was read and the resultant new parity was written. For RAID 1 and 10, one half of the mirror was copied to the other half (mirrors are synchronized). This message will not appear for a foreground initialization.
Troubleshooting 0009 Drive timeout detected Event Type Error Cause A drive has failed to respond to a command from a 3ware RAID controller within the allowed time limit (20 secs.). After sending this error message, the controller will attempt to recover the drive by sending a reset to that drive and retrying the failed command. Possible causes of drive time-outs (also known as ATA-Port time-outs) include a bad or intermittent disk drive, power cable or interface cable.
Error and Notification Messages Action If you see this message, the drive repairs may lie outside of the 3ware RAID controller’s abilities.Try running the drive manufacturer’s diagnostic and repair utilities on the drive. If necessary, replace the drive. See Also For links to drive manufacturer diagnostic utilities and troubleshooting advice, see http://www.3ware.com/KB/article.aspx?id=10894. 000B Rebuild started Event Type Information Cause The 3ware RAID controller started to rebuild a degraded unit.
Troubleshooting Action Allow the initialization to complete. This will return the unit to its normal redundant state. See Also For more information, see “About Initialization” on page 158 000E Initialize failed Event Type Error Cause The 3ware RAID controller was unable to complete the initialization. This error can be caused by unrecoverable drive errors. If this unit was a redundant unit, and the initialization failed because of a problem on a particular disk drive, then the unit will be degraded.
Error and Notification Messages as error rates and retry counts.This type of monitoring may be able to predict a drive failure before it happens, allowing you to schedule service of the unit before it becomes degraded. The SMART status of each drive attached to the 3ware RAID controller is monitored daily. Action AMCC recommends that you replace any drive that has exceeded the SMART threshold. If the drive is part of a redundant unit, remove the drive through 3DM 2 or CLI.
Troubleshooting Action The drive is now available for use. If the drive is part of a unit add the remaining drives and rescan the controller, in 3DM or CLI, to bring the unit online. 001E Unit inoperable Event Type Error Cause The 3ware RAID controller is unable to detect sufficient drives for the unit to be operable. Some drives have failed or are missing. Examples of inoperable units are as follows: • RAID 0 missing any drives.
Error and Notification Messages Cause Drive insertion caused a unit that was inoperable to become operational again. Any data that was on that unit will still be there. This message is only sent if the unit was inoperable for more than 20 seconds. That means that if the hot swap of a drive occurred within 20 seconds, messages are not generated. Action None Required. The unit is available for use.
Troubleshooting 0022 Upgrade UDMA mode Event Type Warning Cause During a self-test, the controller found that a drive was not in the optimal UDMA mode and upgraded its UDMA transfer rate. Action None required. The drive and cable are working in optimal mode. 0023 Sector repair completed Event Type Warning Cause The 3ware RAID controller moved data from a bad sector on the drive to a new location.
Error and Notification Messages 0024 Buffer integrity test failed Event Type Error. Cause The 3ware RAID controller performs diagnostics on its internal RAM devices as part of its data integrity features. Once a day, a non-destructive test is performed on the cache memory. Failure of the test indicates a failure of a hardware component on the 3ware RAID controller. This message is sent to notify you of the problem. Action You should replace the 3ware RAID controller.
Troubleshooting 0026 Drive ECC error reported Event Type Error Cause Drive ECC errors are an indication of grown defects on a particular drive. For redundant units, this typically means that dynamic sector repair has been invoked (see message “0023 Sector repair completed” on page 274). For nonredundant units (Single Disk, RAID 0 and degraded units), which do not have another copy of the data, drive ECC errors result in the 3ware RAID controller returning failed status to the associated host command.
Error and Notification Messages Action If this error occurs, please contact 3ware technical support at http:// www.3ware.com/support/index.asp for assistance. 0028 DCB version unsupported Event Type Error Cause The unit that is connected to your 3ware RAID controller was created on a legacy 3ware product that is incompatible with your new controller. During the evolution of the 3ware product line, the format of the Drive Configuration Block (DCB) has been changed to accommodate new features.
Troubleshooting See Also For information on scheduling a verify process, see “Scheduling Background Tasks” on page 173. For information on verification of a unit, see “About Verification” on page 162. 002A Verify failed Event Type Error Cause Verification of a unit has terminated with an error. For each RAID level being verified, this may mean: • Single and Spare. A single drive returned an error, possibly because of a media defect. • RAID 0.
Error and Notification Messages place during off-hours. For more information, see “Scheduling Background Tasks” on page 166. You can also set the initialization process to go slower and use fewer system resources. For more information, see “Setting Background Task Rate” on page 165. (Initialization occurs at the Rebuild rate.) See Also “About Initialization” on page 158 002B Verify completed Event Type Information Cause Verification of the data integrity of a unit was completed successfully.
Troubleshooting 002D Source drive error occurred Event Type Error Cause An error on the source drive was detected during a rebuild operation. The rebuild has stopped as a result. Action The controller will report an error, even if the area of the source drive that had the error did not contain data. Scheduling regular verifies will lessen the chance of getting this error.
Error and Notification Messages Action Use a replacement drive equal to or larger than the drives already in use 002F Verify not started; unit never initialized Event Type Warning Cause A verify operation has been attempted by the 3ware RAID controller, but the unit has never been initialized before. The unit will automatically transition to initializing mode and then start a verify. Action None required. This is considered a normal part of operation.
Troubleshooting See Also For a list of compatible drives, see http://www.3ware.com/products/compatibility_sata.asp 0032 Spare capacity too small Event Type Warning Cause There is a valid hot spare but the capacity is not sufficient to use it for a drive replacement in existing units. Action Replace the spare with a drive of equal or larger capacity than the existing drives. 0033 Migration started Event Type Information Cause The 3ware RAID controller has started the migration of a unit.
Error and Notification Messages Cause The migration of a unit has failed. Migration changes can include: • Expanding capacity of a unit by adding drives. • Changing RAID levels, for example, from RAID 1 to RAID 5 Action Review the list of events on the Alarms page for other entries that may give you an idea of why the migration failed (for example, a drive error on a specific port). You may also wish to get the logs and contact technical support at http:// www.3ware.com/support/index.asp.
Troubleshooting 0036 Verify fixed data/parity mismatch Event Type Warning Cause A verify error was found and fixed by the 3ware RAID controller. Some examples of errors that can be fixed include: • A parity inconsistency for a RAID 5 or RAID 50 unit. • A data mismatch for a RAID 1 or RAID 10 unit. Action None required. 0037 SO-DIMM not compatible Event Type Error Cause There is incompatible SO-DIMM memory connected to the 9500S controller.
Error and Notification Messages Cause The 3ware 9500S RAID controller is inoperable due to missing SO-DIMM memory. 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 Install a compatible SO-DIMM on the controller. See Also For a list of SODIMMs compatible with the 9500S, see http://www.3ware.com/KB/article.aspx?id=11748.
Troubleshooting Action If this drive was the only one to lose power, check the cable connections. Also, check that your power supply is adequate for the type and number of devices attached to it. See Also For troubleshooting information and a link to drive manufacturer diagnostic utilities, see http://www.3ware.com/KB/article.aspx?id=14927. 003B Rebuild paused Event Type Information Cause The rebuild operation is paused.
Error and Notification Messages See Also “Viewing Current Task Schedules” on page 174 “About Initialization” on page 158 003D Verify paused Event Type Information Cause The verify operation is paused. Verifies are normally paused for 2 (formerly 10) minutes after a system first boots up. Verifies are also paused during non-scheduled times when scheduling is enabled.
Troubleshooting “Scheduling Background Tasks” on page 173 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. The 3ware RAID controller stores configuration parameters as files in its flash memory. These files can be corrupted when a flash operation is interrupted by events such as a power failure. The controller will attempt to restore the flash files from a backup copy.
Error and Notification Messages 0041 Unit number assignments lost Event Type Warning Cause The unit number assignments have been lost. This may have occurred as a result of a soft reset. Action Please contact AMCC 3ware technical support at http://www.3ware.com/ support/index.asp. 0042 Primary DCB read error occurred Event Type Warning Cause The controller found an error while reading the primary copy of the Disk Configuration Block (DCB).
Troubleshooting 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. If the primary copy is valid, the backup DCB will be rewritten to rectify the errors. Action AMCC recommends verifying the unit. See “Starting a Verify Manually” on page 165.
Error and Notification Messages Cause The battery pack voltage being monitored by the Battery Backup Unit has risen above 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. 0047 Battery voltage is too low Event Type Error Cause The battery pack voltage being monitored by the Battery Backup Unit is too low to backup the 3ware RAID controller.
Troubleshooting 2 Remove the BBU control module from the 3ware RAID controller and the battery module from the remote card. 3 Unplug the battery from the control module. 4 Return the BBU control module and battery module to 3ware. For more details on removing the BBU, see the installation guide that came with your 3ware RAID controller.
Error and Notification Messages 004B Battery temperature is high Event Type Error Cause The battery pack temperature being monitored by the Battery Backup Unit has risen above the acceptable range. However, the BBU is still able to backup the 3ware RAID controller. Action Check for sufficient airflow around the card.
Troubleshooting 004D Battery temperature is too high Event Type Error Cause The battery pack temperature being monitored by the Battery Backup Unit is too high. The BBU is unable to backup the 3ware RAID controller. Action Check for sufficient airflow around the card. To increase airflow you can: • Leave the PCI slots next to the controller empty • Add fans to your computer case • Move and bundle wiring that is blocking air circulation Contact 3ware technical support at http://www.3ware.
Error and Notification Messages See Also See the Install Guide for your controller. 004F Cache synchronization skipped Event Type Warning Cause The cache synchronization that is normally performed when power is restored after a power failure was skipped and write data is still being backed up in the controller cache. This can occur if a unit was physically removed or became inoperable during the power outage. Action Return missing drive(s) to the controller so that the missing write data can be saved.
Troubleshooting 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. This message is posted to the host when this health check has completed. 0053 Battery capacity test is overdue Event Type Information Cause There has not been a battery capacity test run in the last 6 months, which is the maximum recommended interval.
Error and Notification Messages 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.
Troubleshooting 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. 005A Battery is present Event Type Information Cause A battery pack is connected to the 3ware RAID controller.
Error and Notification Messages 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.
Troubleshooting You will also see this message if drive insertion causes a unit to become operational and retained write cache data was flushed. 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. 0062 Enclosure removed Event Type Warning. Cause Applies only to the 9690SA controller.
Error and Notification Messages 0064 Local link up Event Type Information. Cause Applies only to the 9690SA controller. A cable has been plugged in, restoring a link to a controller phy. 0065 Local link down Event Type Warning. Cause Applies only to the 9690SA controller. A cable has been unplugged, removing a link to a controller phy. 8000 Enclosure fan normal Event Type Information. Cause Applies only to the 9690SA controller. The fan’s performance or operation is now back within the acceptable range.
Troubleshooting The enclosure fan is not functioning normally and may be blocked or defective. Action Check that the fan or fans are not blocked. If a fan appears defective, replace it as soon as possible. For information on replacing a fan, see your enclosure documentation or contact your enclosure manufacturer. 8002 Enclosure fan removed Event Type Warning. Cause Applies only to the 9690SA controller. A fan has either been removed or has become unplugged.
Error and Notification Messages Cause Applies only to the 9690SA controller. The enclosure is unable to recognize the fan. The fan may not be seated correctly or may be malfunctioning. Action Reseat the fan. If it is necessary to replace the fan, see your enclosure documentation or contact your enclosure manufacturer. 8005 Enclosure fan off Event Type Warning. Cause Applies only to the 9690SA controller. An enclosure fan has been turned off. It is no longer cooling the enclosure.
Troubleshooting 8021 Enclosure temp low Event Type Information. Cause Applies only to the 9690SA controller. The enclosure temperature is lower than normal. Action In general, cooler operating temperatures are good for enclosure components. However, if the temperature is very cold, condensation can occur and cause media errors and damage. Take steps to bring the operating environment back within the enclosure manufacturer’s specifications. Allow cold equipment to warm up gradually before powering on.
Error and Notification Messages Cause Applies only to the 9690SA controller. The enclosure temperature is below the enclosure manufacturer’s specified operating temperature. Action In general, cooler operating temperatures are good for enclosure components. However, if the temperature is very cold, condensation can occur and cause media errors and damage. Take steps to bring the operating environment back within the enclosure manufacturer’s specifications.
Troubleshooting Action The temperature sensor should be replaced or repaired. This may require specialized skills. Contact your enclosure manufacturer for more information. 8026 Enclosure temp added Event Type Information. Cause Applies only to the 9690SA controller. A temperature sensor has been added to the enclosure or an existing sensor has been plugged in. This error message can occur due to a poor connection. Action If due to a poor connection, the repair will require specialized skills.
Error and Notification Messages 8028 Enclosure temp unknown Event Type Warning. Cause Applies only to the 9690SA controller. The enclosure is reporting that it is unable to determine the temperature of the unit. This may be due to a failed or missing sensor. Action Check the operational status of the temperature sensor. If it has failed, replace it. See your enclosure documentation or contact your enclosure manufacturer for more information. 8030 Enclosure power normal Event Type Information.
Troubleshooting Action Reseat the power supply cord. Replace any failed power supply as soon as possible. It is recommended to use an uninterruptible power supply (UPS) to protect against power failures. 8032 Enclosure power removed Event Type Warning. Cause Applies only to the 9690SA controller. One of the enclosure power supplies has been removed from the enclosure or a power supply is unplugged. Action Return or reconnect the power supply as soon as possible.
Error and Notification Messages Cause Applies only to the 9690SA controller. There is a power supply in the enclosure, but it is not of a known type. Action Check to be sure the power supply is operational by re-seating or replacing the failed power supply. See your enclosure documentation or contact your enclosure manufacturer for more information. It is recommended to use an uninterruptible power supply (UPS) to protect against power failures. 8037 Enclosure power off Event Type Warning.
Troubleshooting 8041 Enclosure voltage over Event Type Error. Cause Applies only to the 9690SA controller. The enclosure power supply voltage is higher than the normal range. Action This error is rare. If you see it you may need a UPS or voltage regulator to stay within the recommended voltage range. 8042 Enclosure voltage under Event Type Error. Cause Applies only to the 9690SA controller. The enclosure power supply voltage is lower than the normal range.
Error and Notification Messages Action If applicable, replace the failed power supply. Contact your enclosure manufacturer for more information. 8044 Enclosure current normal Event Type Information. Cause Applies only to the 9690SA controller. The enclosure power supply current is now back within the acceptable range. Action None required. 8045 Enclosure current over Event Type Error. Cause Applies only to the 9690SA controller. The enclosure power supply amperage is higher than normal.
Troubleshooting Cause Applies only to the 9690SA controller. The enclosure’s amperage is unknown. A power supply may have failed. Action If applicable, replace the failed power supply. See your enclosure documentation or contact your enclosure manufacturer for more details. 312 3ware SAS/SATA RAID Software User Guide, Version 9.5.
Appendices The following information is available in the appendices: 313 • Appendix A, “Glossary” on page 314 • Appendix B, “Software Installation” on page 322 • Appendix C, “Compliance and Conformity Statements” on page 335 • Appendix D, “Warranty, Technical Support, and Service” on page 337 3ware SAS/SATA RAID Software User Guide, Version 9.5.
A Glossary • 3BM. 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.
• Background rebuild rate. The rate at which a particular controller initializes, rebuilds, and verifies redundant units (RAID 1, RAID 5, RAID 6, RAID 10, RAID 50). • Boot volume size. The size to be assigned to volume 0 when creating a unit through 3BM or CLI 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.
Glossary • 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.
• Hot swapping. The process of removing a disk drive from the system while the power is on. Hot swapping can be used to remove units with data on them, when they are installed in hot swap bays. Hot swapping can also be used to remove and replaced failed drives when a hot swap bay is used. • 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.
Glossary • 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. Information that the controller calculates using an exclusive OR (XOR) algorithm and writes to the disk drives in RAID 5, RAID 6, and RAID 50 units. This data can be used with the remaining user data to recover the lost data if a disk drive fails. • PCB. Printed circuit board. • P-Chip.
• Rebuild task schedule. The specification for when rebuilding, may occur, including start time and duration. • Rebuild a unit. To generate data on a new drive after it is put into service to replace a failed drive in a fault tolerant unit (for example, RAID 1, 10, 5, 6, or 50). • • Redundancy. Duplication of data on another drive or drives, so that it is protected in the event of a drive failure. Remove a drive. The process of making a drive unavailable to the controller. • Remove a unit.
Glossary • Stripe size. The size of the data written to each disk drive in RAID unit levels that support striping. The size of stripes can be set for a given unit during configuration. In general, smaller stripe sizes are better for sequential I/O, such as video, and larger strip sizes are better for random I/O (such as databases). The stripe size is user-configurable at 64KB, 128KB, or 256KB. This stripe size is sometimes referred as a “minor” stripe size.
• WWN (World Wide Number). The unique worldwide 64-bit SAS address assigned by the manufacturer to each SAS port and expander device in the SAS domain. Many SAS drives have 2 ports and thus 2 WWNs. www.3ware.
B Software Installation This appendix provides detailed instructions for installing the 3ware management software for your 3ware RAID controller and the 3ware HTML Bookshelf. You can install all software at once, or you can use the installer to install some or all of the following specific components: • 3DM 2 • CLI (Command Line Interface) • 3ware HTML Bookshelf If you install the disk management tool 3DM 2, you will be asked to specify some settings, such as email notifications and security settings.
Installing Software Installing Software from a Graphical User Interface (GUI) The steps below describe how to install the 3ware RAID management software from a windowing graphical user interface such as Microsoft Windows or X Windows in Linux. To install the 3ware management software 1 With your computer on, insert the AMCC 3ware CD that came with your 3ware RAID controller. The CD should automatically launch and display the AMCC License window. If it does not, you can start it manually.
Software Installation 5 On the License Agreement page, accept the agreement and click Next. Figure 115. License Agreement Screen 6 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 116. Specify Directory Path Screen 7 Select what components you want to install and click Next. 3DM and CLI are applications that let you set up and manage RAID units.
Installing Software The 3ware Documentation option installs the 3ware HTML Bookshelf on your computer. This is a combined HTML version of the User Guide and CLI Guide. Figure 117. Select Components to Install Screen 8 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.
Software Installation Figure 118. 3DM 2 Email Configuration Screen 9 When a message asks you whether you want to enable 3DM command logging, click Yes to enable it, or No to disable it. Command logging saves all changes you make to RAID configurations using 3DM to a special file. This information can be useful for troubleshooting problems with AMCC technical support. Figure 119. 3DM 2 Command Logging Message 326 3ware SAS/SATA RAID Software User Guide, Version 9.5.
Installing Software 10 [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. For more information, see “Enabling and Disabling Remote Access” on page 84. Figure 120.
Software Installation 12 If you want the Installation Wizard to connect to 3DM 2 after you finish the wizard, check the Connect to 3DM 2 box. This allows you to log into 3DM and configure a RAID unit right away. If you do not want to connect to 3DM 2 at this time, leave the box unchecked. When you are ready, click Next to continue. Figure 122. Final Installation Screen 13 On the summary screen, review the installation that is about to occur.
Installing Software 14 When the final installation screen lets you know that installation is complete, click Finish. Figure 124. Final Installation Screen Tip: You can now access the documentation through the 3ware HTML Bookshelf. For Windows, from the Start menu, choose Programs > AMCC > Bookshelf shortcut. For Linux, open a browser window to the following location: /opt/AMCC/Documentation/index.html For more information, see “Using the 3ware HTML Bookshelf” on page xi.
Software Installation The install file name will be one of the following, depending on your operating system and processor type. ./setupLinux_x86.bin -console ./setupLinux_x64.bin -console 3 After you press Enter, the application starts in text mode. 4 Respond to each screen as it walks you through the installation process. The Console installation screens mirror those that display using the GUI installer. For specific information about the screens, see the previous section in this chapter.
Installing Software Installing Software on FreeBSD 6.x or 7.x and later from the Command Line The following steps describe how to install software on FreeBSD from the command line, using a console application.[ To install software on FreeBSD from the command line 1 Navigate to the folder on the 3ware CD containing the installer for your operating system and processor type (x86 or x64). It will be one of the following: /packages/installers/tools/freebsd/6.x/x86 /packages/installers/tools/freebsd/6.
Software Installation To manually install CLI under FreeBSD 5.x 1 Mount the 3ware CD-ROM mount /cdrom 2 Copy the CLI utility to the destination directory. The path will be one of the following, depending on your processor type: cp -R /cdrom/packages/cli/freebsd/x86/tw_cli /usr/local/bin cp -R /cdrom/packages/cli/freebsd/x86_64/tw_cli /usr/local/bin To manually install 3DM under FreeBSD 5.x For instructions for manually installing 3DM, see the knowledgebase article http://www.3ware.com/KB/article.
Uninstalling 3ware Software Uninstalling 3ware Software This section tells you how to uninstall 3ware RAID controller management software for these operating systems. • Uninstalling 3ware Software under Microsoft Windows • Uninstalling 3ware Software under Linux and FreeBSD • Uninstalling 3DM Software on VMware Note: If 3DM is reinstalled or restarted, close any open web browsers before starting 3DM again to close the server socket.
Software Installation Uninstalling 3DM Software on VMware You can uninstall CLI, 3DM 2 or the 3ware RAID controller driver. To uninstall software for VMware 1 Login as root. 2 Check for installed packages. esxupdate -l query You will see a list of the packages that have been installed on VMware. 3 Run the command rpm -e on the package you wish to uninstall. The software is removed. 334 3ware SAS/SATA RAID Software User Guide, Version 9.5.
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.
Compliance and Conformity Statements 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, Technical Support, and Service 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.
AMCC Technical Support and Services 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 92 3BM help 69 main screen 63 navigation 64 screens 63 starting 60 working in 64 3DM 3DM menus 76 Alarms page 240 Battery Backup Information page 241 browser requirements 71 Controller Details page 214 Controller Settings page 224 Controller Summary page 213 Disk Management Utility Overview 70 Drive Details page 221 Drive Information page 219 enabling remote access 84 Enclosure Details page (3DM) 244 Enclosure Summary page (3DM) 243 installation 322 main 3DM screen 76 Maintenance
Drive timeout detected (0009) 268 Flash file system error detected (003F) 288 Flash file system repaired (0040) 288 Incomplete unit detected (0006) 266 Initialize completed (0007) 267 Initialize failed (000E) 270 Initialize paused (003C) 286 Initialize started (000C) 269 Migration completed (0035) 283 Migration failed (0034) 282 Migration paused (003E) 287 Migration started (0033) 282 Primary DCB read error occurred (0042) 289 Rebuild completed (0005) 266 Rebuild failed (0004) 265 Rebuild paused (003B) 286
bootable unit, specifying 63 browser requirements, 3DM 71 Buffer ECC error corrected (0039) 285 Buffer integrity test failed (0024) 275 C Cache flush failed, some data lost (0025) 275 Cache synchronization completed (005E) 299 Cache synchronization failed 300 Cache synchronization skipped (004F) 295 cancel rebuild 172 carve size 88 setting 95, 227 certificate message when starting 3DM 73 CLI definition 315 installation 322 Compliance and Conformity 335 configuration changing 128 controller 86 definition 315
status, viewing (3DM) 146 statuses 151 types 3 viewing SMART data 157 Drive Details page, 3DM 221 Drive ECC error reported (0026) 276 Drive error detected (000A) 268 Drive Information page (3BM) 149 Drive Information page (3DM) 148 Drive Information page, 3DM 219 Drive inserted (001A) 271 drive locate 216, 220, 246 Drive not supported (0030) 281 drive performance monitoring definition 16 using 253 Drive power on reset detected (003A) 285 Drive removed (0019) 271 drive requirements 3 Drive timeout detected (
G grown defect, definition 316 formatting 41 making units available 41 partitioning 41 H hardware installation, troubleshooting 255 help, getting for 3BM 69 hot spare 11 creating 113, 114, 115 hot spare (definition) 316 specifying 30 hot swap 6 hot swap (definition) 317 HTTP port number for 3DM 249 J JBOD 11 JBOD disks exporting 96 JBOD policy 89 setting 96 I identify drive by blinking LED 216, 220 enclosure components by blinking 211 identify checkbox in 3DM 216, 220 slot by blinking LED 246 identify c
RAID 1 7 motherboard boot sequence 31 motherboard requirements 2 Mozilla, setting up 71 Multi LUN support (auto-carving) 88, 92 multiple volumes in one unit 92 N name of unit 103, 216 assigning 115, 226 navigation, 3BM 64 NCQ (native command queuing) definition 317 NCQ policy 226 non-redundant units definition 317 O Online Capacity Expansion (OCE), definition 318 operating systems informing of changed configuration 132 operating systems supported 4 Other Controller Settings, 3DM 227 P page refresh 3DM 249 f
3DM 233 definition 319 removing a unit 235 definition 319 Replacement drive capacity too small (002E) 280 rescan controller 145, 231 roaming, array 136, 138 S S.M.A.R.
U UDMA mode, definition 320 ultra DMA protocol 273 Unclean shutdown detected (0008) 267 unconfigured disks, exporting 96 unconfigured drives making visible to operating system 31 uninstalling 3DM on Linux 333 Windows 333 unit checking status in 3DM 146 configuring 101 creating a unit in 3DM 105 introduction 101 creating a unit for the first time, in BIOS 22 creating in 3BM 107 definition 5, 320 deleting a unit 133 in 3BM 135 in 3DM 134 expanding capacity 131 maintaining 146 moving from one controller to ano
disable on degrade, part of Storsave profile 125 enabling in 3BM 119 enabling in 3DM 118 write journaling, part of StorSave profile 124 WWN (World Wide Number) (definition) 321 348 3ware SAS/SATA RAID Software User Guide, Version 9.5.
www.3ware.
