INSTALLATION AND USER’S GUIDE ADAPTEC SATA AND SCSI RAID CONTROLLERS
Adaptec SATA and SCSI RAID Controllers Installation and User’s Guide R
Copyright ©2004 Adaptec, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of Adaptec, Inc., 691 South Milpitas Blvd., Milpitas, CA 95035. Trademarks Adaptec, the Adaptec logo, and Adaptec Storage Manager are trademarks of Adaptec, Inc., which may be registered in some jurisdictions.
Adaptec Customer Support If you have questions about installing or using your Adaptec product, check this document first—you will find answers to most of your questions here. If you need further assistance, use the support options listed below. Technical Support Identification (TSID) Number ■ Before contacting Technical Support, you need your unique 12-digit TSID number. The TSID number identifies your product and support status.
Europe ■ Visit our Web site at www.adaptec-europe.com. ■ German: To speak with a Technical Support Specialist, call +49 89 43 66 55 22, Monday to Friday, 9:00 to 17:00, CET. For support via e-mail, submit your question to Adaptec’s Technical Support Specialists at ask-de.adaptec.com. ■ French: To speak with a Technical Support Specialist, call +49 89 43 66 55 33, Monday to Friday, 9:00 to 17:00, CET. For support via e-mail, submit your question to Adaptec’s Technical Support Specialists at ask-fr.
Limited 3-Year Hardware Warranty 1. Adaptec, Inc. (“Adaptec”) warrants to the purchaser of this product that it will be free from defects in material and workmanship for a period of three (3) years from the date of purchase.
Regulatory Compliance Statements Federal Communications Commission Radio Frequency Interference Statement WARNING: Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment. 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 rules.
Canadian Compliance Statement This Class B digital apparatus meets all requirements of the Canadian InterferenceCausing Equipment Regulations. Cet appareil numérique de la classe B respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada. Japanese Compliance (Voluntary Control Council Initiative) This equipment complies to class B Information Technology equipment based on VCCI (Voluntary Control Council for Interface).
Contents 1 Introduction Kit Contents 1-2 Overview of the Installation Process 1-3 System Requirements and Compatibility 1-3 Drive Requirements 1-4 System Requirements 1-4 Operating System Compatibility 1-4 Motherboard Compatibility 1-5 Controller Features 1-5 Features Overview 1-5 SATA RAID Controller Features Summary 1-6 SCSI RAID Controller Features Summary 1-7 Advanced RAID Features 1-8 About the Documentation 1-11 Using the Adaptec Installation CD 1-12 Booting from the CD with No Operating System 1-12
Contents 3 Installing the Driver Overview of the Driver Installation Process 3-2 Creating the Driver Disk 3-2 Installing the Windows Driver 3-3 Installing the Driver When You Install Windows 3-3 Installing the Driver in an Existing Windows System 3-4 Installing the Linux Module 3-5 Installing the Module When You Install Red Hat 3-5 Installing the Module in an Existing Linux System 3-6 Installing the Unix Driver 3-6 OpenServer 3-6 UnixWare and OpenUNIX 3-8 Installing the NetWare Driver 3-10 Installing the
Contents A Adaptec RAID Configuration Utility (ARC) Overview A-1 Using the ACU A-2 Creating Arrays A-2 Managing Arrays A-4 Initializing Drives A-7 Rescanning Drives A-8 Using SATASelect and SCSISelect A-9 Controller Configuration Options A-10 SATA Configuration Options A-12 SCSI Configuration Options A-13 Using the Disk Utilities A-15 Viewing the Event Log A-16 B ACU for DOS Introduction B-1 Creating the ACU Utility Disk B-1 Running the ACU Interactively B-2 Running the ACU Using Scripts B-3 Playback Mo
Contents Running the AFU from the Command Line C-5 Command Summary C-5 AFU Command Line – Step-by-Step C-9 D Command Line Interface Introduction D-2 Terminology D-2 Accessing the CLI D-4 Accessing the CLI in MS-DOS D-4 Accessing the CLI in Windows D-4 Accessing the CLI in Unix D-4 Using the CLI D-5 Opening and Closing a Controller D-5 Managing Failover Options and Hotspares D-8 Displaying Controller Information D-9 Displaying Disk Information D-11 Displaying Array Information D-12 CLI Command Dictionary
Contents F About SCSI SCSI Device Support F-2 Setting SCSI IDs F-2 Changing SCSI Termination on the Controller F-3 Enabling CD Drive Support F-3 Mixing SE Devices with LVD Devices F-3 G Controller Illustrations H Specifications Glossary xii
1 Introduction In this Chapter...
Introduction Kit Contents Your controller kit includes: ■ Adaptec RAID controller. For controller illustrations, see Appendix G. ■ Installation CD ■ The cables supplied depend on the controller model: Adaptec Model Cables Supplied 2020ZCR None 2120S/2200S 1 internal LVD SCSI cable1 2410SA 4 SATA cables 2810SA 8 SATA cables 21610SA 16 SATA cables 1. Features a multimode terminator. All these SCSI RAID controllers support multimode termination.
Introduction Overview of the Installation Process This section provides an overview of the process of installing, setting-up, and configuring the Adaptec RAID controller: 1 Install and configure the controller and hard drives, as described in Chapter 2, Installing the Controller and Drives. 2 Your next steps depend on your system: In a system without an operating system (fresh install)... a Build the bootable array, as described in Creating a Bootable RAID 5 Array on page 2-4.
Introduction Drive Requirements You need to have enough drives available for the RAID array level you want to build. For details, see Appendix E, About RAID. Note: Arrays work best when all array members (drives) are identical.
Introduction Motherboard Compatibility The Adaptec RAID controller requires a motherboard that meets the following compatibility requirements: ■ Complies with the PCI Local Bus Specification, Revision 2.2 and higher. ■ Supports multifunction devices where one of the devices is a PCI bridge. ■ Provides large memory-mapped address ranges. Refer to the Readme file on the Adaptec installation CD for additional motherboard compatibility information.
Introduction ■ Centralized management across all Adaptec host-based RAID products using Adaptec Storage Manager. In addition to local console access, Adaptec Storage Manager provides remote configuration and management of RAID subsystems through password-protected Web access.
Introduction SCSI RAID Controller Features Summary The SCSI RAID controller features are described in the table below. Note: For more on SCSI, see Appendix F, About SCSI.
Introduction Advanced RAID Features Adaptec RAID controllers support the following advanced features: ■ Optimized Disk Utilization—Allows you to use the full capacity of all your drives, even if drive sizes vary. ■ SATA/SCSI Disk Hot Plug—Allows you to add and remove disks without shutting down your system.
Introduction Drive Enclosures – SCSI only Adaptec SCSI controllers support drive enclosures that include SAF-TE enclosure management hardware per the SAF-TE specification. Hotspares Adaptec RAID controllers support hotspares, drives that are reserved to replace a failing drive in a redundant array. In the event of drive failure, hotspares replace failed drives and arrays are automatically rebuilt.
Introduction Silencing the Alarm The alarm continues to sound until one of the following actions is taken: ■ The array with the failed member is deleted. ■ If the array is redundant, a rebuild begins. ■ The alarm is silenced using SATASelect or SCSISelect. For details, see the Alarm Control option on page A-11 or Adaptec Storage Manager online Help. Automatic Failover Adaptec RAID controllers can automatically rebuild an array when a failed drive is replaced with a new drive.
Introduction About the Documentation The documentation set for the Adaptec RAID controllers includes: ■ Quick Installation Guide—Printed guide that provides the very minimum installation instructions necessary to install and create a bootable array. ■ Readme text file—Contains additional technical information about device compatibility, operating system support, and drivers. (For location, see table below.
Introduction Using the Adaptec Installation CD The Adaptec RAID Installation CD contains array management software, device drivers, and documentation for the Adaptec RAID controller. You can use the CD the following ways: ■ Booting from the CD with No Operating System ■ Using the CD Autorun in Windows ■ Browsing the CD Booting from the CD with No Operating System The Adaptec installation CD is bootable.
Introduction ■ View Documentation—Provides quick access to the PDF files listed in the table on page 1-11. ■ Create Driver Diskette—Allows you to create a driver disk for any supported operating system. Browsing the CD If your installation process requires you to directly access files on the Adaptec installation CD, you can save time by limiting your browsing to the following files and folders, available at the root level: ■ Autorun executable—In Windows, click on autorun.
Introduction ■ UNIX—Use Acrobat Viewer because Reader is not available for all operating systems. Your system must have Java Runtime Environment 1.1.7B from April 11, 2000 or later. The Viewer is located on the installation CD at mount-point/Acrobat_Reader. Note: To download Java Virtual Machine (JVM), visit java.sun.com. ■ NetWare—Acrobat Reader and Viewer are not available for this operating system or any DOS environment. You need to use a computer that supports Acrobat Reader or Acrobat Viewer.
Introduction Command Line Interface (CLI)—Allows you to automate array creation or testing in a production environment using scripts. For details, see Appendix D. ■ Safety Information To ensure your personal safety, as well as the safety of you equipment: ■ Keep your work area and the computer clean and clear of debris. ■ Before opening the system cabinet, unplug the power cord. Electrostatic Discharge Electrostatic Discharge (ESD) is a natural by-product of human activity.
2 Installing the Controller and Drives In this Chapter...
Installing the Controller and Drives SATA Drives and Cables To install an Adaptec SATA RAID controller and drives, you need equal numbers of each of the following: ■ Serial ATA hard drives ■ Serial ATA cables (supplied in this kit) Configuration of Serial ATA drives is simple for the following reasons: ■ There are no jumpers or switches to set on SATA controllers or hard drives.
Installing the Controller and Drives Installing the Controller and Drives To install Adaptec RAID controller and drives: 1 If you have a low-profile controller and a low-profile computer cabinet, replace the original full-height bracket with the lowprofile bracket supplied in Adaptec RAID controller kit. To verify the form factor of your controller model, see Controller Features on page 1-5. 2 Turn off your computer. 3 Ground yourself by touching the system chassis. 4 Unplug the power cord.
Installing the Controller and Drives Determining the Boot Controller Note: If your system will contain two or more bootable controllers, read this section. Otherwise, skip this section. The Adaptec RAID controller supports bootable drives and arrays. The default setting of the controller and system Setup usually allows you to install and boot from either a hard drive connected to the motherboard, or from a drive or array connected to the controller.
Installing the Controller and Drives Why build a RAID 5? This array level is supported by your controller. It provides a versatile combination of performance and redundancy on a minimum of three drives. Because RAID 5 uses parity, it is the safest, and most recoverable, of all RAID levels. What if I prefer a different array level? That’s no problem.
Installing the Controller and Drives 9 Press Y, then Enter. The selected drives are initialized, then the ACU screen is displayed. 10 Using the arrow keys, highlight Create Array, then press Enter. 11 Using the arrow keys as in Step 7, highlight at least three drives to be used in the array and press Insert for each highlighted drive. 12 Press Enter.
Installing the Controller and Drives Using the Adaptec Installation CD Note: SCSI only—You cannot create the RAID using a CD drive connected to the RAID controller. To build a bootable RAID 5 array using the Adaptec installation CD: 1 Install the controller and drives, as described in Installing the Controller and Drives on page 2-3. 2 Start or restart the computer. 3 Insert the Adaptec installation CD.
Installing the Controller and Drives 10 Click Next. 11 Type the name you want to assign to the RAID 5 you are creating, then click Apply. The system creates the array. The display refreshes to show the just-created RAID 5 on the right side of the display. You may use the array immediately. However, if you want to make the array bootable you must allow the array to finish building before restarting the system. 12 When you are ready to continue, close all windows. The Main Menu is active.
3 Installing the Driver In this Chapter...
Installing the Driver Overview of the Driver Installation Process Adaptec recommends the following driver installation procedure: 1 Create a driver disk. See Creating the Driver Disk on page 3-2 for details. 2 Identify the appropriate installation procedure for your computer. You need to know the operating system and whether you are installing the driver while also installing the operating system, or installing the drive onto a system that already has the operating system installed.
Installing the Driver 4 Click Create Driver Disk, then select the appropriate operating system. 5 If you selected Linux, you need to also select the architecture, one of the following: – i386—For Intel 386 or 486 computers – i586—For Pentium I or II computers – i686—For Pentium III, IV, or AMD K-6 computers – Athlon—AMD Athlon computers 6 Select the appropriate floppy drive letter, then choose the appropriate format. You need a full format only if the disk has never been formatted or may have bad sectors.
Installing the Driver 5 When prompted to install a third-party driver, press F6. Note: When F6 is active, a prompt appears at the bottom of the screen for only 5 seconds. If you miss your chance to press F6, restart the computer. 6 Insert the driver floppy disk and wait until prompted to install a driver. Press S to specify that the driver is on the floppy disk, then press Enter. The computer reads the disk. 7 When the Adaptec driver is found, press Enter.
Installing the Driver Installing the Linux Module This section contains the following procedures: ■ Installing the Module When You Install Red Hat ■ Installing the Module in an Existing Linux System Notes: ■ SuSE Linux only—The controller is not supported as a bootable controller. In other words, you can only use Installing the Module in an Existing Linux System on page 3-6. ■ For the most up-to-date information on Adaptec’s support of Linux, visit www.adaptec.com.
Installing the Driver Installing the Module in an Existing Linux System To install the module in an existing Red Hat or SuSE Linux system: 1 Insert and mount the Adaptec installation CD. 2 Install the module RPM by typing: rpm -Uvh mount-point/linux/arc/driver/aac1.1.4-2322.rpm 3 Run fdisk, mkfs, and create mount points for any new drives.
Installing the Driver 9 To enable RAID management software and utilities, type the following commands: cd mount-point/openserv/arc/driver/aacraid/reloc/tmp/aacraid/scripts cp ./aacaifd /usr/sbin cp ./S98aacaifd /etc/rc2.d chmod 755 /usr/sbin/aacaifd /etc/rc.d/S98aacaifd Installing the Driver in an Existing OpenServer System To install the driver in an existing operating system: 1 Install and configure your Adaptec RAID controller and hard drives, as described in Chapter 2.
Installing the Driver UnixWare and OpenUNIX This section contains the following procedures: ■ Installing the Driver When You Install UnixWare or OpenUNIX ■ Installing the Driver in an Existing UnixWare or OpenUNIX System Note: Although the driver disk you create for UnixWare and OpenUNIX differ, the installation procedures for these operating systems are the same.
Installing the Driver 3 Turn on the computer, then insert the driver disk. 4 To run the pkgadd utility, type pkgadd -d diskette1 and then press Enter. UNIX reads the disk and package information. 5 Press Enter. 6 Restart the computer. The system rebuilds the kernel automatically. 7 Add devices created on the RAID controller to the operating system. For details, refer to your OpenServer documentation.
Installing the Driver Installing the NetWare Driver This section contains the following procedures: ■ Installing the Driver When You Install NetWare on page 3-10 ■ Installing the Driver in an Existing NetWare System on page 3-11 ■ Loading NetWare Drivers During Server Restart on page 3-12 Installing the Driver When You Install NetWare To install the driver with the operating system during a fresh install: 1 Install and configure the controller and hard drives, as described in page 2-3.
Installing the Driver 13 Press the Enter key to scan the floppy drive. Once the driver is selected, the parameter screen is displayed. 14 Verify the loaded drivers. From the lower window menu, select Continue, then press Enter. Note: If the driver installation process fails, the server console is displayed so you can see the cause of the failure. Now that you have installed the drivers, refer to your NetWare documentation to modify disk partitions, apply hot fixes, or perform volume maintenance.
Installing the Driver 13 Press Enter to scan for the drivers. 14 Select Adaptec AdvancedRAID Controller and press Enter. The aacraid parameters screen is displayed. 15 Select Select/Modify driver Parameters and press Enter. 16 Select Save parameters and load driver. 17 When prompted to select an additional driver, select No. 18 Press Esc to exit the Nwconfig utility. 19 Create any arrays using the ARC utility (see Using the ACU on page A-2) or remotely using Adaptec Storage Manager (refer the online Help).
Installing the Driver To modify the startup.ncf file: 1 At the server console prompt, type load nwconfig and press Enter. 2 Select the NCF File Options menu, then press Enter. 3 Select the Modify Startup.ncf option, then press Enter. 4 Make the necessary changes. When you are done, press Esc. Note: You can also use your DOS text editor to modify the startup.ncf file, it resides on the DOS partition. For additional information on the startup.ncf file, refer to your NetWare documentation.
4 Installing and Starting Adaptec Storage Manager In this Chapter...
Installing and Starting Adaptec Storage Manager Installing Storage Manager on Windows This section provides instructions for installing Storage Manager. Note: On Windows, Storage Manager supports up to 16 Adaptec RAID controllers. To install Storage Manager: 1 Insert the Adaptec installation CD and wait for the Autorun executable to start the installation. If this does not occur, browse the CD and click Autorun.
Installing and Starting Adaptec Storage Manager Installing Storage Manager on Linux Notes: ■ With Linux, Storage Manager supports up to 12 Adaptec RAID controllers. ■ Storage Manager includes the Java Runtime Environment (JRE). ■ If a previous version of Storage Manager is already installed and you are upgrading, you must first remove that version. Any customization files you may have created when you used the previous version are saved and used in the upgrade.
Installing and Starting Adaptec Storage Manager Installing Storage Manager on OpenServer Notes: ■ With OpenServer, Storage Manager supports up to 12 Adaptec RAID controllers. ■ You need either the Java Development Kit (JDK) for SCO or the Java Runtime Environment (JRE) for SCO, version 1.3.1. To download these, visit www.thescogroup.com. ■ OpenServer 5.06 only—Requires the following packages: urwfonts and package set OSR-compatible Version 8.0.
Installing and Starting Adaptec Storage Manager When successful, a copyright message is displayed in the terminal window. If you want RAID Agent to run at startup all the time, add the following line to the /etc/inittab and /etc/conf/init.d/kernel files: nfra:12346:once:sh /opt/RaidMan/RaidAgnt.sh Installing Storage Manager on UnixWare & OpenUNIX Notes: ■ With UnixWare and OpenUNIX, Storage Manager supports up to 12 Adaptec RAID controllers. ■ You need root privileges to install Storage Manager.
Installing and Starting Adaptec Storage Manager 6 UnixWare Only—To start RAID Agent, type the following casesensitive command: sh /opt/RaidMan/RaidAgnt.sh When successful, a copyright message is displayed in the terminal window. If you want RAID Agent to run at startup all the time, add the following line to the /etc/inittab and /etc/conf/init.d/kernel files: nfra:12346:once:sh /opt/RaidMan/RaidAgnt.
Installing and Starting Adaptec Storage Manager Starting Storage Manager Note: You need root privileges to run Storage Manager. To start Storage Manager, use the procedure outlined in the table below for your operating system. If your operating system is... Start Storage Manager as follows... Windows To run Storage Manager as a standalone application, click Start > Programs > Adaptec Storage Manager, then select the appropriate icon.
Installing and Starting Adaptec Storage Manager Logging into Remote Systems To log into a remote system: 1 Click Remote > Add Remote System. Storage Manager displays the login screen, as shown below. 2 Type the IP address. The default System startup port number, 34571, is supplied for you. 3 For Username, type admin 4 For Password, type adaptec Note: The username and password are case sensitive. Once you are logged in for the first time, you can add new accounts and change account passwords.
5 Understanding Adaptec Storage Manager In this Chapter... Introduction 5-1 Overview 5-2 Changing How Drives are Displayed 5-3 Collapsed and Expanded Views 5-4 Component Views 5-5 Introduction This chapter provides an overview of Adaptec Storage Manager, the user-friendly graphical user interface that you use to easily create and manage arrays. For more details on using Adaptec Storage Manager to set up and manage arrays, refer to the online Help.
Understanding Adaptec Storage Manager Overview Adaptec Storage Manager provides an expandable tree view of the systems and controllers you are managing. You can perform most configuration and management tasks by selecting a controller from the tree and working with related objects. The figure below shows how Adaptec Storage Manager displays information about Physical and Logical devices. Using the buttons in the Physical devices and Logical devices views, you can: ■ Change how drives are displayed.
Understanding Adaptec Storage Manager For example, the fan indicator changes to yellow when one fan fails; it changes to red when a second fan fails and cooling is no longer adequate. Logical Devices View This view displays information about the logical devices created using the physical devices, including the number of logical devices, the RAID level of each device, and whether a logical device is protected by a hotspare.
Understanding Adaptec Storage Manager Collapsed and Expanded Views You can display a collapsed or expanded view of the system configuration. Initially, Storage Manager displays a collapsed textual view of the configuration information in both the Logical devices and Physical devices views. In the Logical devices view... Click to expand and collapse information about disk groups and logical devices.
Understanding Adaptec Storage Manager Component Views When you click a physical or logical device in the device views, the related components are highlighted in the other view. ■ When you click a logical device in the Logical devices view, the physical drives that make up the logical device are highlighted in the Physical devices view, and vice-versa. ■ When you click a hotspare, the logical devices protected by that spare are highlighted.
A Adaptec RAID Configuration Utility (ARC) In this Appendix... Overview A-1 Using the ACU A-2 Using SATASelect and SCSISelect A-9 Using the Disk Utilities A-15 Viewing the Event Log A-16 Overview The Adaptec RAID Configuration (ARC) utility is part of the controller BIOS. The utility includes: ■ Array Configuration Utility (ACU)—Used to create, configure, and manage arrays, and make arrays bootable. Also used to initialize and rescan drives.
Adaptec RAID Configuration Utility (ARC) The Adaptec RAID Controller menu presents the following options: ■ Array Configuration Utility ■ SATASelect and SCSISelect Utilities ■ Disk Utilities To select a menu option in ARC, browse with the arrow keys, then press Enter. Sometimes, selecting an option displays another menu; to return to the previous menu at any time, press Esc. The following sections discuss each of these menu options.
Adaptec RAID Configuration Utility (ARC) 4 From the ARC menu, select Array Configuration Utility. 5 From the ACU menu, select Create Array. 6 Browse with the arrow keys to select a channel. 7 Select the disks for the new array, then press Insert. To deselect a disk, highlight the disk, then press Delete. ACU displays the largest usable space available for each disk. You can use available space from multiple disks for the new array.
Adaptec RAID Configuration Utility (ARC) 3 Enter the desired array size. The maximum array size available based on the partitions you selected is displayed automatically. If you want to designate a different array size, type the desired array size and select MB (megabytes), GB (gigabytes), or TB (terabytes) from the dropdown list. If the available space from the selected partitions is greater than the size you specify, the remaining space is available for use in other arrays.
Adaptec RAID Configuration Utility (ARC) Viewing Array Properties To view the properties of an existing array: 1 From the ACU main menu, select Manage Arrays. 2 From the List of Arrays dialog box, select the array you want to view, then press Enter. To view properties related to the array’s physical disks: – RAID 0, 1, 5 (Single-Level Arrays)—View the Array Properties dialog box. – RAID 10, 50 (Dual-Level Arrays)—Highlight the array member you want to view, then press Enter to display the second level.
Adaptec RAID Configuration Utility (ARC) You can make an array bootable so that the system boots from the array instead of from a stand-alone (single) disk. To make an array bootable: 1 From the ACU main menu, select Manage Arrays. 2 Select the array you want to make bootable, then press Ctrl+B. This changes the selected array’s number to 00, making it the controller’s boot array. 3 Restart the computer. Deleting Arrays ! Caution: When you delete an array, you delete all the data from the array.
Adaptec RAID Configuration Utility (ARC) 3 Select a drive, then press Insert to assign the drive as a hotspare. The specified drive is displayed in the Assigned Hotspares drives list. 4 Press Enter to save the hotspare assignment. 5 If you are finished managing hotspares, press Y (for yes) when prompted to return to the main menu. To remove an assigned hotspare from an array: 1 Select Manage Arrays from the main menu.
Adaptec RAID Configuration Utility (ARC) To initialize drives: 1 Restart the computer, then press Ctrl+A when prompted to access the ARC utility. 2 From the ARC menu, select Array Configuration Utility. 3 Select Initialize Drives. 4 Browse with the arrow keys to select a channel. 5 Browse with the arrow keys to highlight the disk you want to initialize, then press Insert. 6 Repeat Step 5 until all the drives to be initialized are selected. 7 Press Enter.
Adaptec RAID Configuration Utility (ARC) Using SATASelect and SCSISelect The SATASelect and SCSISelect utilities allow you to change controller and device settings without opening the computer cabinet or handling the controller. To access these utilities: 1 Restart the computer, then press Ctrl+A when prompted to access the ARC utility. 2 If multiple controllers are installed, select the controller you want to configure, then press Enter.
Adaptec RAID Configuration Utility (ARC) Controller Configuration Options The Controller Configuration options are described in the table below. Models Affected Option Default Description Drives Write Cache Drive's Default All When Enabled, write cache is enabled, providing maximum drive performance. When Disabled, no write cache is used on the drive. By default, the drive’s setting is used.
Adaptec RAID Configuration Utility (ARC) Option Default Models Affected Array-based BBS Support Disabled All When Enabled in systems that support BBS, the controller presents attached bootable devices up to the host system's BIOS for boot device selection. This is relevant for logical arrays. Physical Drives Display during POST Disabled All When Enabled, attached physical devices are displayed during system POST. Displaying the devices adds a few seconds to the overall POST time.
Adaptec RAID Configuration Utility (ARC) SATA Configuration Options The SATA Configuration options are described in the table below. Models Affected Option Default Description Write Cache Yes All SATA controllers When Enabled, write cache is enabled, providing maximum performance. Caution—When Enabled, there is a potential for data loss or corruption during a power failure.
Adaptec RAID Configuration Utility (ARC) SCSI Configuration Options To access the SCSI Device Configuration options, select SCSI Configuration. SCSI Channel Interface Definitions The SCSI Channel Interface Definitions are described in the table below. Option Default Description Controller SCSI Channel ID 7 Sets the controller’s SCSI ID. Adaptec recommends that you leave the controller set to the default, which gives it the highest priority on the SCSI channel.
Adaptec RAID Configuration Utility (ARC) SCSI Device Configuration Options The SCSI device settings allow you to configure certain parameters for each device on the SCSI channel. To configure settings for a specific device, you must know the SCSI ID assigned to that device. If you are not sure of the SCSI ID, see Using the Disk Utilities on page A-15. To access the SCSI Device Configuration options, select SCSI Configuration, then select Additional Options.
Adaptec RAID Configuration Utility (ARC) Using the Disk Utilities The disk utilities allow you to low-level format or verify the media of the hard drives. To access the disk utilities: 1 Restart the computer, then press Ctrl+A when prompted to access the ARC utility. 2 If multiple controllers are installed, select the controller you want to configure, then press Enter. 3 From the ARC menu, select Disk Utilities. 4 Select the desired disk, then press Enter.
Adaptec RAID Configuration Utility (ARC) Viewing the Event Log The BIOS-based event log stores all firmware events (configuration changes, array creation, boot activity, and so on). The event log has a fixed size. Once full, old events are flushed as new events are stored. Also, the log is volatile; therefore, it is cleared after each system restart. To access the event log: 1 Restart the computer, then press Ctrl+A when prompted to access the ARC utility.
B ACU for DOS In this Appendix... Introduction B-1 Creating the ACU Utility Disk B-1 Running the ACU Interactively B-2 Running the ACU Using Scripts B-3 Introduction The Array Configuration Utility (ACU) allows you to create, configure, and manage arrays. Creating the ACU Utility Disk The DOS version of this utility runs from a floppy disk that you need to create using the following procedure: 1 To find the ACU executable, acu.
ACU for DOS Running the ACU Interactively To run the ACU interactively: 1 Insert the ACU utility disk you created in Creating the ACU Utility Disk. 2 Start or restart your computer. The computer boots to the DOS command line. 3 Type ACU on the command line, then press Enter.
ACU for DOS Running the ACU Using Scripts To use the ACU scripting features, use the ACU command, specify a script file (see Creating the Script File Manually on page B-5), and specify one (but not both) of the required switches listed in the table below. You may also add one or both of the optional switches listed in the table. Note: Command line syntax is not case sensitive.
ACU for DOS Playback Mode In this mode, the ACU reads the contents of the specified script file and creates arrays based on the keywords specified in the script. The syntax is ACU /P where file is the parameter specifying name of the script file. The file parameter can include a drive, directory, filename, and extension. If no drive or directory is specified, the file is placed in the location of the ACU executable.
ACU for DOS Notes: ■ ■ ■ Record Mode can be used to record only one controller at a time. Therefore, if you want to record multiple controllers, record them separately using separate script files. Because the ACU supports only a subset of array types available, it cannot record all the possible array configurations.
ACU for DOS Array Definition Block Keywords The array definition block always begins with the keyword Array and ends with the keyword End. The other required array definition keywords are Drives and Type. The array definition keywords are listed in the table below alphabetically. Required? Default Value Array Yes None Indicates the start of an array definition block. See page B-7). Drives Yes None Specifies the devices used in creating the array. See page B-7).
ACU for DOS The keywords are described in detail in the sections that follow. Array Keyword Array is a required keyword, indicating the start of an array definition block. The syntax is Array=
ACU for DOS HotspareDrives Keyword HotspareDrives is an optional keyword, specifying the hotspares to assign to the array. The syntax for listing hotspares is the same as the Drives Keyword on page B-7. If HotspareDrives is not specified, no hotspares are assigned to the array. Notes: ■ HotspareDrives creates only dedicated hotspares. If the same drive is assigned to protect multiple arrays, only the last array that drive is assigned to is protected.
ACU for DOS Notes: ■ InitializeAll is a global keyword that you need to specify only once. ■ InitializeAll is always performed prior to array creation regardless of its position in the script. ■ If both InitializeAll=Yes and InitializeAll=No are specified in the same script file, InitializeAll=Yes is always the overriding value. ■ If an array is deleted during a build/verify process, the process is automatically terminated. Possible values are as follows: ■ Yes—Initialize all drives.
ACU for DOS ReadCache Keyword ReadCache indicates whether the array uses read caching. Possible values are: ■ Yes (the default)—Enable read caching. ■ No—Disable read caching. Example ReadCache=Yes Size Keyword The Size keyword specifies the size of the array. Specify Maximum (the default) to create an array using the maximum available space, based on the array type and drives selected.
ACU for DOS Type Keyword Type is a required keyword, indicating the array type. There is no default value. The Type keyword values are: ■ Volume ■ RAID5 ■ RAID0 ■ RAID10 ■ RAID1 ■ RAID50 Note: For information about which array types your controller supports, see Controller Features on page 1-5. Wait Keyword Wait is an optional keyword that you can use to tell the ACU to allow the ACU to continue while the build/verify or clear completes in the background; specify wait=no.
ACU for DOS Channel Definition Block Keywords – SCSI only The channel definition block is optional. If used, it always begins with the keyword Channel and ends with the keyword End. The channel definition block keywords are listed in the table below. Keyword Description Channel Used to identify the channel. End Indicates the end of a channel definition block. ControllerID Changes the SCSI ID of the controller.
ACU for DOS ACU Error Codes When the ACU detects an error, it reports the error and exits immediately. If a log file is specified, the ACU writes the error code to the log file. Otherwise, it displays the error code on the screen. The possible error messages returned by the ACU are listed in the table below. ACU Error Codes Code Description 0 ACU ran without changes—The ACU exited with no errors (success) and no report is required.
ACU for DOS ACU Error Codes "Continued" Code Description 14 Insufficient memory to run the application—There is not enough memory to run the ACU. 15 Incorrect controller number—The controller number you specified is invalid or out-of-range. 16 Controller not responding—The controller has stopped responding to the ACU. 17 Build/Verify/Clear failed—The build/verify or clear operation for one or more arrays has failed.
ACU for DOS The following sample script file creates a maximum-size threedrive RAID 5.
C Adaptec Flash Utility (AFU) In this Appendix... Introduction C-1 Creating the Firmware Floppy Disks C-3 Running the AFU from the GUI C-4 Running the AFU from the Command Line C-5 Command Summary C-5 Introduction The Adaptec Flash Utility (AFU) is a DOS utility used to update, save, or verify RAID controller firmware BIOS, and NVRAM. ! Caution: The AFU is easy to use and contains safeguards to prevent you from accidentally damaging the controller’s flash contents.
Adaptec Flash Utility (AFU) The AFU is used to: ■ Update—Updates all the flash components on a controller with the flash image data from a User Flash Image (UFI) file. The AFU updates the controller’s flash by reading UFI files and writing them to the controller’s flash components. Note: The UFI includes the controller’s type, thereby ensuring that the AFU uses the correct file. ■ Save—Reads the contents of a controller’s flash components and saves the data to a UFI file.
Adaptec Flash Utility (AFU) Firmware and UFI File Locations The firmware and UFI file locations on the Adaptec Installation CD are as follows Creating the Firmware Floppy Disks Controller firmware is available two ways: ■ From the Adaptec installation CD—The CD includes the AFU executable, AFU.exe, the corresponding documentation, and a separate flash image. The flash image may be comprised of multiple UFI files.
Adaptec Flash Utility (AFU) 3 Start the AFU as described in Running the AFU from the GUI on page C-4 and follow the prompts. Running the AFU from the GUI The easy way to run the AFU is to use its Graphical User Interface (GUI). If you prefer to run the AFU from the command line, see page C-5. To access the AFU: 1 Create the firmware floppy disks, as described in Creating the Firmware Floppy Disks on page C-3.
Adaptec Flash Utility (AFU) Running the AFU from the Command Line At the DOS command prompt (typically A:\>), type AFU followed by a command and any switches. The AFU processes the command, prompts you to insert additional floppy disks as needed, exits, and reports success or an error message code. Command Summary This section describes each of the AFU commands in detail. The commands appear alphabetically. HELP The HELP command displays a summary of AFU functions and command switches.
Adaptec Flash Utility (AFU) SAVE The SAVE command saves the contents of a controller’s flash in a UFI file. The name of the UFI file is based on the controller type and cannot be changed. You must restart the computer following a SAVE command.
Adaptec Flash Utility (AFU) Examples In the following example, the AFU saves flash contents from controller 0 to a UFI file in the current default drive and directory: A:\> AFU SAVE /C 0 In the following example, the AFU saves flash contents from Controller 1 to a UFI file in C:\UFI_FILES. A:\> AFU SAVE /C 1 /D C:\UFI_FILES UPDATE The UPDATE command updates a controller’s flash components from the flash image data in a UFI file.
Adaptec Flash Utility (AFU) VERIFY The VERIFY command compares the contents of each of the flash components on a controller to the corresponding image in a UFI file and indicates whether they match. Use this command to determine whether a controller’s flash components are up-to-date when compared to a specific UFI file. After using the VERIFY command, you must restart the computer upon completion of this command.
Adaptec Flash Utility (AFU) Example The following example displays version information about all supported controllers. A:\> AFU VERSION /C 0 Adaptec Flash Utility V4.0-0 B5749 (c)Adaptec Inc. 1999–2002. All Rights Reserved. Version Information for Controller #0 (Adaptec 2410) ROM: Build 5748 [VALID] Fri Sep 27 13:28:40 EDT 2002 A:\> AFU VERSION /C ALL AFU Command Line – Step-by-Step This section provides step-by step instructions for updating your the flash.
Adaptec Flash Utility (AFU) b Updating the Flash on Multiple Controllers—To flash the firmware on multiple controllers, type: afu update /C , Where and is the number of one of the Adaptec RAID controllers whose firmware you are updating.
D Command Line Interface In this Appendix...
Command Line Interface Introduction The Command Line Interface (CLI) allows you to configure and manage controller components. The CLI contains most of the functionality offered by Adaptec Storage Manager, plus some additional functionality not offered by Adaptec Storage Manager. CLI commands allow you to automate testing or array creation in a production environment using Windows command scripts and Linux and Unix shell scripts. This appendix describes briefly some of the commands available in the CLI.
Command Line Interface All Controllers The following terms are used in discussing the CLI: ■ Array, container—A logical disk created from available space and made up of one or more partitions on one or more physical disks. ■ Stripe, chunk—Contiguous set of data distributed across all the disks in an array. A striped array distributes data evenly across all members in equal-sized sections called stripes. ■ Free or available space—Space on an initialized disk that is not in use.
Command Line Interface Accessing the CLI The method you use to access the CLI depends on the operating system (OS), as described below. Accessing the CLI in MS-DOS To access the CLI from the MS-DOS prompt, move to the directory containing the afacli executable, then type afacli. Accessing the CLI in Windows To access the CLI: Note: The following procedure assumes that you accepted the default location for the software during installation. 1 Click the Start button. 2 Click Programs.
Command Line Interface From the NetWare server console To access the CLI from the NetWare server console, type aaccli at the prompt. When the system displays the CLI> prompt, which indicates that you can now use CLI commands. Using the CLI This section contains some examples of using CLI commands to perform common tasks. Opening and Closing a Controller To prepare a controller to receive a CLI command, you first need to open the controller. You may open only one controller at any time.
Command Line Interface Displaying Information about Your Array After creating an array, use the container list command to display information about the array. In the following example, the Num Label column indicates the array ID 0 and the array label Venus. The Type column indicates a volume set. The Total Size column indicates that the array is 100 MB.
Command Line Interface Creating a RAID 1 To create a RAID 1, use the container create new_mirror command. In the following example, a RAID 1 is created on devices 0:02:0 and 0:03:0 using 100 MB of available space from each device. AAC0> container create new_mirror ((0,2,0), 100M) (0,3,0) Executing: container create new_mirror ((CHANNEL=0,ID=2,LUN=0),104,857,600 ) (CHANNEL=0,ID=3,LUN=0) Creating a RAID 5 When you create a RAID 5, you use a form of redundancy called parity.
Command Line Interface Managing Failover Options and Hotspares To assign one or more hotspares to a single array, use the container set failover command. To assign one or more spare disks for all arrays, use the container set global_failover command. These commands allow you to add hotspares to an array prior to a drive failure so that the array contains the resources it needs to survive a failure.
Command Line Interface Enabling Automatic Failover To enable automatic failover, use the controller set automatic_failover command with the /failover switch, as in the following example: AAC0> controller set automatic_failover /failover_enabled=TRUE Executing: controller set automatic_failover /failover_enabled=TRUE After running the controller set automatic_failover command, use the controller show automatic_failover command to verify that automatic failover has been enabled.
Command Line Interface Controller Details The controller details attributes are defined as follows: ■ Controller Name—Name ■ Controller Type—Product name ■ Controller Availability—Access mode ■ Controller Remote Computer—Name of the remote computer on which an open controller resides ■ Controller Serial Number—Last six hexadecimal characters of the serial number ■ Controller CPU Type—CPU ■ Number of Channels—Number of channels ■ Number of Devices Per Channel—Maximum number of devices, not in
Command Line Interface Displaying Disk Information The CLI allows you to monitor or manage disk attributes, prepare a disk for use by a controller, and detect defects using the following commands: ■ Disk List ■ Disk Show Defects ■ Disk Verify Disk List The disk list attributes are defined as follows: ■ Device ID—An ID number assigned to each device attached to a channel ■ Device Type—Reports whether the device is a disk, printer, scanner, and so on ■ Removable Media—Reports whether the media is
Command Line Interface Disk Show Defects The disk show defects command shows the following types on information: ■ Total number and location of primary defects (defects that originate during manufacturing) ■ Total number and location of grown defects (defects that originate after manufacturing) Example In the example below, the drive contains five primary defects and no grown defects: AAC0> disk show defects /full=true (0,1,0) Executing: disk show defects /full=TRUE (CHANNEL=0,ID=1,LUN=0) Number of PR
Command Line Interface ■ Root Special File (Unix/Linux only)—File associated with the array and created by the OS after array creation. Appears in the Num Label column. ■ Array Number—ID of an array (0 to 63). ■ Array Label—Name assigned to an array. Not automatically assigned. Appears in the Num Label column. ■ Array Type—Defines an array as a volume, RAID 0, RAID 1, etc., or a reconfigured array. ■ Creation Date—Month, day, and year the array was created.
Command Line Interface ■ Mirror Set Create—Creation of a RAID 1 (mirror). ■ Mirror Set Normal—The RAID 1 is in the normal state. ■ Reconfiguration Copy Container—An array is being used as a copy (hidden) array (Copy). ■ Reconfiguration Destination Container—An array is being used as a destination (hidden) array (Dest). ■ Reconfiguration RAID 5 Set—An array is being used as a RAID 5 (hidden array). ■ Reconfiguration Source Container—An array is being used as a source (hidden) array.
Command Line Interface CLI Command Dictionary This section contains a command reference for the following command groupings: ■ General Control Commands ■ Container (Array) Commands ■ Controller Commands ■ Disk Commands ■ Logfile Commands ■ Task Commands ■ Enclosure Commands General Control Commands close Closes the currently opened controller. exit Closes the opened controller and exits the CLI. help [/full] [{command}] Invokes general or topical help.
Command Line Interface open [/readonly={boolean}] [/domain={string}] {name} Opens a controller, a prerequisite for any controller command to be used on that controller. Parameters {name}—Computer name and the controller to open. Switches /readonly—If TRUE, the controller is opened for read-only access. (The default is FALSE.) If you open a controller with read-only access, you can use only those commands that do not change the controller configuration.
Command Line Interface Switches /always—Specifies whether to clear the array even if it has data on it. The default is FALSE, meaning that the command clears the array only if it has no data on it. All user files must be closed; the /always switch cannot override this restriction. /wait— If FALSE (the default), the operation is performed in the background and the command prompt is returned immediately. If TRUE, the operation is performed immediately and the command prompt is returned only when done.
Command Line Interface Switches /io_delay—Number of milliseconds between each I/O used for the RAID 1 create. /wait— If FALSE (the default), the operation is performed in the background and the command prompt is returned immediately. If TRUE, the operation is performed immediately and the command prompt is returned only when done. container create mstripe [/stripe_size={integer}] [/label={string}] {container} [{container}...] Creates a multilevel RAID 0 (stripe).
Command Line Interface container create raid5 [/cache={boolean}] [/stripe_size={integer}] [/clear={boolean}] [/label={string}] [] [/scrub={boolean}] [/wait={boolean}] {free_space} [{device_ID}...] Creates a RAID 5. Parameters {free_space}—Drive and its associated available space used to create the array. {device_ID}—One or more devices whose available space to be used to create the array. Switches /cache—Specifies whether to enable the array’s cache.
Command Line Interface Switches /cache—Specifies whether to enable caching on the array. /stripe_size—Stripe size for the RAID 0. The default is 64 KB. /label—Label to assign to the new RAID 0. container create volume [/cache={boolean}] [/label={string}] {device_ID}, {free_space}, {device_ID}, [{free_space}...] Creates a volume. Parameters {device_ID}—Drive and its associated available space to be used to create the volume. {free_space}—Available space to be used to create the volume.
Command Line Interface container list [/all={boolean}] [/full={boolean}] [{container}] Lists information about the arrays on the controller. Parameters {container}—ID number of the array containing information to display. Switches /all—Specifies whether to list all containers on the system. /full—Specifies whether to display detailed information. container move {container1} {container2} Moves the first array number specified to the second array number specified; in effect, to renumber an array.
Command Line Interface Parameters {container}—ID number of the array to set to read-write access. container reconfigure [/stripe_size={integer}] [/mirror={boolean}] [/partition_move={boolean}] [/partition_size={integer}] [/raid5={boolean}] [/raid10={boolean}] [/restart={boolean}] [/stripe={boolean}] [/volume={boolean}] [/wait={boolean}] {container} [{device_ID}...] Changes the configuration of an array. Parameters {container}—ID number of the array to reconfigure. {device_ID}—One or more devices.
Command Line Interface Parameters {container}—ID number of the array whose assigned failover disk is to be removed. {device_ID}—ID for the device to remove as a failover disks. container remove global_failover {device_ID} [{device_ID}...] Removes a global failover assignment. Parameters {device_ID}—ID for the device to remove as a failover disk. container restore RAID5 {container} Tries to restore a RAID 5 that has a number of dead partitions as members.
Command Line Interface container set cache [/read_cache_enable={boolean}] [/unprotected={boolean}] [/write_cache_enable={boolean}] {container} Sets cache parameters for a specific array. Useful only if a native OS's file system resides on the array. Parameters {container}—ID number of the array on which to set cache parameters. Switches /read_cache_enable—Specifies whether to enable the readahead cache.
Command Line Interface Parameters {container}—ID number of the array on which to set the I/O delay. {integer}—Number of milliseconds the controller waits between I/O operations. container set label {container} {label} Assigns a new label to the array. Parameters {container}—ID number of the array to which to assign a label. {label}—Specifies the label to assign. container show cache {container} Displays caching parameters for an array.
Command Line Interface controller details Shows details about the open controller and software. controller firmware compare [/C{controller}] [{controller}...] [/D{UFI_file_path}] Compares the contents of each of the flash components on a controller to the corresponding image in User Flash Image (UFI) files and indicates whether they match. Switches /C{controller}—ID representing the set of controllers on which to perform the firmware comparison. /D{UFI_file_path}—Location of the UFI files.
Command Line Interface controller list [/domain={string}] [{string}] Lists all controllers or displays information about the currently opened controller. Parameters {name}—Computer name from which to display all controllers or specific information about the open controller. Switches /domain (Windows only)—Specifies the domain in which the host to be searched resides. controller pause_io [{integer}] Windows only—Pauses all I/O activity on the open controller to allow online manipulation of hardware.
Command Line Interface controller set container_verify [/verify_enabled={boolean}] Turns the container verify task on or off. Switches /verify_enabled—Specifies whether to turn on or off the container verify feature. The default is TRUE, which means the command turns on the container verify feature. controller show automatic_failover Displays the automatic failover status (enabled or disabled) for the controller.
Command Line Interface Switches /always—Specifies whether to initialize the disk even if the disk has existing data. (Cannot override open files.) The default is FALSE. /unconditional—Specifies whether to initialize the disk even if arrays on the disk have open files. The default is FALSE. disk list [/all={boolean}] [/full={boolean}] [{device_ID}] Lists the disks available on the controller. Parameters {device_ID}—ID number of the device to display information.
Command Line Interface Switches /all—Specifies whether to enable SMART configurations for all disks. /clear—Clears the SMART error counts for the disk. /enable_exceptions—Specifies whether to enable SMART exception reporting. /logerr—If FALSE (the default), logging of SMART exception reports is dissabled. If TRUE, logging of SMART exception reports is enabled. /perf—If FALSE (the default), reporting of exceptions according to the MRIE mode is dissabled.
Command Line Interface Parameters {device_ID}—ID number of the device for which to display SMART information. Switches /all—Specifies whether to display SMART configurations for all disks. /full—Specifies whether to display detailed SMART configuration information for one or all disks. /view_changeable—Specifies whether to display the configuration information that can be set on a SMART disk. disk show space [/all={boolean}] [{device_ID}] Displays space usage information.
Command Line Interface disk zero [/repair={boolean}] [/wait={boolean}] {device_ID} Clears an entire disk (by writing zeros). All data is erased and cannot be recovered. Parameters {device_ID}—ID number of the device to clear. Switches /repair—If FALSE (the default), the command only reports failures. If TRUE, bad blocks are automatically repaired, if possible. /wait— If FALSE (the default), the operation is performed in the background and the command prompt is returned immediately.
Command Line Interface task list [/all={boolean}] [{integer}] Lists the tasks running on the controller. Parameters {integer}—Task ID. Switches /all—Specifies whether to list all currently running tasks. task resume [/all={boolean}] {integer} Resumes a task that was suspended or all of the tasks that were suspended. Parameters {integer}—Task ID for the task to resume. Switches /all—Specifies whether to resume all suspended tasks.
Command Line Interface Enclosure Commands Note: You can use the enclosure commands only with enclosures that support Version 1.0 of the SAF-TE specification. enclosure activate slot {enclosure} {slot} Activates a device in a slot in the SAF-TE enclosure. Parameters {enclosure}—ID number of the enclosure management device on which to activate a device. {slot}—Unit number of the slot. enclosure identify slot [/stop={boolean}] {enclosure} {slot} Identifies a device in the enclosure.
Command Line Interface Parameters {enclosure}—ID number of the enclosure management device on which to prepare a slot. {slot}—Unit number of the slot. enclosure set alarm [/on={boolean}] {enclosure} Turns the audible alarm on or off. Parameters {enclosure}—ID number of the enclosure management device whose audible alarm to set. Switches /on—Specifies whether to turn the audible alarm on or off. enclosure set fan [/off={boolean}] {enclosure} {fan} [{speed}] Sets the speed of a specific fan.
Command Line Interface Parameters {enclosure}—ID number of the enclosure management device. {powersupply}—Unit number of the power supply. Switches /off—Specifies whether to turn on or off the power supply of the unit number. enclosure set scsiid {enclosure} {slot} {device_ID} Sets the ID number of the device slot. Parameters {enclosure}—ID number of the enclosure management device. {slot}—Unit number of the device slot to assign a channel number. {device_ID}—ID number of the device.
Command Line Interface Parameters {enclosure}—ID number of the enclosure management device for which to display power supply status. {powersupply}—Unit number of the power supply. enclosure show slot [{enclosure}] [{slot}] Displays the status of a specific device slot on a specific enclosure. Parameters {enclosure}—ID number of the enclosure management device for which to display device slot status. {slot}—Unit number of the device slot whose status to display.
Command Line Interface Using Automated Command Scripts To execute a CLI command script, type the at sign (@), followed by the filename that contains the CLI commands, for example: AAC0>@commandscript.txt In a CLI command script text file, each line ends with a line feed inserted by pressing Enter. Example open AAC0 controller details close AAC0 exit The above CLI command script: 1 Opens controller AAC0 by invoking the CLI command open. 2 Invokes controller details.
E About RAID A RAID (Redundant Array of Independent Disks) provides better performance and reliability from combinations of drives than is possible with the same total storage space without RAID. This Appendix describes the various RAID levels supported by Adaptec RAID controllers. The table below shows the number of drives needed and supported for your controller according to RAID level.
About RAID Spanned Volume A spanned volume is created by joining, or concatenating, two or more drives. The drives do not have to be of equal capacity and are connected end-to-end. A spanned volume offers no redundancy and no performance advantage over a single drive. RAID 0 A RAID 0 is created by striping data across two or more drives. This striping scheme creates no redundancy to protect the data.
About RAID RAID 5 This RAID type requires at least three drives. Like RAID 0, data is striped across the drives. However, in RAID 5, parity is stored separately from data, and occupies the equivalent of one drive. The controller generates parity every time data is written to the array, and it is distributed in stripes across all the drives. In the event of a drive failure, the contents of the failed drive can be rebuilt from the data and parity on the remaining drives.
About RAID RAID 10 This dual-level RAID type is created by using two or more equalsized RAID 1 arrays to create a RAID 0. Both read and write performance are improved due to array striping. However, the performance improvement costs additional storage space due to the mirroring of the arrays.
About RAID RAID 50 This dual-level RAID type is created by using two or more equalsized RAID 5 arrays to create a RAID 0. The top level RAID 0 shares the load among the second-level RAID 5s, improving both read and write performance. Parity, used in the second level RAID 5s, provides efficient redundancy.
F About SCSI In this Appendix...
About SCSI SCSI Device Support The SCSI RAID controller is designed to work with Ultra320 SCSI hard drives. In addition, the controller operates at reduced performance with all Ultra2 or higher SCSI drives and peripherals, as described in the table below. Operating Systems Devices Supported All Ultra2 and faster SCSI drives All except Linux Tape, CD-ROM, CD-RW, and magneto-optical drives and jukeboxes. Note: Adaptec does not recommend using SCSI devices older than Ultra2 with this controller.
About SCSI Changing SCSI Termination on the Controller The default termination for the controller is Auto Mode and you will probably never need to change this setting. However, if you do need to change the termination, you can use the SCSISelect Controller SCSI Channel Termination option to change the setting to Disabled. For details, see page A-13. All these SCSI controllers support multimode SCSI termination.
G Controller Illustrations This Appendix shows the Adaptec RAID controllers.
Controller Illustrations Internal high-density SCSI connector External VHDCI SCSI Connector Battery connector Adaptec PCI connector Low-profile bracket Adaptec SCSI RAID 2120S Component Layout Internal high-density SCSI connectors External VHDCI SCSI connectors Battery connector Adaptec PCI connector Low-profile bracket Adaptec SCSI RAID 2200S Component Layout G-2
Controller Illustrations SATA ports Battery connector PCI connector Full-height bracket Adaptec SATA RAID 2410SA Component Layout 3 2 1 0 Adaptec SATA RAID 2410SA Port Numbers G-3
Controller Illustrations Battery connector SATA ports PCI connector Full-height bracket Adaptec SATA RAID 2810SA Component Layout 1 3 0 4 2 6 5 7 Adaptec SATA RAID 2810SA Port Numbers G-4
Controller Illustrations Battery connector SATA ports SATA ports PCI connector Full-height bracket Adaptec SATA RAID 21610SA Component Layout 1 3 4 6 9 11 12 14 0 8 2 5 7 10 13 15 Adaptec SATA RAID 21610SA Port Numbers G-5
H Specifications Environmental Specifications Ambient temperature without battery backup module 0 °C to 50 ° C Relative humidity 10% to 90%, noncondensing Altitude up to 3,000 meters Note: Forced airflow is recommended, but not required. DC Power Requirements Ripple and noise 50 mV peak-to-peak (max) DC Voltage 5 V ± 0.5 V Current Requirements Adaptec Model Maximum Current (A) 2020ZCR 1.5 A @ 3.3 VDC; 0.75 A @ 5 VDC 2120S 2.50 A 2200S 2.72 A 2410SA 1A 2810SA 2.1 A @ 5 VDC 21610SA 3.
Glossary A activity See task. ACU Array Configuration Utility. Used to create, configure, and manage arrays from the controller’s BIOS or MS-DOS. array A logical disk created from available space and made up of one or more partitions on one or more physical disks. Arrays are typically used to provide data redundancy or enhanced I/O performance. See also container, volume, spanned volume, and RAID signature. Also known as a container. array initialization See initialize.
Glossary bootable array Array configured as the boot device. build Background initialization of a redundant array. The array is accessible throughout. RAID 1 copies the contents of the primary drive to a secondary drive. See also clear. bus See channel. C cache Fast-access memory on the controller that serves as intermediate storage for data that is read from, or written to, drives. capacity Total usable space available in megabytes or gigabytes.
Glossary consistency check command The controller continuously performs a verification on a redundant array to data integrity. In the case of RAID 1 or 10, consistency checks assure that the data between like blocks match. In the case of a RAID 5, consistency checks assure that data in the stripe and the calculated parity for the stripe match. container See array. D dead partition See failed. degraded A redundant (for example, a RAID 1) array in which one or more members have failed.
Glossary drive LED Indicator light that illuminates during read or write operations. E event Notification or alert from the system, indicating that a change has occurred. event log File used to maintain information about prior controller activities or errors. event notification Process for transmitting events. F failed State of a nonredundant array that has suffered a single drive failure, or a redundant array that has suffered multiple drive failures. A failed array is inaccessible and data is lost.
Glossary free space/partition See available space/partition. H hard disk, hard drive Basic unit of nonvolatile, nonremovable, magnetic storage media. See also drive. hot swap To remove a component from a system and install a new component while the power is on and the system is running. hotspare A hard drive, an array member, that is not used in day-to-day data storage but, instead, is reserved for use as a replacement for one of the other drives in the array in the event of a failure.
Glossary L legacy disk Disk that contained a valid partition table when connected to the controller. The controller manages the disk as a legacy disk array where there is a one-to-one logical-to-physical mapping of array to disk. logical device Volume comprised of space from one or more physical drives and presented to the operating system as if it were a single storage unit. low-level format Process performed by the drive firmware that completely removes the file system from the disk.
Glossary P partition Contiguous area of a physical drive that makes up some or all of an array. When an array is created, space is automatically converted into partitions. phantom object Object that represents a component that cannot be configured by the controller management software; for example, a missing drive. Q quick init An array initialized using the Quick Init option is available immediately, with no on-going background controller activity.
Glossary redundant The ability of an array to maintain operability when one or more hardware failures occur. RAID 1 is an example of a redundant array. In the event of a drive failure, redundant arrays can be restored to normal operation by replacing the failed drive and rebuilding the array. rescan Process of updating the current screen to show all currently available resources. S segment Disk drive or portion of a disk drive used to create a logical device.
Glossary stripe Contiguous set of data distributed across all the disks in an array. A striped array distributes data evenly across all members in equalsized sections called stripes. stripe size The amount of data in each section of a striped array. striped array See RAID signature and RAID 5 on page E-3. T task An operation that occurs only on the RAID controller, asynchronous to all other operations; for example, initializing a disk or verifying an array.
R Adaptec, Inc. 691 South Milpitas Boulevard Milpitas, CA 95035 USA ©2004 Adaptec, Inc. All rights reserved. Adaptec and the Adaptec logo are trademarks of Adaptec, Inc. which may be registered in some jurisdictions. Part Number: 513853-06, Ver.
