Raid Installation Guide Aacraid Arc
Raid Installation Guide Aacraid Arc
Raid Installation Guide Aacraid Arc
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.
Windows 2000 and Windows XP are trademarks of Microsoft Corporation in the US
and other countries, used under license.
All other trademarks are the property of their respective owners.
Changes
The material in this document is for information only and is subject to change
without notice. While reasonable efforts have been made in the preparation of this
document to assure its accuracy, Adaptec, Inc. assumes no liability resulting from
errors or omissions in this document, or from the use of the information contained
herein.
Adaptec reserves the right to make changes in the product design without
reservation and without notification to its users.
Disclaimer
IF THIS PRODUCT DIRECTS YOU TO COPY MATERIALS, YOU MUST HAVE
PERMISSION FROM THE COPYRIGHT OWNER OF THE MATERIALS TO AVOID
VIOLATING THE LAW WHICH COULD RESULT IN DAMAGES OR OTHER
REMEDIES.
ii
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.
■ Affix a copy of the TSID label to the CD jacket so that you don’t lose it.
Support Options
■ Search the Adaptec Support Knowledgebase (ASK) at ask.adaptec.com for
articles, troubleshooting tips, and frequently asked questions for your product.
■ For support via Email, submit your question to Adaptec’s Technical Support
Specialists at ask.adaptec.com.
North America
■ Visit our Web site at www.adaptec.com.
■ For information about Adaptec’s support options, call +1 408-957-2550,
24 hours per day, 7 days per week. To speak with a Technical Support Specialist,
■ For Hardware products call +1 408-934-7274,
Monday to Friday, 3:00 A.M. to 5:00 P.M., Pacific Time.
■ For RAID and Fibre Channel products call +1 321-207-2000 ,
Monday to Friday, 3:00 A.M. to 5:00 P.M., Pacific Time.
To expedite your service, have your computer in front of you.
■ To order Adaptec products, including accessories and cables, call +1 408-957-7274.
Or, you can order cables online at www.adaptec.com/buy-cables.
iii
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.adaptec.com.
■ English: To speak with a Technical Support Specialist, call +49 89 43 66 55 44,
Monday to Friday, 9:00 to 17:00, GMT. For support via e-mail, submit your
question to Adaptec’s Technical Support Specialists at ask.adaptec.com.
■ You can order Adaptec cables online at www.adaptec.com/buy-cables.
Japan
■ Visit our Web site at www.adaptec.co.jp.
■ To speak with a Technical Support Specialist, call +81 3 5308 6120
Monday–Friday, 9:00 A.M. to 12:00 P.M and 1:00 P.M. to 6:00 P.M.
iv
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. If the product should become defective within the warranty period, Adaptec, at
its option, will repair or replace the product, or refund the purchaser’s purchase price for the
product, provided it is delivered at the purchaser’s expense to an authorized Adaptec
service facility or to Adaptec.
2. Repair or replacement parts or products will be furnished on an exchange basis and will
either be new or reconditioned. All replaced parts or products shall become the property of
Adaptec. This warranty shall not apply if the product has been damaged by accident,
misuse, abuse or as a result of unauthorized service or parts.
3. Warranty service is available to the purchaser by delivering the product during the warranty
period to an authorized Adaptec service facility or to Adaptec and providing proof of
purchase price and date. The purchaser shall bear all shipping, packing and insurance costs
and all other costs, excluding labor and parts, necessary to effectuate repair, replacement or
refund under this warranty.
4. For more information on how to obtain warranty service, write or telephone Adaptec at 691
South Milpitas Boulevard, Milpitas, CA 95035, (800) 959-7274.
5. THIS LIMITED WARRANTY DOES NOT EXTEND TO ANY PRODUCT WHICH HAS
BEEN DAMAGED AS A RESULT OF ACCIDENT, MISUSE, ABUSE, OR AS A RESULT OF
UNAUTHORIZED SERVICE OR PARTS.
6. THIS WARRANTY IS IN LIEU OF ALL OTHER EXPRESS WARRANTIES WHICH NOW
OR HEREAFTER MIGHT OTHERWISE ARISE RESPECT TO THIS PRODUCT. IMPLIED
WARRANTIES, INCLUDING THOSE OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NON-INFRINGEMENT SHALL (A) HAVE NO GREATER
DURATION THAN 3 YEARS FROM THE DATE OF PURCHASE, (B) TERMINATE
AUTOMATICALLY AT THE EXPIRATION OF SUCH PERIOD AND (C) TO THE EXTENT
PERMITTED BY LAW BE EXCLUDED. IN THE EVENT THIS PRODUCT BECOMES
DEFECTIVE DURING THE WARRANTY PERIOD, THE PURCHASER’S EXCLUSIVE
REMEDY SHALL BE REPAIR, REPLACEMENT OR REFUND AS PROVIDED ABOVE.
INCIDENTAL OR CONSEQUENTIAL DAMAGES, INCLUDING WITHOUT LIMITATION
LOSS OF DATA, ARISING FROM BREACH OF ANY EXPRESS OR IMPLIED WARRANTY
ARE NOT THE RESPONSIBILITY OF ADAPTEC AND, TO THE EXTENT PERMITTED BY
LAW, ARE HEREBY EXCLUDED BOTH FOR PROPERTY DAMAGE, AND TO THE
EXTENT NOT UNCONSCIONABLE, FOR PERSONAL INJURY DAMAGE.
7. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL
OR CONSEQUENTIAL DAMAGES FOR CONSUMER PRODUCTS, AND SOME STATES
DO NOT ALLOW LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY LASTS, SO
THE ABOVE LIMITATION OR EXCLUSIONS MAY NOT APPLY TO YOU.
8. This warranty gives you specific legal rights, and you may also have other rights which vary
from state to state.
v
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. These limits are designed to provide reasonable protection
against harmful interference in a residential installation. This equipment generates, uses, and
can radiate radio frequency energy, and if not installed and used in accordance with the
instruction manual, may cause harmful interference to radio communications. However, there is
no guarantee that interference will not occur in a particular installation. However, if this
equipment does cause interference to radio or television equipment reception, which can be
determined by turning the equipment off and on, the user is encouraged to try to correct the
interference by one or more of the following measures:
■ Reorient or relocate the receiving antenna.
■ Increase the separation between equipment and receiver.
■ Connect the equipment to an outlet on a circuit different from that to which the receiver is
connected.
■ Consult the dealer or an experienced radio/television technician for help.
■ Use a shielded and properly grounded I/O cable and power cable to ensure compliance of
this unit to the specified limits of the rules.
This device complies with part 15 of the FCC rules. Operation is subject to the following two
conditions: (1) this device may not cause harmful interference and (2) this device must accept
any interference received, including interference that may cause undesired operation.
Tested to Comply
With FCC Standards
vi
Canadian Compliance Statement
This Class B digital apparatus meets all requirements of the Canadian Interference-
Causing Equipment Regulations.
Cet appareil numérique de la classe B respecte toutes les exigences du Règlement sur
le matériel brouilleur du Canada.
vii
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
Using the CD Autorun in Windows 1-12
Browsing the CD 1-13
Installing the Adobe Acrobat Reader 1-13
Software Tools Overview 1-14
Safety Information 1-15
Electrostatic Discharge 1-15
viii
Contents
ix
Contents
x
Contents
E About RAID
Simple Volume E-1
Spanned Volume E-2
RAID 0 E-2
RAID 1 E-2
RAID 5 E-3
RAID 10 E-4
RAID 50 E-5
xi
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...
1-1
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:
1-2
Introduction
1-3
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.
System Requirements
The following system features are required:
■ Intel Pentium, or equivalent, processor
■ At least 128 MB of RAM
■ An available 32- or 64-bit PCI slot
■ 20 MB of free drive space
■ 16-bit SVGA color monitor with a resolution of at least 800 x 600
■ CD-ROM drive (that is not part of the RAID you are installing)
■ SCO—
– UnixWare 7.1.x/OpenUNIX 8 (Base and Business Editions)
– OpenServer 5.06 and 5.07
■ Novell—NetWare 6.x
1-4
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.
Controller Features
This section contains the following subsections:
■ Features Overview
■ SATA RAID Controller Features Summary
■ SCSI RAID Controller Features Summary
■ Advanced RAID Features
Features Overview
Adaptec RAID controllers offer the following features:
■ Supports PCI Local Bus Specification, Revision 2.2. Some models also
support the PCI-X Addendum, Revision 1.0a. See pages 1-6 and 1-7.
■ 64-bit, 66-MHz PCI interface compatible with 32-bit/33-MHz
PCI slots.
■ At least 64 MB of on-board RAM. Some controllers are available
with more RAM.
■ All except Adaptec 2020ZCR—Optional battery backup module
available. For details, see page 1-9.
■ Operating system independent configuration and RAID
creation using the Adaptec RAID Configuration (ARC) utility.
■ Flash ROM for easy updates of controller firmware, BIOS, and
ARC. For details on updating the flash, see Appendix C.
■ Event logging and broadcasting, including messaging for
alphanumeric pagers.
1-5
Introduction
1-6
Introduction
1-7
Introduction
1-8
Introduction
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.
The Adaptec RAID controllers support two types of hotspares:
■ 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.
Audible Alarm
Adaptec RAID controllers are equipped with an audible alarm that
can alert you to situations that affect data safety. This section
discusses the following topics:
■ Sounding the Alarm
■ Silencing the Alarm
For additional details on how to control the alarm, see page A-11
and the Adaptec Storage Manager online Help.
Sounding the Alarm
The alarm sounds under the following circumstances:
■ When the controller is running, the alarm sounds when a drive
fails. For example, if a drive becomes unplugged, the alarm
sounds.
■ When restarting the system, the alarm sounds if an array is
degraded. For example, if a drive is missing from a three-drive
RAID 5, the alarms sounds.
■ If an array can’t be configured, the alarm sounds. For example,
if a drive is missing from a RAID 0, or if two drives are missing
from a RAID-5, the alarm sounds.
1-9
Introduction
Automatic Failover
Adaptec RAID controllers can 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.
Notes:
■ To see if the controller is available with battery modules,
see Controller Features on page 1-5.
■ To see the battery module connector location for your
controller, see Appendix G.
■ To purchase a battery module, visit www.adaptec.com.
1-10
Introduction
Document CD Location
Readme /
Installation and User’s Guide /books/RAID Install Gd 513853vAA.pdf
Command Line Interface /books/RAID SW Ref 513852vAA.pdf
Reference Guide
1-11
Introduction
1-12
Introduction
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.exe if your
computer does not automatically execute it when you insert the
CD in the drive.
■ Readme text file—Contains additional technical information
about device compatibility, operating system support, and drivers.
■ DOCS folder—Contains the user documentation PDF files.
■ PACKAGES folder (and subfolders)—Contains the
management software and device drivers.
■ SOURCES folder (and subfolders)—Contains driver source
files and other components developed under the GNU General
Public License (GPL) agreement.
1-13
Introduction
1-14
Introduction
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. ESD is produced by materials that accumulate and retain
electrical charges which are transferred to people or other objects
upon contact.
1-15
2
Installing the Controller
and Drives
In this Chapter...
2-1
Installing the Controller and Drives
Notes:
■ For additional considerations related to installing SCSI
drives, see Appendix F, About SCSI.
■ Use only good quality cables. Poor quality cables may
degrade system reliability. Avoid cables not rated for
Ultra320 operation.
■ To buy cables, visit www.adaptec.com.
■ Use device adapters as needed to connect any SE drives.
■ Do not attach a cable to the controller unless the other end
of the cable is attached to a least one drive. Doing so
would cause unstable operation.
2-2
Installing the Controller and Drives
2-3
Installing the Controller and Drives
2-4
Installing the Controller and Drives
2 Turn on the computer, then press Ctrl-A to enter the ARC utility.
The first screen shows all installed Adaptec RAID controllers.
3 If more than one Adaptec RAID controller is installed, highlight
the boot controller, then press Enter.
4 To select the ACU utility, press Enter.
The ACU screen appears.
5 Using the arrow keys, highlight Initialize Drives, then press
Enter.
6 Press Insert to highlight the drives you want to initialize, then
press Enter to start the initialization process.
7 Using the arrow keys, highlight at least three drives to be used
for the array and press Insert for each highlighted drive.
The utility displays the selected drives.
8 Press Enter.
A red warning box appears—this is normal.
2-5
Installing the Controller and Drives
2-6
Installing the Controller and Drives
6 Click Create.
7 In the configuration wizard, select Custom.
8 Click the RAID 5 button, then click Next.
9 Click at least three drives to be used in your array.
Each drive you select is marked with a check.
2-7
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.
13 Click Reboot to restart your system.
14 Remove the Adaptec installation CD.
15 If you want to make the array bootable, do so now. For details,
see page A-5.
2-8
3
Installing the Driver
In this Chapter...
3-1
Installing the Driver
Note: If you don’t like your initial RAID level selection, you
can change it later using Array Level Migration. For details,
see page 1-8 and the Adaptec Storage Manager online
Help for details.
3-2
Installing the Driver
3-3
Installing the Driver
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. Respond to the
on-screen instructions to complete the installation.
3-4
Installing the Driver
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.
3-5
Installing the Driver
OpenServer
This section contains procedures for installing the driver in
OpenServer systems.
3-6
Installing the Driver
3-7
Installing the Driver
Note: Although the driver disk you create for UnixWare and
OpenUNIX differ, the installation procedures for these
operating systems are the same.
3-8
Installing the Driver
3-9
Installing the Driver
3-10
Installing the Driver
Now that you have installed the drivers, refer to your NetWare
documentation to modify disk partitions, apply hot fixes, or
perform volume maintenance. Also see Loading NetWare Drivers
During Server Restart on page 3-12 for a summary of array
management options in NetWare.
3-11
Installing the Driver
Notes:
■ Command line options are not case sensitive.
■ Placing commas between command line options is
optional.
3-12
Installing the Driver
Note: You can also use your DOS text editor to modify the
startup.ncf file, it resides on the DOS partition.
3-13
4
Installing and Starting
Adaptec Storage Manager
In this Chapter...
After you have installed your Adaptec RAID controller and driver,
you are ready to install and use Adaptec Storage Manager—a user-
friendly graphical user interface that makes it easy for you to create
and manage arrays without having to restart the computer and use
the BIOS utility.
4-1
Installing and Starting Adaptec Storage Manager
4-2
Installing and Starting Adaptec Storage Manager
4-3
Installing and Starting Adaptec Storage Manager
4-4
Installing and Starting Adaptec Storage Manager
4-5
Installing and Starting Adaptec Storage Manager
4-6
Installing and Starting Adaptec Storage Manager
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. To run Storage
Manager in a browser, open the browser, then type in
the IP address, colon (:), and 34572 as the port number.1
Linux Change to the directory where you installed Storage
Manager by typing cd /usr/RaidMan. Then, use the
sh RaidMan.sh shell command.
OpenServer Change to the directory where you installed Storage
UnixWare Manager by typing cd /opt/RaidMan. Then, use the
OpenUNIX sh RaidMan.sh shell command.
NetWare Type the LOAD RAIDMAN command.
1. To run Storage Manager in a browser, your network's DNS configuration must
have matching forward and reverse lookups.
4-7
Installing and Starting Adaptec Storage Manager
Once you are logged in for the first time, you can add new accounts
and change account passwords. For details, refer to the online
Help.
4-8
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.
5-1
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.
■ Yellow—Warning
■ Red—Error
5-2
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.
5-3
Understanding Adaptec Storage Manager
■ Drive ID
■ Drive state
5-4
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.
■ In the graphical views, if the logical device uses only part of the
available storage, only those segments are highlighted (in dark
blue).
5-5
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. (Also available as a stand-alone
DOS utility as described in Appendix B, ACU for DOS.)
■ SATASelect and SCSISelect—Used to change device and
controller settings.
■ Disk Utilities—Used to format or verify media.
To run the ARC utility, press Ctrl+A when prompted by the
following message during system startup:
Press <Ctrl><A> for Adaptec RAID Configuration Utility
A-1
Adaptec RAID Configuration Utility (ARC)
Creating Arrays
To create an array:
1 For systems with RAID enclosures—Power up any enclosures.
Note: The ACU may not find disks or enclosures that were
powered up after system power-up. Therefore, power up
enclosures prior to powering up the computer.
A-2
Adaptec RAID Configuration Utility (ARC)
A-3
Adaptec RAID Configuration Utility (ARC)
Managing Arrays
With the Manage Arrays option, you can perform the following tasks:
■ Viewing Array Properties
■ Making an Array Bootable
■ Deleting Arrays
■ Managing Failover Drive Assignments
A-4
Adaptec RAID Configuration Utility (ARC)
Notes:
■ If the controller is not a boot device, you can disable its
runtime BIOS. (For details, see the table on 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.
■ The controller always uses the lowest numbered array as its
bootable array. If you delete Array 00, the next lowest
numbered array becomes the bootable array.
■ You cannot make a non-00 array bootable while the array
is in a build/verify or rebuild process.
■ You may need to change the system BIOS to modify the
boot order. For more information, refer to the system
documentation.
A-5
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. Before proceeding, back up any data.
A-6
Adaptec RAID Configuration Utility (ARC)
Initializing Drives
If a correctly installed disk does not appear in the disk selection list
for creating a new array, or it appears grayed out, you need to
initialize it.
! Caution:
■ During initialization, all data is deleted from the disk.
Before proceeding, back up any data.
■ If the drive is already used in an array, initialization may
make the array unusable.
■ Do not initialize a disk that is part of a boot array. The boot
array is the lowest numbered array (normally 00) in the
List of Arrays dialog box. For information on determining
which disks are associated with a particular array, see
Viewing Array Properties on page A-5.
A-7
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.
8 Read the warning message, ensure that you have selected the
correct drives to initialize, and then press Y to continue.
Rescanning Drives
To rescan the drives connected to the controller:
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 Rescan Drives.
A-8
Adaptec RAID Configuration Utility (ARC)
A-9
Adaptec RAID Configuration Utility (ARC)
Models
Option Default Affected Description
Drives Write Drive's All When Enabled, write cache is
Cache Default enabled, providing maximum drive
performance. When Disabled, no
write cache is used on the drive. By
default, the drive’s setting is used.
Caution—When Enabled, there is a
slight possibility (less than with
controller cache) of data loss or
corruption during a power failure.
Runtime BIOS Enabled All When Enabled, the controller BIOS
allows the controller to act as a
bootable device. Disabling the BIOS
allows another suitable controller to
act as the boot device.
Automatic Enabled All When Enabled, the controller
Failover automatically rebuilds an array
when the failed drive is replaced.
When disabled, the array must be
rebuilt manually.
Array Disabled All When Enabled, the controller
Background constantly performs a verification
Consistency on a redundant array to data
Check 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 or a RAID 0,
consistency checks assure that data
in the stripe and the calculated
parity for the stripe match.
Consistency checking processes
reduce performance. For a RAID 5
or a RAID 50, the performance
reduction is significant.
BBS Support Enabled See When Enabled in systems that
note 1 support BBS, controller is presented
as a bootable device in the host
system's BIOS for boot device
selection.
A-10
Adaptec RAID Configuration Utility (ARC)
Models
Option Default Affected Description
Array-based Disabled All When Enabled in systems that
BBS Support 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 Disabled All When Enabled, attached physical
Drives Display devices are displayed during system
during POST POST. Displaying the devices adds a
few seconds to the overall POST
time.
CD-ROM Boot Enabled SCSI When Enabled, the system can be
Support only booted from a bootable CD.
Removable Enabled SCSI When Enabled, removable media
Media Devices only devices, such as CD drives and Zip
Support drives, are supported.
Alarm Control Enabled See When Enabled, the alarm sounds.
note 2
A-11
Adaptec RAID Configuration Utility (ARC)
Models
Option Default Affected Description
Write Cache Yes All SATA When Enabled, write cache is enabled,
controllers providing maximum performance.
Caution—When Enabled, there is a
potential for data loss or corruption
during a power failure.
DMA Yes Adaptec When Enabled, Direct Memory Access
2410SA (DMA) mode is used for the drive,
only providing maximum performance.
SMART Yes Adaptec Controls the predictive failure feature
2410SA of the drive. When Enabled and the
only 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. Messages
are logged to the Storage Manager log
file when they occur. When Event
Broadcasting is enabled for your
operating system, SMART events are
also sent to destinations according to
the system’s particular configuration
(for example, system log file, Event
Viewer, pop ups, email, etc.) When
Disabled, or when the drive does not
support SMART, the SMART status is
not displayed.
Allow Read Yes Adaptec When Enabled, the drive’s read ahead
Ahead 2410SA cache algorithm is use, providing
only maximum performance under most
circumstances.
A-12
Adaptec RAID Configuration Utility (ARC)
A-13
Adaptec RAID Configuration Utility (ARC)
1. Adaptec recommends that you not enable QAS if you are using an enclosure that
contains Ultra320 expander ICs.
A-14
Adaptec RAID Configuration Utility (ARC)
A-15
Adaptec RAID Configuration Utility (ARC)
A-16
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.
B-1
ACU for DOS
For details on using the ACU interactively, see Using the ACU on
page A-2.
B-2
ACU for DOS
B-3
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 <file> 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.
Record Mode
There are two methods available for creating a script file:
■ Use Record Mode.
■ Create the script manually. (See page B-5.)
Regardless of which method you use to create the script, you need
to use Playback Mode (/P) to use the script.
In Record Mode, the ACU writes a controller’s existing array
configuration to a specified script file, enabling you to create the
same configuration by running the ACU in Playback Mode (/P
switch) with the resulting script.
The syntax is ACU /R <file> where file is the parameter
specifying name of the script file. The file parameter can include
a drive, directory, filename, and extension, but only the filename
and extension are required. If no drive or directory is specified, the
file is placed in the location of the ACU executable.
B-4
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. If the ACU encounters an array that it
cannot create, it displays a warning (or records the
warning in the log file, if the /L switch is used) and does
not record any keywords for that array in its script file.
■ When recording an array, the ACU always uses the default
Wait setting (equivalent to Wait=Yes) unless you edit the
script file and include Wait=No in the array’s definition
block. For details, see the Wait Keyword on page B-11
Comments
To enter a comment in the script file, start with a pound character (#).
You can start anywhere on a line. For a sample script that includes
comments, see Example – Running the ACU with a Script on page B-14.
B-5
ACU for DOS
Default
Keyword Required? Value Description
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).
End Yes None Indicates the end of an array
definition block. See page B-7
for details.
HotspareDrives No None Specifies the hotspares to
assign to the array. See
page B-8).
InitializeAll No No Indicates whether to initialize
all the drives connected to the
controller. See page B-8).
Method Yes Build Indicates the method (Build/
Verify, Clear, or Quick Init) to
use when creating a redundant
array (see page B-9.
ReadCache No Yes Indicates whether read
caching is enabled for this
array (see page B-10).
Size No Maximum Specifies the size of the array
(see page B-10).
StripeSize No 64 Specifies the size of contiguous
I/O, in bytes (see page B-10).
Type Yes None Indicates the type of array to
create (see page B-9).
Wait No Yes Indicates whether the ACU
should wait for the new array’s
build/verify or clear to com-
plete before continuing (see
page B-11).
WriteCache No Yes Indicates whether write cach-
ing is enabled for this array
(see page B-11).
B-6
ACU for DOS
Array Keyword
Array is a required keyword, indicating the start of an array
definition block. The syntax is Array=<label>, where label is
an optional alphanumeric string.
Examples
Array
Array=MyData
Drives Keyword
Drives is a required keyword, specifying the devices to use in
creating the array. There is no default value.
A drive is identified by its channel number, ID (target), and LUN,
separated by colons; for example, 0:0:0 or 0:1:0. Separate
multiple drive identifiers with commas.
Prior to creating any new arrays, the ACU initializes any drives
specified by the Drives keyword. If a drive is specified in more
than one array definition block in a script, it is initialized only once.
Examples
Drives=0:0:0
Drives=0:0:0,0:1:0,0:2:0
End Keyword
End is a required keyword, indicating the end of the block.
Example
End
B-7
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.
■ HotspareDrives does not verify that the available space
on the specified hotspares is sufficient to serve as failover
for the array.
■ When assigning hotspares to a multilevel array,
HotspareDrives assigns all the hotspares in the list to all
arrays within the multilevel array.
Example
HotspareDrives=0:0:0,0:1:0
InitializeAll Keyword
If you want the ACU to initialize all drives connected to the
controller and delete any existing arrays before any new arrays are
created, even those that are not specified in any Drives keyword
definition, specify InitializeAll=yes. Otherwise, the ACU
initializes only those drives specified by the Drives keyword.
B-8
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.
Method Keyword
Method is an optional keyword, indicating which method to use
when creating a redundant (RAID 1, 5, and 10) array. Possible
values are:
■ Build (the default)—Perform a build/verify process on the array.
Takes longer than Clear, but allows you to begin using the array
immediately.
■ Clear—Clear the array. Faster than a build/verify process, but
you have to wait for the operation to be completed before you
can begin using the array.
■ Quick Init—Makes the array available immediately, but does not
accomplish a build/verify. Parity and mirror information is created
as data is written to the drive (called full-stripe write mode), which
reduces overall array performance. Maximum performance is
achieved by starting and completing a build/verify.
Example
Method=Build
B-9
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. Otherwise, specify the
size as an integer or a decimal number, followed by the unit
keyword MB (megabytes), GB (gigabytes), or TB (terabytes).
Examples
Size=2.5GB
Size=300MB
Size=Maximum
StripeSize Keyword
The StripeSize keyword specifies the stripe size (in MB) written
to each member of a striped (RAID 0, RAID 5, RAID 10) array.
The possible values for StripeSize are 16 KB, 32 KB, and 64 KB
(the default).
Example
StripeSize=64
B-10
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
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. Otherwise, the
ACU waits by default.
Examples
Wait=Yes
Wait=No
WriteCache Keyword
The WriteCache keyword indicates whether write caching is used
for this array if write caching is supported for the system. Possible
values are as follows:
■ Yes (the default)—Enable the write cache.
■ No—Disable the write cache.
Example
WriteCache=Yes
B-11
ACU for DOS
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.
Channel Keyword
Channel is an optional keyword that begins a channel definition
block and specifies the channel number to which the channel
keywords apply. Channels are numbered from zero to the
maximum number of channels on the controller minus one.
You can include multiple channel definition blocks within a script file,
each beginning with a Channel keyword and value. For example:
Example
Channel=0
ControllerID Keyword
ConrollerID is an optional keyword to change the SCSI ID of the
controller. Normally, the SCSI controller is assigned SCSI ID 7 on
each of its channels. You can specify any ID value between 0 and 7.
Example
ControllerID=7
End Keyword
End is a required keyword, indicating the end of the block.
Example
End
B-12
ACU for DOS
Code Description
0 ACU ran without changes—The ACU exited with no errors
(success) and no report is required.
1 No controller found—The ACU did not detect any controllers in the
system.
2 Syntax or logical error in the script file—The ACU encountered an
invalid command or keyword in the specified script file.
3 Unable to open file—The ACU was unable to open the specified
script or log file.
4 Error in the command line parameters—You passed an invalid
command-line switch to the ACU. (See Running the ACU Using
Scripts on page B-3 for the list of valid command-line switches.)
5 Unable to read system configuration—The ACU was unable to get
the configuration information from the specified controller.
6 No drives detected—The ACU did not detect any devices attached
to the selected controller.
7 Specified drive not found in system—The device you specified
does not exist on the selected controller.
8 Specified array size too small—You specified an array size that is
smaller than the minimum size allowed for this array.
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.
13 Too many spare drives assigned—You attempted to assign more
than the maximum number of hotspares allowed for the specified
array.
B-13
ACU for DOS
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.
100 You ran ACU and made changes—The ACU exited with no errors
(success) and you must restart the computer.
B-14
ACU for DOS
B-15
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.
C-1
Adaptec Flash Utility (AFU)
System Requirements
The requirements for AFU are as follows:
■ MS–DOS version 5.0 or later. It cannot run from a DOS
command prompt window under any version of Windows.
■ At least 8 MB of extended memory.
Note: You cannot create the bootable floppy using Windows 2000.
Compatibility
The AFU has the following compatibility issues:
■ Supports HIMEM.SYS; compatible with other DOS drivers
running under HIMEM.SYS (for example, SMARTDRV.SYS and
SETVER.SYS).
■ Does not support DOS extenders installed in memory, such as
EMM386.SYS and DOS4GW.
C-2
Adaptec Flash Utility (AFU)
Note: You cannot create the bootable floppy using Windows 2000.
C-3
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.
C-4
Adaptec Flash Utility (AFU)
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.
Examples
The following are examples of command syntax that will work to
get help:
A:\> AFU HELP
A:\> AFU /?
LIST
The LIST command displays the AFU-supported controllers
installed on your computer. Use this command to see which
controllers are installed on this system, or to identify the ID
numbers assigned to each physical controller.
You do not have to restart the computer upon completion of this
command.
Example
The following example shows typical system output in response to
a LIST command.
A:\> AFU LIST
Adaptec Flash Utility V4.0-0 B5749
(c)Adaptec Inc. 1999–2002. All Rights Reserved.
Controllers Detected and Recognized:
Controller #0 (03:05:00) Adaptec 2410
C-5
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.
Command Syntax
The command syntax for the SAVE command is as follows:
AFU SAVE [/C<Controller ID>] [/D <UFI File Path>]
Command Switches
The following switches are available:
■ /C <Controller ID> is one or more controller IDs representing
the set of controllers on which to perform the specified
command. The default is 0, which means that if the computer
has multiple controllers, the AFU defaults to controller 0 unless you
specify otherwise.
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.
Note: You cannot specify the name of a UFI file, only its path.
UFI filenames are predefined, based on the controller type.
C-6
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
UPDATE
The UPDATE command updates a controller’s flash components
from the flash image data in a UFI file. You can use the UPDATE
command to update a single controller’s flash components or to
update multiple controllers on your computer.
You must restart the computer following an UPDATE command.
Command Syntax
The command syntax for the UPDATE command is as follows:
AFU UPDATE [/C<Controller ID>] [/D <UFI File Path>]
Command Switches
For details on the /C and /D switches, see the SAVE command on
page C-6.
Example
The following example shows typical system response after an
update has been performed.
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.
C-7
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.
Command Syntax
The command syntax for the VERIFY command is as follows:
AFU VERIFY [/C<Controller ID>] [/D <UFI File Path>]
Command Switches
For details on the /C and /D switches, see the SAVE command on
page C-6.
Example
The following example shows a typical display resulting from a
verify operation.
A:\> AFU VERIFY /C 0
Adaptec Flash Utility V4.0-0 B5749
(c)Adaptec Inc. 1999–2002. All Rights Reserved.
Reading flash image file (Build 5748)
Controller #0: Adaptec 2410
ROM: Checksum: 797B [VALID] (Build 5748)
File: Checksum: 797B [VALID] (Build 5748)
Image Compares Correctly
VERSION
The VERSION command displays version information about the
flash components on a controller.
After using the VERSION command, you must restart the computer
upon completion of this command.
Command Syntax
The command syntax for the VERSION command is as follows:
AFU VERSION [/C<Controller ID>]
Command Switches
For details on the /C switch, see the SAVE command on page C-6.
C-8
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
C-9
Adaptec Flash Utility (AFU)
C-10
D
Command Line Interface
In this Appendix...
Introduction D-2
Terminology D-2
Accessing the CLI D-4
Using the CLI D-5
General Control Commands D-15
Container (Array) Commands D-16
Controller Commands D-25
Disk Commands D-28
Logfile Commands D-32
Task Commands D-32
Enclosure Commands D-34
Using Automated Command Scripts D-38
D-1
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. For a full description of all the CLI commands, refer to the
Command Line Interface Reference Guide.
Terminology
This section discusses terminology used in this Appendix.
Adaptec 2410SA/2810SA Controllers Only
D-2
Command Line Interface
All Controllers
D-3
Command Line Interface
D-4
Command Line Interface
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.0KB:8.47GB
0:02:0 Free 64.0KB:8.47GB
0:03:0 Free 64.0KB:8.47GB
0:04:0 Free 64.0KB:8.47GB
D-5
Command Line Interface
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 partition before the I/O data stream switches to the
next partition in the array.
The stripe size can be 16, 32, or 64 KB; the default is 64 KB. Note
that you can change the stripe size later using the container
reconfigure command.
To create a RAID 0, use the container create stripe command. In
the following example, the Array 0 is created on device 0:01:0
from 100 MB of available space. The array’s cache is enabled, and
the label is Mars.
AAC0> container create stripe /cache=TRUE /label=Mars ((0,01,0), 100M)
Executing: container create stripe /cache=TRUE
/label="Mars" ((CHANNEL=0,ID=1,LUN=0),104,857,600 )
container 0 created
D-6
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. When you set up parity, the parity stripes are initialized, by
default, using a scrub switch (/scrub=TRUE). Parity is set up in the
background, and the disks are available immediately.
The stripe size can be 16, 32, or 64 KB; the default is 64 KB. Note
that you can change the stripe size later using the container
reconfigure command.
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:
AAC0> container create raid5 /stripe_size=64K ((0,1,0), 100M) (0,2,0) (0,3,0)
Executing: container create raid5 /stripe_size=65,536
((CHANNEL=0,ID=1,LUN=0),104,857,600) (CHANNEL=0,ID=2,LUN=0)
(CHANNEL=0,ID=3,LUN=0)
Deleting an Array
To delete an array, use the container delete command. In the
following example, Array 0 is deleted.
AAC0> container delete 0
Executing: container delete 0
D-7
Command Line Interface
D-8
Command Line Interface
Controller List
The controller list attributes are defined as follows:
■ Adapter Name—Name
■ Adapter Type—Product name
■ Controller Availability—Access mode
Example
D-9
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 including the host controller
■ Controller CPU Speed—Clock speed (in MHz)
■ Controller Memory—Total amount of available memory for
applications and data
Example
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.0-0 (Build #5478)
API: 3.0-0 (Build #5478)
Miniport Driver: 3.0-0 (Build #5478)
Controller Software: 3.0-0 (Build #5478)
Controller BIOS: 3.0-0 (Build #5478)
Controller Firmware: (Build #5478)
Controller Hardware: 3.3
D-10
Command Line Interface
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 removable
(floppy disk or CD-ROM, for example)
■ Vendor ID—Name of a device vendor
■ Product ID—Device model number
■ Revision Number—Device revision number
■ Number of Blocks—Total number of disk block available on a
device
■ Bytes per Block—Number of bytes for each block
■ Disk Usage—Either MS-DOS, Initialized, Not Initialized,
Offline, or Unknown
■ Shared Channel—N/A
Example
AAC0> disk list
Executing: disk list
C:ID:L Device Type Blocks Bytes/Block Usage Shared
------ ----------- -------- ----------- ----------- ------
0:01:0 Disk 17783240 512 Initialized NO
0:02:0 Disk 17783240 512 Initialized NO
D-11
Command Line Interface
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 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
The disk verify 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)
Container List
The container list attributes are defined as follows:
■ Drive Letter—Letter associated with an array. Not
automatically assigned when you create an array.
D-12
Command Line Interface
D-13
Command Line Interface
D-14
Command Line Interface
exit
Closes the opened controller and exits the CLI.
history_size {buffer_size}
Linux/Unix only—Sets the size of the history buffer.
Parameters
{buffer_size}—Size of the command history buffer. The
default is 200.
D-15
Command Line Interface
reset_window
Linux/Unix only—Resets the window.
D-16
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.
D-17
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.
D-18
Command Line Interface
D-19
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.
D-20
Command Line Interface
D-21
Command Line Interface
Parameters
{container}—ID number of the array to set to read-write
access.
D-22
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.
D-23
Command Line Interface
D-24
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.
Controller Commands
Use the Controller commands to display the status of a variety of
controller attributes and to perform such tasks as pausing or
resuming I/O, and enabling or disabling automatic failover.
D-25
Command Line Interface
controller details
Shows details about the open controller and software.
D-26
Command Line Interface
controller rescan
Rescans the channels and updates all underlying structures.
controller resume_io
Performs rescan operation, then resumes I/O after pause_io.
D-27
Command Line Interface
Disk Commands
Use the disk commands to manage disks connected to a RAID
controller. The CLI allows you to monitor disk characteristics and
parameters, prepare a disk for use, and detect defects.
D-28
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.
D-29
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. If TRUE, reporting of
exceptions according to the MRIE mode is enabled.
/report_count—Number of times an exception can be
reported. A value of zero indicates no limit.
D-30
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.
D-31
Command Line Interface
Logfile Commands
logfile end
Ends logging of all output and closes the log file.
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 allows
you to display, stop, suspend, and resume the task.
D-32
Command Line Interface
D-33
Command Line Interface
Enclosure Commands
D-34
Command Line Interface
Parameters
{enclosure}—ID number of the enclosure management device
on which to prepare a slot.
{slot}—Unit number of the slot.
D-35
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.
D-36
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.
D-37
Command Line Interface
D-38
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.
Maximum Drives Supported / Minimum Drives Required
for Adaptec Controller Models
2020ZCR/
Array Type 2410SA 2810SA 2120S 21610SA 2200S
RAID 0 4/2 8/2 15 / 2 16 / 2 30 / 2
RAID 1 2/2 2/2 2/2 2/2 2/2
RAID 5 4/3 8/3 15 / 3 16 / 3 16 / 3
RAID 10 4/4 8/4 14 / 4 16 / 4 30 / 4
RAID 50 N/A 8/6 15 / 6 16 / 6 30 / 6
Simple Volume
A simple volume consists of a single drive.
E-1
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.
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.
RAID 0 RAID 1
RAID 1
A RAID 1 array is created by copying, or mirroring, all data from
one drive onto a second drive. This mirroring provides redundancy,
ensuring that if one drive fails no data is lost. Redundancy also
means that only half of the total capacity is available.
RAID 1 offers no write performance advantage over a simple
volume configuration. However, because the drives share read load
equally, RAID 1 provides improved read performance. An example
of a RAID 1 array is shown above.
E-2
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.
RAID 5
E-3
About RAID
RAID 10
This dual-level RAID type is 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 10
Data 2 Data 3
Data 4 Data 5
Data 6 Data 7
Second-Level Arrays
Drive Drive Drive Drive
Data 0 Data 0 Data 1 Data 1
E-4
About RAID
RAID 50
This dual-level RAID type is created by using two or more equal-
sized 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.
RAID 50
Top-Level Arrays
RAID 5 RAID 5
Data 0 & Data 1 Data 2 & Data 3
Second-Level Arrays
RAID 0 RAID 0
E-5
F
About SCSI
In this Appendix...
F-1
About SCSI
See Mixing SE Devices with LVD Devices on page F-3 for more
details.
F-2
About SCSI
F-3
G
Controller Illustrations
This Appendix shows the Adaptec RAID controllers.
PCI connector
Low-profile bracket
G-1
Controller Illustrations
Adaptec
External VHDCI
SCSI Connector
PCI connector
Low-profile bracket
Adaptec
External VHDCI
SCSI connectors
PCI connector
Low-profile bracket
G-2
Controller Illustrations
SATA ports
Battery connector
PCI connector
Full-height bracket
3 2 1 0
G-3
Controller Illustrations
Battery connector
SATA ports
PCI connector
Full-height bracket
1 3 4 6
0 2 5 7
G-4
Controller Illustrations
Battery connector
SATA ports
SATA ports
PCI connector
Full-height bracket
1 3 4 6
9 11 12 14
0 2 5 7
8 10 13 15
G-5
H
Specifications
Environmental Specifications
Ambient temperature without 0 °C to 50 ° C
battery backup module
Relative humidity 10% to 90%, noncondensing
Altitude up to 3,000 meters
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.5 A @ 5 VDC
H-1
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.
available space/partition
Unused space on an initialized disk from which logical devices
(arrays) are created. When an array is deleted, the space that it used
is returned to the available space pool.
B
background consistency check
Consistency check performed as a background process. See also
consistency check command.
bad partition
partition that is in an unknown state.
Glossary-1
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.
channel
Any path, or bus, used for the transfer of data between storage
devices and a RAID controller.
chunk
See stripe.
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.
Glossary-2
Glossary
D
dead partition
See failed.
degraded
A redundant (for example, a RAID 1) array in which one or more
members have failed. The data is intact but redundancy has been
compromised. Any further failure would cause the array to fail and
result in data loss.
dirty data
Data that has been written to a cache, but which has not been
“flushed” out to its final destination.
disk
A nonremovable platter in a hard drive, or removable media used
in a CD drive, floppy disk drive, or Zip drive. See also disk ID,
drive, and hard disk, hard drive.
disk ID
Unique disk identifier that consists of the channel number, ID, and
LUN (channel:ID:LUN), for example, 1:04:0. See also channel.
drive
Device used for storing data. May contain one or more removable
or nonremovable, writable or read only media. See also hard disk,
hard drive.
Glossary-3
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.
failed partition
A partition that is no longer usable by an array because it is either
logically bad and therefore no longer needed, or physically
damaged.
failover drive
See hotspare.
fault-tolerant array
Refers to an array that can continue to function after a disk drive
failure without loss of data. See also redundant.
foreign disk
Disk that has previously been initialized on another Adaptec RAID
controller. The RAID signature on the disk allows the RAID
controller to identify whether or not the disk was initialized on the
controller it is currently connected to.
Glossary-4
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.
I
impacted
An impacted array is one which has been created, but for some
reason the initial build operation did not complete. All member
drives are present and operational, and all data written to the array
is protected. To optimize the array, run a Verify with Fix task.
initialize
Process of preparing a disk for use by the controller. When a disk is
initialized, the controller records the RAID signature on the disk.
initialized array
An array that is ready for data reads and writes. Arrays can be
initialized by build or clear.
Glossary-5
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.
M
migration
See reconfiguration.
mirrored array/mirroring
See RAID 1 on page E-2.
monitoring
Process of receiving, displaying, and logging system events.
multipartition array
Array with multiple operating systems or MS-DOS partitions.
O
offline array
Array that can no longer be accessed.
optimal
The state of an array when it is fully operational. For redundant
arrays, the entire array is protected.
Glossary-6
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. 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).
RAID signature
The area on each disk reserved for use by the RAID controller.
RAID volume
Concatenates two or more arrays of the same type.
rebuild
Background regeneration of redundant data on a RAID 1.
reconfiguration
Process of expanding an array or migrating an array from one
RAID type to another; changing the stripe size of a RAID 0, or
moving a logical device’s partitions to other disks.
Glossary-7
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.
A disk can include RAID segments and available segments. A
RAID segment is part of a logical device; it can be used by only one
logical device at a time. Available segments can be used to define a
new logical device. If the disk is not part of any logical device, the
entire disk is an available segment.
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 partitions. See also volume, spanned
volume, RAID signature, and RAID 1 on page E-2.
spanned volume
A simple volume that spans two or more drives.
spare
See hotspare.
Glossary-8
Glossary
stripe
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.
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. Some tasks can take an extended period of time, particularly if
the RAID controller is also performing intensive data I/O while the
task is running.
V
verify
See consistency check command.
volume
See simple volume, spanned volume.
Glossary-9
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.