INSTALLATION AND USER’S GUIDE ADAPTEC SERIAL ATA RAID 2410SA
Adaptec Serial ATA RAID 2410SA Installation and User’s Guide R
Copyright ©2003 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 Read this First 1-1 System Requirements 1-2 Operating System Compatibility 1-2 Storage Requirements 1-2 Motherboard Compatibility 1-2 Device Compatibility 1-2 Kit Contents 1-3 Adaptec 2410SA Controller 1-3 About the Documentation 1-4 Installing the Adobe Acrobat Reader 1-4 Controller Features 1-5 Adaptec’s Advanced RAID Technology Features Array Migration 1-6 Drive Enclosures 1-6 Hot Spares 1-6 Automatic Failover 1-7 Overview of the Installation Process 1-7 Storage Management Softwa
Contents Windows 3-3 Installing the Driver in a New System 3-3 Adding the Driver to an Existing System 3-4 Linux 3-5 Installing the Driver in a New Red Hat System Adding the Driver to an Existing System 3-6 UnixWare and OpenUNIX 3-7 Installing the Driver on a New System 3-7 Adding the Driver to an Existing System 3-7 4 3-5 Installing Adaptec Storage Manager – Browser Edition Overview 4-1 Supported Browsers 4-2 Typical, Custom, and Compact Installations 4-2 Remote and Managed Systems 4-3 Installing Adapt
Contents Using SATASelect A-9 Using the Disk Utilities A-11 Viewing the Event Log A-12 B DOS Utilities Using the Adaptec Flash Utility (AFU) B-1 Overview of the AFU B-2 System Requirements B-2 Firmware Floppy Disk Kit B-3 Running the AFU B-4 Accessing the AFU from the GUI B-4 Accessing the AFU from the Command Line B-4 Flashing the Firmware Using AFU B-5 AFU Commands B-7 AFU Error Handling B-10 Using the Array Configuration Utility (ACU) B-11 Interactive Versus Script Mode B-11 Running the ACU B-12 Using
Contents Using the CLI C-3 Opening and Closing a Controller C-4 Managing Failover Options and Hot Spares Displaying Controller Information C-9 Displaying Disk Information C-11 Displaying Array Information C-12 CLI Command Dictionary C-15 General Control Commands C-15 Container (Array) Commands C-16 Controller Commands C-25 Disk Commands C-28 Logfile Commands C-32 Task Commands C-33 Enclosure Commands C-34 Using Automated Command Scripts C-38 D C-7 Supported RAID Types RAID 0 D-2 RAID 1 D-2 RAID 5 D-3 RA
1 Introduction In this Chapter... Read this First 1-1 System Requirements 1-2 Kit Contents 1-3 About the Documentation 1-4 Controller Features 1-5 Overview of the Installation Process 1-7 Storage Management Software Overview 1-8 Safety Information 1-9 Read this First Read this chapter before you begin installing your new Adaptec Serial ATA RAID 2410SA controller. This is a guide to the rest of the document, providing a summary of the installation process.
Introduction System Requirements The following system requirements are presented: ■ Operating system compatibility ■ Storage requirements for drivers and software ■ Motherboard compatibility. ■ Device compatibility (for Serial ATA) Operating System Compatibility ■ Microsoft Windows® 2000, Windows XP®, Windows Server 2003 ■ Linux ■ Red Hat 7.3 and 8.0 ■ SuSE 8.0 and 8.1 ■ UnixWare 7.1.1 and OpenUNIX 8 Note: For the latest Linux compatibility information, visit www..adaptec.com.
Introduction Kit Contents Your Adaptec controller kit includes: ■ Adaptec 2410SA controller (shown below) ■ Adaptec Serial ATA RAID 2410SA Quick Installation Guide ■ Installation CD ■ Low-profile bracket (in addition to the standard full-height bracket attached to the controller) ■ Four Serial ATA interface cables ■ Technical Support ID (TSID) label (See page iii for details.) Adaptec 2410SA Controller The Adaptec 2410SA controller is shown below.
Introduction About the Documentation The documentation set for this kit includes: ■ Adaptec Serial ATA RAID 2410SA Quick Installation Guide—This printed guide contains the essential information for installing the controller in most situations. ■ Adaptec Serial ATA RAID 2410SA Installation and User’s Guide (this guide) ■ Adaptec Serial ATA RAID 2410SA Command Line Interface Software Reference Guide—Provides detailed descriptions of the command line driven RAID management utility.
Introduction Controller Features The Adaptec 2410SA controller supports four Serial ATA drives. The controller offers the features and performance ideal for highend workstations and entry-level servers. ■ Conforms with PCI Local Bus Specification, Revision 2.2 ■ 64-bit, 66-MHz PCI interface compatible with 32-bit/33-MHz PCI slots ■ 64 MB of on-board RAM ■ Low-profile, MD2 form factor ideal for 1U/2U servers ■ Supports the Serial ATA Specification, version 1.
Introduction ■ Multiple Arrays—Create multiple arrays from a single set of drives. ■ SATA Disk Hot Plug—You can add and remove disks without shutting down your system. Array Migration The Adaptec 2410SA controller supports modifying existing arrays by expansion, migration from one array type to another, and changing the stripe size, as described by the table below.
Introduction The Adaptec 2410SA controller supports two types of hot spares: ■ Global—Protects every array that the drive has enough available capacity to protect. ■ Dedicated—Protects only the array that it has been assigned to protect. Automatic Failover This feature allows the controller to automatically rebuild an array when a failed drive is replaced with a new drive. This feature applies only to redundant arrays in SES- or SAF-TE-enabled drive enclosures. See page A-10 for details.
Introduction Storage Management Software Overview The Adaptec 2410SA controller includes the following software tools to manage your storage subsystem: ■ Adaptec Storage Manager – Browser Edition—Browser-based storage management software that provides all of the creation, management, and data logging needed to manage arrays. Arrays may be set up and managed on systems using the following operating systems: ■ Windows 2000, Windows XP, and Windows Server 2003 ■ Red Hat Linux 7.3 and 8.0 ■ SuSE Linux 8.
Introduction Safety Information To ensure you 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. Notes and Cautions This Installation and User’s Guide uses notes and cautions that emphasize important information, as described below: Note: Emphasizes important information that, if ignored, would not result in injury, property damage, or data loss.
Introduction ■ Avoid touching the controller against your clothing. The wrist strap protects components from ESD voltages present on the body only. ESD voltages on clothing can still cause damage. ■ Handle your controller by its bracket or edges only. Avoid touching the printed circuit board or the connectors. ■ When you need to put your controller down, use an antistatic surface such as the bag supplied in your kit.
2 Installing the Controller In this Chapter... Overview 2-1 Installing the Controller 2-2 Checking Your Controller and Devices 2-3 Determining the Boot Controller 2-3 Overview To install the controller and drives, all you need is up to four of each of the following: ■ Serial ATA hard disk drives ■ Serial ATA cables (supplied in this kit) Configuration of Serial ATA devices is simple for the following reasons: ■ There are no jumpers or switches to set on the controller or hard drives.
Installing the Controller Installing the Controller To install the controller in the system cabinet: 1 Shut down your computer and disconnect the power cord. 2 Open the computer cabinet and identify an unused PCI slot. 3 If your computer accepts low-profile brackets only, install the low-profile bracket supplied with your kit in place of the standard full-height bracket. 4 Identify an unused PCI slot and remove the slot cover, as illustrated below.
Installing the Controller Checking Your Controller and Devices Now that you have installed your Adaptec 2410SA controller and connected your Serial ATA hard drives, you are ready to use the ARC utility to check your controller and devices, as described below: 1 Turn on your computer. 2 When prompted, enter the ARC utility by pressing Ctrl+A. 3 If your drives have already been used in another system (even if not part of an array), select Array Configuration Utility and initialize the drives.
3 Installing the Driver In this Chapter... Creating the Driver Disk 3-2 Windows 3-3 Linux 3-5 UnixWare and OpenUNIX 3-7 This chapter presents several scenarios for installing the controller driver. The scenarios depend on the following terminology: ■ New system—The computer has no operating system and the driver installation is a part of the operating system installation. ■ Existing system—The computer has an operating system and the Adaptec 2410SA is being installed as a secondary controller.
Installing the Driver Creating the Driver Disk Installing a driver is easier if you create a driver disk. To create the driver disk: 1 Set your system BIOS so that your computer boots from the CD-ROM drive. 2 Insert the Adaptec installation CD and turn on the computer. 3 Follow instructions and respond to prompts as necessary to get to the Adaptec Start Menu. 4 Click Create Driver Disk. Then, select the appropriate operating system. 5 Select the appropriate floppy drive letter.
Installing the Driver Windows The following sections describe procedures for installing the controller with Windows 2000, Windows XP, or Windows Server 2003. The following installation scenarios are described: ■ Installing the Driver in a New System on page 3-3 ■ Adding the Driver to an Existing System on page 3-4 Installing the Driver in a New System In this scenario, you are installing the controller in a new Windows system.
Installing the Driver Adding the Driver to an Existing System In this scenario, you are adding the driver to an existing Windows system. To install the driver: 1 Install and configure the controller and hard disk drives according to the instructions in Chapter 2. 2 Start Windows. Windows launches the Found New Hardware Wizard, which searches for the controller driver. 3 Insert the driver disk, select the floppy drive as the source and then click Next.
Installing the Driver Linux The controller supports Red Hat and SuSE Linux versions as described in the table below. Red Hat SuSE Version Kernel Version Version Kernel Version 7.3 2.4.18-3 8.0 2.4.18 8.0 2.4.18-14 8.1 2.4.19 Notes ■ If you do not find your kernel version listed above, either of the following conditions may apply: ■ Your kernel contains embedded drivers ■ Drivers are not available and you need to create a custom driver.
Installing the Driver 6 When prompted, insert the driver disk and then select OK. 7 Follow the prompts to set up your preferred environment. 8 If you intend to install other third-party devices, proceed with the installation of those devices. Otherwise, select Done. 9 Proceed with the Linux installation according to the Red Hat instructions. Adding the Driver to an Existing System These driver installation instructions apply to both Red Hat and SuSE Linux systems.
Installing the Driver UnixWare and OpenUNIX Although the driver disk you create for UnixWare 7.1.1 and OpenUNIX 8 differ, the installation procedures for these operating systems are the same. Installing the Driver on a New System In this scenario, you are installing the controller in a new UnixWare 7.1.1 or OpenUNIX 8 system. To install the driver: 1 Install and configure the controller and hard disk drives according to the instructions in Chapter 2.
4 Installing Adaptec Storage Manager – Browser Edition In this Chapter... Overview 4-1 Supported Browsers 4-2 Typical, Custom, and Compact Installations 4-2 Installing Adaptec Storage Manager on Windows 4-4 Installing Adaptec Storage Manager on Linux 4-8 Installing Adaptec Storage Manager on UNIX 4-9 Overview This chapter discusses the installation procedure for installing Adaptec Storage Manager – Browser Edition to enable remote and local management of arrays.
Installing Adaptec Storage Manager – Browser Edition Supported Browsers To run Adaptec Storage Manager – Browser Edition, your computer must have a Web browser supporting JavaScript and cookies only. The following versions are supported: ■ On Windows ■ Internet Explorer (IE) 5.0 or later ■ Netscape 7 or later ■ On Linux ■ Adaptec-supplied and installed version of Mozilla ■ Netscape 7 or later When using Adaptec Storage Manager, you need to log on to your system with administrator privileges.
Installing Adaptec Storage Manager – Browser Edition Remote and Managed Systems The illustration below shows a typical configuration of a single remote system connected to several managed systems. The remote system does not necessarily contain a RAID controller; however, it must contain, at minimum, the Adaptec Web Server and a browser (either Internet Explorer or Netscape). The managed systems contain RAID controllers and arrays, and at least the Managed System Components.
Installing Adaptec Storage Manager – Browser Edition Installing Adaptec Storage Manager on Windows Note: When installing on a FAT 32 file system, the folder being installed is automatically hidden. To install Adaptec Storage Manager – Browser Edition: 1 Verify that a supported browser is installed. See Supported Browsers on page 4-2 for details. 2 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 Adaptec Storage Manager – Browser Edition 11 When prompted to restart your computer, accept the default (Yes) and click Finish. 12 The system restarts to complete the installation. 13 Remove the Adaptec installation CD before the system restarts. Configuring Internet Browsers on Windows If you are managing a local storage array and your computer uses a proxy server, you need to configure your browser to enable Adaptec Storage Manager to bypass the proxy server.
Installing Adaptec Storage Manager – Browser Edition Configuring Internet Explorer for Local Management When using the High security setting, you must enable the following settings manually: ■ JavaScript ■ Cookies (not stored) You do not need to enable the following custom level security settings for the local intranet in Internet Explorer 5 and 5.5. Select Tools > Internet Options to access these settings: ■ Active Scripting ■ Allow per session cookies (not stored) Note: In Internet Explorer 6.
Installing Adaptec Storage Manager – Browser Edition Configuring Internet Explorer for Remote Management If you know the IP address of the managed system you want to manage remotely: 1 Select Tools > Internet Options > Connections > LAN Settings. 2 Select Use a proxy server for your LAN > Advanced. 3 In the Exceptions section, type the managed system’s IP address. Configuring Netscape Navigator for Local Management Note: These instructions apply specifically to Version 7 and may differ in later versions.
Installing Adaptec Storage Manager – Browser Edition Installing Adaptec Storage Manager on Linux Note: When performing this installation, keep in mind that Linux is case sensitive. To install Adaptec Storage Manager on a Linux computer and configure the desired Internet browser: 1 Insert the Adaptec installation CD. 2 Install the software by typing: sh /install.sh. The differs among computers, but /mnt/cdrom, /media/cdrom, or cdrom usually works. A Welcome window appears.
Installing Adaptec Storage Manager – Browser Edition 9 Click OK. The Shell window you used to launch the installation indicates that some daemons are being started. The installation creates a shortcut to Adaptec Storage Manager in the System tab. This shortcut launches Adaptec Storage Manager using Netscape. Unless the controller driver was installed as part of this installation, you do not need to restart your computer. 10 Remove the Adaptec installation CD.
5 Using Adaptec Storage Manager – Browser Edition In this Chapter...
Using Adaptec Storage Manager – Browser Edition Overview This chapter describes how to use Adaptec Storage Manager – Browser Edition to manage arrays. Once you are logged in, you will find convenient online help to guide you through the details of creating, configuring, and managing arrays. Note: Your controller may not support all of the features described. In most cases if a feature is not supported by your controller the feature does not appear in the interface.
Using Adaptec Storage Manager – Browser Edition Architecture Overview A locally managed system requires all of the following components: ■ A supported Web browser, which should already be installed on the system. ■ The Adaptec Web service which supplies content displayed on the Web browser. ■ An Adaptec-supplied storage agent. A remotely managed system requires all of the following components: ■ The remote system must contain a browser. ■ The managed system must contain an Adaptec storage agent.
Using Adaptec Storage Manager – Browser Edition Logging In To login: 1 Start Adaptec Storage Manager – Browser Edition. ■ In Windows, click Start > Programs > Adaptec Storage Manager > Adaptec Storage Manager – Browser Edition. ■ In Linux, click Start > System > Adaptec Storage Manager. The Login screen, shown below, is presented. 2 Enter the host name or IP address of the system you want to manage and the username and password you would use to log into that system. 3 Click Login.
Using Adaptec Storage Manager – Browser Edition To log in from any system with a Web browser: 1 Start the Web browser application and type the IP address for the system you want to access in the address bar and then press Enter. For example, https://10.6.3.14:3513/adaptec. When connection to the remote system is established, the System Login screen appears. Note: If you are using a proxy server to access the Internet, you must bypass the proxy server to access the Adaptec Storage Manager Web server.
Using Adaptec Storage Manager – Browser Edition Installing a Security Certificate If you chose not to install a security certificate when you installed Adaptec Storage Manager – Browser Edition, you must install the certificate when you run the application for the first time. To create the certificate: 1 When the Security Alert window appears, click View Certificate. 2 When the Certificate window appears, click Install Certificate. 3 When the Certificate Import wizard, appears, click Next.
Using Adaptec Storage Manager – Browser Edition The Basics An example of a typical Adaptec Storage Manager – Browser Edition screen is shown below. Note: Depending on your operating system, browser, and color scheme you may notice some differences between this illustration and your screen. The header frame, at the top of the screen, contains the name of the system that you are currently connected to and a number of buttons that perform various actions or open additional windows.
Using Adaptec Storage Manager – Browser Edition Immediately following the header frame is a controller information line including the model number of the first Adaptec RAID controller found in the system and the amount of cache memory (if any) installed on that controller. Beneath the controller information are Physical Devices and Logical Devices views that show connected devices and existing arrays on this controller.
Using Adaptec Storage Manager – Browser Edition Changing How Drives are Displayed By default, the Physical Devices displays a condensed view of the controller configuration that hides detailed information about the drives. More information is available by either positioning the mouse pointer over the device or clicking on the arrowhead to the left of a row of devices. The selected display mode button will appear in a lighter shade of blue than the other two buttons.
Using Adaptec Storage Manager – Browser Edition Any part of a drive used in an array is shown as a gray segment within the bar. Selecting any gray segment will highlight it in amber and, in the Logical Devices view, highlight the array of which this segment is a member. In either the Full Size Capacity View or the Relative Size Capacity View, a small portion at each end of the drive may be shown in dark gray.
Using Adaptec Storage Manager – Browser Edition The main area of the Logical Devices view is used to display the arrays on this controller. It defaults to a condensed view of toplevel arrays. Note: The Options button allows you to display second-level arrays if your controller supports them. In this condensed view, the RAID level of each device as well as whether it is protected by a hot spare, is visible.
A Adaptec RAID Configuration Utility In this Appendix... Using the Array Configuration Utility A-2 Using SATASelect A-9 Using the Disk Utilities A-11 Viewing the Event Log A-12 The Adaptec RAID Configuration (ARC) utility is an embedded BIOS utility that includes: ■ Array Configuration Utility (ACU)—Used to create, configure, and manage arrays. Also used to initialize and rescan drives.
Adaptec RAID Configuration Utility The Adaptec RAID Controller menu appears, presenting the following options: ■ Array Configuration Utility ■ SATASelect Utility ■ Disk Utilities To select an option from this menu, or from any of the menus within ARC, browse with the arrow keys and then press Enter. In some cases, 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 Viewing Array Properties To view the properties of an existing array: 1 At the BIOS prompt, press Ctrl+A. 2 From the ARC menu, select Array Configuration Utility. 3 From the ACU menu, select Manage Arrays. 4 From the List of Arrays dialog box, select the array you want to view information on and then press Enter. Single Level Arrays Only—For RAID levels 0, 1, and 5, the Array Properties dialog box shows detailed information on the array physical disks.
Adaptec RAID Configuration Utility Notes ■ If the controller is not a boot device, you can disable its runtime BIOS, see page A-10. When the BIOS is disabled, it does not occupy any of the expansion ROM region of the system’s memory map. In a system with several expansion ROMs, disabling the BIOS may be helpful. ■ You cannot make a non-00 array bootable while the array is in a build/verify or reconfiguration process. ■ The controller always uses the lowest numbered array as its bootable array.
Adaptec RAID Configuration Utility 6 Select Yes to delete the array or No to return to the previous menu. At the Array Properties dialog box, select Delete again and then press Enter. 7 Press Esc to return to the previous menu. Managing Failover Drive Assignments To assign a hot spare drive to an array: 1 Select Manage Arrays from the Main menu. 2 From the List of Arrays dialog box, select the array to which you want to assign a hot spare, and then press Ctrl+S.
Adaptec RAID Configuration Utility Creating Arrays Before creating arrays, make sure the disks for the array are connected and installed in your system (or enclosure). Note that any disks with MS-DOS partitions, disks with no usable space, or disks that are uninitialized appear dimmed and cannot be used for creating a new array. For information on how to initialize a disk drive, see page A-8. To create an array: 1 Shut down and restart the system. 2 At the BIOS prompt, press Ctrl+A.
Adaptec RAID Configuration Utility Assigning Array Properties The ACU can be used to assign array properties only prior to array creation. (After the array is created, you need to use Adaptec Storage Manager.) To assign properties to the new array: 1 In the Array Properties menu, select an array type and then press Enter. The display shows only the array types available for the number of drives selected.
Adaptec RAID Configuration Utility 6 Specify whether you want to enable write caching for the array. When you are finished, select Done. Initializing Disk Drives If an installed disk does not appear in the disk selection list for creating a new array or if it appears grayed out, you need to initialize it before you can use it as part of an array. ! Caution: Initializing a disk overwrites the partition table on the disk and makes any data on the disk inaccessible.
Adaptec RAID Configuration Utility Rescanning Disk Drives To rescan the drives connected to the controller: 1 At the BIOS prompt, press Ctrl+A. 2 From the ARC menu, select Array Configuration Utility. 3 Select Rescan Drives. Using SATASelect SATASelect enables you to change device and controller settings without opening the computer cabinet or handling the card. With this utility, you can modify the Channel Interface Definitions and Device Configuration Options.
Adaptec RAID Configuration Utility ■ ■ DMA (Default: Enabled)—When Enabled, Direct Memory Access (DMA) mode is used for the drive, providing maximum performance. ■ SMART (Default: Disabled)—Controls the predictive failure feature of the disk drive. When Enabled and the drive supports Self-Monitoring, Analysis and Reporting Technology (SMART) configuration, the SMART status of the drive (Healthy or Failed) is displayed along with the physical drive display during POST.
Adaptec RAID Configuration Utility ■ Array Background Consistency Check (Default: Disabled)—When Enabled, 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. Consistency checking processes reduce performance.
Adaptec RAID Configuration Utility ■ Format Disk—Simulates a format of the hard drive by removing the file system and writing zeros to the entire disk. Serial ATA drives are formatted at the factory and do not need to be formatted again. ! ■ Caution: Formatting destroys all data on the drive. Be sure to back up your data before performing this operation. Verify Disk Media—Scans the media of a disk drive for defects. Any errors found are corrected.
B DOS Utilities In this Appendix... Using the Adaptec Flash Utility (AFU) Using the Array Configuration Utility (ACU) B-1 B-11 Using the Adaptec Flash Utility (AFU) The Adaptec® Flash Utility (AFU) is a DOS application used to update the flash EEPROM components on one or more Adaptec SCSI RAID controllers. The utility can also be used to verify a controller’s current flash contents against the flash images in a specified file or to save a controller’s current flash contents to a file.
DOS Utilities The process of updating a controller’s flash must be done carefully to avoid rendering the controller inoperable. AFU is designed to be easy to use with all the necessary safeguards to prevent a user from accidentally damaging the controller’s flash contents. Overview of the AFU The AFU performs the following primary functions: ■ Update—Updates all the flash components on a controller with the flash image data from a UFI file.
DOS Utilities ■ The AFU can run from a partition on a drive or array attached to the controller you are updating. Once the flash update begins, no I/O is possible to any array attached to that controller until the flash operation is completed and the system is restarted. ■ If you want to update multiple controllers in the same system, you should first update the boot controller’s flash, restart the system, and then update the flash for any remaining controllers.
DOS Utilities Running the AFU You can run the AFU from its graphical user interface (GUI) or from the command line. Accessing the AFU from the GUI To access the AFU: 1 At the DOS command prompt (typically A:\>), type AFU with no arguments. The main menu to the AFU is displayed. 2 Select Select Controllers and select the controllers to be flashed. 3 Select Select an Operation. 4 Select any available AFU function and follow the on-screen instructions.
DOS Utilities The AFU switches are as follows ■ /C is one or more controller IDs representing the set of controllers on which to perform the specified command. You can specify a single controller ID, for example: /C 0 multiple IDs separated by commas, for example: /C 0,2 or ALL to indicate all controllers. This switch is required. If no /C switch is specified, the system returns a fatal error message. See each individual command for the default switch values.
DOS Utilities 5 At the DOS prompt, type afu list and press Enter. This command displays a list of the controllers in your system. Take note of the controllers you would like to update and its number (or numbers if there are more than one). Verify that the controller you wish to update is identified.
DOS Utilities 9 If there are additional UFI files this process is repeated until the complete image has been read, the controller flash is updated with the new image. AFU Commands The following pages describe each of the AFU commands in detail. For ease of use, the commands are presented in alphabetical order. HELP The HELP command displays a summary of AFU functions and command switches.
DOS Utilities 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. Use the /D switch to specify the drive and directory where you want AFU to create the UFI file. Note: You can specify only one controller ID. If you include the /C switch and specify more than one controller, the AFU displays an error message and exits. You must restart the computer following a SAVE command.
DOS Utilities Example A:\> AFU UPDATE /C 0 Adaptec Flash Utility V4.0-0 B5749 (c)Adaptec Inc. 1999–2002. All Rights Reserved. Updating Controller 0 (Adaptec 2410) Reading flash image file (Build 5749) AFU is about to update firmware on controllers Adaptec 2410 ***PLEASE DO NOT REBOOT THE SYSTEM DURING THE UPDATE*** This might take a few minutes. Writing Adaptec 2410 (4MB) Flash Image to controller 0...OK. Verifying...OK Please restart the computer to allow firmware changes to take effect.
DOS Utilities After using the VERSION command, you must restart the computer upon completion of this command. Default Switch Values If you do not include the /C switch, the AFU returns a fatal error message. Examples 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.
DOS Utilities Using the Array Configuration Utility (ACU) Adaptec RAID Configuration (ARC) is a embedded BIOS utility that includes: ■ SATASelect—Used for changing device and controller settings, ■ Disk Utilities—Used for low-level formatting or verifying disk media, and for performing other functions. ■ Array Configuration Utility (ACU)—Used for creating, configuring, and managing arrays.
DOS Utilities Running the ACU To run the ACU for MS-DOS: 1 Browse to Dos\Apps\Acu on the Adaptec installation CD. 2 Copy acu.exe onto a bootable MS-DOS floppy disk and insert this disk into your drive. 3 Restart your system. If you issue the command ACU without any command-line switches, the ACU displays its main window and waits for your menu selection (interactive mode).
DOS Utilities Selecting Segments for New Arrays To select one or more segments to assign as members of the new array: 1 Use the arrow keys to select a channel. 2 Use the arrow keys to select the drives to assign to the new array and press Insert. The ACU displays the largest usable space available for each drive. You can use some or all of the available space from multiple drives to create the new array. To deselect a drive, highlight the drive and press Delete.
DOS Utilities 2 Type in an optional label for the array and press Enter. 3 Enter the desired array size. The maximum array size available based on the segments 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 drop-down list. If the available space from the selected segments is greater than the size specified, the remaining space is available for use in other arrays.
DOS Utilities Managing Arrays The Manage Arrays option enables you to perform the following functions: ■ Viewing Array Properties ■ Assigning Hot Spares ■ Removing Hot Spare Drives ■ Initializing a Hard Drive ■ Making an Array Bootablee ■ Deleting Arrays These operations are described in greater detail in the sections that follow. Viewing Array Properties To view the properties of an existing array: 1 Select Manage Arrays from the Main menu.
DOS Utilities 3 Select a drive and press the Insert key to assign the drive as a spare. The specified drive is displayed in the Assigned Hotspares Drives list. 4 Press Enter to save the spare drive assignment. The following prompt is displayed: Have you finished managing Hotspare drives? 5 Press Y (for yes) to return to the Main menu. Removing Hot Spare Drives To remove an assigned spare drive from an array: 1 Select Manage Arrays from the Main menu.
DOS Utilities To initialize a drive: 1 Select Initialize Drives from the Main menu. 2 Use the arrow keys to select a channel. 3 Select the disks you want to initialize and press Insert. 4 Press Enter. 5 Read the warning message and ensure that you have selected the correct devices to initialize. Press Y to continue. Making an Array Bootable You can make an array bootable so the system boots from the array instead of from a stand-alone (single) device.
DOS Utilities Deleting Arrays ! Caution: Back up the data on an array before you delete it. All data on the array is lost when you delete the array, and you cannot restore a deleted array. To delete an existing array: 1 Select Manage Arrays from the Main menu. 2 Select the array you want to delete and press Delete. 3 From the Array Properties dialog box, press Delete again and then press Enter. The following message is displayed: Warning!! Deleting will erase all data from the array.
DOS Utilities The table below lists the required and optional ACU command-line switches. Switch Description /P Playback Mode Switch—In this mode, the ACU reads the contents of the specified script file and creates arrays and configures channel settings based on the properties defined in the script. The is the name of the script file. It can include a drive, directory, and filename and extension, but only the filename is required. If no drive or directory is specified, defaults are used.
DOS Utilities Playback Mode Playback mode enables you to create one or more arrays based on the properties defined in a script file. It also enables you to configure certain properties for each channel on the controller. When you create an array, you can specify any of the array properties listed in the table below. Property Type Description Supported array types are: Volume ■ RAID 0 ■ RAID 1 ■ RAID 5 ■ RAID 10 ■ Size Size of the array to be created.
DOS Utilities In addition, there are other array properties that enable you to control the various array settings during creation. See Array Definition Block Properties on page B-25 for the complete list of array properties. Note: You can configure each individual channel on the controller using this property, which specifies the device ID number of the controller on the channel.
DOS Utilities Because the ACU reads the entire script file before creating any arrays, the position of the InitializeAll=Yes property within the script is not significant. Continuing the previous example, if InitializeAll=Yes is specified in the second RAID 5’s definition, the ACU initializes all drives before creating the first RAID 0. Note: If a build/verify is in progress when an array is deleted, it is automatically terminated.
DOS Utilities The ACU provides a way to do this. When you use record mode to record a controller’s configuration and you specify a log file (/L switch), the ACU writes build/verify and clear status information about each array in the configuration to the log file. An application or batch file can then parse the resulting log file to determine whether an array’s build/verify or clear is complete, in progress (a percentage of the task completed), or failed.
DOS Utilities Build/Verify Operations on RAID 10 Arrays For a RAID 10 array, the status message indicates the percent of the build/verify completed for the parent and child tasks. The status updates to OK when the tasks are complete. A sample RAID 10 build status is as follows: Array #1 Status : BUILD/VERIFY = 30% Script File Syntax An ACU script file consists of one of the following: ■ Array definition block—Specifies the properties of an array, such as type, size, and cache settings.
DOS Utilities Array Definition Block Properties The table below lists the properties that can be specified within an array definition block. The table lists each property’s keyword, whether it is required, and its default value (if any). Note that the keywords are arranged so the required keywords are listed first. Required ? Default Value Array Yes None Indicates the start of an array definition block. See page B-26 for details. Drives Yes None Specifies the devices used in creating the array.
DOS Utilities Required ? Default Value Wait No Yes Indicates whether the ACU should wait for the new array’s build/verify or clear to complete before continuing. See page B-31 for details. WaitForBuild No Yes Provided for backward compatibility only. See page B-31 for details. WriteCache No Yes Indicates whether write caching is enabled for this array. See page B-31 for details. Keyword Description The following sections describe each of these keywords in detail.
DOS Utilities Type Keyword Type is a required keyword, indicating the array type. There is no default value. Note: For information about the maximum number of drives supported and minimum number of drives required, see page B-14. The Type keyword values are: ■ Volume ■ RAID0 ■ RAID1 ■ RAID5 ■ RAID10 Examples Type=Volume Type=RAID1 End Keyword End is a required keyword, indicating the end of an array definition block.
DOS Utilities Notes ■ When assigning spare drives to a RAID 10 array, the ACU assigns all the drives in the list to all the arrays within the multilevel array. ■ ACU only creates dedicated hot spares. If the same drive is assigned to protect multiple arrays, only the last array that drive is assigned to is protected. ■ The ACU makes no checks to ensure that the amount of available space on the specified spare drives is sufficient to serve as failover for the given array.
DOS Utilities Examples InitializeAll=Yes InitializeAll=No Method Keyword Method is an optional keyword, indicating which method to use when creating a RAID 5 array. Possible values are: ■ Build (the default)—Build/verify the array. ■ Clear—Clear the array. ■ Quick Init - Make the array available immediately Overall, the Build method takes longer than Clear, but it enables you to begin using the array immediately. Although faster, Clear must complete before you can begin using the array.
DOS Utilities Size Keyword The Size keyword specifies the size of the array. Specify the size as an integer or a decimal number, followed by the unit keyword MB (megabytes), GB (gigabytes), or TB (terabytes). A unit keyword is required with a numeric size value. If no unit keyword is specified, the ACU exits with an error. Specify Maximum (the default) to create an array using the maximum available space, based on the array type and drives selected. Examples Size=2.
DOS Utilities Wait Keyword The Wait keyword indicates whether the ACU should wait for the new array’s build/verify or clear to complete before continuing. The Wait property is optional; if not specified, the ACU waits for the array’s build/verify or clear to complete before continuing. Specify Wait=No to allow the ACU to continue while the build/ verify or clear completes in the background.
DOS Utilities Error Handling Because the ACU scripting feature is designed to run without user interaction, the ACU handles errors during record and playback by simply exiting immediately whenever an error is detected. Whenever the ACU encounters an error during record or playback—for example, an unrecognized keyword in a script file— it reports the error and exits. If a log file is opened, the ACU writes the error message to the log file. Otherwise, it displays the message on the screen.
DOS Utilities Code Description 9 Specified array size too big—You specified an array size that is larger than the maximum size allowed for this array. 10 Number of drives do not match the array type—The number of drives you selected is invalid for the type of array specified. 11 Unable to initialize drive—The ACU was unable to initialize one or more devices. 12 Error occurred while creating array—The ACU encountered an error creating an array.
DOS Utilities Playback and Record Notes When using ACU in playback or record mode, note the following: ■ When recording an array, the ACU does not create a Wait keyword within an array’s definition block in a script file. When playing back any script file generated from the ACU record option, the ACU uses the default setting Wait=Yes when creating an array unless you first edit the script file and include a Wait=No line in the array’s definition block.
DOS Utilities The following sample script file is a sample RAID.ACU script as referred to in the previous ACU command. This script creates the following arrays—a 500 MB, single-disk volume and a 2-GB, twodrive RAID 1 with a hotspare.
C Command Line Interface (CLI) In this Appendix... Introduction C-1 Accessing the CLI C-2 Terminology C-2 Using the CLI C-3 General Control Commands C-15 Container (Array) Commands C-16 Controller Commands C-25 Disk Commands C-28 Logfile Commands C-32 Task Commands C-33 Enclosure Commands C-34 Using Automated Command Scripts C-38 Introduction This Command Line Interface (CLI) enables you to configure and manage controller components.
Command Line Interface (CLI) CLI commands enable 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. For a full description of all the CLI commands, refer to the CLI Software Reference Guide.
Command Line Interface (CLI) Accessing the CLI in MS-DOS To access the CLI from the MS-DOS prompt, move to the directory containing the afacli executable and 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. 3 Browse to SMBE. The Adaptec program group displays. 4 Click CLI.
Command Line Interface (CLI) 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. To open controller AAC0 and prepare it to receive more CLI commands, type: CLI> open AAC0 The prompt changes to reflect the open controller, as shown in the next example.
Command Line Interface (CLI) Displaying Information about Your Disks Before creating any array, use the disk show space command to display information about your disks. Note: Before you can create arrays, you need to initialize the member drives. In the following example, the Usage column indicates Free for each disk, which means that the space on each disk consists of available space. AAC0> disk show space Executing: disk show space Scsi C:ID:L Usage Size ----------- ---------- ------------0:01:0 Free 64.
Command Line Interface (CLI) Creating a RAID 0 When creating a RAID 0, you need to determine the stripe size that is most suitable for your environment. The stripe size attribute indicates the number of bytes in a stripe, the amount of data written to a segment before the I/O data stream switches to the next segment in the array. The stripe size can be 16, 32, or 64 KB. The default stripe size is 64 KB. Note that you can use the container reconfigure command at a later time to change the stripe size.
Command Line Interface (CLI) The stripe size can be 16, 32, or 64 KB. The default stripe size is 64 KB. Note that you can use the container reconfigure command at a later time to change the stripe size. To create a RAID 5, use the container create raid5 command. In the following example, a RAID 5 is created on devices 0:01:0, 0:02:0, and 0:03:0 using 100 MB of available space from each device.
Command Line Interface (CLI) Alternatively, you can use the automatic failover commands that enable you to remove a failed drive and add a hot spare in its place. The controller automatically assigns the new hot spare to replace the failed drive without your having to first assign it using the container set failover or container set global_failover commands. Note: Automatic failover works only with disks that reside in an SAF-TE- or SES-enabled enclosure.
Command Line Interface (CLI) Displaying Controller Information Controllers exhibit a number of attributes that you can display or manage using the following CLI commands: ■ controller list Controller Attribute Indicates... controller (adapter) name Name controller (adapter) type Product name controller availability Access mode Example of controller list: CLI> controller list Executing: controller list Adapter Name Adapter Type ----------------------\\.
Command Line Interface (CLI) Example of controller details: AAC0> controller details Executing: controller details Controller Information ---------------------Remote Computer: . Device Name: AAC0 Controller Type: Adaptec xxxxxx Access Mode: READ-WRITE Controller Serial Number: Last Six Digits = 8A277A Number of Buses: 2 Devices per Bus: 15 Controller CPU: i960 Controller CPU Speed: 100 Mhz Controller Memory: 64 Mbytes Battery State: Not Present Component Revisions ---------------------CLI: 3.
Command Line Interface (CLI) Displaying Disk Information The CLI enables you to monitor or manage disk attributes, prepare a disk for use by a controller, and detect defects using the following CLI commands: ■ disk list Disk Attribute Indicates...
Command Line Interface (CLI) Example of disk show defects: AAC0> disk show defects /full=true (0,1,0) Executing: disk show defects /full=TRUE (CHANNEL=0,ID=1,LUN=0) Number of PRIMARY defects on drive: 5 Defect 1 at cylinder 229, head 7, sector 203 Defect 2 at cylinder 575, head 0, sector 219 Defect 3 at cylinder 576, head 0, sector 55 Defect 4 at cylinder 578, head 0, sector 238 Defect 5 at cylinder 579, head 0, sector 74 Number of GROWN defects on drive: 0 ■ disk verify Disk Attribute Indicates...
Command Line Interface (CLI) Array Attribute Indicates... stripe size Number of bytes in a stripe (amount of data written to a segment before the I/O data stream switches to the next segment/array). read only Whether an array is read-only accessible. An array can be set to read-only if not in use by an application. read/write Whether an array is read-write accessible. lock Whether an array is locked into volatile memory space on the currently open controller.
Command Line Interface (CLI) Example of container list: AAC0> container list Executing: container list Total Oth Stripe Label Type Size Ctr Size Usage ----- ----- ----- --- ------ ------0 Volume 30MB None Venus ■ Scsi Partition C:ID:L Offset:Size ----- -----------0:01:0 64KB: 15MB 02 64KB: 15MB container show cache Cache Attribute Indicates... global container read cache Number of blocks dedicated to the read cache. size global container write cache Number of blocks dedicated to the write cache.
Command Line Interface (CLI) CLI Command Dictionary This section contains a command reference. 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. Parameters {command}—If a command has more subcommands, help lists the subcommands and their functions. If a complete command is used, such as container list, the help displays all possible switches.
Command Line Interface (CLI) open [/readonly={boolean}] [/domain={string}] {string} Opens a controller for access by the CLI. The controller must be open before any command can be targeted at that controller. Parameters {string}—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 the commands that do not change the controller configuration.
Command Line Interface (CLI) 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 (CLI) 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 (CLI) 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}—Device and its associated available space used to create the array. {device_ID}—One or more devices whose available space to use to create the array. Switches /cache—Specifies whether to enable the array’s cache.
Command Line Interface (CLI) 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}—Device and its associated available space to use to create the volume. {free_space}—Available space to use to create the volume.
Command Line Interface (CLI) Parameters {container}—ID 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. Parameters {container1}—ID of the array to renumber. {container2}—ID number to assign to the array specified in container1.
Command Line Interface (CLI) 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. Switches /stripe_size—Stripe size of the array.
Command Line Interface (CLI) 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 segments as members. Parameters {container}—ID of the RAID 5 to restore. container scrub [/io_delay={integer}] [/no_repair={boolean}] [/wait={boolean}] {container} Checks and repairs the consistency of a redundant array.
Command Line Interface (CLI) Switches /read_cache_enable—Specifies whether to enable the readahead cache. /unprotected—Specifies whether to set the container's NVRAM write-back cache to disable, enable when protected, or enable always. Use this switch in conjunction with the /write_cache_enable switch. /write_cache_enable—Specifies whether to set the container's NVRAM write-back cache to disable, enable when protected, or enable always. Use this switch in conjunction with the /unprotected switch.
Command Line Interface (CLI) container set label {container} {string} Assigns a new label to the array. Parameters {container}—ID of the array to which to assign a label. {string}—Specifies the label to assign. container show cache {container} Displays caching parameters for an array. Parameters {container}—ID of the array whose associated cache parameters to display. container show failover [{container}] Displays an array’s assigned failover disks.
Command Line Interface (CLI) 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. controller firmware save [/C{controller}] [{controller}...
Command Line Interface (CLI) 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. Parameters {integer}—Time in seconds to cause the controller to wait before resuming I/O. controller rescan Rescans the channels and updates all underlying structures. controller reset_channel {integer} Resets a specific channel on the open controller.
Command Line Interface (CLI) 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 command defaults to 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 (CLI) disk initialize [/always={boolean}] [/unconditional={boolean}] {device_ID} Initializes a disk on the currently opened controller. Parameters {device_ID}—ID of the device to initialize, Switches /always—Specifies whether to initialize the disk even if the disk has existing data. (Cannot override open files.) Default is FALSE. /unconditional—Specifies whether to initialize the disk even if arrays on the disk have open files. The default is FALSE.
Command Line Interface (CLI) disk set smart [/all={boolean}] [/clear={boolean}] [/enable_exceptions={boolean}][/logerr={boolean}] [/perf={boolean}] [/report_count={boolean}] [{device_ID}] Changes a disk’s Self-Monitoring, Analysis and Reporting Technology (SMART) configuration configuration. Parameters {device_ID}—ID of the device on which to change SMART configurations. Switches /all—Specifies whether to enable SMART configurations for all disks. /clear—Clears the SMART error counts for the disk.
Command Line Interface (CLI) disk show partition Displays a list of partitions on the disks attached to the currently opened controller. disk show smart [/all={boolean}] [/full={boolean}] [/view_changeable={boolean}] {device_ID} Displays drive Self-Monitoring, Analysis and Reporting Technology (SMART) configuration information for one or all disks. Parameters {device_ID}—ID of the device for which to display SMART information. Switches /all—Specifies whether to display SMART configurations for all disks.
Command Line Interface (CLI) 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. If TRUE, the operation is performed immediately and the command prompt is returned only when done. disk zero [/repair={boolean}] [/wait={boolean}] {device_ID} Clears an entire disk (by writing zeros).
Command Line Interface (CLI) Task Commands Use the CLI commands to display and manage tasks. A task is an operation that occurs only on the controller, asynchronous to all other operations. Examples of tasks are clearing a disk and creating a RAID 1. Once a task is running on the controller, the CLI enables you to display, stop, suspend, and resume the task. task list [/all={boolean}] [{integer}] Lists the tasks running on the controller. Parameters {integer}—Task ID.
Command Line Interface (CLI) Enclosure Commands The enclosure commands operate on enclosure management devices that support Version 1.0 of the SAF-TE specification. If you are not using an enclosure, the following commands will not be available. enclosure activate slot {enclosure} {slot} Activates a device in a slot in the SAF-TE enclosure. Parameters {enclosure}—ID associated with the enclosure management device on which to activate a device. {slot}—Unit number associated with the slot.
Command Line Interface (CLI) enclosure prepare slot {enclosure} {slot} Prepares a device in a slot for insertion/removal. Parameters {enclosure}—ID associated with the enclosure management device on which to prepare a slot. {slot}—Unit number associated with the slot. enclosure set alarm [/on={boolean}] {enclosure} Turns the audible alarm on or off. Parameters {enclosure}—ID associated with the enclosure management device whose audible alarm to set.
Command Line Interface (CLI) enclosure set power [/off{=boolean}] {enclosure} {powersupply} Turns on or off a specific power supply. Parameters {enclosure}—ID associated with the enclosure management device. {powersupply}—Unit number associated with the power supply. Switches /off—Specifies whether to turn on or off the power supply associated with the unit number. enclosure set scsiid {enclosure} {slot} {device_ID} Sets the ID of the device slot.
Command Line Interface (CLI) enclosure show power [{enclosure}] [{powersupply}] Displays the status of one or more power supplies. Parameters {enclosure}—ID associated with the enclosure management device for which to display power supply status. {powersupply}—Unit number associated with the power supply. enclosure show slot [{enclosure}] [{slot}] Displays the status of a specific device slot on a specific enclosure.
Command Line Interface (CLI) Using Automated Command Scripts To execute a CLI command script, type the at sign (@) followed by the file name that contains the CLI commands, for example: AAC0>@commandscript.txt In its simplest form, a CLI command script is a text file that contains valid CLI commands. Each line ends with a line feed inserted by pressing Enter. The following CLI command script: 1 Opens controller AAC0 by invoking the CLI command open. 2 Invokes controller details.
D Supported RAID Types RAID is an acronym for Redundant Array of Independent Disks. The goal of RAID is to provide better performance and reliability from combinations of disk drives than possible with the same total storage space without RAID. When creating RAIDs, select drives of equal capacity and performance. Otherwise, the RAID tends to be limited in capacity and performance to that of the smallest and slowest drive.
Supported RAID Types RAID 0 A RAID 0 is created by striping data across two or more disk drives. This striping scheme creates no redundancy to protect the data. However, because the drives share load equally, RAID 0 provides the best read and write performance of any RAID type. An example of a RAID 0 array is shown below.
Supported RAID Types 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.
Supported RAID Types 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.
E Specifications DC Power Requirements Voltage 5 V ± 10% Ripple and noise 50 mV peak-to-peak maximum Current Requirements Adaptec 2410SA 1 A maximum Environmental Specifications Ambient temperature 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.
Glossary A activity See task. ACU Array Configuration Utility. An application 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 segments on one or more physical disks. Arrays are typically used to provide data redundancy or enhanced I/O performance. See also container, segment, volume, spanned volume, RAID 0, RAID 1, RAID 5, and RAID 10. Also known as a container.
Glossary B bad segment Segment that is in an unknown state. background consistency check Consistency check performed as a background process. See also consistency check command. 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.
Glossary clear Foreground initialization of a fault-tolerant array. A clear operation zeros all blocks of the array. The array is not accessible until the clear task is complete. concatenation Joining of physical or logical drives in sequential order. 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.
Glossary drive LED Disk indicator LED that illuminates during read or write operations. 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/segment See available space/segment. H hard disk, hard drive Basic unit of nonvolatile, nonremovable, magnetic storage media. See also disk drive. hot spare 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. hot swap To remove a component from a system and install a new component while the power is on and the system is running.
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 See segment. 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. All data written to an array that has been quick initialized is protected. R RAID Redundant Array of Independent Disks (alternative definition Redundant Array of Inexpensive Disks).
Glossary drive. The controller generates parity every time data is written to the array, and it is distributed in stripes across all the drives. RAID 10 Dual-level RAID type created by using two or more equal-sized 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. RAID signature The area on each disk reserved for use by the RAID controller.
Glossary Serial ATA (SATA) A successor to ATA that uses a serial, instead of parallel, interface. simple volume A volume made up of disk space from a single disk. It can consist of a single region on a disk or concatenated, multiple regions of the same disk. single-level array Array created from one or more segments. See also volume, spanned volume, RAID 0, RAID 1. spanned volume A simple volume that spans two or more drives. spare See hot spare.
Glossary V verify See consistency check command. volume See simple volume, spanned volume.
R Adaptec, Inc. 691 South Milpitas Boulevard Milpitas, CA 95035 USA ©2003 Adaptec, Inc. All rights reserved. Adaptec and the Adaptec logo are trademarks of Adaptec, Inc. which may be registered in some jurisdictions. Part Number: 513602-06, Ver.
