advertisement
Serial Attached SCSI RAID Controllers
Installation and User’s Guide
●
2
Copyright
©2009 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, Adaptec Storage Manager, Serial Select and the Adaptec logo are trademarks of Adaptec, Inc., which may be registered in some jurisdictions.
Microsoft, Windows, and Vista are trademarks of Microsoft Corporation in the US and other countries, used under license.
Red Hat is a trademark of Red Hat, Inc. 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.
●
3
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. If you need further assistance, use the support options listed below. To expedite your service, have your computer in front of you.
Technical Support Identification (TSID) Number
● Before contacting Technical Support, you need your product unique TSID number. The TSID number identifies your product and support status.
● The TSID number is included on a white, bar-coded label, like this example:
● Affix a copy of the TSID label to the CD jacket so that you don’t lose it. In addition, it's recommended that you register your product so that you have easy access to your TSID when contacting Customer Support.
Note: The phone numbers below are subject to change. Please visit the Support section of www.adaptec.com
for the most up to date contact information.
North America
● Visit our Web site at www.adaptec.com
.
●
●
Search the Adaptec Support Knowledgebase (ASK) at ask.adaptec.com
for articles, troubleshooting tips, and frequently asked questions for your product.
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, call +1 408-934-7274.
For support via e-mail, submit your question at ask.adaptec.com
.
●
● You can order Adaptec products, including accessories and cables, by calling +1 408-957-7274. Or, you can order cables online at www.adaptec.com/buy-cables .
Europe
● Visit our Web site at www.adaptec-europe.com
.
●
●
German: Call +49 89 43 66 55 22. For support via e-mail, submit your question at ask-de.adaptec.com
.
French: Call +49 89 43 66 55 33. For support via e-mail, submit your question at ask-fr.adaptec.com
.
● English: Call +49 89 43 66 55 44. For support via e-mail, submit your question 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
.
● Call +0044-2213-2601.
Australia
● Call +61-2-9503-1555.
●
4
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.
●
5
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.
Adaptec, Inc.
Use only with the listed ITE:
Adaptec RAID 5085/Adaptec RAID 5405/Adaptec RAID 5445/
Adaptec RAID 5805/
Adaptec RAID 5405Z/Adaptec RAID 5805Z/Adaptec RAID 5445Z/
Adaptec RAID 51245/Adaptec RAID 51645/Adaptec RAID 52445/
Adaptec RAID 2045/Adaptec RAID 2405
Tested to Comply
With FCC Standards
FOR HOME OR OFFICE USE
European Union Compliance Statement
This Information Technology Equipment has been tested and found to comply with EMC Directive 89/336/EEC, as amended by 92/31/EEC and 93/68/EEC, in accordance with:
● EN55022 (1998+A1:2000+A2:2003) Emissions
● EN55024 (1998+A1:2001+A2:2003) Immunity:
– EN61000-4-2 (1995) Electrostatic discharge: ±4 kV contact, ±8 kV air
– EN61000-4-3 (1996) Radiated immunity
– EN61000-4-4 (1995) Electrical fast transients/burst: ±1 kV AC, ±0.5 kV I/O
– EN61000-4-5 (1995) Surges ±1 kV differential mode, ±2 kV common mode
– EN61000-4-6 (1996) Conducted immunity: 3 V
– EN61000-4-11 (1994) Supply dips and variation: 30% and 100%
In addition, all equipment requiring U.L. listing has been found to comply with EMC Directive 73/23/EEC as amended by 93/68/EEC in accordance with EN60950 with amendments A1, A2, A3, A4, A11.
Australian/New Zealand Compliance Statement
This device has been tested and found to comply with the limits for a Class B digital device, pursuant to the Australian/New Zealand standard
AS/NZS 3548 set out by the Spectrum Management Agency.
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.
Japanese Compliance (Voluntary Control Council Initiative)
This equipment complies to class B Information Technology equipment based on VCCI (Voluntary Control Council for Interface). This equipment is designed for home use but it may causes radio frequency interference problem if used too near to a television or radio. Please handle it correctly per this documentation.
!
Caution: Risk of explosion if the battery is replaced by an incorrect type. Dispose of used batteries according to the instructions.
Contents
About This Guide
What You Need to Know Before You Begin ................................................... 11
Kit Contents and System Requirements
About Your RAID Controller
Advanced Data Protection Suite ................................................................ 16
Contents ●
7
Getting Started
Installing with an Operating System.......................................................... 34
Installing on an Existing Operating System .............................................. 34
Installing the Controller and Disk Drives
Installing a RAID Controller with Zero Maintenance Cache Protection 37
Connecting Disk Drives to Your Controllers .................................................. 38
Connecting Directly to the Controller....................................................... 38
Connecting to a System Backplane ............................................................ 39
Creating a Bootable Array
Creating an Array with the ACU ............................................................... 42
Creating an Array with Adaptec Storage Manager ................................... 44
Installing the Driver and an Operating System
Installing with Windows Server 2003 or Windows XP............................. 48
Installing with Windows Server 2008 or Windows Vista ......................... 48
Contents ●
8
Installing the Driver on an Existing Operating System
Installing on Windows Server 2003 or Windows XP................................ 54
Installing with Windows Server 2008 or Windows Vista ......................... 54
Managing Your Storage Space
Installing Adaptec Storage Manager .......................................................... 58
About the Adaptec RAID Controller Configuration Utility........................... 58
About the Adaptec RAID Configuration Utility ............................................. 59
Solving Problems
Failed Disk Drive Protected by a Hot Spare .............................................. 62
Not
Protected by a Hot Spare ....................................... 62
Failure in Multiple Arrays Simultaneously................................................ 62
Disk Drive Failure in a RAID 0 Array........................................................ 63
Multiple Failures in the Same Array .......................................................... 63
Introduction to SAS
How Do SAS Devices Communicate?.............................................................. 67
How are Disk Drives Identified in SAS? .......................................................... 69
What are the SAS Connection Options?.......................................................... 69
Contents ●
9
SAS Expander Connections........................................................................ 70
How is SAS Different from Parallel SCSI? ....................................................... 71
Understanding RAID
Using the Adaptec RAID Configuration Utility
Using the ACU to Create and Manage Arrays................................................. 82
Managing Global Hot Spares ..................................................................... 85
Using the ACU to Create and Manage JBODs ................................................ 85
Managing Existing JBODs.......................................................................... 86
Select
to Modify Controller Settings............................................. 86
Select
.................................................................................... 86
Applying Changes and Exiting................................................................... 86
Modifying Your Controller’s Configuration............................................. 86
Formatting and Verifying Disk Drives............................................................. 88
Using the Array Configuration Utility for DOS
Working in the ACU Using Menus.................................................................. 92
Contents ●
10
Creating the Script File Manually .............................................................. 94
Array Definition Block Keywords.............................................................. 95
Using the Adaptec Flash Utility
Creating the Firmware Update Disks ...................................................... 103
Running the AFU from the Command Line ................................................. 104
Updating the Flash Using the AFU Command Line..................................... 107
Controller LED and I2C Connector Quick Reference
Adaptec RAID 5085 LED Connector Specification....................................... 109
Adaptec RAID 5405/5405Z LED and I2C Connector Specification ............ 111
Adaptec RAID 5445/5445Z LED and I2C Connector Specification ............ 112
Adaptec RAID 5805/5805Z LED and I2C Connector Specification ............ 114
Adaptec RAID 51245 LED and I2C Connector Specification ...................... 116
Adaptec RAID 51645 LED and I2C Connector Specification ...................... 118
Adaptec RAID 52445 LED and I2C Connector Specification ...................... 120
Adaptec RAID 2045 LED Connector Specification....................................... 123
Adaptec RAID 2405 LED and I2C Connector Specification ........................ 123
Safety Information
Technical Specifications
Index
About This Guide
1
In this chapter...
This Installation and User’s Guide explains how to install your Adaptec
®
RAID controller. It also describes the utilities included in your controller kit, and provides a basic overview of
Serial Attached SCSI (SAS) and Redundant Array of Independent Disk (RAID) technology.
These RAID controller models are described in this Guide :
● Adaptec RAID 5085
●
●
●
Adaptec RAID 5405/5405Z
Adaptec RAID 5445/5445Z
Adaptec RAID 5805/5805Z
●
●
●
●
●
Adaptec RAID 51245
Adaptec RAID 51645
Adaptec RAID 52445
Adaptec RAID 2045
Adaptec RAID 2405
What You Need to Know Before You Begin
You should be familiar with computer hardware, data storage, RAID technology, and SAS and
Serial ATA (SATA) technology. (For an introduction to SAS, see page 65
.)
Chapter 1: About This Guide ●
12
You should also be familiar with Direct-Attached Storage (DAS) or Network-Attached Storage
(NAS)—whichever is appropriate for your storage space—and Storage Area Network (SAN) concepts and technology.
Note: Because this Guide covers multiple Adaptec RAID products, some of the features and
functions described may not be available for your controller. For more information, see About
Your RAID Controller on page 15
.
Terminology Used in this Guide
Because you can use your Adaptec RAID controller to manage data storage in a variety of configurations from DAS to NAS to SAN, the generic term “storage space” is used to refer to controller(s) and disk drives being managed with Adaptec Storage Manager TM or the other utilities described in this Guide .
Many of the terms and concepts referred to in this Guide are known to computer users by multiple names. This Guide uses these terms:
●
●
Controller (also known as adapter, board, or card)
Disk drive (also known as hard disk, hard drive, or hard disk drive)
●
●
Enclosure (also known as a RAID enclosure, storage enclosure, or JBOD enclosure)
Array (also known as a container or logical drive)
Note: In DAS environments, Adaptec Storage Manager refers to arrays as logical drives.
Why? Your RAID controller creates arrays , which your operating system (and Adaptec
Storage Manager) recognizes as logical drives .
In NAS environments, Adaptec Storage Manager displays both arrays and logical drives. For more information, refer to the Adaptec Storage Manager User’s Guide on the Adaptec
Storage Manager Installation CD.
How to Find More Information
You can find more information about your Adaptec RAID controller and the software and utilities included with it by referring to these documents:
●
●
●
●
Readme.txt
—Includes updated product information and known issues; located on the
RAID Installation CD.
Adaptec Storage Manager User’s Guide —Describes how to install and use the Adaptec
Storage Manager software (see page 58 ) to manage your direct attached storage; located on
the Adaptec Storage Manager Installation CD.
Adaptec Storage Manager Online Help —Describes how to use the Adaptec Storage Manager software; accessible from the main window of Adaptec Storage Manager.
Adaptec RAID Controller Command Line Utility User’s Guide —Describes how to use the included Adaptec RAID Controller Configuration (ARCCONF) command line utility (see
page 58 ) to perform basic array and configuration management functions; located on the
Adaptec Storage Manager Installation CD.
Kit Contents and System
Requirements
2
In this chapter...
This chapter lists the contents of your Adaptec RAID controller kit and the system requirements that must be met for you to successfully install and use your controller.
Chapter 2: Kit Contents and System Requirements ●
14
Kit Contents
● Adaptec RAID controller
●
●
●
●
●
RAID Installation CD (bootable), including controller drivers, and this Guide
Adaptec Storage Manager Installation CD (not bootable), including user guides for
Adaptec Storage Manager and the ARCCONF command line utility
Cables (Not all kits contain cables. If your kit does, the type and quantity vary—for cable information about your controller, visit the Adaptec Web site at www.adaptec.com
.)
( Selected models only ) Low-profile bracket
Adaptec Serial Attached SCSI RAID Controllers Quick Start Guide
System Requirements
● PC-compatible computer with Intel Pentium, or equivalent, processor
● Motherboard with these features:
●
●
Support for multifunction devices where one of the devices is a PCI bridge
Large memory-mapped address ranges
●
Refer to the Readme file on the RAID installation CD for additional motherboard compatibility information.
One of these operating systems:
●
●
Microsoft
®
Windows
®
Server 2008, Windows Vista TM (with SP1), Windows Server
2003 (Enterprise and Standard with SP1 or SP2, 32-bit and 64-bit), Windows XP (with
SP1, SP2, or SP3, 32-bit and 64-bit)
Red Hat
®
Enterprise Linux 4, Red Hat Enterprise Linux 5 (32-bit and 64-bit)
●
SUSE Linux ES 9.0 SP4, 10.0 SP2 (32-bit and 64-bit)
●
●
●
●
●
Note: For the latest on Adaptec’s support of Linux or to download driver sources, visit the Support area of the Adaptec Web site at www.adaptec.com
.
SCO
®
OpenServer
®
6.0
UnixWare
®
7.1.4
Sun
®
Solaris TM 10, Solaris 10 x86 U4, Solaris 10 x64 U4
VMware ESX Server 3.5 with U1, U2, or U3, VMware ESX Server 4.0 (storage management must be done by command-line, BIOS utility, or remote GUI
FreeBSD 6.3, 7.0
Note: For up-to-date operating system version support check the readme on your RAID
Installation CD or visit the Adaptec Web Site at www.adaptec.com
. From the main menu select Support>Knowledgebase>Find Answers. Select your controller type and OS support to generate a list of supported operating systems.
●
●
●
●
●
128 MB (or more) of RAM
Available compatible PCIe slot (depending on your controller model—see the descriptions starting on
)
20 MB of free disk drive space
16-bit SVGA color monitor with a resolution of at least 800 x 600
CD drive
About Your RAID Controller
3
In this chapter...
This chapter provides an overview of standard Adaptec RAID controller features, and describes the unique features of your controller.
Chapter 3: About Your RAID Controller ●
16
Standard RAID Controller Features
● Support for SAS, SATA, and SATA II disk drives
●
●
●
●
●
●
●
●
●
●
Flash ROM for updates to controller firmware, BIOS, and the Adaptec RAID
Configuration utility
Disk drive hot-swapping
Event logging and broadcasting including email and SNMP messages
Multiple options for creating and managing RAID arrays—A full software application
(Adaptec Storage Manager), a BIOS-based utility (ACU), a command line utility
(ARCCONF), and a DOS utility (see
Managing Your Storage Space on page 57 )
Native command queuing (NCQ), which lets disk drives arrange commands into the most efficient order for optimum performance
Support for disk drive enclosures with SES2 enclosure management hardware
Support for a battery backup module (see page 17
)
Support for a zero maintenance cache protection module (see page 36
)
Audible alarm
Power-management of disk drives in your storage space to reduce cooling and electricity
)
I/O statistics logging and automatic forwarding for remote analysis (“call home”) ●
Array-level Features
Note: Not all features are supported by all controllers. For more information, refer to the Adaptec
Storage Manager User’s Guide or online Help.
●
●
●
●
●
●
Support for RAID 0, RAID 1, RAID 5, RAID 10, RAID 50, simple volumes, and spanned volumes
Support for JBOD disks (appear as a physical disk drives to the operating system; not redundant)
Support for hot spares (global and dedicated)
Support for automatic failover, so arrays are automatically rebuilt when a failed disk drive is replaced (applies to redundant arrays in SES2- or SAF-TE-enabled disk drive enclosures only )
Optimized disk utilization, which ensures that the full capacity of all disk drives can be used, even if the disk drives vary in size
Online capacity expansion, so you can increase the capacity of an array without recreating it
Support for array migration from one RAID level to another ●
Advanced Data Protection Suite
Note: The following features are supported by Adaptec 5-Series controllers only.
● Copyback Hot Spare —You can use this feature to move data from a hot spare back to its original location after a failed disk drive is replaced.
Chapter 3: About Your RAID Controller ●
17
●
●
●
●
Striped Mirror (RAID 1E) —A RAID 1 Enhanced array is similar to a RAID 1 array except that data is both mirrored and striped, and more disk drives can be included.
Hot Space (RAID 5EE) —A RAID 5EE array is similar to a RAID 5 array except that it includes a distributed spare and must be built from a minimum of four disk drives.
Dual Drive Failure Protection (RAID 6) —A RAID 6 array is similar to a RAID 5 array except that it includes two independent sets of parity data instead of one.
Dual Drive Failure Protection (RAID 60) —A RAID 60 array is similar to a RAID 50 array except that it includes four independent sets of parity data instead of two.
Adding a Battery Backup Module
This table shows the battery model supported by your Adaptec RAID controller.
RAID Controller
Adaptec RAID 5085/Adaptec RAID 5405/Adaptec RAID
5445/Adaptec RAID 5805/
Adaptec 51245/Adaptec 51645/Adaptec 52445
Battery Model
Adaptec Battery Module 800
Adaptec Battery Module 800T
To purchase a battery backup module, refer to the Adaptec Web site at www.adaptec.com
.
Upgrading the Controller Firmware
To upgrade the firmware on your Adaptec RAID controller, follow the instructions in Using the
Adaptec Flash Utility on page 101 . You can also use the Adaptec Storage Manager to upgrade
your controller firmware, refer to the Adaptec Storage Manager User’s Guide.
Chapter 3: About Your RAID Controller ●
18
About the Adaptec RAID 5085
The Adaptec RAID 5085 is a SAS RAID controller with these features:
Ext. Alarm
Aggregate Activity
Mode 0 Flash connector
Activity
LEDs
Diagnostic
LEDs
Audible Alarm
Drive Activity LED connectors for CN1/CN0
CN0
CN1
2 external SAS connectors
Mounting bracket
PCIe x8 connector
Battery connector
Form Factor
Bus compatibility
PCIe bus width
PCIe bus speed
Phys (Unified Serial Ports)
Standard cache
Connectors, external
Maximum number of disk drives
Enclosure Support
Onboard speaker
Battery Backup Module
Low-profile MD2
PCIe x8
2.5 Gb/s
8
512 MB DDR2
2 mini-SAS x4 (SFF-8088)
8 direct-attached (or up to 256 with expanders)
I2C and SGPIO (Serial General Purpose Output)
Yes
Adaptec Battery Module 800/800T (sold separately—see
Chapter 3: About Your RAID Controller ●
19
About the Adaptec RAID 5405
The Adaptec RAID 5405 is a SAS RAID controller with these features:
Drive Activity LED connectors for CN0/CN1
Drive Activity LEDs for CN0/CN1
Mode 0 Flash connector
Aggregate
Activity
Diagnostic LEDs
Internal mini-SAS connector CN0
Status CN0
PCIe x8 connector
Mounting bracket
Ext. Alarm connector
I2C connector for CN0
Battery connector
Form Factor
Bus compatibility
PCIe bus width
PCIe bus speed
Phys (Unified Serial Ports)
Standard cache
Connectors, internal
Maximum number of disk drives
Enclosure Support
Onboard speaker
Battery Backup Module
Low-profile MD2
PCIe x8
2.5 Gb/s
4
256 MB DDR2
1 mini-SAS x4 (SFF-8087)
4 direct-attached (or up to 256 with expanders)
I2C and SGPIO
Yes
Adaptec Battery Module 800/800T (sold separately—see
Chapter 3: About Your RAID Controller ●
20
About the Adaptec RAID 5445
The Adaptec RAID 5445 is a SAS RAID controller with these features:
Drive Activity CN1/CN0
Status CN1/CN0
Mode 0 Flash connector
Ext. Alarm
Diagnostic LEDs
(back of card)
Internal mini-SAS connector CN0
ABM-800 connector
External SAS connector CN1
Aggregate
Activity
Audible Alarm
I2C connector for CN0
PCIe x8 connector
Mounting bracket
Form Factor
Bus compatibility
PCIe bus width
PCIe bus speed
Phys (Unified Serial Ports)
Standard cache
Connectors
Maximum number of disk drives
Enclosure Support
Onboard speaker
Battery Backup Module
Low-profile MD2
PCIe x8
2.5 Gb/s
8
512 MB DDR2
1 mini-SAS x4 (SFF-8087) internal
1 mini-SAS x4 (SFF-8088) external
8 direct-attached (or up to 256 with expanders)
I2C and SGPIO
Yes
Adaptec Battery Module 800/800T (sold separately—see
Chapter 3: About Your RAID Controller ●
21
About the Adaptec RAID 5805
The Adaptec RAID 5805 is a SAS RAID controller with these features:
Drive Activity LED connectors for CN0/CN1
Drive Activity LEDs for CN0/CN1
Mode 0 Flash connector
Aggregate
Activity
Diagnostic LEDs
CN1
CN0
2 internal mini-SAS connectors
Status CN1, CN0
I2C connector for CN1
I2C connector for CN0
Battery connector
Mounting bracket
PCIe x8 connector
Ext. Alarm connector
Form Factor
Bus compatibility
PCIe bus width
PCIe bus speed
Phys (Unified Serial Ports)
Standard cache
Connectors, internal
Maximum number of disk drives
Enclosure Support
Onboard speaker
Battery Backup Module
Low-profile MD2
PCIe x8
2.5 Gb/s
8
512 MB DDR2
2 mini-SAS x4 (SFF-8087)
8 direct-attached (or up to 256 with expanders)
I2C and SGPIO
Yes
Adaptec Battery Module 800/800T (sold separately—see
Chapter 3: About Your RAID Controller ●
22
About the Adaptec RAID 51245
The Adaptec RAID 51245 is a SAS RAID controller with these features:
Mode 0 Flash
I2C, CN2 Activity CN2
I2C, CN1
I2C, CN0
Activity
CN0, CN1
CN6
1 external mini-SAS connector
CN0
CN1
CN2
3 internal mini-SAS connectors
Reserved
Ext. Alarm
Aggregate Activity
ABM-800 connector
Form Factor
Bus compatibility
PCIe bus width
PCIe bus speed
Phys (Unified Serial Ports)
Standard cache
Connectors, Internal
Connectors, Exteneral
Maximum number of disk drives
Enclosure Support
Onboard speaker
Battery Backup Module
Full Height, Half Length
PCIe x8
2.5 Gb/s
16
512 MB DDR2
3 mini-SAS x4 (SFF-8087)
1 mini-SAS x4 (SFF-8088)
16 direct-attached (or up to 256 with expanders)
I2C and SGPIO
Yes
Adaptec Battery Module 800/800T (sold separately—see
Chapter 3: About Your RAID Controller ●
23
About the Adaptec RAID 51645
The Adaptec RAID 51645 is a SAS RAID controller with these features:
I2C, CN2
I2C, CN3
Mode 0 Flash
Activity CN2, CN3
I2C, CN1
I2C, CN0
Activity
CN0, CN1
CN6
1 external mini-SAS connector
CN0
CN1
CN2
4 internal mini-SAS connectors
CN3
ABM-800 connector
Reserved
Ext. Alarm
Aggregate Activity
Form Factor
Bus compatibility
PCIe bus width
PCIe bus speed
Phys (Unified Serial Ports)
Standard cache
Connectors, Internal
Connectors, Exteneral
Maximum number of disk drives
Enclosure Support
Onboard speaker
Battery Backup Module
Full Height, Half Length
PCIe x8
2.5 Gb/s
20
512 MB DDR2
4 mini-SAS x4 (SFF-8087)
1 mini-SAS x4 (SFF-8088)
20 direct-attached (or up to 256 with expanders)
I2C and SGPIO
Yes
Adaptec Battery Module 800/800T (sold separately—see
Chapter 3: About Your RAID Controller ●
24
About the Adaptec RAID 52445
The Adaptec RAID 52445 is a SAS RAID controller with these features:
I2C, CN2
I2C, CN3
I2C, CN4
I2C, CN5
Activity CN2, CN3
Mode 0 Flash connector
I2C, CN1
I2C, CN0
CN4 CN5
CN0
Activity
CN0, CN1
CN1
CN2
CN6
1 external mini-SAS connector
ABM-800 connector
CN3
6 internal mini-SAS connectors
Reserved
Ext. Alarm
Aggregate Activity
Activity CN4, CN5
Form Factor
Bus compatibility
PCIe bus width
PCIe bus speed
Phys (Unified Serial Ports)
Standard cache
Connectors, Internal
Connectors, Exteneral
Maximum number of disk drives
Enclosure Support
Onboard speaker
Battery Backup Module
Full Height, Half Length
PCIe x8
2.5 Gb/s
28
512 MB DDR2
6 mini-SAS x4 (SFF-8087)
1 mini-SAS x4 (SFF-8088)
28 direct-attached (or up to 256 with expanders)
I2C and SGPIO
Yes
Adaptec Battery Module 800/800T (sold separately—see
Chapter 3: About Your RAID Controller ●
25
About the Adaptec RAID 5405Z
The Adaptec RAID 5405Z is a SAS RAID controller with these features:
Drive Activity LED connectors for CN0
Drive Activity LEDs for CN0
I2C connector for CN0
Ext. Alarm connector
Aggregate Activity
Mode 0 Flash connector
Diagnostic LEDs
Internal mini-SAS connector CN0
Mounting bracket
PCIe x8 connector
ZMM-100CC Cap
Card connector
ZMM-100DB
Daughterboard
Form Factor
Bus compatibility
PCIe bus width
PCIe bus speed
Phys (Unified Serial Ports)
Standard cache
Connectors, internal
Maximum number of disk drives
Enclosure Support
Onboard speaker
Zero Maintenance Cache
Protection Module
Low-profile MD2
PCIe x8
2.5 Gb/s
4
512 MB DDR2
1 mini-SAS x4 (SFF-8087)
4 direct-attached (or up to 256 with expanders)
I2C and SGPIO
Yes
Adaptec ZMM-100DB daughterboard (pre-installed),
Adaptec ZMM-100CC super cap card (user installed—see
Chapter 3: About Your RAID Controller ●
26
About the Adaptec RAID 5445Z
The Adaptec RAID 5445Z is a SAS RAID controller with these features:
Drive Activity LED connectors for CN0/CN1
Drive Activity LEDs for CN0/CN1
I2C connectors for CN0/CN1
Ext. Alarm connector
Aggregate Activity
Mode 0 Flash connector
Diagnostic LEDs
Internal mini-SAS connector CN0
CN1
1 external mini-SAS connector
Mounting bracket
PCIe x8 connector
ZMM-100CC Cap
Card connector
ZMM-100DB
Daughterboard
Form Factor
Bus compatibility
PCIe bus width
PCIe bus speed
Phys (Unified Serial Ports)
Standard cache
Connectors
Maximum number of disk drives
Enclosure Support
Onboard speaker
Zero Maintenance Cache
Protection Module
Low-profile MD2
PCIe x8
2.5 Gb/s
8
512 MB DDR2
1 mini-SAS x4 (SFF-8087) internal
1 mini-SAS x4 (SFF-8088) external
8 direct-attached (or up to 256 with expanders)
I2C and SGPIO
Yes
Adaptec ZMM-100DB daughterboard (pre-installed),
Adaptec ZMM-100CC super cap card (user installed—see
Chapter 3: About Your RAID Controller ●
27
About the Adaptec RAID 5805Z
The Adaptec RAID 5805Z is a SAS RAID controller with these features:
Drive Activity LED connectors for CN0/CN1
Drive Activity LEDs for CN0/CN1
I2C connectors for CN0/CN1
Ext. Alarm connector
Aggregate Activity
Mode 0 Flash connector
Diagnostic LEDs
CN1
CN0
2 internal mini-SAS connectors
Mounting bracket
PCIe x8 connector
ZMM-100CC Cap
Card connector
ZMM-100DB
Daughterboard
Form Factor
Bus compatibility
PCIe bus width
PCIe bus speed
Phys (Unified Serial Ports)
Standard cache
Connectors, internal
Maximum number of disk drives
Enclosure Support
Onboard speaker
Zero Maintenance Cache
Protection Module
Low-profile MD2
PCIe x8
2.5 Gb/s
8
512 MB DDR2
2 mini-SAS x4 (SFF-8087)
8 direct-attached (or up to 256 with expanders)
I2C and SGPIO
Yes
Adaptec ZMM-100DB daughterboard (pre-installed),
Adaptec ZMM-100CC super cap card (user installed—see
Chapter 3: About Your RAID Controller ●
28
About the Adaptec RAID 2045
The Adaptec RAID 2045 is a SAS RAID controller with these features:
Aggregate Activity
Mode 0 Flash connector
CN1
1 external mini-
SAS connector
PCIe x8 connector
Mounting bracket
Form Factor
Bus compatibility
PCIe bus width
PCIe bus speed
Phys (Unified Serial Ports)
Standard cache
Connectors, external
Maximum number of disk drives
Enclosure Support
Onboard speaker
Battery Backup Module
Low-profile MD2
PCIe x8
2.5 Gb/s
4
128 MB DDR2
1 mini-SAS x4 (SFF-8088)
4 direct-attached (or up to 128 with expanders)
I2C and SGPIO
No
No
Chapter 3: About Your RAID Controller ●
29
About the Adaptec RAID 2405
The Adaptec RAID 2405 is a SAS RAID controller with these features:
Activity connector for CN0
Aggregate Activity
Mode 0 Flash connector
Internal mini-SAS connector CN0
Mounting bracket
I2C, CN0
PCIe x8 connector
Form Factor
Bus compatibility
PCIe bus width
PCIe bus speed
Phys (Unified Serial Ports)
Standard cache
Connectors, internal
Maximum number of disk drives
Enclosure Support
Onboard speaker
Battery Backup Module
Low-profile MD2
PCIe x8
2.5 Gb/s
4
128 MB DDR2
1 mini-SAS x4 (SFF-8087)
4 direct-attached (or up to 128 with expanders)
I2C and SGPIO
No
No
Getting Started
4
In this chapter...
This chapter provides the basic information you need to set up your disk drives and arrays the way you want them. It also describes the options you have for installing your Adaptec controller and disk drives, and creating arrays for data storage.
Chapter 4: Getting Started ●
31
Choosing a RAID Level
This section provides a brief overview of the RAID levels supported by your Adaptec RAID controller, including the minimum and maximum number of disk drives required by each.
Note: Before you begin, familiarize yourself with your Adaptec controller’s physical features
and the RAID levels that it supports (see Standard RAID Controller Features on page 16
).
●
●
●
●
RAID 0 (Non-redundant Array) —Stripes data across multiple disk drives. Improved performance but no redundancy (see
RAID 1 Array —Created from two disk drives where one disk drive is a mirror of the other
(the same data is stored on each disk drive). Redundancy, but reduced capacity (see
).
RAID 1E Array —Similar to a RAID 1 array except that data is mirrored and striped, and more
disk drives can be included (see page 74
).
RAID 5 Array —Stripes data for improved performance and uses parity data to provide redundancy (see
●
●
RAID 5EE Array —Similar to a RAID 5 array, but includes a distributed spare and must
include a minimum of four disk drives (see page 77
).
RAID 10 Array —Built from two or more equal-sized RAID 1 arrays, stripes and mirrors data across multiple disk drives. Redundancy and improved performance (see
●
●
●
RAID 50 Array —Built from multiple disk drives configured as two or more RAID 5
arrays, stripes stored data and parity data across all disk drives (see page 78
).
RAID 6 Array —Similar to a RAID 5 array except that it includes two independent sets of parity data instead of one (see
RAID 60 Array —Similar to a RAID 50 array except that it includes four independent sets of parity data instead of two (see
to see how many disk drives you must connect to your RAID controller to support the RAID level you want.
Chapter 4: Getting Started ●
32
Selecting Disk Drives and Cables
Disk Drives
Your SAS controller supports both SAS and SATA disk drives. When selecting disk drives for your
RAID array, ensure that all the disk drives have the same performance level. You can use different-sized disk drives in the array, but the array will be limited to the capacity of the smallest and slowest disk drive. For more information about arrays, refer to the Adaptec Storage Manager
User’s Guide or online Help. For more information about compatible disk drives, refer to the
Adaptec Web site at www.adaptec.com/compatibility .
Cables
Depending on your requirements, you can use any of these cables:
External mini-SAS (SFF-8088 to SFF-8470)—Connects to an external SAS enclosure.
Internal mini-SAS with power (SFF-8087 to SFF-8482)—Connects to four SAS or SATA disk drives.
Chapter 4: Getting Started ●
33
Internal mini-SAS to SATA fan-out (SFF-8087 to 4x SATA)—Connects to four SATA disk drives.
External mini-SAS to mini-SAS (SFF-8088 to SFF-8088)—
Connects to a backplane or enclosure.
Internal mini-SAS to mini-SAS (SFF-8087 to SFF-8087)—
Connects to a backplane or enclosure.
Cable connectors are keyed so that you can’t insert them incorrectly.
Adaptec recommends using only Adaptec SAS cables. For more information or to purchase cables, visit the Adaptec Web site at www.adaptec.com
.
Installation Options
When you install your Adaptec controller, you can choose to create a bootable array and then install your operating system and the controller driver on that array.
Alternatively, you can complete a standard installation, where the controller driver is installed on an existing operating system.
Chapter 4: Getting Started ●
34
Basic Installation Steps
This section describes the installation process. Follow the steps for the installation option you’ve chosen.
Installing with an Operating System
1 Install and connect your controller and internal disk drives (see
2
3
4
5
If your controller has an external connector, you can connect external disk drives as well
(or instead).
Set the boot controller (see page 42
).
Create a bootable array (see
Install your operating system and the controller driver (see page 46
.)
Install Adaptec Storage Manager and begin to manage your data storage (see page 57
).
Installing on an Existing Operating System
1 Install and connect your controller and internal disk drives (see
2
3
If your controller has an external connector, you can connect external disk drives as well
(or instead).
Install the controller driver (see
Install Adaptec Storage Manager and begin to manage your data storage (see page 57
).
Installing the Controller and Disk
Drives
5
In this chapter...
This chapter explains how to install your Adaptec RAID controller, and how to install and connect internal and external disk drives.
Chapter 5: Installing the Controller and Disk Drives ●
36
Before You Begin
●
Read Safety Information on page 125 .
●
●
●
●
Familiarize yourself with your Adaptec RAID controller’s physical features and the RAID levels that it supports (see
Ensure you have the right quantity of disk drives for the RAID level you want to use for
).
Ensure that you have the proper cables for your controller and disk drives (see
If you are installing a low-profile RAID controller into a low-profile computer cabinet, replace the original full-height bracket with the low-profile bracket included in the kit.
Caution: Handle the controller by its bracket or edges only.
!
Installing the Controller
This section describes how to install your Adaptec RAID controller into your computer cabinet.
Adaptec RAID controllers come in two basic configurations: standard and zero maintenance cache protection with batteryless backup. Follow one of these sets of instructions:
●
●
To install a standard series Adaptec RAID controller (without zero maintenance cache protection), see the following section.
To install an Adaptec RAID controller with zero maintenance cache protection, see page 37
.
Installing a RAID Controller
1 Turn off your computer and disconnect the power cord. Open the cabinet, following the manufacturer’s instructions.
2 Select an available PCIe expansion slot that’s compatible with your RAID controller and remove the slot cover, as shown at right. (PCIe bus compatibility is marked to the controller figures in
About Your RAID Controller on page 15 .)
!
Caution: Touch a grounded metal object before handling the RAID controller.
3
4
5
As shown at right, insert the RAID controller into the expansion slot and press down gently but firmly until it clicks into place.
When installed properly, the RAID controller should appear level with the expansion slot.
Secure the bracket in the expansion slot, using the retention device
(for instance, a screw or lever) supplied with your computer.
Connect your computer’s disk activity LED cable to the LED
connector on the controller (marked on the figures in About
Your RAID Controller on page 15
).
Ensure that the positive lead of the LED cable (usually a red wire or a wire marked with a red stripe) is attached to pin 1.
Chapter 5: Installing the Controller and Disk Drives ●
37
6
7
Optional —Connect your RAID controller’s I2C connector (not available on all models) to an I2C connector on an internal backplane or enclosure, using an I2C cable. For more
connection details, see About Your RAID Controller on page 15
.
Prepare and install your internal disk drives, following the instructions in
Drives to Your Controllers on page 38 .
If you are not installing internal disk drives, close your computer cabinet, reattach the
power cord, then continue with Connecting External Devices on page 40 .
Installing a RAID Controller with Zero Maintenance Cache Protection
Warning: Do not attempt to connect a Battery Backup Module (see
) to an
Adaptec RAID controller with Zero Maintenance Cache Protection. The battery module can overheat and may even explode!
1
2
Turn off your computer and disconnect the power cord. Open the cabinet, following the manufacturer’s instructions.
Select an available PCIe expansion slot that’s compatible with your RAID controller and remove the slot cover, as shown at right. (PCIe bus compatibility is marked to the controller figures in
About Your RAID Controller on page 15 .)
!
Caution: Touch a grounded metal object before handling the RAID controller.
3
4
As shown at right, insert the RAID controller into the expansion slot and press down gently but firmly until it clicks into place. When installed properly, the RAID controller should appear level with the expansion slot.
Secure the bracket in the expansion slot, using the retention device (for instance, a screw or lever) supplied with your computer.
5
6
Attach the zero maintenance module (ZMM) to the
RAID controller by inserting the connector into the socket on the ZMM daughter-board, as shown at right.
The connector attaches to the socket in only one direction.
Choose a location on the chassis or in the system to fix the tethered ZMM using the included tie-backs such that (i) the cable (18.5") reaches the mating location on the RAID controller when the controller is installed in the expansion slot; (ii) wiring is routed and secured so that it does not contact any moving parts (fans, for instance); and (iii) the ZMM is protected from excessive heat.
Chapter 5: Installing the Controller and Disk Drives ●
38
7
8
Thread the tie-backs through the slots on the
ZMM and fix to the selected location on the computer chassis. The tie-backs should completely encircle the ZMM to ensure that it is held in place securely, as shown at right. Be careful not to restrict air-flow through your system.
Connect your computer’s disk activity LED
cable to the LED connector on the controller (marked on the figures in About Your RAID
).
Ensure that the positive lead of the LED cable (usually a red wire or a wire marked with a red stripe) is attached to pin 1.
9 Connect your RAID controller’s I2C connector to an I2C connector on an internal backplane or enclosure, using an I2C cable. For more connection details, see
.
10 Prepare and install your internal disk drives, following the instructions in
Drives to Your Controllers on page 38 .
If you are not installing internal disk drives, close your computer cabinet, reattach the
power cord, then continue with Connecting External Devices on page 40 .
Connecting Disk Drives to Your Controllers
You can connect SAS disk drives, SATA disk drives, or a combination of both to your SAS RAID controller. (See www.adaptec.com/compatibility for a list of compatible disk drives.) There are no jumpers or switches to set before installation.
If you plan to build a bootable array using internal disk drives, ensure you install at least the
minimum number disk drives required to support the RAID level you want. See page 31
for more information.
Note: Although you can connect both SAS and SATA disk drives to your SAS controller, Adaptec recommends that you not combine SAS and SATA disk drives within the same array or logical
for more information.
You have two connection options:
● To connect directly to the controller, see the following section.
●
To connect to a backplane, see page 39
.
Connecting Directly to the Controller
In a direct-attach connection, SAS or SATA disk drives are connected directly to a SAS card with SAS cables.The number of direct-attached disk drives is limited to four per internal SAS
connector. (For more information about direct-attach connections, see page 69 .)
1 Install your internal SAS or SATA disk drives, following the instructions in your system’s documentation.
Chapter 5: Installing the Controller and Disk Drives ●
39
2 Use internal SAS or mini-SAS cables to attach the disk drives to the controller, as shown in the following example.
SAS/SATA disk drives internal x4 mini-SAS connectors mini-SAS to SATA fan-out cable
Single-port connector
Note: SAS fan-out cables are also available with an additional sideband (SFF-8448) cable that caries SGPIO signals for enclosure management. This additional sideband cable is not used with direct-attached disk drives.
3 When all internal disk drives have been installed and attached to the controller, close your
computer cabinet, reattach the power cord, then continue with Connecting External
Connecting to a System Backplane
In a backplane connection, disk drives and SAS cards are attached to and communicate with each other through a system backplane.
The number of disk drives is limited to the number of slots available on the backplane. Some backplanes have embedded SAS expanders and can support up to 128 end devices. (For more
information about backplane and expander connections, see page 69
.)
1
2
Connect one or more internal SAS or SATA disk drives to the backplane. (Refer to your system’s documentation for more information.)
Use an internal SAS cable to connect the controller to the backplane, as shown in the
Chapter 5: Installing the Controller and Disk Drives ●
40
Disk drives on backplane
Controller connected to backplane with Internal mini-SAS to mini-SAS
(SFF-8087 to SFF-8087)
Disk drives on backplane
External SAS cable connecting to a drive bay
Controller connected to backplane with multi-lane cable (SFF-8484)
3 When all internal disk drives have been installed and connected, close your computer
cabinet, reattach the power cord, then continue with Connecting External Devices on page 40
.
Connecting External Devices
Note: If you are not connecting any external devices, see the following section,
Use high-quality cables to connect your controller to your external device(s), such as disk drives or disk drive enclosures.
Adaptec recommends using only Adaptec cables. For more information or to purchase cables, visit the Adaptec Web site at www.adaptec.com
.
Next Steps
If you are installing the controller driver and an operating system onto a bootable array, continue with
Creating a Bootable Array on page 41
.
If you are completing a standard installation onto an existing operating system, continue with
Installing the Driver on an Existing Operating System on page 52
.
Creating a Bootable Array
6
In this chapter...
This chapter explains how to set your Adaptec controller to be the boot controller, and how to create a bootable array.
Note: If you are completing a standard installation onto an existing operating system, you
Chapter 6: Creating a Bootable Array ●
42
Setting the Boot Controller
Note: If your system won’t contain more than one bootable controller, skip to the next section,
.
Your Adaptec RAID controller supports bootable disk drives and bootable arrays. To enable your system to boot from either a disk drive or an array connected to your controller:
1
2
3
Enter the system setup.
Navigate to the drive boot sequence.
Move the boot controller to the top of the list.
For more information, refer to your computer documentation.
Creating an Array
This section explains how to create an array.
A RAID 5 array is created in the examples shown in this section because RAID 5 provides the most security and best performance with a minimum of three disk drives. However, you can choose to create an array with a different RAID level; you can also change array level later, after the operating system is installed.
You can create an array using any of these tools:
●
●
Array Configuration Utility (ACU) —BIOS-based menus and keyboard navigation (see the following section).
Adaptec Storage Manager —Graphical software application (running from a bootable
RAID installation CD) that you can navigate with your mouse (see page 58
).
● ARCCONF —Command line utility. For instructions, refer to the Adaptec RAID Controller
Command Line Utility User’s Guide.
You can use either tool, but the ACU utility is the quicker and easier tool for this task.
Note: Adaptec recommends that you not combine SAS and SATA disk drives within the same array. Adaptec Storage Manager generates a warning if you try to create a logical drive using a
combination of SAS and SATA disk drives. See page 66 for more information.
Creating an Array with the ACU
The ACU is menu-based and instructions for completing tasks appear on-screen. Menus can be navigated using the arrows, Enter, Esc, and other keys on your keyboard.
To create a RAID 5 array:
1 Power on your computer. When prompted, press Ctrl+A to enter the ARC utility.
Note: During boot up, if your system has insufficient memory the following message will display. “Adaptec RAID Configuration Utility will load after, system initialization. Please wait...
Or press <Enter> Key to attempt loading the utility forcibly [Generally, not recommended]”
2
3
If you have more than one controller of the same model or family in your computer, select your controller, then press Enter .
Select Array Configuration Utility , then press Enter .
Chapter 6: Creating a Bootable Array ●
43
4
5
7
8
6
9
Select Initialize Drives , then press Enter .
Select at least three disk drives for the array, press Insert for each selected disk drive, then press Enter .
!
Caution: During initialization, all data is deleted from the disk. Before continuing, back up any data you want to keep.
Press Y , then press Enter .
The selected disk drives are initialized, then the ACU screen appears.
Select Create Array , then press Enter .
Select the disk drives that were just initialized, press Insert for each selected disk drive, then press Enter .
When the Array Properties screen opens, follow the instructions in the following table.
Property Line
Array Type
Array Label
Array Size
Stripe Size
Read Caching
Entry or Selection
Select RAID 5 , then press Enter .
Type a name, then press Enter .
Press Enter , then press Enter again to use the default granularity of GB.
Press Enter to use the default (256 KB).
Press Enter to use the default (Yes).
Write Caching Press Enter to use the default (Enable always).
Create RAID via Press Enter to use the default (Build/Verify).
[Done] Press Enter .
10 When a cache warning message displays, type Y .
11 Once the array is created, a message displays telling you that the array can now be used.
Press any key to return to the ACU Menu.
You can start using the array immediately. However, performance is reduced until the build process is complete.
12 Press Esc until the Exit utility window appears.
13 Select Yes , then press Enter .
The computer restarts.
14 Continue with
Making Your Array Bootable on page 45
.
Chapter 6: Creating a Bootable Array ●
44
Creating an Array with Adaptec Storage Manager
This section describes how to use the Adaptec Storage Manager configuration wizard to build a
RAID 5 array.
Note: You will need the Adaptec Storage Manager Installation CD to complete this task.
To create a RAID 5 array:
1 Insert the Adaptec Storage Manager Installation CD into your CD drive, then restart your computer.
2
3
4
5
When prompted, select the language you want, then press Enter .
Review the license information, then press Enter .
The main menu opens.
Click Launch Configuration Utility .
Adaptec Storage Manager opens.
Click Create .
The Configuration wizard opens.
6 Select Express configuration...
, then click Next .
Chapter 6: Creating a Bootable Array ●
45
7 Review the information that is displayed.
Note: In DAS environments, Adaptec Storage Manager uses the term logical drives when referring to arrays
In this example, Adaptec Storage Manager has used thirteen equal-sized disk drives to automatically create one logical drive with RAID 5 and a hot spare.
8
To exclude specific disk drives from the logical drive, specify a size for the logical drive, or to make other changes to the configuration, click Modify logical devices .
Click Apply , then click Yes when prompted to confirm applying your new configuration.
Adaptec Storage Manager builds the logical drive.
The configuration is saved on the Adaptec controller (as an “array”, see page 12 ) and on the
physical disk drives.
9 Partition and format your logical drive.
The logical drive you created appears as a physical disk drive on your operating system.
You must partition and format these logical drives before you can use them to store data.
10 Close all windows, then click Reboot to restart your system.
11 Remove the Adaptec Storage Manager Installation CD.
For information on installing and using Adaptec Storage Manager as a full software application, refer to the Adaptec Storage Manager User’s Guide or online Help.
12 Continue with the following section.
Making Your Array Bootable
Use the ACU to make the array bootable (see
Creating Bootable Arrays on page 83
).
Then continue with Installing the Driver and an Operating System on page 46
.
Installing the Driver and an
Operating System
7
In this chapter...
This chapter explains how to install your Adaptec RAID controller driver and an operating
system onto a bootable array (see page 41
).
To install the driver on an existing operating system, see
.
Chapter 7: Installing the Driver and an Operating System ●
47
Before You Begin
●
Install and connect your Adaptec RAID controller and internal disk drives (see page 35
).
●
●
Create a bootable array (see
Create a driver disk (see the following section).
Note: For up-to-date operating system version support, visit the Adaptec Web Site at www.adaptec.com
. From the main menu select Support>Knowledgebase>Find Answers. Select your controller type and OS support to generate a list of supported operating systems and to download the latest drivers.
Creating a Driver Disk
Note: You will need a floppy disk to complete this task for all operating systems except
Windows Vista and Windows Server 2008.
To create a driver disk:
1 Set your system BIOS so that your computer boots from the CD drive. (For instructions, refer to your computer documentation.)
2 Turn on your computer, then insert the RAID Installation CD included in your RAID controller kit.
3
4
Follow the on-screen instructions to get to the Adaptec Start Menu.
Click Create Driver Disk(s) for Installing/Updating your OS , then select your operating system.
Note: Linux only— If prompted, select your operating system and then the version.
6
7
5 When prompted, insert a floppy disk, then click OK .
The system creates the driver disk.
Remove and label the driver disk.
Continue with the instructions for your operating system:
●
For Windows, see
●
●
For Red Hat Linux, see page 49
.
For SUSE Linux, see
●
●
●
●
●
.
.
For Solaris, see
For VMware, see
.
Installing with Windows
Note: You will need your Windows Installation CD to complete this task.
Chapter 7: Installing the Driver and an Operating System ●
48
Installing with Windows Server 2003 or Windows XP
To install the Adaptec RAID controller driver while installing Windows:
1
2
3
Insert your Windows CD, then restart the computer.
Follow the on-screen instructions to begin the Windows installation.
When prompted to install a third-party driver, press F6 .
Note: When F6 is active, a prompt appears at the bottom of the screen for only 5 seconds.
If you miss your chance to press F6, restart your computer.
4
5
6
7
8
Insert the driver disk, then wait until you are prompted to install a driver.
Press S to specify that the driver is on a floppy disk, then press Enter .
The computer reads the disk.
When the Adaptec driver is found, press Enter .
Follow the on-screen instructions to complete the installation.
Continue with
Managing Your Storage Space on page 57
.
Installing with Windows Server 2008 or Windows Vista
To install the Adaptec RAID controller driver while installing Windows:
1
2
3
4
5
6
7
8
Insert your Windows CD, then restart the computer.
Follow the on-screen instructions to begin the Windows installation.
When prompted to specify a location for Windows, select Load Driver .
Insert the Adaptec Installation CD, then click OK .
When the Adaptec driver is found, press Next .
Click Next again to accept the default partition configuration, or refer to your Windows documentation to configure partitions manually.
Follow the on-screen instructions to complete the installation.
Continue with
Managing Your Storage Space on page 57
.
Chapter 7: Installing the Driver and an Operating System ●
49
Installing with Red Hat Linux
Note: You will need your Red Hat Installation CD to complete this task.
To install the Adaptec RAID controller driver while installing Red Hat Linux:
1 Insert the first Red Hat Installation CD.
2
3
Restart your computer.
When the Red Hat Welcome screen appears, type linux dd at the Boot: prompt.
4
5
6
7
8
When prompted, insert the driver disk, then select OK .
Follow the prompts to set up the environment you want.
If you are installing other third-party devices, install them now. Otherwise, select Done .
Complete the Linux installation, following the instructions included with your operating system.
Continue with
Managing Your Storage Space on page 57
.
Installing with SUSE Linux
To install the Adaptec RAID controller driver while installing SUSE Linux:
1
2
3
4
5
6
7
8
Insert the first SUSE Installation CD.
Restart your computer.
When the SUSE installation selection screen appears, choose the type of installation you want, then press the F6 key to indicate the use of a driver disk. (If F6 is not shown on the screen, you may have an older version of SUSE; press the Alt key instead.)
When prompted, insert the driver disk, then press any key to continue.
Follow the prompts to set up the environment you want.
If you are installing other third-party devices, install them now. Otherwise, select Back .
Complete the Linux installation, following the instructions included with your operating system.
Continue with
Managing Your Storage Space on page 57
.
Installing with OpenServer
Note: You will need your OpenServer Installation CD to complete this task.
To install the driver when installing OpenServer:
1 Insert the OpenServer Installation CD.
2
3
4
Restart your computer.
Follow the on-screen instructions to begin the OpenServer installation.
When prompted to load more HBA drivers, insert the driver disk, then select Yes . (To load more HBA drivers, repeat this step.)
Chapter 7: Installing the Driver and an Operating System ●
50
5
6
7
When all drivers have loaded, select No .
Complete the OpenServer installation, following the instructions included with your operating system.
Continue with
Managing Your Storage Space on page 57
.
Installing with UnixWare
Note: You will need your UnixWare Installation CD to complete this task.
To install the driver when installing UnixWare:
1 Insert the UnixWare Installation CD.
2
3
Restart your computer.
Follow the on-screen instructions to begin the UnixWare installation.
4
5
6
7
When prompted to load more HBA drivers, insert the driver disk, then select Yes . (To load more HBA drivers, repeat this step.)
When all drivers have loaded, select No .
Complete the UnixWare installation, following the instructions included with your operating system.
Continue with
Managing Your Storage Space on page 57
.
Installing with Solaris
Note: This task is not necessary if you are installing Solaris 10 Update 2 or later. Instead, you can choose to install Solaris using the in-box driver and update it either during or after the installation is complete, if required. You will need a floppy disk to complete this task.
To create a driver disk:
1 Start your computer.
2 Interrupt the autoboot, press the ESC key. The Device Configuration Assistant (DCA)
Utility will open.
3
4
5
Select F4_Add Driver .
Insert a floppy disk.
Complete the Solaris installation, following the instructions included with your operating system.
Chapter 7: Installing the Driver and an Operating System ●
51
Installing with VMware
Note: You will need your VMware Installation CD to complete this task.
To install the driver when installing VMware:
1 Insert the VMware Installation CD.
2
3
Restart your computer.
Follow the on-screen instructions to begin the VMware installation.
Note: The VMware embedded driver will see the device and install.
4 Complete the VMware installation, following the instructions included with your operating system.
Note: Currently, the Adaptec Storage Manager GUI is not supported on VMware. To create and manage arrays, you must connect to the VMware machine from a remote GUI or use the
ARCCONF
utility. See page 59 for more information.
Installing with FreeBSD
Note: You will need your FreeBSD Installation CD to complete this task.
To install the driver when installing FreeBSD:
1 Insert the FreeBSD Installation CD.
2
3
Restart your computer.
When the FreeBSD start screen opens, select 6 to escape to loader prompt.
4
5
6
Type load kernel
.
Insert the driver floppy disk.
Type load disk0:aacu.ko
.
If the driver fails to load, run lsdev and check for the floppy disk drive. Then, try again with the appropriate device.
7
8
9
Type boot
.
Complete the FreeBSD installation, following the instructions included with your operating system.
Reboot your computer, then remove the driver disk.
10 Repeat Steps 3 through 7 the first time you boot the operating system to load the drivers again for the initial bootup.
Installing the Driver on an Existing
Operating System
8
In this chapter...
This chapter explains how to install your Adaptec RAID controller driver.
Note: To install the driver while you’re installing an operating system, see
Chapter 8: Installing the Driver on an Existing Operating System ●
53
Before You Begin
Before you begin, install and connect your Adaptec RAID controller and internal disk drives
(see
).
You must also create a driver disk (see page 47 ) before you begin installing the controller driver.
Note: For up-to-date operating system version support, visit the Adaptec Web Site at www.adaptec.com
. From the main menu select Support>Knowledgebase>Find Answers. Select your controller type and OS support to generate a list of supported operating systems and to download the latest drivers.
Creating a Driver Disk
Note: You will need a floppy disk to complete this task.
To create a driver disk:
1 Set your system BIOS so that your computer boots from the CD drive. (For instructions, refer to your computer documentation.)
2
3
4
Turn on your computer, then insert the RAID Installation CD included in your RAID controller kit.
Follow the on-screen instructions to get to the Adaptec Start Menu.
Click Create Driver Disk(s) for Installing/Updating your OS , then select your operating system.
Note: Linux only— If prompted, select your operating system and then the version.
6
7
5 When prompted, insert a floppy disk, then click OK .
The system creates the driver disk.
Remove and label the driver disk.
Continue with the instructions for your operating system:
●
●
For Windows, see
For Red Hat or SUSE Linux, see page 54 .
●
●
●
●
●
.
.
For Solaris, see
For VMware, see
.
Chapter 8: Installing the Driver on an Existing Operating System ●
54
Installing on Windows
Follow the instructions in this section for your version of Windows.
Installing on Windows Server 2003 or Windows XP
To install the driver on Windows:
1
2
3
4
5
6
Start or restart Windows.
The Found New Hardware Wizard opens and searches for the driver.
Insert the driver disk, select Floppy drive , then click Next .
Click Next , then click Next again.
Follow the on-screen instructions to complete the driver installation.
Remove the driver disk and restart your computer.
Continue with
Managing Your Storage Space on page 57
.
Installing with Windows Server 2008 or Windows Vista
1 Start or restart Windows.
2
3
4
5
The Found New Hardware Wizard opens and searches for the driver.
Insert the driver disk, then select Locate and Install Driver Software...
. and Don’t Search
Online .
Click Next , then click Close .
When the installation is complete, remove the driver disk and restart your computer.
Continue with
Managing Your Storage Space on page 57
.
Installing on Red Hat or SUSE Linux
To install the module on Red Hat or SUSE Linux:
1 Insert and mount the RAID Installation CD:
2
3
4
5
Red Hat: mount /dev/cdrom /mnt/cdrom
SUSE: mount /dev/cdrom /media/cdrom
Install the module RPM: rpm -Uvh mount-point/xxx/yyy.rpm
where mount-point
is the specific mount point on the Linux system, xxx
is the driver path, and yyy.rpm
is the rpm file.
Reboot your computer to ensure the driver loaded correctly.
Run fdisk, mkfs, and create mount points for any new disk drives.
Continue with
Managing Your Storage Space on page 57
.
Chapter 8: Installing the Driver on an Existing Operating System ●
55
Installing on OpenServer
To install the driver on OpenServer:
1
2
Start your computer, then insert the driver disk.
Begin the driver package installer: pkgadd -d diskette1
3
4
5
6
7
At the installer prompt, type go .
Select 1 for the aacraid package.
When the installation is complete, select q to quit the installer.
Reboot your computer and remove the driver disk.
Continue with
Managing Your Storage Space on page 57
.
Installing on UnixWare
To install the driver on UnixWare:
1
2
Start your computer, then insert the driver disk.
Begin the driver package installer: pkgadd -d diskette1
3
4
5
6
7
At the installer prompt, type go
.
Select 1 for the aacraid package.
When the installation is complete, select q to quit the installer.
Reboot your computer and remove the driver disk.
Continue with
Managing Your Storage Space on page 57
.
Installing on Solaris
To install the driver on Solaris:
1
2
Start your computer.
Check for any pre-existing Adaptec driver by performing a pkginfo SUNWaac
in a terminal window. If there is no pre-existing Adaptec driver on your computer, continue with Step 3 .
If an Adaptec driver is already installed on your computer, perform a pkgrm SUNWaac
to remove it.
!
Caution: If your operating system currently boots from the Adaptec controller, do not reset your computer after you remove the pre-existing Adaptec driver. Instead, follow the steps in this section to install a new driver before rebooting your computer.
3
4
Insert and mount the driver disk: volcheck
Change to the driver installer directory: cd /floppy/floppy0/DU/sol_210/i86pc/Tools
Chapter 8: Installing the Driver on an Existing Operating System ●
56
6
7
5 Start the driver installer:
./install.sh -i
Reboot your computer, then remove the driver disk.
Continue with
Managing Your Storage Space on page 57
.
Installing on VMware
Note: The embedded driver provided by VMware should be suitable for most applications. If an updated driver is needed, use the following procedure.
To install the driver on VMware:
1 Start your computer, then insert the driver disk.
2 At the console screen of the VMware server, mount the Adaptec Installation CD: mount –r /dev/cdrom /mnt/cdrom.
3 Install the module RPM: rpm -i --force VMware-3.5-64607-esx-drivers-scsi-aacraid-1.1.5-2457.i586.rpm
Note: The rpm version string may differ for your VMware distribution.
4
5
Follow the on-screen instructions to save the boot image and run the vmware-mkinitrd command manually.
Reboot your computer and remove the driver disk.
Note: Currently, the Adaptec Storage Manager GUI is not supported on VMware. To create and manage arrays, you must connect to the VMware machine from a remote GUI or use the
ARCCONF
utility. See page 59 for more information.
Installing on FreeBSD
To install the driver on FreeBSD:
1
2
Start your computer.
Insert and mount the driver disk:
3 mount -t msdos /dev/fd0 /mnt
Copy the driver package to the /tmp directory:
4
5 cp /mnt/aac-02.00.00-x.tgz /tmp
Install the driver package: pkg_add /tmp/aac-02.00.00-x.tgz
Reboot your computer, then remove the driver disk.
Managing Your Storage Space
9
In this chapter...
Once you have installed your Adaptec RAID controller, disk drives (or other devices), and device driver, you can begin to build and manage your storage space.
This chapter introduces Adaptec Storage Manager, and describes the other utilities included with your Adaptec RAID controller.
Chapter 9: Managing Your Storage Space ●
58
About Adaptec Storage Manager
Adaptec Storage Manager is a full-featured software application that helps you build a storage space for your online data, using Adaptec RAID controllers and disk drives.
With Adaptec Storage Manager, you can group disk drives into logical drives and build in redundancy to protect your data and improve system performance.
From a single workstation, you can use Adaptec Storage Manager to monitor and manage all the controllers and disk drives in your storage space, including DAS and NAS.
When Adaptec Storage Manager is installed on a computer, the Adaptec Storage Manager agent is also installed automatically. The agent is like a service that keeps your storage space running.
It’s designed to run in the background, without user intervention, and its job is to monitor and manage system health, event notifications, task schedules, and other on-going processes on that system. It sends notices when tasks are completed successfully, and sounds an alarm when errors or failures occur on that system.
The agent uses less memory than the full application. If your storage space includes systems that won’t be connected to monitors (and therefore won’t require the user interface), you can choose to run the agent only on those systems instead of the full application. For more information, refer to the Adaptec Storage Manager online Help, or to the Adaptec Storage
Manager User’s Guide on the Adaptec Storage Manager Installation CD.
Installing Adaptec Storage Manager
Adaptec Storage Manager is included on the Adaptec Storage Manager Installation CD. For installation instructions, refer to the Adaptec Storage Manager User’s Guide , also included on the Adaptec Storage Manager Installation CD.
About the Adaptec RAID Controller Configuration Utility
The Adaptec RAID Controller Configuration (ARCCONF) is a command line utility that you can use to perform some basic array and configuration management functions.
With ARCCONF, you can:
● Create and delete logical drives
●
●
Modify and copy configuration settings
Recover from disk drive failures and troubleshoot
ARCCONF and the Adaptec RAID Controller Command Line Utility User’s Guide , which describes how to use ARCCONF, are included on the Adaptec Storage Manager Installation
CD.
Note: Adaptec recommends that only advanced users familiar with command line interfaces use ARCCONF.
Chapter 9: Managing Your Storage Space ●
59
About the Adaptec RAID Configuration Utility
The Adaptec RAID Configuration (ARC) utility is a BIOS-based utility that you can use to create and manage controllers, disk drives and other devices, and arrays. The ARC utility comprises these tools:
● Array Configuration Utility (ACU) —For creating and managing arrays, and initializing and rescanning disk drives. (ACU for DOS is also available. See
.)
●
●
Serial Select —For modifying your controller and disk drive settings.
Disk Utilities —For formatting or verifying disk drives.
The ARC utility is included in your controller’s BIOS. For more information, see
Adaptec RAID Configuration Utility on page 81 .
Note: The ARC utility is primarily intended for preoperating system installation configuration.
About the Adaptec Flash Utility
The Adaptec Flash Utility (AFU) is a text-based DOS utility that you can use to update, save, or verify your RAID controller’s firmware BIOS and Non-Volatile Random Access Memory
(NVRAM).
!
Caution: Although the AFU contains safeguards to prevent you from accidentally damaging your RAID controller’s flash contents, it is still important to use the AFU carefully and correctly to avoid rendering your RAID controller inoperable.Adaptec recommends that only advanced users familiar with working in DOS use the AFU. You can also use Adaptec
Storage Manager to update the controller firmware/BIOS. See the Adaptec Storage
Manager User’s Guide for more information.
Which Utility Should I Use?
To create a bootable array, Adaptec recommends that you use the BIOS-based ACU (See
Adaptec RAID Configuration Utility on page 81 ).
For all subsequent storage management tasks, Adaptec recommends that you install and use
Adaptec Storage Manager (see page 58 ). As a full-featured software application with a graphical
user interface, it is the easiest to use and offers the widest range of management functions.
Solving Problems
10
In this chapter...
This chapter provides basic troubleshooting information and solutions for solving controller problems.
Chapter 10: Solving Problems ●
61
Troubleshooting Checklist
If you encounter difficulties installing or using your Adaptec RAID controller, check these items first:
●
●
With your computer powered off, check the connections to each disk drive, power supply,
LED connector, and so on.
Try disconnecting and reconnecting disk drives from the Adaptec RAID controller.
Check that your Adaptec RAID controller is installed in a compatible PCIe expansion slot.
To double-check the bus compatibility of your controller, see About Your RAID Controller on page 15
.
●
●
●
Ensure that your Adaptec RAID controller is firmly seated and secured in the PCIe expansion slot.
If your Adaptec RAID controller is not detected during system boot, try installing it in a different compatible expansion slot. (See
for instructions.)
Did the driver install correctly?
If you have external disk drives (or other devices), are they powered on?
●
● Check the Readme on your installation CD for compatibility issues and known problems.
If you are still unable to resolve a problem, you can find additional troubleshooting information and direction on the Adaptec Web site at www.adaptec.com
or the Support
Knowledgebase at ask.adaptec.com
.
Monitoring Disk Drives Status
You can use the ‘blink’ feature of Adaptec Storage Manager to monitor the status of your SAS and SATA disk drives. When you blink a specific disk drive or set of disk drives, the LED(s) on the selected disk drives flash.
This table describes the LED flash states.
Controller Device State
Failed
Rebuilding
Blink
Other
Slot State
Device is faulty
Device is rebuilding
Identify the device
No error
LED Flash State
On
Slow flash
Fast flash
Off
For more information about backplanes, see Backplane Connections on page 69 . For more
information about using Adaptec Storage Manager to monitor your disk drives, refer to the
Adaptec Storage Manager User’s Guide or the online Help.
Silencing the Alarm
If your Adaptec RAID controller includes an alarm, the alarm will sound when an error occurs. To silence the alarm, use Adaptec Storage Manager (see
Managing Your Storage Space on page 57
.) OR
Serial Select
(see Modifying Your Controller’s Configuration on page 86
.)
Chapter 10: Solving Problems ●
62
Recovering from a Disk Drive Failure
This section explains how to recover when a disk drive fails:
●
●
●
●
●
If the array was protected by a hot spare (see page 62 ).
If the array was not protected by a hot spare (see
If there is a disk drive failure in more than one array simultaneously (see
If it is a RAID 0 array (see page 63
).
If multiple disk drives fail within the same array (see
Note: In DAS environments, Adaptec Storage Manager uses the term logical drives when referring to arrays
Failed Disk Drive Protected by a Hot Spare
When an array is protected by a hot spare, if a disk drive in that array fails the hot spare is automatically incorporated into the array and takes over for the failed drive.
To recover from the failure:
1 Remove and replace the failed disk drive.
2 If copyback is not enabled —In Adaptec Storage Manager, remove the ‘hot spare’ designation from the original hot spare (the disk drive that was built into the array). Then, designate a new hot spare to protect the arrays on that controller.
If copyback is enabled —Data is automatically moved back to its original location once the controller detects that the failed drive has been replaced. No action is required.
Failed Disk Drive Not Protected by a Hot Spare
When a array is not protected by a hot spare, if a disk drive in that array fails, remove and replace the failed disk drive. The controller detects the new disk drive and begins to rebuild the array.
If the controller fails to rebuild the array, check that the cables, disk drives, and controllers are properly installed and connected. Make sure that the new disk drive is equal or greater in size than the failed disk drive. Then, if necessary, use Adaptec Storage Manager to rebuild the array.
For instructions, refer to the Adaptec Storage Manager User’s Guide or online Help.
Failure in Multiple Arrays Simultaneously
If there’s a disk drive failure in more than one array at the same time (one failure per array), and the arrays have hot spares protecting them, the controller rebuilds the arrays with these limitations:
●
●
A hot spare must be of equal or greater size than the failed disk drive it’s replacing.
Failed disk drives are replaced with hot spares in the order in which they failed. (The array that includes the disk drive that failed first is rebuilt first, assuming an appropriate hot spare is available—see bullet above.)
If there are more disk drive failures than hot spares, see
Failed Disk Drive Not Protected by a Hot
Chapter 10: Solving Problems ●
63
If copyback is enabled, data is moved back to its original location once the controller detects that the failed drive has been replaced.
Disk Drive Failure in a RAID 0 Array
Because RAID 0 volumes do not include redundancy, if a disk drive fails in a RAID 0 array, the data can’t be recovered.
Correct the cause of the failure or replace the failed disk drives. Then, restore your data (if available).
Multiple Failures in the Same Array
Except in RAID 6 and RAID 60 arrays (see page 72
), if more than one disk drive fails at the same time in the same array, the data normally can’t be recovered.
You may be able to recover the data by forcing the logical drive online or by recreating the logical drive without the initialization step. You can use the BIOS utility, ACU (see
the command-line utility, ARCCONF, or Adaptec Storage Manager. For more information, refer to the Adaptec RAID Controller Command Line Interface User’s Guide and the Adaptec.
Storage Manager User’s Guide .
Note: In some instances, RAID 10 and RAID 50 arrays may survive multiple disk drive failures, depending on which disk drives fail.
Resetting the Controller
This section explains how to reset (or Mode 0 flash ) your Adaptec RAID controller. You may want to do this if the controller becomes inoperable, or if a firmware upgrade is unsuccessful.
To reset your Adaptec RAID controller:
1 Download the firmware version currently installed on your controller from www.adaptec.com
2
3
Extract the downloaded files to a folder on your local hard drive (for example,
C:\Download\Drivers).
Create a bootable MS–DOS floppy disk and copy the AFU.exe file to it. Copy the first firmware image to the same floppy disk.
4
5
6
7
8
Create additional bootable MS–DOS floppy disks and copy each additional firmware image to its own floppy disk.
Power off your computer, disconnect the power cord, then open the cabinet following the manufacturer’s instructions.
Disconnect all cables from the controller, then attach a shorting jumper to the Mode 0 flash connector. (To locate the Mode 0 flash connector on your Adaptec RAID controller,
see the figures in About Your RAID Controller on page 15
.)
Reconnect the power cord, power on your computer, then boot to the floppy disk containing the AFU.exe file (see
At the prompt, type a:\afu update /c x where x
is the controller number.
Chapter 10: Solving Problems ●
64
9 Insert the other floppy disks when prompted.
10 When the flash is complete, power off your computer, disconnect the power cord, then remove the jumper.
11 Close the computer cabinet, reconnect the power cord, then power on your computer.
The controller should boot correctly.
Introduction to SAS
A
In this appendix...
This section provides a basic overview of the main features of SAS, introduces some common
SAS terms, and explains how SAS differs from parallel SCSI.
Note: For technical articles and tutorials about SAS, refer to the SCSI Trade Association
(STA TM ) Web site at www.scsita.org.
Appendix A: Introduction to SAS ●
66
Terminology Used in This Chapter
For convenience, SAS HBAs and SAS RAID controllers are referred to generically in this chapter as SAS cards . HBAs, RAID controllers, disk drives, and external disk drive enclosures are referred to as end devices and expanders are referred to as expander devices .
For convenience, this chapter refers to end devices and expander devices collectively as SAS devices .
What is SAS?
Legacy parallel SCSI is an interface that lets devices such as computers and disk drives communicate with each other. Parallel SCSI moves multiple bits of data in parallel (at the same time), using the SCSI command set.
SAS is an evolution of parallel SCSI to a point-to-point serial interface. SAS also uses the SCSI command set, but moves multiple bits of data one at a time. SAS links end devices through direct-attach connections, or through expander devices.
SAS cards can typically support up to 128 end devices and can communicate with both SAS and SATA devices. (You can add 128 end devices—or even more—with the use of SAS
.)
Note: Although you can use both SAS and SATA disk drives in the same SAS domain
70 ), Adaptec recommends that you not combine SAS and SATA disk drives within the same
array or logical drive. The difference in performance between the two types of disk drives may adversely affect the performance of the array.
Data can move in both directions simultaneously across a SAS connection (called a link —see
page 67 ). Link speed is 300 MB/sec in half-duplex mode. Therefore, a SAS card with eight links
has a bandwidth of 2400 MB/sec.
Although they share the SCSI command set, SAS is conceptually different from parallel SCSI physically, and has its own types of connectors, cables, connection options, and terminology, as described in the rest of this chapter.
To compare SAS to parallel SCSI, see
How is SAS Different from Parallel SCSI?
Appendix A: Introduction to SAS ●
67
How Do SAS Devices Communicate?
SAS devices communicate with each other through links. A link is a physical connection between two phys.
As shown in the following figure, SAS devices contain ports (see
phys , and each phy contains one transmitter and one receiver—one transceiver . A phy can belong to one port only.
SAS Device
Narrow
Port
Phy
Receiver
Transmitter link
SAS Device
Transmitter
Receiver
Phy
Narrow
Port
SAS Device
Wide
Port
Phy
Receiver
Transmitter
Phy
Receiver
Transmitter
Transmitter
Receiver
Phy
Transmitter
Receiver
Phy
Wide
Port
Wide
Port
Phy
Receiver
Transmitter
Phy
Receiver
Transmitter
Phy
Receiver
Transmitter
Phy
Receiver
Transmitter
SAS Device
Transmitter
Receiver
Phy
Transmitter
Receiver
Phy
Transmitter
Receiver
Phy
Transmitter
Receiver
Phy
Wide
Port
What’s a Phy?
Phys are part of the physical communication connection between SAS devices. Each phy contains a transceiver that sends data back and forth between SAS devices.
When a connection is formed between two end devices, a link is established from a phy in one port to a phy in the other port. As shown in the figure above, a wide port can support multiple independent links simultaneously.
Phys are internal, within SAS connectors (see page 68
).
SAS cables physically connect one or more phys on one SAS device to one or more phys on another SAS device.
Appendix A: Introduction to SAS ●
68
What’s a SAS Port?
Note: Because the physical link between SAS devices is from phy to phy, rather than port to port, a “port” is more of a virtual concept, different from what is normally considered a port on other types of RAID controllers and storage devices.
A port is one or more phys. A narrow port contains one phy. A wide port typically contains four phys.
Each port has its own unique SAS address (see page 69
), and all the phys in a port share that same SAS address.
SAS card port options vary. A SAS card with four phys could be configured with one wide port, with two wide ports that comprise two phys, or with four narrow ports each containing one phy. (A wide port with four phys is referred to as a 4-wide or 4x port.)
What’s a SAS Address?
Each SAS port is identified with a unique SAS address, which is shared by all phys on that port.
For example, a SAS disk drive might have two narrow ports. Each port has one unique SAS address. The single phy in each port uses its port’s SAS address.
In another example, a SAS device might have one 4-wide port. That port has one SAS address, which is shared by all four phys in the port.
Unlike SCSI devices and SCSI IDs, SAS devices self-configure their SAS addresses. User intervention is not required to set SAS addresses, and SAS addresses cannot be modified.
What’s a SAS Connector?
A SAS or mini-SAS connector is the physical plug or receptacle that you see on a SAS device.
It’s what you plug a SAS cable into, or the end of the SAS cable that’s being plugged in. (See
A connector is what forms physical links between phys. Some SAS connectors can support multiple links. The number of links a SAS connector can support is referred to as its width .
Narrow connectors support a single link; wide connectors supports more than 1 link.
A single SAS device may have one or more connectors. A single SAS connector may help form links between more than two SAS devices. (For instance, as shown in the figure on
, the
4-wide internal SAS connector forms links with four independent disk drives.)
What do SAS Cables Look Like?
Internal standard SAS cables are narrower than internal parallel SCSI cables. The connectors vary in size depending on the number of links they support, from single link connectors to
4-wide (or larger) connectors. Internal fan-out cables let you attach four disk drives to a single
4-wide connector.
Mini-SAS connectors support both internal and external SAS connections. The mini-SAS connectors are smaller than the standard SAS internal and external connectors. Mini-SAS connectors support single and multilinks with the ability to scale to future speed needs.
For examples of some internal SAS/mini-SAS cables and an external SAS/mini-SAS cables, see
Appendix A: Introduction to SAS ●
69
How are Disk Drives Identified in SAS?
In the BIOS and in the management utilities (see
Identifying Disk Drives on page 89 ), disk
drives are identified in the following formats:
●
●
CNX:DevY = Device Y is attached to Connector X (see Direct-attach Connections below for
more information)
BoxX:SlotX = Enclosure X is attached to a disk drive in Slot X (see
below for more information)
● ExpX:PhyX = Expander X is attached to Phy X (see
below for more information) where X is the count number.
Note: Devices other than disk drives (CDROM, tape drives, etc...) are listed in order after your system disk drives.
In parallel SCSI, XX is the disk drive’s channel number, YY is the target number, and ZZ is the logical unit number (LUN).
What are the SAS Connection Options?
You can connect end devices to each other through direct cable connections and through backplane connections. When you use one or more expander devices (see
create large configurations.
Direct-attach Connections
In a direct-attach connection, SAS or SATA disk drives are connected directly to a SAS card with SAS or mini-SAS cables. One disk drive is attached to one SAS/mini-SAS connector with one SAS/mini-SAS cable (or multiple disk drives are attached to one SAS/mini-SAS connector
with one fan-out cable). The figure on page 39
shows an example of direct-attach connections.
The number of direct-attached disk drives is limited to the number of phys supported by the
SAS card. (Note that there may be multiple phys within a single connector. See
Backplane Connections
In a backplane connection, disk drives and SAS cards are attached to and communicate with each other through a system backplane.
There are two types of backplane connections, passive and active . When connecting to either backplane, it’s important to properly connect your disk drive LEDs in order to identify disk drive conditions. See
About Your RAID Controller on page 15
for your RAID controller Activity
LED connections and locations.
Once you have connected to a backplane, the Adaptec Storage Manager enables you to manage your disk drives. For more information, refer to the Adaptec Storage Manager User’s Guide on the Adaptec Storage Manager Installation CD.
.The number of end devices is limited to the number of slots available on the backplane. For example, the Adaptec S50 enclosure, which contains an expander, is a backplane connection that supports up to 12 SAS or SATA disk drives.
Appendix A: Introduction to SAS ●
70
Some backplanes support daisy-chain expansion to other backplanes. For example, you can daisy-chain (connect one to the next) up to nine Adaptec S50 enclosures to a single SAS card in a host system.
SAS Expander Connections
A SAS expander device literally expands the number of end devices that you can connect
together. Expander devices, typically embedded into a system backplane (see page 69
), support large configurations of SAS end devices, including SAS cards and SAS and SATA disk drives.
With expander devices, you can build large and complex storage topologies.
There are two types of SAS expanders: fanout expanders and edge expanders . Each performs a different role in a storage system. (For more information about how SAS expanders work, refer to the STA Web site at www.scsita.org.)
You can connect up to 128 SAS ports to an edge expander. (A single edge expander can therefore support up to 128 SAS addresses.)
You can connect up to 128 edge expanders to a fanout expander.
You can use only one fanout expander in any single SAS domain (a topology of SAS—and possibly SATA—end devices and expander devices). A single SAS domain can therefore comprise up to 16,384 SAS ports (and therefore up to 16,384 SAS addresses including the fanout expander).
The next figure illustrates (in very basic terms) a SAS domain and shows how SAS cards, SAS and SATA disk drives, and expander devices can fit together in a large data storage topology.
Disk Drives
SAS
SAS SATA
Disk Drives
SATA
Disk Drives
SATA SAS
Fanout Expander
SAS Card
SAS SATA
Disk Drives
SAS Card
SAS SATA
Disk Drives
SATA
Disk Drives
SATA
SAS Card
SATA
Disk Drives
SAS
Appendix A: Introduction to SAS ●
71
How is SAS Different from Parallel SCSI?
In summary, although SAS and parallel SCSI both use the SCSI command set, how they move data from one place to another is very different. To support point-to-point serial data transport, SAS introduces new types of connectors, cables, connection options, and terminology.
Generally speaking, SAS is faster and more flexible than parallel SCSI, and provides more options for building your storage space. SAS lets you mix SAS and SATA disk drives together, and lets you connect many, many more devices.
This table describes many of the main differences between the two interfaces.
Parallel SCSI
Parallel interface
Maximum speed 320 MB/sec shared by all devices on the bus
Supports SCSI devices only
Up to 16 devices per SCSI channel
Supports single-port devices only
Uses SCSI IDs to differentiate between devices connected to the same adapter
User intervention required to set SCSI IDs
Requires bus termination
Standard SCSI connectors
Serial Attached SCSI
Serial interface
Maximum speed 300 MB/sec per phy when in halfduplex mode
Supports SATA and SAS disk drives simultaneously
More than 100 disk drives per SAS card, using an
) or 50 SATAII disk drives.
Supports single- and dual-port devices
Uses unique SAS addresses to differentiate between devices
SAS addresses self-configured by SAS devices
Requires no bus termination
SAS connectors (see
)
Understanding RAID
B
In this appendix...
When you create arrays (or logical drives), you can assign a RAID level to protect your data.
Each RAID level offers a unique combination of performance and redundancy. RAID levels also vary by the number of disk drives they support.
This appendix describes the RAID levels supported by your Adaptec RAID controller, and provides a basic overview of each to help you select the best level of protection for your data storage.
Appendix B: Understanding RAID ●
73
Understanding Drive Segments
A drive segment is a disk drive or portion of a disk drive that is used to create an array. A disk drive can include both RAID segments (segments that are part of an array) and available segments. Each segment can be part of only one logical device at a time. If a disk drive is not part of any logical device, the entire disk is an available segment.
Non-redundant Arrays (RAID 0)
An array with RAID 0 includes two or more disk drives and provides data striping , where data is distributed evenly across the disk drives in equal-sized sections. However, RAID 0 arrays do not maintain redundant data, so they offer no data protection .
Compared to an equal-sized group of independent disks, a RAID 0 array provides improved I/O performance.
Drive segment size is limited to the size of the smallest disk drive in the array. For instance, an array with two 250 GB disk drives and two 400 GB disk drives can create a RAID 0 drive segment of 250 GB, for a total of 1000 GB for the volume, as shown in this figure.
Disk Drive 1 250 GB
Drive Segment Size
(Smallest Disk Drive)
Disk Drive 2 250 GB
Disk Drive 3 400 GB
Disk Drive 4 400 GB
Disk Drives in Logical Drive
Disk Drive 1 1 5 ...
997
Disk Drive 2 2 6 ...
998
Disk Drive 3 3 7 ...
999
Unused Space = 150 GB
Disk Drive 4 4 8 ... 1000
Unused Space = 150 GB
RAID 0 Logical Drive = 1000 GB
Appendix B: Understanding RAID ●
74
RAID 1 Arrays
A RAID 1 array is built from two disk drives, where one disk drive is a mirror of the other (the same data is stored on each disk drive). Compared to independent disk drives, RAID 1 arrays provide improved performance, with twice the read rate and an equal write rate of single disks.
However, capacity is only 50 percent of independent disk drives.
If the RAID 1 array is built from different- sized disk drives, the free space, drive segment size is the size of the smaller disk drive, as shown in this figure.
Drive Segment Size
(Smallest Disk Drive)
Disk Drive 1 250 GB
Disk Drive 2 400 GB
Disk Drives in Logical Drive
Disk Drive 1 1 – 250
Disk Drive 2 1 – 250
Unused Space = 150 GB
RAID 1 Logical Drive = 250 GB
RAID 1 Enhanced Arrays
A RAID 1 Enhanced (RAID 1E) array—also known as a striped mirror —is similar to a RAID 1 array except that data is both mirrored and striped, and more disk drives can be included. A
RAID 1E array can be built from three or more disk drives.
In this example, the large bold numbers represent the striped data, and the smaller, non-bold numbers represent the mirrored data stripes.
Disk Drive 1 400 GB
Disk Drive 2 400 GB
Disk Drive 3 400 GB
Disk Drives in Logical Drive
Disk Drive 1 1 3 4 6
Disk Drive 2 2 1 5 4
Disk Drive 3 3 2 6 5
RAID 1E Logical Drive = 600 GB
Appendix B: Understanding RAID ●
75
RAID 10 Arrays
A RAID 10 array is built from two or more equal-sized RAID 1 arrays. Data in a RAID 10 array is both striped and mirrored. Mirroring provides data protection, and striping improves performance.
Drive segment size is limited to the size of the smallest disk drive in the array. For instance, an array with two 250 GB disk drives and two 400 GB disk drives can create two mirrored drive segments of 250 GB, for a total of 500 GB for the array, as shown in this figure.
Disk Drive 1 250 GB
Drive Segment Size
(Smallest Disk Drive)
Disk Drive 2 250 GB
Disk Drive 3 400 GB
Disk Drive 4 400 GB
Disk Drives in Logical Drive
Disk Drive 1 1 3 ...
499
Disk Drive 2 2 4 ...
500
Disk Drive 3 1 3 ...
499
Unused Space = 150 GB
Disk Drive 4 2 4 ...
500
Unused Space = 150 GB
RAID 10 Logical Drive = 500 GB
Appendix B: Understanding RAID ●
76
RAID 5 Arrays
A RAID 5 array is built from a minimum of three disk drives, and uses data striping and parity data to provide redundancy. Parity data provides data protection, and striping improves performance.
Parity data is an error-correcting redundancy that’s used to re-create data if a disk drive fails.
In RAID 5 arrays, parity data (represented by Ps in the next figure) is striped evenly across the disk drives with the stored data.
Drive segment size is limited to the size of the smallest disk drive in the array. For instance, an array with two 250 GB disk drives and two 400 GB disk drives can contain 750 GB of stored data and 250 GB of parity data, as shown in this figure.
Disk Drive 1 250 GB
Drive Segment Size
(Smallest Disk Drive)
Disk Drive 2 250 GB
Disk Drive 3 400 GB
Disk Drive 4 400 GB
Disk Drives in Logical Drive
Disk Drive 1 1 4 ...
P
Disk Drive 2 2 5 ...
748
Disk Drive 3 3 P ...
749
Unused Space = 150 GB
Disk Drive 4 P 6 ...
750
Unused Space = 150 GB
RAID 5 Logical Drive = 750 GB plus Parity
Appendix B: Understanding RAID ●
77
RAID 5EE Arrays
A RAID 5EE array—also known as a hot space —is similar to a RAID 5 array except that it includes a distributed spare drive and must be built from a minimum of four disk drives.
Unlike a hot spare, a distributed spare is striped evenly across the disk drives with the stored data and parity data, and can’t be shared with other logical disk drives. A distributed spare improves the speed at which the array is rebuilt following a disk drive failure.
A RAID 5EE array protects your data and increases read and write speeds. However, capacity is reduced by two disk drives’ worth of space, which is for parity data and spare data.
In this figure, S represents the distributed spare, P represents the distributed parity data.
Disk Drive 1 250 GB
Drive Segment Size
(Smallest Disk Drive)
Disk Drive 2 250 GB
Disk Drive 3 400 GB
Disk Drive 4 400 GB
Disk Drives in Logical Drive
Disk Drive 1 1 S ...
P
Disk Drive 2 2 P ...
449
Disk Drive 3 S 3 ...
S
Unused Space = 150 GB
Disk Drive 4 P 4 ...
500
Unused Space = 150 GB
Based on the drive segment sizes used:
RAID 5EE Logical Drive = 500 GB plus parity and hot spare.
Appendix B: Understanding RAID ●
78
RAID 50 Arrays
A RAID 50 array is built from six to forty-eight disk drives configured as two or more RAID 5 arrays, and stripes stored data and parity data across all disk drives in both RAID 5 arrays. (For
more information, see RAID 5 Arrays on page 76 .)
The parity data provides data protection, and striping improves performance. RAID 50 arrays also provide high data transfer speeds.
Drive segment size is limited to the size of the smallest disk drive in the array. For example, three 250 GB disk drives and three 400 GB disk drives comprise two equal-sized RAID 5 arrays with 500 GB of stored data and 250 GB of parity data. The RAID 50 array can therefore contain
1000 GB (2 x 500 GB) of stored data and 500 GB of parity data.
In this figure, P represents the distributed parity data.
RAID 50
Logical Drive
=
1000 GB plus Parity
1, 5, P
Drive 1
250 GB
RAID 5
A
Each RAID 5 Logical Drive has
500 GB Data Storage
250 GB Parity Data
RAID 5
B
3, P, 9
Drive 2
250 GB
P, 7, 11
Drive 3
250 GB
2, 6, P
Drive 4
400 GB
4, P, 10
Drive 5
400 GB
P, 8, 12
Total Unused
Space = 150 GB
Drive 6
400 GB
Appendix B: Understanding RAID ●
79
RAID 6 Arrays
A RAID 6 array—also known as dual drive failure protection—is similar to a RAID 5 array because it uses data striping and parity data to provide redundancy. However, RAID 6 arrays include two independent sets of parity data instead of one. Both sets of parity data are striped separately across all disk drives in the array.
RAID 6 arrays provide extra protection for your data because they can recover from two simultaneous disk drive failures. However, the extra parity calculation slows performance
(compared to RAID 5 arrays).
RAID 6 arrays must be built from at least four disk drives. Maximum stripe size depends on the number of disk drives in the array.
Disk Drive 1 250 GB
Drive Segment Size
(Smallest Disk Drive)
Disk Drive 2 250 GB
Disk Drive 3 400 GB
Disk Drive 4 400 GB
Disk Drives in Logical Drive
Disk Drive 1 1 P1 ...
P2
Disk Drive 2 2 P2 ... 449
Disk Drive 3 P1 3 ...
P1
Unused Space = 150 GB
Disk Drive 4 P2 4 ... 500
Unused Space = 150 GB
Based on the drive segment sizes used:
RAID 6 Logical Drive = 500 GB plus parity (P1 & P2)
RAID 60 Arrays
Similar to a RAID 50 array (see
), a RAID 60 array—also known as dual drive failure protection—is built from eight disk drives configured as two or more RAID 6 arrays, and stripes stored data and two sets of parity data across all disk drives in both RAID 6 arrays.
Two sets of parity data provide enhanced data protection, and striping improves performance.
RAID 60 arrays also provide high data transfer speeds.
Appendix B: Understanding RAID ●
80
Selecting the Best RAID Level
Use this table to select the RAID levels that are most appropriate for the logical drives on your storage space, based on the number of available disk drives and your requirements for performance and reliability.
RAID Level Redundancy
RAID 0 No
RAID 1 Yes
RAID 1E
RAID 10
RAID 5
RAID 5EE
RAID 50
RAID 6
RAID 60
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Disk Drive
Usage
100%
50%
50%
50%
67 – 94%
50 – 88%
67 – 94%
50 – 88%
50 – 88%
Read
Performance
Write
Performance
Built-in
Hot Spare
No
No
No
No
No
Yes
No
No
No
Disk drive usage, read performance, and write performance depend on the number of drives in the logical drive. In general, the more drives, the better the performance.
Minimum
Disk
Drives
2
2
3
4
3
4
6
4
8
Using the Adaptec RAID
Configuration Utility
C
In this appendix...
The Adaptec RAID Configuration (ARC) utility is a BIOS-based utility that you can use to create and manage controllers, disk drives and other devices, and arrays.
Note: Adaptec recommends that only advanced users familiar with working in a computer BIOS use the ARC
utility tools. For more information, see Managing Your Storage Space on page 57
.
Appendix C: Using the Adaptec RAID Configuration Utility ●
82
Introduction to the ARC Utility
The ARC utility comprises these tools:
● The Array Configuration Utility (ACU) —For creating and managing arrays, and initializing and rescanning disk drives (see
Note:
Also available—ACU for DOS. See page 91
.
●
●
Serial Select —For modifying your controller and disk drive settings (see
).
Disk Utilities —For formatting or verifying disk drives (see
Running the ARC Utility
If your Adaptec controller is connected to a RAID enclosure, power on your enclosure (or enclosures) before you power on your computer.
Start or restart your computer. When prompted, press Ctrl+A .
During boot up, if your system has insufficient memory this message displays:
“Adaptec RAID Configuration Utility will load after, system initialization. Please wait... Or press <Enter> Key to attempt loading the utility forcibly [Generally, not recommended]”
Note: The first time you power on your computer after you install a new controller, the BIOS may display a configuration that doesn’t match your system’s configuration. This is normal.
Navigating the ARC Utility
All the tools within the ARC utility are menu-based and instructions for completing tasks appear on-screen. Menus can be navigated using the arrows, Enter, Esc, and other keys on your keyboard.
Using the ACU to Create and Manage Arrays
To open the ACU, start the ARC utility (see
page 82 ). If you have more than one controller, select
your controller, then press Enter . Select Array Configuration Utility , then press Enter .
Follow the on-screen instructions to create and manage arrays, and initialize, rescan, and erase disk drives.
Creating a New Array
To begin creating an array, select Create Arrays from the main ACU menu.
Only disk drives that can be used in a new array are available for selection. (Disk drives must be initialized before they can be used in an array. See
Initializing Disk Drives on page 84 for more
information.)
Use the Array Properties menu to modify the array’s RAID level, size, name, stripe size, and caching settings.
Note: For more information about RAID levels and using disk drives to create arrays, see
Choosing a RAID Level on page 31
.
Appendix C: Using the Adaptec RAID Configuration Utility ●
83
Managing Existing Arrays
To view or modify existing arrays, select Manage Arrays from the main ACU menu.
From the Manage Arrays menu, you can:
● View the properties of an array.
Note: Failed drives are displayed in a different text color.
●
●
●
●
●
Make an array bootable (see
Creating Bootable Arrays on page 83
).
Assign or remove hot spares.
Modify power management settings.
Change the cache settings for an array.
Delete an array.
!
Caution: Before deleting an array, back up the data to avoid permanently losing it.
Creating Bootable Arrays
Note: You may need to change the system BIOS to modify the boot order. For more information, refer to your computer documentation.
The controller always uses the lowest numbered array as its bootable array.
To make an array bootable:
1
2
Select Manage Arrays from the main ACU menu.
Select the array that you want to make bootable, then press Ctrl+B .
Note: You cannot make an array bootable while it’s building, verifying, or rebuilding.
3
The array’s number changes to Array 00, which makes this array the controller’s boot array.
Restart your computer.
Modifying Power Management Settings
Power management settings switch the array to low power state when it is inactive for a specific time.
To modify power management settings:
1 Select Manage Arrays from the main ACU menu.
2 Select the array, then press Ctrl+W .
In the power management console, enter these details:
Option
Power Management
Description
When enabled, switches the array to low power state, when the array/ drive is inactive.
Slow Down Drive After The duration of inactive state of the array/drive after which it is slowed down to low power mode. This is an optional setting.
Note: The disk drive should support low power mode.
Appendix C: Using the Adaptec RAID Configuration Utility ●
84
Option
Power Off Drive After
Verify Drive After
Description
The duration of inactive state of the array/drive after which it is powered off. This is an optional setting.
Note: Power Off Drive After duration should be greater than Slow
Down Drive After Duration.
The regular time interval at which the system performs a health check of the array/drive.
Modifying Cache Settings
You can modify the read and write cache settings for an array.
To modify cache settings:
1 Select Manage Arrays from the main ACU menu.
2
3
4
5
6
Select the array, then press Ctrl+C .
The Modify Cache Settings window opens.
Enable or disable read caching.
Press Tab .
Enable or disable write caching: select Enable always for “write-back” caching; select
Disable for “write-through” caching.
Press Enter to accept the values.
Initializing Disk Drives
If a disk drive appears grayed-out (unavailable for use in a new array), it may need to be initialized.
To begin initializing a disk drive, select Initialize Drives from the main ACU menu. You can initialize one drive or multiple drives. If an error occurs during initialization, the message
“Initializing drives...FAILED x of n” is displayed. Press Enter to see a list of drives that failed to initialize. Press Esc to continue.
!
Caution: Do not initialize a disk drive that is part of an array. Initializing a disk drive that’s part of an array may make the array unusable.
Back up all data from your disk drive before you initialize it.
Rescanning Disk Drives
To begin rescanning a disk drive, select Rescan Drives from the main ACU menu.
Secure Erasing Disk Drives
When you perform a secure erase on a disk drive, all data on that disk drive is completely and irretrievably eradicated. Secure erase performs three distinct writing passes to the disk drive being erased—it does not just write zeros.
Appendix C: Using the Adaptec RAID Configuration Utility ●
85
Performing a secure erase takes up to six times longer than clearing (or zeroing) a disk drive.
You may want to perform a secure erase only on disk drives that contain confidential or classified information.
Note: To erase (or zero) a disk drive with non-classified information, you may choose to format it (see
) instead, or clear it using Adaptec Storage Manager—both options take much less time than the secure erase option.
To begin a secure erase, select Secure Erase from the main ACU menu, then select Y (yes). To return to the main ACU menu once the secure erase has begun, press Esc .
The selected disk drive(s) cannot be used until the erase is complete.
Stopping a Secure Erase
To stop a secure erase in progress:
1
2
In the main ACU window, select Secure Erase .
Select the disk drive being secure erased, then press Ctrl+Q .
The secure erase stops and the ACU returns to its main window.
Managing Global Hot Spares
A hot spare is a disk drive that automatically replaces any failed drive in a logical drive. A global hot spare is not assigned to a specific logical drive. It protects any logical drive on the controller
(except RAID 0 logical drives). You can create and delete global hot spares even if no arrays exist.
To create and delete global hot spares:
1 Select Global Hotspares from the main ACU menu.
2
The Global Hotspare Management window opens.
Using the arrow keys, select a drive from the list. Existing hot spares are marked with a “*”.
3
4
Press Ins to create a new global hot spare. Press Del to delete a hot spare.
Press Enter to save your changes and return to the main menu.
Using the ACU to Create and Manage JBODs
To open the ACU, start the ARC utility (see
page 82 ). If you have more than one controller, select
your controller, then press Enter . Select Array Configuration Utility , then press Enter .
Follow the on-screen instructions to create and manage JBODs.
Creating a New JBOD
A JBOD disk appears as a physical disk drive to the operating system. A JBOD disk is not redundant and not bootable.
To begin creating a JBOD, select Create JBOD from the main ACU menu. All the supported disk drives are displayed. Select a disk drive and Enter .
Appendix C: Using the Adaptec RAID Configuration Utility ●
86
Managing Existing JBODs
To delete a JBOD or morph a JBOD into a simple volume, select Manage JBODs from the main ACU menu.
From the Manage JBODs menu, you can:
● Morph a JBOD into a simple volume.
● Delete a JBOD
Note: When you delete a JBOD, you lose all data on that disk.
Converting a JBOD Into a Simple Volume
You can convert any JBOD into a simple volume.
1
2
Select Manage JBODs from the main ACU menu.
Select the JBOD that you want to morph into a simple volume and press Ctrl+V .
Using Serial Select to Modify Controller Settings
The Serial Select utility is a tool for modifying the settings of your controller and the disk drives connected to it.
Opening Serial Select
To open Serial Select
, start the ARC utility (see page 82
), select Serial Select , then press Enter .
Follow the on-screen instructions to modify the settings of your controller and connected disk drives as required.
Applying Changes and Exiting
1 To exit Serial Select, press Esc until you are prompted to exit.
2
If you modified any settings, you are prompted to save the changes before you exit.
Select Yes to exit, then press any key to restart your computer.
Any changes you made take effect after the computer restarts.
Modifying Your Controller’s Configuration
Note: Default controller settings are suitable for most computers. Adaptec recommends that you do not change the default setting.
To modify your controller’s basic settings, select Controller Configuration from the main
Serial Select menu.
To modify your controller’s power management settings, select Advanced Configuration .
Note: The PHY settings are read-only and not editable.
This section describes the controller configuration options. Some options may not be available for your controller.
Appendix C: Using the Adaptec RAID Configuration Utility ●
87
General Controller Settings
Note: Default settings are shown in bold type.
Option
Drive’s Write Cache
Runtime BIOS
Automatic Failover
Array Background
Consistency Check
Array-based BBS
Support
SATA Native Command
Queuing (NCQ)
Physical Drives Display
During POST
DVD/CD-ROM Boot
Support
Description
When set to Enable All, write cache is enabled on all disk drives on the controller. (Enabling the write cache overrides any individual drive settings in Adaptec Storage Manager.) When set to Disable All, write cache is not used on the disk drives. When set to Drive Specific, write cache is enabled/disabled on a per-drive basis in Adaptec Storage
Manager.
Caution —When write cache is enabled, there is a slight possibility of data loss or corruption during a power failure.
When enabled , the controller BIOS allows the controller to act as a bootable device. Disabling the BIOS allows another controller to act as a bootable device.
When enabled , the controller automatically rebuilds an array when a failed disk drive is replaced. When disabled, the array must be rebuilt manually.
When enabled, the controller constantly verifies a redundant array. Note that there may be a significant performance reduction. Default is disabled .
When enabled in systems that support BBS, the controller presents attached bootable devices up to the BIOS for boot device selection. This is relevant for logical arrays. Default is disabled .
When enabled , NCQ is enabled. Disable this feature if you want to attach more than 48 SATA II disk drives. Only available with SATA II disk drives.
When enabled, connected disk drives are displayed during system Power
On Self Test (POST). Displaying the disk drives adds a few seconds to the overall POST time. Default is disabled .
When enabled , the system can be booted from a bootable CD. (This setting is not available on all RAID controller models.)
Note —CD’s are not supported by current software.
When enabled , removable media devices, such as CD drives, are supported. (This setting is not available on all RAID controller models.)
Removable Media
Devices Boot Support
Alarm Control
LED Indication Mode
Selectable Performance
Mode
When enabled, the alarm sounds. Default is enabled .
Note —When the alarm is turned off (disabled), it will automatically turn back on after a reboot.
When set to Activity/Fault, the drive LEDs blink to indicate I/O activity
(randomly depending on I/O load) and fault (steady 1Hz). When set to
Fault Only, the drive LEDs blink to indicate fault state only. Default is
Activity/Fault .
When set to Dynamic, performance criteria adjusts automically based on controller usage, RAID level, and disk drive type. When set to OLTP/Db, performance criteria is optimized for transaction-oriented applications, such as data entry and retrieval. Default is Dynamic .
Appendix C: Using the Adaptec RAID Configuration Utility ●
88
Power Management Settings
Note: When power management is disabled, no related options will be displayed.
Note: Make sure the operating system driver supports power management.
Note: Default settings are shown in bold type.
Option
Power Management
Settings
Time Zone
Description
When enabled, switches the system to low power state, based on the specified settings.
The time zone of the place in which the system is located. Time specific power management settings are implemented based on the set time zone. By default, it is set to 00:00 .
The valid range for the time zone settings is -12:00 to +12:00.
Stay Awake Start
Stay Awake End
The time from which the system should operate in the full power mode, irrespective of other power management settings, daily. By default it is set to 00:00 .
The valid range is 00:00 to 23:59.
The time until which the system should operate in the full power mode, irrespective of other power management settings, daily. By default it is set to 00:00 .
The valid range is 00:00 to 23:59.
Spin Up Limit (Internal) The number of internal drives to be spun up at any given moment. By default it is set to 0 . In the default setting, all the internal drives will spin up.
Spin Up Limit (External) The number of external drives to be spun up at any given moment. By default it is set to 0 . In the default setting, all the external drives will spin up.
PHY Settings
Note: These details are read-only and non-editable.
Option
PHY Rate
Description
The data transfer rate between the controller and devices. The default setting is
Auto , which allows the SAS card to adjust the data transfer rate as required.
CRC Checking When enabled, determines whether the controller verifies the accuracy of data transfer on the serial bus. Default setting is Yes (enabled). Set to No (disabled) only if the controller is connected to a device that does not support CRC Checking.
SAS Address In a situation where you want each phy on a controller to be in a different SAS domain, this setting specifies a unique world-wide name for each phy. Default is 0 .
Note: This setting is for SAS address conflict resolution only and should otherwise remain at its default value.
Formatting and Verifying Disk Drives
You can use the disk utilities to low-level format or verify your disk drives. (New disk drives are low-level formatted at the factory and do not need to be low-level formatted again.)
!
Caution: Before you format a disk drive, back up all data. Formatting destroys all data on a disk drive.
Appendix C: Using the Adaptec RAID Configuration Utility ●
89
To format or verify a disk drive:
1 Start the ARC utility (see
2
3
Select the controller you want, then press Enter .
Select Disk Utilities .
4
5
Select the disk drive you want, then press Enter .
Select Format Disk or Verify Disk Media .
Locating Disk Drives
Note: This feature is only available with disk drives that have an activity LED.
You can use the Identify Drive feature to physically locate a disk drive by blinking the LED.
To locate a disk drive:
1
2
Start the ARC utility (see
Select the controller you want, then press Enter .
3
4
5
6
Select Disk Utilities .
Select the disk drive you want, then press Enter .
Select Identify Drive , then press Enter .
When you have finished locating your disk drive, press any key to stop the blinking.
Identifying Disk Drives
You can identify disk drives by viewing the list of disk drives on your system. Only physical drives that display during POST are shown.
To identify a disk drive:
1 Start the ARC utility (see
2
3
Select the controller you want, then press Enter .
Select Disk Utilities .
The Disk Utilities view will provide you with the following information:
Location
CN1=DEV1
Box0=Slot0
Exp0=phy0
Model
The manufacturer information.
Rev#
The revision number of the disk drive.
Speed
The speed of the disk drive.
Size
The size of the disk drive.
The location information of a disk drive is determined by three types of connections:
● Direct attached drives —The connection is determined by the cable connected to a device, for example CN1 (connector 1) is connected to DEV1 (device 1). For more information, see
Direct-attach Connections on page 69
.
Appendix C: Using the Adaptec RAID Configuration Utility ●
90
●
●
Storage Enclosure Processor (SEP) managed devices —The connection is determined by an active backplane. Box0 (enclosure 0) is connected to slot0 (disk drive slot 0 in the
enclosure). For more information, see Backplane Connections on page 69
.
Expanders —The connections is determinded by an expander. Exp0 (expander 0) is connected to phy0 (phy 0 within a connector). For more information, see
Note: Devices other than disk drives (CDROM, tape drives, etc...) are listed in order after your system disk drives.
Viewing the Event Log
The BIOS-based event log records all firmware events, such as configuration changes, array creation, and boot activity.
Some events are not stored indefinitely—the event log is cleared of any non-persistent events each time you restart your computer; additionally, once the log is full, new events overwrite old events.
To view the event log:
1 Start the ARC utility (see
2
3
4
Select the controller you want, then press Enter .
When the ARC utility menu appears, then press Ctrl+P .
Select Controller Log Information , then press Enter .
The current event log opens.
Using the Array Configuration Utility for DOS
D
In this appendix...
This chapter describes the Array Configuration Utility (ACU) for DOS, a text-based utility that you can use to create, configure, and manage arrays. (A BIOS-based ACU is also available. See
Note: Adaptec recommends that only advanced users familiar with working in DOS use the
ACU for DOS utility. For more information, see Managing Your Storage Space on page 57 .
Appendix D: Using the Array Configuration Utility for DOS ●
92
Getting Started
Note: You need a bootable floppy disk to complete this task.
The ACU for DOS runs from a floppy disk which you can create using the RAID Installation
CD that came in your Adaptec RAID controller kit.
To create the ACU floppy disk:
1 Insert your RAID Installation CD into the CD drive, then browse to this file:
2
3 packages/firmware/ controllermodel /acu.exe
Where controllermodel is the model number of your Adaptec RAID controller.
Insert a bootable floppy disk and copy the acu.exe file to it.
Continue in one of two ways:
●
●
Work in the ACU using menus (see the following section)
Run the ACU using scripts (see
Working in the ACU Using Menus
To work in the ACU using menus:
1
2
Insert the ACU floppy disk (see Getting Started
above), then start or restart your computer.
The computer boots to the DOS command line.
Type
ACU
on the command line, then press Enter .
The ACU is menu-based and instructions for completing tasks appear on-screen. Menus can be navigated using the arrow, Enter, Esc, and other keys on your keyboard.
For more information about completing tasks, see
Using the ACU to Create and Manage
.
Appendix D: Using the Array Configuration Utility for DOS ●
93
Running the ACU Using Scripts
To work in the ACU using scripts:
1
2
Insert the ACU floppy disk (see
page 92 ), then start or restart your computer.
The computer boots to the DOS command line.
Type
ACU
on the command line, specify a script file, and specify either the /P or /R switches listed in the following table. (Don’t specify both.)
You may also add one or both of the optional switches.
Note: Command line syntax is not case sensitive.
Switch
/P < file >
/R <
/L < file file
>
>
Description
Playback Mode —The ACU reads the contents of the specified script file and creates arrays and configures channel settings based on the keywords
defined in the script. See page 93 .
Record Mode —The ACU writes a RAID controller’s existing array configuration to a specified script file, which lets you create the same configuration by running the ACU in playback mode (/P switch) with the resulting script. See
.
(Optional) Log Filename Switch —If you include this switch, the ACU records its activity and any errors it encounters in the log file. If you do not include this switch, the ACU displays activity and errors on the screen.
The file is a standard MS-DOS file, which can include a drive, directory, filename, and extension. Only the filename and extension (.log) are required. If no drive or directory is specified, the file is placed in the same location as the
ACU executable.
/C < number > (Optional) Controller Number Switch —In systems with more than one controller, this switch specifies which controller to change, where number is the controller number. The default controller number is 0 .
Note— The number assigned to a particular controller depends on the controller’s physical PCI slot and the order in which your system scans its PCI slots.
About 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 name of the script file. The file parameter can include a drive, directory, filename, and extension. If no drive or directory is specified, the script file used should be placed in the same location as the ACU executable.
Note: The script file syntax allows only one hot spare to be assigned to an array. Therefore, when recording a RAID 10, the ACU can’t map hot spares assigned to the individual mirror sets in the resulting script file. Instead, the ACU creates a single list for all hot spares assigned to the RAID 10. For more information, see
Appendix D: Using the Array Configuration Utility for DOS ●
94
About Record Mode
Note: You can also create a script file manually (see the following section).
In Record Mode, the ACU writes a RAID controller’s existing array configuration to a specified script file, which lets you create the same configuration by running the ACU in Playback Mode
(/P switch) with the resulting script.
You can only record one RAID controller at a time with Record Mode. Record multiple RAID controllers separately using separate script files.
The syntax is
ACU /R < file >
where file
is the 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 same location as the ACU executable.
The ACU supports only a subset of available array types. If it encounters an array it can’t create, a warning displays (or is recorded in the log file, if the /L switch is used); no keywords for that array are recorded 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 more information, see
Creating the Script File Manually
Script files contain blocks:
●
●
Array definition block keywords (see page 95
)
Optional —ACU error codes (see
The syntax rules are:
●
●
Each keyword must start its own line.
Syntax is not case sensitive.
Entering Comments in the Script File
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
.
Appendix D: Using the Array Configuration Utility for DOS ●
95
Array Definition Block Keywords
The array definition block always begins with the keyword Array and ends with the keyword
End. The other required array definition keywords are Drives and Type.
Array definition keywords and descriptions are listed in this table.
Keyword
Array
Drives
End
HotspareDrives
InitializeAll
Method
ReadCache
Size
StripeSize
Type
Wait
WriteCache
Required?
Description
Yes
Indicates the start of an array definition block. No default. See page 95
.
Yes Specifies the disk drives used in creating the array. No default. See
.
Yes
No
Indicates the end of an array definition block. No default. See
.
Specifies hot spares to assign to the array. No default. See
No
Yes
No
No
No
Yes
No
No
Indicates whether to initialize all the drives connected to the controller. Default is No
Indicates the method (Build/Verify, Clear, or Quick Init) to use when creating a redundant array. Default is Build . See
.
Indicates whether read caching is enabled for this array. Default is
Yes
Specifies the size of the array. Default is Maximum
Specifies size of contiguous I/O, in bytes. Default is 256 . See
.
Indicates the type of array to create. No default. See page 98
.
Indicates whether the ACU should wait for the new array’s Build/
Verify or Clear to complete before continuing. Default is Yes . See
.
Indicates whether write caching is enabled for this array. Default is
Yes
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.
For example:
Array=MyData
Drives Keyword
Drives is a required keyword, specifying the devices to use in creating the array. There is no default value.
A disk 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 disk drive identifiers with commas.
Prior to creating any new arrays, the ACU initializes any drives specified by the Drives keyword. If a disk drive is specified in more than one array definition block in a script, it is initialized only once.
!
Caution: Any disk drive specified within the script file is initialized, which destroys any data on that disk drive.
Appendix D: Using the Array Configuration Utility for DOS ●
96
For example:
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.
HotspareDrives Keyword
Hotspare Drives is an optional keyword, specifying the hot spares to assign to the array. The
syntax for listing hot spares is the same as the Drives Keyword on page 95
. If Hotspare Drives is not specified, no hot spares are assigned to the array.
For example:
HotspareDrives=0:0:0,0:1:0
The same disk drive can be assigned to protect multiple arrays (as a pool spare). Once a pool spare is used by a failed disk drive, however, it is no longer available to protect the other arrays its assigned to.
This keyword does not verify that the available space on the specified hot spares is sufficient to serve as failover for the array.
When assigning hot spares to a multilevel array, Hotspare Drives assigns all the hot spares in the list to all arrays within the multilevel array.
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.
!
Caution: Initializing a disk drive automatically deletes any existing arrays with that disk drive as their member.
Possible values:
● Yes —Initialize all drives.
● No ( default )—Do not initialize all drives; only those drives specified with the
Drives keyword are initialized.
For example:
#Initialize the drives prior array creation.
InitializeAll=Yes
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.
Appendix D: Using the Array Configuration Utility for DOS ●
97
Method Keyword
Method is an optional keyword, indicating which method to use when creating a redundant
(RAID 1, 1E, 10, 5, 5EE, 50, 6 and 60) array. Possible values:
●
●
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 disk drive (called full-stripe write mode), which reduces overall array performance. Maximum performance is achieved by starting and completing a Build/Verify.
Skip Init —If multiple disk drives fail in the same logical drive, you may be able to recover the data by recreating the logical drive without the initialization step. Omitting the initialization step reconstructs the logical drive metadata without modifying or destroying any other data on the disks.
For example:
Method=Build
ReadCache Keyword
ReadCache indicates whether the array uses read caching.
Possible values:
● Yes ( default )—Enable read caching.
● No —Disable read caching.
For 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).
Note: A unit keyword is required with a numeric size value. If no unit keyword is specified, the
ACU exits with an error.
For example:
Size=2.5GB
Size=300MB
Size=Maximum
StripeSize Keyword
The StripeSize keyword specifies the stripe size (in KB) written to each member of a striped array (RAID 0, 10, 5, 5, 5EE, 50, 6 or 60).
The possible values for StripeSize are 16, 32, 64, 128, 256, 512 and 1024 KB. Default is 256 .
Appendix D: Using the Array Configuration Utility for DOS ●
98
For example:
StripeSize=256
Type Keyword
Type is a required keyword, indicating the array type. There is no default value. The possible values: Volume, RAID0, RAID1, RAID5, RAID10, or RAID50.
Depending on the RAID levels supported by your RAID controller, additional possible values are: RAID1E, RAID5EE, RAID6, RAID60.
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.
If the host is powered off before the Build/Verify or Clear process completes and is then restarted, the process resumes without any user intervention.
For example:
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 ( default )—Enable the write cache.
No —Disable the write cache.
Setting an array’s WriteCache keyword to Yes might result in data loss or corruption during a power failure.
For example:
WriteCache=Yes
ACU Error Codes
When the ACU detects an error, it reports the error and exits immediately. If a log file is specified, the ACU writes the error code to the log file. Otherwise, it displays the error code on the screen.
The possible error messages returned by the ACU are listed in this table.
Code Description
0 ACU ran without changes —ACU exited with no errors (success) and no report is required.
1 No controller found .
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 .
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 93 for a list of valid command-line switches.)
Appendix D: Using the Array Configuration Utility for DOS ●
99
Code Description
5 Unable to read system configuration —The ACU was unable to get the configuration information from the specified controller.
6 No drives detected .
7 Specified drive not found in system .
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 .
12 Error occurred while creating array .
13 Too many spare drives assigned —You attempted to assign more than the maximum number of hot spares allowed for the specified array.
14 Insufficient memory to run the application .
15 Incorrect controller number .
16 Controller not responding .
17 Build/Verify/Clear failed .
18 Cannot use drives on shared channel.
21 Failed in getting kernel version. Unknown product ID.
22 Kernel timeout in writing command.
23 No RAID channels available
24 Error: wrong stripe size in creating array - script mode.
100 You ran ACU and made changes —The ACU exited with no errors (success) and you must restart the computer.
Sample Scripts
This command invokes the ACU and creates arrays on controller 1 based on the array keywords defined in the script file A:\RAID.ACU. It also configures Channel 0 and saves a log of the operation in the log file C:\RAID.LOG:
A:\> ACU /P A:\RAID.ACU /L C:\RAID.LOG /C1
This sample script file is the RAID.ACU script as referred to in the ACU command above. This script creates these arrays—a 500 MB single-disk volume, and a 2-GB two-disk drive RAID 1 with a hot spare:
# Create a 500MB volume labeled ‘MySystem’
Array=MySystem
Type=Volume
Size=500MB
Drives=0:0:0
End
# Create a 2GB mirror labeled ‘MyMirror’
Array=MyMirror
Type=RAID1
Size=2GB
Appendix D: Using the Array Configuration Utility for DOS ●
100
# Use drives 1 and 2
Drives=0:1:0,0:2:0
# Disable write cache
WriteCache=No
# Assign 1 spare drive
HotspareDrives=0:3:0
End
This sample script file creates a maximum-size three-disk-drive RAID 5:
# Create a maximum size RAID 5 labeled ‘MyData’
Array=MyData
Type=RAID5
Size=Maximum
# Use the maximum stripe size
StripeSize=1024
# Clear the array (don’t build/verify it)
Method=Clear
# Don’t wait for clear to complete
Wait=No
# Use drives 0, 1, 2
Drives=0:0:0, 0:1:0, 0:2:0
End
Using the Adaptec Flash Utility
E
In this appendix...
This chapter describes how to use the Adaptec Flash Utility (AFU), a text-based DOS utility that you can use to update, save, or verify the RAID controller’s firmware BIOS and NVRAM.
!
Caution: Although the AFU contains safeguards to prevent you from accidentally damaging your RAID controller’s flash contents, it is still important to use the AFU carefully and correctly to avoid rendering your RAID controller inoperable.
Adaptec recommends that only advanced users familiar with working in DOS use the AFU.
For more information, see
Managing Your Storage Space on page 57
.
Appendix E: Using the Adaptec Flash Utility ●
102
System Requirements
● MS–DOS version 5.0 or later.
Note: You can’t run the AFU from a DOS command prompt window under any version of
Windows.
● At least 8 MB of extended memory.
Compatibility Notes
● 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.
Before You Begin
1 Obtain the firmware (see the following section).
2
Create firmware disks (see page 103 ).
There are two ways to run the AFU:
1
2
Using the AFU menus (see
From the command line (see page 104
)
Obtaining the Firmware
To obtain RAID controller firmware, go to:
●
●
The RAID Installation CD —Includes the AFU executable (AFU.exe) and a separate flash image. The flash image may comprise multiple User Flash Image (UFI) files.
The Adaptec Web site —Download a new firmware file to get the most recent version of firmware/BIOS and AFU.
See www.adaptec.com
for more information.
Appendix E: Using the Adaptec Flash Utility ●
103
Creating the Firmware Update Disks
To create the firmware update disks:
1 Copy these files to empty, formatted floppy disks, a USB flash drive, or a writable CD:
●
AFU.exe
●
Ax xxx 01.ufi
where xxx is the model number of your controller.
Note: Most controller model numbers have a suffix (for example Adaptec RAID 3405).
Check that the .ufi file is the correct file for your controller before copying.
2
3
If using floppy disks, copy each additional Axxxx0x.ufi file to a separate floppy disk. (Some
RAID controllers have two UFI files; some have four. Each goes onto its own floppy disk.)
To use a menu-based AFU, see the following section.
To run the AFU from the command line, see page 104
.
Running the Menu-based AFU
To run the menu-based AFU:
1
2
3
4
5
6
Shut down your operating system and reboot to DOS from a bootable MS-DOS floppy disk or from a DOS partition on a bootable drive. (You can use a disk drive connected to the controller you are updating.) If your computer isn’t set up to boot from the bootable floppy disk, enter the system setup utility and change the setting.
Insert the firmware update disk (created using the steps above) containing AFU.exe
At the DOS command prompt, type
AFU
with no arguments.
The AFU’s main menu is displayed.
Select Select Controllers , then select the Adaptec RAID controller(s) to be flashed.
To update multiple RAID controllers in the same system, update the boot controller’s flash first, restart the computer, then update the flash for the remaining controllers.
Select Select an Operation .
Choose the operation you want, then follow the on-screen instructions to complete the task:
●
Update flash image —Updates all the flash components on a RAID controller with the flash image data from the UFI file.
●
Save flash image —Reads the contents of a RAID controller’s flash components and saves the data to a UFI file, which you can use to restore a RAID controller’s flash if required.
●
●
●
Verify flash image —Reads the contents of a RAID controller’s flash components and compares it to the contents of the specified UFI file.
Display flash information —Displays version information about a RAID controller’s flash components.
List flash image —Lists all supported RAID controllers detected on your system.
Appendix E: Using the Adaptec Flash Utility ●
104
7 Complete the flash operation and restart your computer before trying to use the RAID controller again. (You can not use your RAID controller while you are updating its flash.)
The AFU processes the selected command, prompts you to insert additional floppy disks as needed, and reports either success or an error message code.
Running the AFU from the Command Line
Note: You can also run a menu-based AFU (see
).
To run the AFU from the command line:
1 Shut down your operating system and reboot to DOS from a bootable DOS floppy disk or from a DOS partition on a bootable drive. (You can use a disk connected to the controller you’re updating.) If your computer isn’t set up to boot from the bootable floppy disk, enter the system setup utility to change the setting.
2
3
Insert the firmware update disk containing AFU.exe
At the DOS command, type AFU followed by a command (see page 104
) and any switches you want.
Note: To find a controller number, type AFU LIST , then press Enter .
The AFU processes the command, prompts you to insert additional floppy disks as needed, exits, and reports either success or an error message code.
To update a RAID controller’s flash using the command line utility ARCCONF, see page 107
.
AFU Commands
This section lists the available AFU commands.
List
Displays the AFU-supported RAID controllers installed on your computer. Also displays the
ID numbers assigned to each controller.
You don’t have to restart the computer after completing this command.
This example shows a typical system response to a LIST command:
A:\> AFU LIST
Adaptec Flash Utility V4.0-0 B5749
(c)Adaptec Inc. 1999–2005. All Rights Reserved.
Controllers Detected and Recognized:
Controller #0 (03:05:00) Adaptec RAID 51645
Save
Saves the contents of a RAID controller’s flash in a UFI file. The name of the UFI file is based on the controller type and can’t be changed.
You must restart the computer following a SAVE command.
The command syntax for the SAVE command is
AFU SAVE [/C<Controller ID>] [/D <UFI File Path>]
Appendix E: Using the Adaptec Flash Utility ●
105
These switches are available:
● /C <Controller ID> —One or more RAID controller IDs representing the set of RAID controllers on which to perform the specified command. The default is 0; if the computer has multiple RAID controllers, the AFU defaults to controller 0 unless you specify otherwise.
For example:
To specify a single RAID controller ID:
/C 0
To specify multiple IDs separated by commas:
/C 0,2
To indicate all RAID controllers:
ALL
●
If you are using multiple RAID controllers, you must specify the controller you want by using the /C switch; otherwise, the AFU displays an error message and exits.
/D <UFI File Path> —Specifies the path where the UFI files are located. If you do not specify the /D switch, the AFU looks for (or creates) its UFI files in the default location.
You cannot specify the name of a UFI file, only its path. UFI filenames are predefined, based on the RAID controller type.
In this example, the AFU saves flash contents from RAID controller 0 to a UFI file in the current default drive and directory:
A:\> AFU SAVE /C 0
In this example, the AFU saves flash contents from Controller 1 to a UFI file in
C:\UFI_FILES:
A:\> AFU SAVE /C 1 /D C:\UFI_FILES
Update
Updates the flash components of one or more RAID controllers on your computer from the flash image data in a UFI file. You must restart the computer following an UPDATE command.
The command syntax for the UPDATE command is:
AFU UPDATE [/C<Controller ID>] [/D <UFI File Path>]
This example shows a typical system response after an update.
A:\> AFU UPDATE /C 0
Adaptec Flash Utility V4.0-0 B5749
(c)Adaptec Inc. 1999–2005. All Rights Reserved.
Updating Controller 0 (Adaptec RAID 31205)
Reading flash image file (Build 5749)
AFU is about to update firmware on controllers Adaptec RAID 51645
***PLEASE DO NOT REBOOT THE SYSTEM DURING THE UPDATE***
This might take a few minutes.
Writing Adaptec RAID 51645 (4MB) Flash Image to controller 0...OK.
Verifying...OK
Please restart the computer to allow firmware changes to take effect.
Appendix E: Using the Adaptec Flash Utility ●
106
Verify
Compares the contents of each of the flash components on a RAID controller to the corresponding image in a UFI file, and indicates whether they match. After using the VERIFY command, you must restart the computer.
The command syntax for the VERIFY command is as follows:
AFU VERIFY [/C<Controller ID>] [/D <UFI File Path>]
This example shows a typical system response after a VERIFY command.
A:\> AFU VERIFY /C 0
Adaptec Flash Utility V4.0-0 B5749
(c)Adaptec Inc. 1999–2005. All Rights Reserved.
Reading flash image file (Build 5748)
Controller #0: Adaptec RAID 51645
ROM: Checksum: 797B [VALID] (Build 5748)
File: Checksum: 797B [VALID] (Build 5748)
Image Compares Correctly
Version
Displays version information about the flash components on a RAID controller. After using the VERSION command, restart your computer.
The command syntax for the VERSION command is:
AFU VERSION [/C<Controller ID>]
This example displays version information about all supported RAID controllers.
A:\> AFU VERSION /C 0
Adaptec Flash Utility V4.0-0 B5749
(c)Adaptec Inc. 1999–2005. All Rights Reserved.
Version Information for Controller #0 (Adaptec RAID 51645)
ROM: Build 5748 [VALID] Fri Sep 27 13:28:40 EDT 2005
A:\> AFU VERSION /C ALL
Help
Displays a summary of AFU functions and command switches. For example:
A:\> AFU HELP
A:\> AFU /?
Appendix E: Using the Adaptec Flash Utility ●
107
Updating the Flash Using the AFU Command Line
1 Create the firmware update disks (see
2
3
4
5
6
Shut down your operating system and reboot to DOS from a bootable DOS floppy disk or from a DOS partition on a bootable drive. (You can use a disk connected to the controller you’re updating.) If your computer isn’t set up to boot from the bootable floppy disk or a bootable device other than a disk drive, enter the system setup utility to change the setting.
Insert the firmware update disk containing AFU.exe
At the DOS command, if you have multiple controllers and you don’t know the number of the controller you want to update, type
AFU LIST
, then press Enter . Otherwise, skip to the next step.
At the DOS command, type AFU followed by a command (see page 104
) and any switches you want.
Update the flash using the instructions suitable for your requirements:
●
To update a single RAID controller :
AFU UPDATE /C < cont_number >
●
●
Where < cont_number > is the number of the RAID controller whose firmware you are updating. For example, to upgrade Controller 0, type AFU UPDATE /C 0
To update multiple RAID controllers :
AFU UPDATE /C < cont_number_a >,< cont_number_b >
Where < controller_number_a > and < controller_number_b > are the numbers of the Adaptec RAID controllers whose firmware you are updating. For example, to upgrade controllers 0, 2, and 3, type
AFU UPDATE /C 0, 2, 3
To update all RAID controllers simultaneously :
AFU UPDATE /C all
Note: The UFI file identifies the RAID controllers, so you don’t have to worry about flashing the wrong controller.
7
8
9
When prompted, insert the first firmware disk into your floppy disk drive.
The AFU reads the first disk.
When prompted, remove the first firmware disk and insert the second firmware disk into your floppy disk drive.
Repeat
Step 8 as required until the flash update is complete.
Controller LED and I2C Connector
Quick Reference
F
In this appendix...
Adaptec RAID 5405/5405Z LED and I2C Connector Specification.................................. 111
Adaptec RAID 5445/5445Z LED and I2C Connector Specification.................................. 112
Adaptec RAID 5805/5805Z LED and I2C Connector Specification.................................. 114
This chapter provides a reference guide for Adaptec
®
RAID controllers of Activity LED and I2C connectors.
Appendix F: Controller LED and I2C Connector Quick Reference ●
109
Adaptec RAID 5085 LED Connector Specification
2249100-R ASR-5085/512MB RoHS SGL
●
●
J2:
Adaptec RAID 5085 Activity LED Header Connector: Molex 10-89-7162 or equivalent
Activity LED Header Mating Cable Connector: Molex 22-55-2161 or equivalent
11
12
13
14
15
7
8
9
10
16
4
5
6
2
3
J2 Pin Number
1
Signal
+3.3V
Description
LED Anode
ACTIVITY CN0, LANE 0 LED Cathode
+3.3V
LED Anode
ACTIVITY CN0, LANE 1 LED Cathode
+3.3V
LED Anode
ACTIVITY CN0, LANE 2 LED Cathode
+3.3V
LED Anode
ACTIVITY CN0, LANE 3 LED Cathode
+3.3V
ACTIVITY CN1, LANE 0
LED Anode
LED Cathode
+3.3V
ACTIVITY CN1, LANE 1
+3.3V
ACTIVITY CN1, LANE 2
+3.3V
ACTIVITY CN1, LANE 3
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
12
11
14
13
16
8
7
10
9
15
3
6
5
22-55-2161
Pin Number
2
1
4
● Adaptec RAID 5085 Aggregate Activity LED Board Connector : Molex 22-28-4023 or equivalent
●
J1:
Aggregate LED Mating Cable Connector : Molex 50-57-9002 or equivalent
J1 Pin Number Signal
2 ACTIVITY
1 +3.3V
Description
LED Cathode
LED Anode
●
●
Adaptec RAID 5085 External Alarm Connector: Molex 22-28-4023 or equivalent
Alarm Mating Cable Connector: Molex 50-57-9002 or equivalent
Appendix F: Controller LED and I2C Connector Quick Reference ●
110
J12:
J12 Pin Number Signal
2 ~2kHz Square Wave
1 +3.3V
Description
Open collector transistor
● Adaptec RAID 5085 Status LED Board Connector: Molex 10-89-7162 or equivalent
●
J14:
Status LED Mating Cable Connector: Molex 22-55-2161 or equivalent
11
12
13
8
9
6
7
10
14
15
16
3
4
5
J14 Pin Number
1
2
Signal
+3.3V
STATUS CN0, LANE 0
+3.3V
STATUS CN0, LANE 1
+3.3V
STATUS CN0, LANE 2
+3.3V
STATUS CN0, LANE 3
+3.3V
STATUS CN1, LANE 0
+3.3V
STATUS CN1, LANE 1
+3.3V
STATUS CN1, LANE 2
+3.3V
STATUS CN1, LANE 3
Description
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
12
11
14
5
8
7
10
9
13
16
15
4
3
6
22-55-2161
Pin Number
2
1
Appendix F: Controller LED and I2C Connector Quick Reference ●
111
Adaptec RAID 5405/5405Z LED and I2C Connector
Specification
2258100-R
2258100JA-R
2258200-R
2266800-R
ASR-5405 RoHS KIT
ASR-5405/JA RoHS KIT
ASR-5405 RoHS Single
ASR-5405Z RoHS Single
● Adaptec RAID 5405/5405Z Activity LED Header Connector: Molex 10-89-7162 or equivalent
●
J2:
Activity LED Header Mating Cable Connector: Molex 22-55-2161 or equivalent
6
7
4
5
8
2
3
J2 Pin Number
1
Signal
+3.3V
ACTIVITY CN0, LANE 0
+3.3V
ACTIVITY CN0, LANE 1
+3.3V
ACTIVITY CN0, LANE 2
+3.3V
ACTIVITY CN0, LANE 3
Description
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
5
8
3
6
7
22-55-2161
Pin Number
2
1
4
● Adaptec RAID 5405/5405Z Aggregate Activity LED Board Connector : Molex 22-28-4023 or equivalent
●
J1:
Aggregate LED Mating Cable Connector : Molex 50-57-9002 or equivalent
J1 Pin Number Signal
2 ACTIVITY
1 +3.3V
Description
LED Cathode
LED Anode
●
●
J12:
Adaptec RAID 5405/5405Z External Alarm Connector: Molex 22-28-4023 or equivalent
Alarm Mating Cable Connector: Molex 50-57-9002 or equivalent
●
J12 Pin Number Signal
2 ~2kHz Square Wave
1 +3.3V
Description
Open collector transistor
—
Adaptec RAID 5405/5405Z I2C Board Connector : Molex 22-43-6030 or equivalent
Appendix F: Controller LED and I2C Connector Quick Reference ●
112
●
J4:
I2C Mating Cable Connector: Molex 22-43-3030 or equivalent
2
1
J4 Pin Number
3
Signal
I2C Clock
Ground
I2C Data
●
●
Adaptec RAID 5405 Status LED Board Connector: Molex 10-89-7162 or equivalent
Status LED Mating Cable Connector: Molex 22-55-2161 or equivalent
J14 (Adaptec RAID 5405 only):
6
7
8
4
5
2
3
J14 Pin Number
1
Signal
+3.3V
STATUS CN0, LANE 0
+3.3V
STATUS CN0, LANE 1
+3.3V
STATUS CN0, LANE 2
+3.3V
STATUS CN0, LANE 3
Description
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
5
8
7
4
3
6
22-55-2161
Pin Number
2
1
Adaptec RAID 5445/5445Z LED and I2C Connector
Specification
2228800-R
2228800JA-R
2244900-R
2267000-R
ASR-5445 RoHS Kit
ASR-5445/JA RoHS Kit
ASR-5445/512MB RoHS SGL
ASR-5445Z RoHS Single
●
●
J2:
Adaptec RAID 5445/5445Z Activity LED Header Connector: Molex 10-89-7162 or equivalent
Activity LED Header Mating Cable Connector: Molex 22-55-2161 or equivalent
Note: For Adaptec RAID 5445, header J2 is a 16-pin connector (pins 1-16). For Adaptec RAID
5445Z, header J2 is an 8-pin connector (pins 1-8 only).
J2 Pin Number
1
2
3
Signal
+3.3V
Description
LED Anode
ACTIVITY CN0, LANE 0 LED Cathode
+3.3V
LED Anode
22-55-2161
Pin Number
2
1
4
Appendix F: Controller LED and I2C Connector Quick Reference ●
113
12
13
14
8
9
10
11
15
16
6
7
J2 Pin Number
4
5
Signal Description
ACTIVITY CN0, LANE 1 LED Cathode
+3.3V
LED Anode
ACTIVITY CN0, LANE 2 LED Cathode
+3.3V
LED Anode
ACTIVITY CN0, LANE 3 LED Cathode
+3.3V
LED Anode
ACTIVITY CN1, LANE 0 LED Cathode
+3.3V
LED Anode
ACTIVITY CN1, LANE 1 LED Cathode
+3.3V
LED Anode
ACTIVITY CN1, LANE 2 LED Cathode
+3.3V
LED Anode
ACTIVITY CN1, LANE 3 LED Cathode
11
14
13
7
10
9
12
16
15
5
8
22-55-2161
Pin Number
3
6
● Adaptec RAID 5445/5445Z Aggregate Activity LED Board Connector : Molex 22-28-4023 or equivalent
●
J1:
Aggregate LED Mating Cable Connector : Molex 50-57-9002 or equivalent
J1 Pin Number Signal
2 ACTIVITY
1 +3.3V
Description
LED Cathode
LED Anode
●
●
J12:
Adaptec RAID 5445/5445Z External Alarm Connector: Molex 22-28-4023 or equivalent
Alarm Mating Cable Connector: Molex 50-57-9002 or equivalent
J12 Pin Number Signal
2 ~2kHz Square Wave
1 +3.3V
Description
Open collector transistor
—
●
●
J4:
Adaptec RAID 5445/5445Z I2C Board Connector : Molex 22-43-6030 or equivalent
I2C Mating Cable Connector: Molex 22-43-3030 or equivalent
●
J4 Pin Number
3
2
1
Signal
I2C Clock
Ground
I2C Data
Adaptec RAID 5445 Status LED Board Connector: Molex 10-89-7162 or equivalent
Appendix F: Controller LED and I2C Connector Quick Reference ●
114
● Status LED Mating Cable Connector: Molex 22-55-2161 or equivalent
J14 (Adaptec RAID 5445 only):
10
11
12
13
14
7
8
9
15
16
5
6
3
4
J14 Pin Number
1
2
Signal
+3.3V
Description
LED Anode
STATUS CN0, LANE 0 LED Cathode
+3.3V
LED Anode
STATUS CN0, LANE 1 LED Cathode
+3.3V
LED Anode
STATUS CN0, LANE 2 LED Cathode
+3.3V
LED Anode
STATUS CN0, LANE 3 LED Cathode
+3.3V
LED Anode
STATUS CN1, LANE 0 LED Cathode
+3.3V
LED Anode
STATUS CN1, LANE 1 LED Cathode
+3.3V
LED Anode
STATUS CN1, LANE 2 LED Cathode
+3.3V
LED Anode
STATUS CN1, LANE 3 LED Cathode
Adaptec RAID 5805/5805Z LED and I2C Connector
Specification
9
12
11
14
13
8
7
10
16
15
6
5
4
3
22-55-2161
Pin Number
2
1
2244100-R
2244100JA-R
2244300-R
2266900-R
ASR-5805 RoHS KIT
ASR-5805/JA RoHS KIT
ASR-5805/512MB RoHS Single
ASR-5805Z RoHS Single
● Adaptec RAID 5805/5805Z Activity LED Header Connector: Molex 10-89-7162 or equivalent
●
J2:
Activity LED Header Mating Cable Connector: Molex 22-55-2161 or equivalent
3
4
5
J2 Pin Number
1
2
Signal
+3.3V
ACTIVITY CN0, LANE 0
+3.3V
ACTIVITY CN0, LANE 1
+3.3V
Description
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
4
3
6
22-55-2161
Pin Number
2
1
Appendix F: Controller LED and I2C Connector Quick Reference ●
115
14
15
16
10
11
12
13
8
9
J2 Pin Number
6
7
Signal
ACTIVITY CN0, LANE 2
+3.3V
ACTIVITY CN0, LANE 3
+3.3V
ACTIVITY CN1, LANE 0
+3.3V
ACTIVITY CN1, LANE 1
+3.3V
ACTIVITY CN1, LANE 2
+3.3V
ACTIVITY CN1, LANE 3
Description
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
13
16
15
9
12
11
14
22-55-2161
Pin Number
5
8
7
10
●
●
J1:
Adaptec RAID 5805/5805Z Aggregate Activity LED Board Connector : Molex 22-28-4023 or equivalent
Aggregate LED Mating Cable Connector : Molex 50-57-9002 or equivalent
J1 Pin Number Signal
2 ACTIVITY
1 +3.3V
Description
LED Cathode
LED Anode
●
●
J12:
Adaptec RAID 5805/5805Z External Alarm Connector: Molex 22-28-4023 or equivalent
Alarm Mating Cable Connector: Molex 50-57-9002 or equivalent
J12 Pin Number Signal
2 ~2kHz Square Wave
1 +3.3V
Description
Open collector transistor
—
●
●
J4 :
Adaptec RAID 5805/5805Z I2C CN0 Board Connector : Molex 22-43-6030 or equivalent
I2C Mating Cable Connector: Molex 22-43-3030 or equivalent
●
●
2
1
J4 Pin Number
3
Signal
I2C Clock
Ground
I2C Data
Adaptec RAID 5805/5805Z I2C CN1 Board Connector : Molex 22-43-6030 or equivalent
I2C Mating Cable Connector: Molex 22-43-3030 or equivalent
Appendix F: Controller LED and I2C Connector Quick Reference ●
116
J5:
2
1
J5 Pin Number
3
Signal
I2C Clock
Ground
I2C Data
●
●
Adaptec RAID 5805 Status LED Board Connector: Molex 10-89-7162 or equivalent
Status LED Mating Cable Connector: Molex 22-55-2161 or equivalent
J14 (Adaptec RAID 5805 only):
10
11
12
7
8
5
6
9
13
14
15
16
2
3
4
J14 Pin Number
1
Signal
+3.3V
STATUS CN0, LANE 0
+3.3V
STATUS CN0, LANE 1
+3.3V
STATUS CN0, LANE 2
+3.3V
STATUS CN0, LANE 3
+3.3V
STATUS CN1, LANE 0
+3.3V
STATUS CN1, LANE 1
+3.3V
STATUS CN1, LANE 2
+3.3V
STATUS CN1, LANE 3
Description
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
8
7
6
5
10
9
12
11
14
13
16
15
1
4
3
22-55-2161
Pin Number
2
Adaptec RAID 51245 LED and I2C Connector Specification
2258400-R
2258300-R
ASR-51245 RoHS Kit
ASR-51245 RoHS Single
●
●
J3:
Adaptec RAID 51245 Activity LED Header Connector for CN0/CN1: Molex 10-89-7162 or equivalent
Activity LED Header Mating Cable Connector: Molex 22-55-2161 or equivalent
J3 Pin Number
1
2
Signal
+3.3V
ACTIVITY CN1, LANE 0
Description
LED Anode
LED Cathode
22-55-2161
Pin Number
2
1
Appendix F: Controller LED and I2C Connector Quick Reference ●
117
11
12
13
7
8
9
10
14
15
16
5
6
J3 Pin Number
3
4
Signal
+3.3V
ACTIVITY CN1, LANE 1
+3.3V
ACTIVITY CN1, LANE 2
+3.3V
ACTIVITY CN1, LANE 3
+3.3V
ACTIVITY CN0, LANE 0
+3.3V
ACTIVITY CN0, LANE 1
+3.3V
ACTIVITY CN0, LANE 2
+3.3V
ACTIVITY CN0, LANE 3
Description
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
● Adaptec RAID 51245 Activity LED Board Connector for CN2: Molex 10-89-7162 or equivalent
●
J1:
Activity LED Mating Cable Connector : Molex 22-55-2161 or equivalent
10
11
12
13
7
8
9
14
15
16
4
5
2
3
6
J1 Pin Number
1
Signal
Unused
Unused
Unused
Unused
Unused
Unused
Unused
Unused
+3.3V
ACTIVITY CN2, LANE 0
+3.3V
ACTIVITY CN2, LANE 1
+3.3V
ACTIVITY CN2, LANE 2
+3.3V
ACTIVITY CN2, LANE 3
Description
Unused
Unused
Unused
Unused
Unused
Unused
Unused
Unused
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
9
12
11
14
8
7
10
13
16
15
3
6
1
4
5
22-55-2161
Pin Number
2
12
11
14
8
7
10
9
13
16
15
6
5
22-55-2161
Pin Number
4
3
● Adaptec RAID 51245 Aggregate Activity LED Board Connector : Molex 22-28-4023 or equivalent
Appendix F: Controller LED and I2C Connector Quick Reference ●
118
●
J10:
Aggregate LED Mating Cable Connector : Molex 50-57-9002 or equivalent
J10 Pin Number
2
1
Signal
ACTIVITY
+3.3V
Description
LED Cathode
LED Anode
●
●
J12:
Adaptec RAID 51245 External Alarm Connector: Molex 22-28-4023 or equivalent
Alarm Mating Cable Connector: Molex 50-57-9002 or equivalent
J12 Pin Number Signal
2 ~2kHz Square Wave
1 +3.3V
Description
Open collector transistor
—
●
●
Adaptec RAID 51245 I2C Board Connector : Molex 22-43-6030 or equivalent
I2C Mating Cable Connector:
J28, J29, J30:
Molex 22-43-3030 or equivalent
2
1
J2 x Pin Number Signal
3 I2C Clock
Ground
I2C Data
Adaptec RAID 51645 LED and I2C Connector Specification
2258500-R
2258600-R
ASR-51645 RoHS Kit
ASR-51645 RoHS Single
●
●
J3:
Adaptec RAID 51645 Activity LED Header Connector for CN0/CN1: Molex 10-89-7162 or equivalent
Activity LED Header Mating Cable Connector: Molex 22-55-2161 or equivalent
5
6
7
2
3
J3 Pin Number
1
4
Signal
+3.3V
ACTIVITY CN1, LANE 0
+3.3V
ACTIVITY CN1, LANE 1
+3.3V
ACTIVITY CN1, LANE 2
+3.3V
Description
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
6
5
8
4
3
22-55-2161
Pin Number
2
1
Appendix F: Controller LED and I2C Connector Quick Reference ●
119
12
13
14
15
16
J3 Pin Number
8
9
10
11
Signal
ACTIVITY CN1, LANE 3
+3.3V
ACTIVITY CN0, LANE 0
+3.3V
ACTIVITY CN0, LANE 1
+3.3V
ACTIVITY CN0, LANE 2
+3.3V
ACTIVITY CN0, LANE 3
Description
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
11
14
13
16
15
22-55-2161
Pin Number
7
10
9
12
● Adaptec RAID 51645 Activity LED Board Connector for CN2/CN3 : Molex 10-89-7162 or equivalent
●
J1:
Activity LED Mating Cable Connector : Molex 22-55-2161 or equivalent
12
13
14
7
8
9
10
11
15
16
5
6
3
4
J1 Pin Number
1
2
Signal
+3.3V
ACTIVITY CN3, LANE 0
+3.3V
ACTIVITY CN3, LANE 1
+3.3V
ACTIVITY CN3, LANE 2
+3.3V
ACTIVITY CN3, LANE 3
+3.3V
ACTIVITY CN2, LANE 0
+3.3V
ACTIVITY CN2, LANE 1
+3.3V
ACTIVITY CN2, LANE 2
+3.3V
ACTIVITY CN2, LANE 3
Description
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
11
14
13
8
7
10
9
12
16
15
6
5
4
3
22-55-2161
Pin Number
2
1
●
●
Adaptec RAID 51645 Aggregate Activity LED Board Connector : Molex 22-28-4023 or equivalent
Aggregate LED Mating Cable Connector : Molex 50-57-9002 or equivalent
Appendix F: Controller LED and I2C Connector Quick Reference ●
120
J10:
J10 Pin Number
2
1
Signal
ACTIVITY
+3.3V
Description
LED Cathode
LED Anode
●
●
J12:
Adaptec RAID 51645 External Alarm Connector: Molex 22-28-4023 or equivalent
Alarm Mating Cable Connector: Molex 50-57-9002 or equivalent
J12 Pin Number Signal
2 ~2kHz Square Wave
1 +3.3V
Description
Open collector transistor
—
●
●
Adaptec RAID 51645 I2C Board Connector : Molex 22-43-6030 or equivalent
I2C Mating Cable Connector:
J27, J28, J29, J30 :
Molex 22-43-3030 or equivalent
2
1
J2 x Pin Number Signal
3 I2C Clock
Ground
I2C Data
Adaptec RAID 52445 LED and I2C Connector Specification
2258800-R
2258700-R
ASR-52445 RoHS Kit
ASR-52445 RoHS Single
● Adaptec RAID 52445 Activity LED Header Connector for CN0/CN1: Molex 10-89-7162 or equivalent
●
J3:
Activity LED Header Mating Cable Connector: Molex 22-55-2161 or equivalent
4
5
6
7
8
2
3
J3 Pin Number
1
Signal
+3.3V
ACTIVITY CN1, LANE 0
+3.3V
ACTIVITY CN1, LANE 1
+3.3V
ACTIVITY CN1, LANE 2
+3.3V
ACTIVITY CN1, LANE 3
Description
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
3
6
5
8
7
22-55-2161
Pin Number
2
1
4
Appendix F: Controller LED and I2C Connector Quick Reference ●
121
13
14
15
16
J3 Pin Number
9
10
11
12
Signal
+3.3V
ACTIVITY CN0, LANE 0
+3.3V
ACTIVITY CN0, LANE 1
+3.3V
ACTIVITY CN0, LANE 2
+3.3V
ACTIVITY CN0, LANE 3
Description
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
14
13
16
15
22-55-2161
Pin Number
10
9
12
11
● Adaptec RAID 52445 Activity LED Board Connector for CN2/CN3 : Molex 10-89-7162 or equivalent
●
J1:
Activity LED Mating Cable Connector : Molex 22-55-2161 or equivalent
13
14
15
8
9
10
11
12
16
6
7
4
5
2
3
J1 Pin Number
1
Signal
+3.3V
ACTIVITY CN3, LANE 0
+3.3V
ACTIVITY CN3, LANE 1
+3.3V
ACTIVITY CN3, LANE 2
+3.3V
ACTIVITY CN3, LANE 3
+3.3V
ACTIVITY CN2, LANE 0
+3.3V
ACTIVITY CN2, LANE 1
+3.3V
ACTIVITY CN2, LANE 2
+3.3V
ACTIVITY CN2, LANE 3
Description
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
14
13
16
7
10
9
12
11
15
5
8
3
6
22-55-2161
Pin Number
2
1
4
● Adaptec RAID 52445 Activity LED Header Connector for CN4/CN5: Molex 10-89-7162 or equivalent
●
J2:
Activity LED Header Mating Cable Connector: Molex 22-55-2161 or equivalent
J2 Pin Number
1
2
Signal
+3.3V
ACTIVITY CN4, LANE 0
Description
LED Anode
LED Cathode
22-55-2161
Pin Number
2
1
Appendix F: Controller LED and I2C Connector Quick Reference ●
122
11
12
13
7
8
9
10
14
15
16
5
6
J2 Pin Number
3
4
Signal
+3.3V
ACTIVITY CN4, LANE 1
+3.3V
ACTIVITY CN4, LANE 2
+3.3V
ACTIVITY CN4, LANE 3
+3.3V
ACTIVITY CN5, LANE 0
+3.3V
ACTIVITY CN5, LANE 1
+3.3V
ACTIVITY CN5, LANE 2
+3.3V
ACTIVITY CN5, LANE 3
Description
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
12
11
14
8
7
10
9
13
16
15
6
5
22-55-2161
Pin Number
4
3
● Adaptec RAID 52445 Aggregate Activity LED Board Connector : Molex 22-28-4023 or equivalent
●
J10:
Aggregate LED Mating Cable Connector : Molex 50-57-9002 or equivalent
J10 Pin Number
2
1
Signal
ACTIVITY
+3.3V
Description
LED Cathode
LED Anode
●
●
J12:
Adaptec RAID 52445 External Alarm Connector: Molex 22-28-4023 or equivalent
Alarm Mating Cable Connector: Molex 50-57-9002 or equivalent
J12 Pin Number Signal
2 ~2kHz Square Wave
1 +3.3V
Description
Open collector transistor
—
●
●
Adaptec RAID 52445 I2C Board Connector : Molex 22-43-6030 or equivalent
I2C Mating Cable Connector:
J25, J26, J27, J28, J29, J30:
Molex 22-43-3030 or equivalent
2
1
J2 x Pin Number Signal
3 I2C Clock
Ground
I2C Data
Appendix F: Controller LED and I2C Connector Quick Reference ●
123
Adaptec RAID 2045 LED Connector Specification
●
●
J1:
Adaptec RAID 2045 Aggregate Activity LED Board Connector : Molex 22-28-4023 or equivalent
Aggregate LED Mating Cable Connector : Molex 50-57-9002 or equivalent
J1 Pin Number Signal
2 ACTIVITY
1 +3.3V
Description
LED Cathode
LED Anode
Adaptec RAID 2405 LED and I2C Connector Specification
2260100-R
2260200-R
ASR-2405 RoHS KIT
ASR-2405 RoHS SGL
●
●
J2:
Adaptec RAID 2405 Activity LED Header Connector: Molex 10-89-7082 or equivalent
Activity LED Header Mating Cable Connector: Molex 22-55-2081 or equivalent
5
6
3
4
7
J2 Pin Number
1
2
8
Signal
+3.3V
ACTIVITY CN0, LANE 0
+3.3V
ACTIVITY CN0, LANE 1
+3.3V
ACTIVITY CN0, LANE 2
+3.3V
ACTIVITY CN0, LANE 3
Description
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
LED Anode
LED Cathode
6
5
4
3
8
22-55-2161
Pin Number
2
1
7
● Adaptec RAID 2405 Aggregate Activity LED Board Connector : Molex 22-28-4023 or equivalent
●
J1:
Aggregate LED Mating Cable Connector : Molex 50-57-9002 or equivalent
J1 Pin Number Signal
2 ACTIVITY
1 +3.3V
Description
LED Cathode
LED Anode
Appendix F: Controller LED and I2C Connector Quick Reference ●
124
●
●
J4:
Adaptec RAID 2405 I2C Board Connector : Molex 22-43-6030 or equivalent
I2C Mating Cable Connector: Molex 22-43-3030 or equivalent
2
1
J4 Pin Number
3
Signal
I2C Clock
Ground
I2C Data
Safety Information
G
To ensure your personal safety and the safety of your equipment:
● Keep your work area and the computer clean and clear of debris.
● Before opening the system cabinet, unplug the power cord.
Electrostatic Discharge (ESD)
!
Caution: ESD can damage electronic components when they are improperly handled, and can result in total or intermittent failures. Always follow ESD-prevention procedures when removing and replacing components.
To prevent ESD damage:
● Use an ESD wrist or ankle strap and ensure that it makes skin contact. Connect the equipment end of the strap to an unpainted metal surface on the chassis.
If a wrist strap is not available, ground yourself by touching the metal chassis before handling the controller or any other part of the computer.
●
●
●
●
Avoid touching the controller against your clothing. The wrist strap protects components from ESD on the body only.
Handle the controller by its bracket or edges only. Avoid touching the printed circuit board or the connectors.
Put the controller down only on an antistatic surface such as the bag supplied in your kit.
If you are returning the controller to Adaptec, put it back in its antistatic bag immediately.
Technical Specifications
H
In this appendix...
Appendix H: Technical Specifications ●
127
Environmental Specifications
Note: With a Battery Backup Unit (BBU), the ambient temperature should not exceed 40 °C
Ambient temperature without forced airflow 0 °C to 40 ° C
Ambient temperature with forced airflow 0 °C to 55 ° C
Relative humidity
Altitude
10% to 90% , noncondensing
Up to 3,000 meters
Note: Forced airflow is recommended.
DC Power Requirements
Bus Type
PCIe
PCIe
Current Requirements
Description
Ripple and noise
DC Voltage
Adaptec Model
Adaptec RAID 5085
Adaptec RAID 5805
Adaptec RAID 5405
Adaptec RAID 5445
Adaptec RAID 5805Z
Adaptec RAID 5405Z
Adaptec RAID 5445Z
Adaptec RAID 51245
Adaptec RAID 51645
Adaptec RAID 52445
Adaptec RAID 2045
Adaptec RAID 2405
Requirements
50 mV peak-to-peak (max)
3.3 V ± 9%, 12 V ± 8%
Typical Current
0.45 A @ 3.3 VDC; 1.0 A @ 12.0 VDC
0.45 A @ 3.3 VDC; 1.0 A @ 12.0 VDC
0.45A @ 3.3VDC; 0.94A @ 12.0VDC
0.45A @ 3.3VDC; 1.0A @ 12.0VDC
0.39 A @ 3.3 VDC; 1.21 A @ 12.0 VDC
0.38 A @ 3.3 VDC; 1.18 A @ 12.0 VDC
0.40 A @ 3.3 VDC; 1.24 A @ 12.0 VDC
0.47A @ 3.3VDC; 1.68A @ 12.0VDC
0.47A @ 3.3VDC; 1.72A @ 12.0VDC
0.47A @ 3.3VDC; 1.78A @ 12.0VDC
0.43A @ 3.3VDC; 0.83A @ 12.0VDC
0.43A @ 3.3VDC; 0.83A @ 12.0VDC
A activity LED connector specifications
arrays
creating arrays
creating bootable arrays
initializing disk drives
managing arrays
rescanning disk drives
secure erasing disk drives
stopping a secure erase
ACU for DOS
array definition block keywords
creating a floppy disk
menus
playback mode
record mode
sample scripts
script file syntax
scripts
switches
Adaptec customer support
AFU
Adaptec RAID Configuration utility
,
Adaptec RAID Controller Configuration utility. See
ARCCONF
Adaptec Storage Manager
creating arrays
installing
See controllers advanced data protection
AFU
Alarm Control setting
ARCCONF
Index
Array Background Consistency Check setting
See ACU array definition block
End keyword
HotspareDrives keyword
array migration
Array-based BBS Support setting
arrays creating (ACU)
creating (Adaptec Storage Manager)
creating bootable arrays
making an array bootable
managing with ACU
non-redundant
RAID 1
RAID 10
RAID 1E
RAID 5
RAID 50
RAID 5EE
RAID 6
RAID 60
arrays (bootable)
audible alarm
automatic failover
Automatic Failover setting
B backplane connections
battery backup module
batteryless backup
BBU
controllers boot controller
Index ●
129 bootable arrays
creating
C
See controllers
CD-ROM Boot Support setting
command line interface (flash utility)
command line utility
connectors
contents of controller kit
controllers activity LED connector specifications
Alarm Control setting
Array Background Consistency Check setting
Array-based BBS Support setting
array-level features
Automatic Failover setting
CD-ROM Boot Support setting
connecting disk drives
connecting external devices
CRC Checking setting
data protection
descriptions
disk drives
Drive’s Write Cache setting
event log
figures
firmware
flashing
I2C connector specifications
installation options
installing
modifying general settings
modifying settings with Serial Select
modifying with Serial Select
Phy Rate setting
Physical Drives Display During POST setting
RAID levels
Removable Media Devices Boot Support setting
resetting
Runtime BIOS setting
SAS Address setting
SAS cables
setting boot controller
specifications
troubleshooting
updating firmware
upgrading firmware
copyback
CRC Checking setting
customer support
D direct-attach connections
disk drives
connecting to controllers
connections
external
failure recovery multiple arrays
multiple disk drives
RAID 0 arrays
with hot spare
without hot spare
formatting
identifying
initializing
recovering from failure
rescanning
SAS identifiers
secure erasing
stopping a secure erase
types of connections
verifying
drive requirements
Drive’s Write Cache setting
driver and operating system installation
driver disk
driver installation
to
drivers installing on FreeBSD
installing on Linux
installing on OpenServer
installing on Solaris
installing on UnixWare
installing on VMWare
installing on Windows
installing with FreeBSD
installing with Linux
installing with OpenServer
installing with UnixWare
installing with VMWare
installing with Windows
E electrostatic discharge
end devices
End property
event log
expander connections
Index ●
130 expander devices
external devices
F failed disk drives
multiple arrays
multiple disk drives
RAID 0 arrays
without hot spare
firmware
creating floppy disks
firmware upgrades
flashing controllers
floppy disks for firmware update
formatting disk drives
FreeBSD driver installation
OS installation
H
hard disk, hard disk drive, hard drive.
See disk drive hot spares
HotspareDrives keyword array definition block
I
I2C connector specifications
initializing disk drives
installation backplane
controllers
creating a driver disk
direct-attach
disk drives
driver
driver and FreeBSD
driver and Linux
driver and OpenServer
driver and operating system
driver and UnixWare
driver and VMWare
driver and Windows
existing operating system
external devices
installation options
with operating system
K kit contents
L
LED connector specifications
LED Indication Mode
Linux driver installation
OS installation
Linux installation
M mini-SAS direct connection
enclosure cable
internal cable
overview
SAS to SATA cable
mirroring
mode 0 flash
N
NCQ
non-redundant arrays
O online expansion
OpenServer driver installation
OS installation
operating system installation
operating systems
P parity
Phy Rate setting
phys
Physical Drives Display During POST setting
playback mode
R
non-redundant arrays
RAID 0
RAID 1
RAID 10
RAID 1E
RAID 5
RAID 50
RAID 5EE
RAID 6
RAID 60
See controllers
RAID levels
record mode
recovering from disk drive failure
Red Hat driver installation
OS installation
Redundant Array of Independent Disks. See
RAID
Removable Media Devices Boot Support setting
replacing failed disk drives
requirements
drive
rescanning disk drives
resetting controllers
Runtime BIOS setting
S safety information
4-wide ports
backplane connections
cables
comparison to parallel SCSI
connectors
description
direct-attach connections
disk drives
edge expanders
end devices
expander connections
expander devices
fanout expanders
link speed
links
narrow connectors
narrow ports
phys
ports
SAS address
SAS cards
SAS devices
SAS domain
terminology
transceivers
wide connectors
wide ports
SAS Address setting
SAS devices
SAS disk drive identifiers
scripts in ACU for DOS
Index ●
131 secure erasing disk drives
stopping a secure erase
Selectable Performance Mode
See SAS
Serial Select
applying changes
exiting
modifying controller settings
opening
software
Solaris driver installation
specifications
storage management
Adaptec RAID Configuration utility
Adaptec Storage Manager
AFU
ARCCONF
storage space
support, customer
SUSE driver installation
SUSE installation
switches in ACU for DOS
system requirements
T technical specifications
technical support
Technical Support Identification (TSID) number
terminology
SAS
tools
Adaptec RAID Configuration utility
Adaptec Storage Manager
AFU
ARCCONF
troubleshooting tips
TSID Number
See Technical Support Identification Number
U
UnixWare driver installation
OS installation
updating firmware
upgrading firmware
utilities
Adaptec RAID Controller utility
AFU
ARCCONF
V verifying disk drives
VMWare driver installation
OS installation
W
Windows driver installation
OS installation
Z zero maintenance cache protection
zero maintenance module (ZMM)
zero maintenance module
Index ●
132
Adaptec, Inc.
691 South Milpitas Boulevard
Milpitas, CA 95035 USA
©2009 Adaptec, Inc.
All rights reserved. Adaptec and the Adaptec logo are trademarks of Adaptec, Inc. which may be registered in some jurisdictions.
Part Number: CDP-00243-03-A Rev. A
JB 06/09
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement