advertisement
SAS, SATA, and SCSI
RAID Controllers
Installation and User’s Guide
●
2
Copyright
©2005-2006 ICP vortex. 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 ICP vortex Computersysteme GmbH, Konrad-Zuse-Str.9, 74172 Neckarsulm, Germany.
Trademarks
ICP vortex, the ICP vortex logo, and ICP Storage Manager, are trademarks of ICP vortex. Adaptec and the Adaptec logo are trademarks of Adaptec, Inc.,which may be registered in some jurisdictions.
Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation in the US and other countries, used under license.
All other trademarks are the property of their respective owners.
Changes
The material in this document is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy, ICP vortex assumes no liability resulting from errors or omissions in this document, or from the use of the information contained herein.
ICP 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
ICP vortex Customer Support
If you have questions about installing or using your ICP product, check this document and the Readme files on the CD first — you will find answers to most of your questions here. If you need further assistance, use the support options listed below.
Technical Support Identification (TSID) Number
● Before contacting Technical Support, you need your unique 12-digit TSID number. The TSID number identifies your product and support status.
● 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.
Support Options
●
●
For support via Email or phone, contact the ICP Technical Support Specialists at [email protected],
+49-(0)7132-9620-900.
For sales information via Email or phone, contact the ICP sales department at [email protected]
, +49-(0)7132-9620-800.
Mailing Address
ICP vortex Computersysteme GmbH
Konrad-Zuse-Str.9
74172 Neckarsulm
Germany
Phone
Phone: +49-(0)7132-9620-0
Fax: +49-(0)7132-9620-200
Web Sites http://www.icp-vortex.com
http://www.vortex.de
●
4
Limited 3-Year Hardware Warranty
1. ICP vortex (“ICP”) 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, ICP, 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 ICP service facility or to ICP.
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 ICP. 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 ICP service facility or to ICP 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 ICP at
Konrad-Zuse-Str. 9, D-74172 Neckarsulm, Germany, +49-7132-9620-900.
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 ICP 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.
ICP vortex ICP9085LI / ICP5085BR / ICP9047MA
ICP9087MA / ICP9014RO / ICP9024RO
ICP5445AU / ICP5085AU
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) Emissions
● EN55024 (1998) Immunity:
– EN61000-4-2 (1998) Electrostatic discharge: ±4 kV contact, ±8 kV air
– EN61000-4-3 (1998) 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.
Contents
About This Guide
What You Need to Know Before You Begin ................................................... 12
Kit Contents and System Requirements
About Your RAID Controller
Advanced Data Protection Suite ................................................................ 17
Getting Started
Disk Drives for SAS Controllers................................................................. 29
Disk Drives for SATA Controllers ............................................................. 29
Disk Drives for SCSI Controllers ............................................................... 29
Contents ●
7
Installing with an Operating System.......................................................... 32
Installing on an Existing Operating System .............................................. 32
Installing the Controller and Disk Drives
Connecting Disk Drives to SAS RAID Controllers ......................................... 35
Connecting Directly to the Controller....................................................... 35
Connecting to a System Backplane ............................................................ 37
Connecting Disk Drives to SATA RAID Controllers ...................................... 37
Connecting Disk Drives to SCSI RAID Controllers........................................ 38
Monitoring Disk Drives with ICP Storage Manager....................................... 39
Creating a Bootable Array
Creating an Array with the ACU ............................................................... 41
Creating an Array with ICP Storage Manager........................................... 43
Installing the Driver and an Operating System
Installing the Driver on an Existing Operating System
Contents ●
8
Managing Your Storage Space
Installing ICP Storage Manager ................................................................. 57
About the Adaptec RAID Controller Configuration Utility........................... 57
About the ICP RAID Configuration Utility .................................................... 58
Solving Problems
Failed Disk Drive Protected by a Hot Spare .............................................. 61
Failed Disk Drive Not Protected by a Hot Spare ....................................... 61
Failure in Multiple Arrays Simultaneously................................................ 61
Disk Drive Failure in a RAID 0 Array........................................................ 61
Multiple Failures in the Same Array .......................................................... 62
Introduction to Serial Attached SCSI
How Do SAS Devices Communicate?.............................................................. 65
How are Disk Drives Identified in SAS? .......................................................... 67
What are the SAS Connection Options?.......................................................... 67
SAS Expander Connections........................................................................ 68
How is SAS Different from Parallel SCSI? ....................................................... 69
Contents ●
9
Understanding RAID
Using the ICP RAID Configuration Utility
Introduction to the ICP RAID Configuration Utility..................................... 80
Running the ICP RAID Configuration Utility ................................................ 80
Navigating the ICP RAID Configuration Utility ...................................... 80
Using the ACU to Create and Manage Arrays................................................. 80
Using the -Select Utility to Modify Controller Settings .................................. 82
Applying Changes and Exiting................................................................... 82
Modifying Your Controller’s Configuration............................................. 83
SAS-specific Controller Settings ................................................................ 84
SATA-specific Controller Settings ............................................................. 84
SCSI-specific Controller Settings ............................................................... 85
Formatting and Verifying Disk Drives............................................................. 86
Using the Array Configuration Utility for DOS
Working in the ACU Using Menus.................................................................. 88
Creating the Script File Manually .............................................................. 90
Array Definition Block Keywords.............................................................. 91
Channel Definition Block Keywords—SCSI only..................................... 94
Contents ●
10
Using the ICP Flash Utility
Creating the Firmware Floppy Disks ....................................................... 100
Running the IFU from the Command Line .................................................. 101
Updating the Flash Using the IFU Command Line ...................................... 104
Safety Information
Technical Specifications
Index
About This Guide
1
In this chapter...
This Installation and User’s Guide explains how to install your ICP 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:
SAS Controllers
ICP5445AU
ICP5085AU
ICP5085BR
ICP9085LI
SATA Controllers
ICP9047MA
ICP9087MA
SCSI Controllers
ICP9014RO
ICP9024RO
Chapter 1: About This Guide ●
12
What You Need to Know Before You Begin
You should be familiar with computer hardware, data storage, RAID technology, and the input/output (I/O) technology—Small Computer System Interface (SCSI), SAS, or Serial ATA
(SATA)—used by your controller. (For an introduction to SAS, see page 63
.)
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 ICP 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 16
.
Terminology Used in this Guide
Because you can use your ICP 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 ICP 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, ICP Storage Manager refers to arrays as logical drives. Why?
Your RAID controller creates arrays, which your operating system (and ICP Storage
Manager) recognizes as logical drives.
In NAS environments, ICP Storage Manager displays both arrays and logical drives. For more information, refer to the ICP Storage Manager User’s Guide on the ICP Storage
Manager Installation CD.
How to Find More Information
You can find more information about your ICP 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.
ICP Storage Manager User’s Guide—Describes how to install and use the ICP Storage
Manager software (see page 57 ); located on the ICP Storage Manager Installation CD.
ICP Storage Manager online Help—Describes how to use the ICP Storage Manager software; accessible from the main window of ICP Storage Manager.
Command Line Utility User’s Guide—Describes how to use the Adaptec RAID Controller
Configuration (ARCCONF) command line utility (see
) to perform basic array and configuration management functions; located on the ICP Storage Manager Installation
CD.
Kit Contents and System
Requirements
2
In this chapter...
This chapter lists the contents of your ICP 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
● ICP RAID controller
●
●
●
●
●
RAID Installation CD (bootable), including controller drivers, and this Guide
ICP Storage Manager Installation CD (not bootable), including user guides for ICP
Storage Manager and the ARCCONF command line utility
Cables (type and quantity vary—for cable information about your controller, visitthe ICP
Web site at www.icp-vortex.com
or the Adaptec Web site at www.adaptec.com
.)
(Selected models only) Low-profile bracket
ICP SAS, SATA, and SCSI RAID Controllers Quick Start Guide
System Requirements
● PC-compatible computer with Intel Pentium, or equivalent, processor
●
●
Motherboard with these features:
●
Compliant with PCI Local Bus Specification, Revision 2.2 or later
●
●
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
®
2000, Windows Server 2003, Windows XP
●
Red Hat
®
Linux
●
SUSE Linux
●
●
●
●
●
Note: For the latest on ICP’s support of Linux, or to download driver sources, visit the
Support area of the ICP Web site at www.icp-vortex.com
.
Novell
®
NetWare
®
6.5
SCO
®
OpenServer
®
6.0
UnixWare
®
7.1.4
Sun
®
Solaris TM 10 (supports secondary controllers only, not boot controller; storage
management must be done through theICP RAID Configuration utility—see page 80 )
FreeBSD 5.4, 6.0 (driver support only; storage management must be done through the
ICP RAID Configuration utility—see page 80 )
Note: For up-to-date operating system version support, visit the ICP Web Site at www.icpvortex.com. From the main menu select Download>firmware, drivers, tools. Select your controller type and version to generate a list of supported operating systems.
●
●
128 MB (or more) of RAM
Available compatible PCI/PCI-X/PCIe slot (depending on your controller model—see the descriptions starting on
Chapter 2: Kit Contents and System Requirements ●
15
●
●
●
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 ICP RAID controller features, and describes the unique features of your controller. It also explains how to upgrade your controller with enhanced features.
Chapter 3: About Your RAID Controller ●
17
Standard RAID Controller Features
● Flash ROM for updates to controller firmware, BIOS, and the ICP 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
(ICP Storage Manager), a BIOS-based utility, a command line utility, and a DOS utility.
See
Managing Your Storage Space on page 56
for more information.
(SAS and SATA RAID controllers only) Native command queuing (NCQ), which lets disk drives arrange commands into the most efficient order for optimum performance
(SATA and SCSI RAID controllers only) Support for disk drive enclosures with SAF-TE enclosure management hardware
(SAS RAID controllers only) Support for disk drive enclosures with SES2 enclosure management hardware
Some RAID controllers support adding a battery backup module (see
●
Array-level Features
Note: For more information, refer to the ICP 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 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
● Snapshots—You can use this feature to move data from a hot spare back to its original location after a disk drive failure.
●
●
●
●
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.
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.
*
The ICP9047MA RAID controller does not support RAID 50 or RAID 60.
Chapter 3: About Your RAID Controller ●
18
● Dual Drive Failure Protection (RAID 60
1
)—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 ICP RAID controller.
RAID Controller
ICP5445AU
ICP5085AU
ICP9085LI / ICP5085BR
ICP9087MA
ICP9014RO / ICP9024RO
Battery Model
Adaptec Battery Module 700
Adaptec Battery Module 700
Adaptec Battery Module 600
Adaptec Battery Module 500
Adaptec Battery Module 400
To purchase a battery backup module, refer to the ICP Web site at www.icp-vortex.com
or the
Adaptec Web site at www.adaptec.com
.
Upgrading the Controller Firmware
To upgrade the firmware on your ICP RAID controller, follow the instructions in
Chapter 3: About Your RAID Controller ●
19
About the ICP5445AU
The ICP5445AU is a low-profile SAS RAID controller with these features:
Activity LED connector
Alarm connector
1 internal mini-SAS connector
Battery connector
Mode 0 Flash connector
PCIe connector
1 external mini-SAS connector
Bus compatibility PCIe x8
I/O processor clock frequency 250 MHz
Standard cache 256 MB DDR2
Maximum number of disk drives 8 (or up to 128 with expanders)
External Connector mini-SAS 4x multilane (SFF-8088)
Internal Connector
Battery backup module
Audible alarm mini-SAS 4x multilane (SFF-8087)
Adaptec Battery Module 700 (sold separately—see page 18 )
Yes
Chapter 3: About Your RAID Controller ●
20
About the ICP5085AU
The ICP5085AU is a SAS RAID controller with these features:
Activity LED connector (for individual ports)
Sum Activity LED connector
2 internal mini-SAS connectors
I2C connectors
Battery connector
Mode 0 Flash connector
Alarm connector
Mounting bracket
PCIe connector
Bus compatibility PCIe x8
I/O processor clock frequency 250 MHz
Standard cache 256 MB DDR2
Maximum number of disk drives 8
Internal Connector 2x mini-SAS 4x multilane (SFF-8087)
Battery backup module
Audible alarm
Adaptec Battery Module 700 (sold separately—see
Yes
Chapter 3: About Your RAID Controller ●
21
About the ICP9085LI
The ICP9085LI is a SAS RAID controller with these features:
Alarm connector
Mounting bracket
Two 4-wide internal
SAS connectors
Mode 0 Flash connector
Activity LED connector
(top 2 left/right pins)
1 external
SAS connector
Battery connector
PCI-X connector
Bus compatibility
Maximum bus width
PCI-X
64-bit
Maximum bus speed 133 MHz
I/O processor clock frequency 800 MHz
Standard cache 256 MB DDR2
Maximum number of disk drives 8 (or up to 128 with expanders)
External Connector
Internal Connector mini-SAS 4x multilane (SFF-8470)
2x SAS 4x multilane (SFF-8484)
Forced airflow required
Battery backup module
Audible alarm
400 lfm (= 2.2 m/sec)
Adaptec Battery Module 600 (sold separately—see
Yes
Note: Although this controller has an onboard speaker, you can connect it to an internal speaker with these specifications: 3.0 V, 90.0 mA. The internal speaker is not required, as the onboard speaker volume is appropriate for most environments.
Chapter 3: About Your RAID Controller ●
22
About the ICP5085BR
The ICP5085BR is a SAS RAID controller with these features:
Alarm connector
Mounting bracket
Two 4-wide internal
SAS connectors
Mode 0 Flash connector
Activity LED connector
(top 2 left/right pins)
1 external
SAS connector
PCIe connector
Battery connector
Bus compatibility PCIe x8
I/O processor clock frequency 800 MHz
Standard cache 256 MB DDR2
Maximum number of disk drives 8 (or up to 128 with expanders)
External Connector mini-SAS 4x multilane (SFF-8470)
Internal Connector
Forced airflow required
2x SAS 4x multilane (SFF-8484)
400 lfm (= 2.2 m/sec)
Battery backup module
Audible alarm
Adaptec Battery Module 600 (sold separately—see page 18 )
Yes
Note: Although this controller has an onboard speaker, you can connect it to an internal speaker with these specifications: 3.0 V, 90.0 mA. The internal speaker is not required, as the onboard speaker volume is appropriate for most environments.
About the ICP9047MA
The ICP9047MA is a SATA II RAID controller with these features:
Activity LED connector
0
SATA ports
1
2
3
Mode 0 Flash connector
LED connector
I2C connector
Chapter 3: About Your RAID Controller ●
23
Mounting bracket
Battery connector
PCI-X connector
Bus compatibility PCI-X, 3.3 V
Bus width
Bus speed
64-bit
133 MHz
Standard cache 256 MB
Maximum number of disk drives 4
Internal Connector 4x SATA connector
Battery backup module
Audible alarm
Adaptec Battery Module 500 (sold separately—see page 18 )
Yes
Note: A low-profile bracket is included with this controller. However, this controller may not fit in all low-profile systems.
Chapter 3: About Your RAID Controller ●
24
About the ICP9087MA
The ICP9087MA is a SATA II RAID controller with these features:
3
Activity LED connector
4
5
SATA ports
6
7
1
2
0
Mode 0 Flash connector
LED connectors
I2C connector
Battery connector
PCI-X connector
Mounting bracket
Bus compatibility
Bus width
Bus speed
Standard cache
Maximum number of disk drives 8
PCI-X, 3.3 V
64-bit
133 MHz
256 MB
Internal Connector
Battery backup module
Audible alarm
8x SATA connector
Adaptec Battery Module 500 (sold separately—see
Yes
Note: A low-profile bracket is included with this controller. However, this controller may not fit in all low-profile systems.
Chapter 3: About Your RAID Controller ●
25
About the ICP9014RO
The ICP9014RO is a low-profile SCSI controller with these features:
Mode 0 Flash connector
1 internal HD SCSI connector
Battery connector
Mounting bracket
1 external VHDCI
SCSI connector
PCI/PCI-X connector
Bus compatibility
Maximum bus width
Maximum bus speed
Standard cache
PCI / PCI-X, 3.3 V
64-bit
133 MHz
256 MB
Number of channels 1
Maximum number of disk drives 15
Battery backup module
Audible alarm
Adaptec Battery Module 400 (sold separately—see page 18 )
Yes
Chapter 3: About Your RAID Controller ●
26
About the ICP9024RO
The ICP9024RO is a low-profile SCSI controller with these features:
Mode 0 Flash connector
2 internal HD SCSI connectors
Battery connector
2 external
VHDCI SCSI connectors
Mounting bracket
PCI/PCI-X connector
Bus compatibility
Maximum bus width
Maximum bus speed
Standard cache
Number of channels
PCI / PCI-X, 3.3 V
64-bit
133 MHz
256 MB
2
Maximum number of disk drives 30 (15 per channel)
Battery backup module
Adaptec Battery Module 400 (sold separately—see page 18 )
Audible alarm Yes
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 ICP controller and disk drives, and creating arrays for data storage.
Note: Before you begin, familiarize yourself with your ICP controller’s physical features and the
RAID levels that it supports (see About Your RAID Controller on page 16 ).
Chapter 4: Getting Started ●
28
Choosing a RAID Level
This section provides a brief overview of the RAID levels supported by your ICP RAID controller, including the minimum and maximum number of disk drives required by each.
●
●
●
●
●
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 72
).
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 75
).
●
●
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 76
).
●
●
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
1
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.
*
Because it s four disk drives only, the ICP9047MA RAID controller can’t support RAID 50 or RAID 60.
Chapter 4: Getting Started ●
29
Selecting 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, refer to the ICP Storage Manager User’s Guide or online Help.
Disk Drives for SAS Controllers
Your SAS controller supports both SAS and SATA disk drives. For cable information, see page 30
.
Disk Drives for SATA Controllers
Your SATA controller supports SATA disk drives only. You need one SATA port for each disk drive you are connecting to your SATA controller.
Disk Drives for SCSI Controllers
Your SCSI controller supports Ultra320 SCSI disk drives. It also supports Ultra2 or higher
SCSI disk drives and peripherals, but at performance levels less than Ultra320. ICP does not recommend using SCSI disk drives or peripherals older than Ultra2.
Note: High-voltage Differential (HVD) disk drives are not supported and will damage your controller.
If you are mixing single-ended (SE) disk drives with Low-voltage Differential (LVD) disk drives:
● Ensure proper termination by using a cable (like the one included in the kit) with a builtin multimode terminator and proper adapters.
●
●
Disable termination on all the SE disk drives.
Put LVD and SE disk drives on separate channels for the best performance.
Note: If you mix SE and Ultra320 disk drives on the same channel, the performance of the
Ultra320 disk drives is reduced to SE levels.
Chapter 4: Getting Started ●
30
Selecting Cables
This section describes the cable options and requirements for your ICP controller:
●
●
●
For SAS cables, see this page.
SATA cables, see
SCSI cables, see
SAS Cables
You need one SAS cable for each disk drive you are connecting to your ICP SAS RAID controller.
Depending on your requirements, you can use any of these cables:
External cable (SFF-8470 to SFF-8470)—Connects to an external SAS enclosure.
External mini-SAS (SFF-8088 to SFF-8470)—Connects to an external SAS enclosure.
Internal cable (SFF-8484)—Connects to a backplane.
Internal fan-out cable (SFF-8484 to 4x SATA)—
Connects to four internal SATA disk drives.
(SAS-to-SAS fan-out cables—not shown—are also available.)
Internal mini-SAS with power (SFF-8087 to SFF-8482)—
Connects to four SAS or SATA disk drives.
Chapter 4: Getting Started ●
31
Internal mini-SAS to SATA fan-out (SFF-8087 to 4x SATA)—
Connects to four SATA disk drives.
Cable connectors are keyed so that you can’t insert them incorrectly.
ICP recommends using only high quality SAScables. For more information or to purchase cables, visitthe ICP Web site at www.icp-vortex.com
or the Adaptec Web site at www.adaptec.com
.
SATA Cables
You need one straight connector to straight connector SATA cable for each disk drive you are connecting to your ICP SATA RAID controller. SATA cables are included in the kit.
All SATA straight connector to straight connector cables have the same connectors, as shown in the following figure, and the connectors are keyed so that you can’t insert them incorrectly.
ICP recommends using onlyhigh quality SATA cables. For more information or to purchase cables, visitthe ICP Web site at www.icp-vortex.com
or the Adaptec Web site at www.adaptec.com
.
SCSI Cables
Depending on your requirements, you may need one or two internal cables. You may also need one external SCSI cable. Ensure that you have cables with the proper connectors for your
RAID controller. One internal SCSI cable is included in the kit.
Internal SCSI cable—Connects to up to seven internal SCSI disk drives and devices.
External SCSI cable—Connects to an external SCSI disk drive or device.
ICP recommends using only high-quality Ultra320-rated cables with multimode terminators for all disk drives that share a channel with Ultra320 disk drives. Avoid poor quality cables, as they may degrade reliability. Do not use cables not rated for Ultra320 operation.
Chapter 4: Getting Started ●
32
ICP recommends using only ICP SCSI cables. For more information or to purchase cables, visitthe ICP Web site at www.icp-vortex.com
or the Adaptec Web site at www.adaptec.com
.
Installation Options
When you install your ICP 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.
Basic Installation Steps
This section describes the installation process. Follow the steps for the installation option you’ve chosen.
Installing with an Operating System
Note: Solaris users only—Because you cannot use your ICP RAID controller as a boot controller, to successfully install and use your controller you must follow the steps in
on an Existing Operating System on page 32
.
2
3
4
5
1 Install and connect your controller and internal disk drives (see
If your controller has an external connector, you can connect external disk drives as well
(or instead).
Set the boot controller (see page 41
).
Create a bootable array (see
Install your operating system and the controller driver (see page 45
.)
Install ICP Storage Manager and begin to manage your data storage (see page 56 ).
Note: Currently, ICP Storage Manager is not supported on FreeBSD or Solaris. To create and manage arrays, use the ICP RAID Configuration
for more information.
Installing on an Existing Operating System
1 Install and connect your controller and internal disk drives (see
2
If your controller has an external connector, you can connect external disk drives as well
(or instead).
Install the controller driver (see
3
Install ICP Storage Manager and begin to manage your data storage (see page 56 ).
Note: Currently, ICP Storage Manager is not supported on FreeBSD or Solaris. To create and manage arrays, use the ICP RAID Configuration
for more information.
Installing the Controller and Disk
Drives
5
In this chapter...
This chapter explains how to install your ICP RAID controller, and how to install and connect internal and external disk drives.
Chapter 5: Installing the Controller and Disk Drives ●
34
Before You Begin
●
Read Safety Information on page 105 .
●
●
●
●
Familiarize yourself with your ICP RAID controller’s physical features and the RAID levels
).
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 ICP RAID controller into your computer cabinet.
1
2
Turn off your computer and disconnect the power cord. Open the cabinet, following the manufacturer’s instructions.
Select an available PCI/PCIe/PCI-X expansion slot that’s compatible with your RAID controller and remove the slot cover, as shown at right. (PCI bus compatibility is marked on the controller figures in
About Your RAID Controller on page
For the best performance, use the fastest available PCI slot that’s compatible with your RAID controller.
!
Caution: Touch a grounded metal object before handling the RAID controller.
3
4
5
6
7
As shown at right, insert the RAID controller into the PCI 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 PCI/PCIe/PCI-X 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 16
).
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.
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.
Prepare and install your internal disk drives, following the instructions for your type of controller:
●
For SAS RAID controllers, see
Chapter 5: Installing the Controller and Disk Drives ●
35
●
●
For SATA RAID controllers, see
For SCSI RAID controllers, see
If you are not installing internal disk drives, close your computer cabinet, reattach the
power cord, then continue with Connecting External Devices on page 38 .
Connecting Disk Drives to SAS RAID Controllers
You can connect SAS disk drives, SATA disk drives, or a combination of both to your SAS
RAID controller. 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 28
for more information.
Note: Although you can connect both SAS and SATA disk drives to your SAS controller, ICP 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 37
.
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 67 .)
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 ●
36
2 Use internal SAS or mini-SAS cables to attach the disk drives to the controller.
SAS fan-out cable
4-wide internal SAS connector
SAS/SATA disk drives
Single-port connector External SAS connector
External SAS cable
Mini-SAS to SATA fan-out cable
SAS/SATA disk drives
Internal mini-SAS connectors
Single-port connector
2 internal mini-SAS connectors
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
Chapter 5: Installing the Controller and Disk Drives ●
37
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 67
.)
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.
Disk drives on backplane
Controller connected to backplane with fan-out cable
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 38
.
Connecting Disk Drives to SATA RAID Controllers
1 Install your SATA disk drives, following the instructions in your system’s documentation.
There are no jumpers or switches to set on the SATA controller or disk drives.
2
3
Connect each disk drive to a SATA port on the controller using a recommended SATA
cable. For cable information, see About Your RAID Controller on page 16
.
When all internal disk drives have been installed and connected, close your computer cabinet, and reattach the power cord.
Continue by either setting the boot controller (see
page 40 ) or by installing the controller
driver on an existing operating system (see
page 51 ), depending on the type of installation
you are completing.
Chapter 5: Installing the Controller and Disk Drives ●
38
Connecting Disk Drives to SCSI RAID Controllers
1 For each controller channel, set the SCSI ID of each disk drive to a unique number between 0 and 15.
The controller is set to ID 7 by default. Although not recommended, you can change the controller ID by using the ICP RAID Configuration utility (see
).
Note: Do not change the controller ID unless absolutely necessary.
2
3
4
Install a terminator (or enable termination) on the disk drive at the end of each cable, or the end of the cable itself.
Remove any terminators (or disable termination) on disk drives between the ends of each cable.
Install your SCSI disk drives, following the instructions in your system’s documentation.
If space inside your computer cabinet is limited, connect your disk drives to the SCSI cable
before installing them. (For installation instructions, refer to your computer’s documentation.)
!
Caution: To avoid causing unstable operation, do not attach a cable to the controller unless the other end of the cable is attached to a least one disk drive.
Alternatively, install your disk drives, then connect them to the controller.
When all internal disk drives have been installed and connected, close your computer cabinet, reattach the power cord, then continue with the following section.
Connecting External Devices
Note: If you are not connecting any external devices, see the following section,
1
2
(SCSI controllers only) Ensure that SCSI IDs and termination are set before completing the
connections to external disk drives or devices. See page 38
.
Use high-quality cables to connect your controller to your external device(s), such as disk drives or disk drive enclosures.
ICP recommends using only ICP cables. For more information or to purchase cables, visit the ICP Web site at www.icp-vortex.com
or 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 40
.
If you are completing a standard installation onto an existing operating system, continue with
Installing the Driver on an Existing Operating System on page 51
.
Chapter 5: Installing the Controller and Disk Drives ●
39
Monitoring Disk Drives with ICP Storage Manager
ICP Storage Manager allows you to monitor the status of your SAS, SATA, or SCSI disk drives.
Within ICP Storage Manager, you can select a disk drive object and a command will be sent to the backplane (for internal disk drives) or enclosure (for external disk drives). The LED associated with that disk drive will flash. The following table describes the LED flash states. For more information refer to the ICP Storage Manager Help.
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
Creating a Bootable Array
6
In this chapter...
This chapter explains how to set your ICP 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 ●
41
Setting the Boot Controller
Note: If your system won’t contain more than one bootable controller, skip to the next section,
.
Your ICP 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’s 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 either of these tools:
●
●
Array Configuration Utility (ACU)—BIOS-based menus and keyboard navigation (see the following section).
ICP Storage Manager—Graphical software application (running from a bootable CD) that you can navigate with your mouse (see
You can use either tool, but the ICP RAID Configuration utility is the quicker and easier tool for this task.
Note: ICP recommends that you not combine SAS and SATA disk drives within the same array.
ICP Storage Manager generates a warning if you try to create a logical drive using a
combination of SAS and SATA disk drives. See page 64 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 ICP RAID
Configuration utility.
Note: During boot up, if your system has insufficient memory the following message will display. “ICP RAID Configuration Utility will load after, system initialization. Please wait... Or press <Enter> Key to attempt loading the utility forcibly [Generally, not recommended]”
3
4
2 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.
Select Initialize Drives, then press Enter.
Chapter 6: Creating a Bootable Array ●
42
7
8
5
6
9
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
Write 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).
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 44
.
Chapter 6: Creating a Bootable Array ●
43
Creating an Array with ICP Storage Manager
This section describes how to use the ICP Storage Manager configuration wizard to build a
RAID 5 array.
Note: You will need the ICP Storage Manager Installation CD to complete this task.
To create a RAID 5 array:
1 Insert the ICP 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.
ICP Storage Manager opens.
Click Create.
The Configuration wizard opens.
6 Select Express configuration..., then click Next.
Chapter 6: Creating a Bootable Array ●
44
7 Review the information that is displayed.
Note: In DAS environments, ICP Storage Manager uses the term logical drives when
referring to arrays (see page 12 ).
In this example, ICP 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.
ICP Storage Manager builds the logical drive.
The configuration is saved on the ICP 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 ICP Storage Manager Installation CD.
For information on installing and using ICP Storage Manager as a full software application, refer to the ICP 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 81
).
Then continue with Installing the Driver and an Operating System on page 45
.
Installing the Driver and an
Operating System
7
In this chapter...
This chapter explains how to install your ICP RAID controller driver and an operating system
onto a bootable array (see page 40
).
Note: Solaris users only—You cannot use your ICP RAID controller as a boot controller. To install the driver on a computer with Solaris already installed, see
.
To install the driver on an existing operating system, see
.
Chapter 7: Installing the Driver and an Operating System ●
46
Before You Begin
●
Install and connect your ICP RAID controller and internal disk drives (see page 33
).
●
●
Create a bootable array (see
Create a driver disk (see the following section).
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’s 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 ICP Start Menu.
Click Create Driver Disk(s) for Installing/Updating your OS, then select your operating system.
●
Windows
●
●
●
●
Linux
NetWare
UnixWare
FreeBSD
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 47
.
For SUSE Linux, see
●
●
●
●
For NetWare, see
.
.
.
Chapter 7: Installing the Driver and an Operating System ●
47
Installing with Windows
Note: You will need your Windows Installation CD to complete this task.
4
5
6
7
8
To install the ICP RAID controller driver while installing Windows:
1 Insert your Windows CD, then restart the computer.
2
3
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.
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 ICP driver is found, press Enter.
Follow the on-screen instructions to complete the installation.
Continue with
Managing Your Storage Space on page 56
.
Installing with Red Hat Linux
Note: You will need your Red Hat Installation CD to complete this task.
To install the ICP 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 56
.
Chapter 7: Installing the Driver and an Operating System ●
48
Installing with SUSE Linux
To install the ICP 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 56
.
Installing with NetWare
Note: You will need your NetWare Installation CD to complete this task.
To install the driver when installing NetWare:
1 Restart your computer, then install NetWare. (For instructions, refer to your NetWare documentation.)
2
To be able to load additional drivers later, select Manual install mode during the first part of the installation.
To load additional drivers: a Select Modify when the storage adapters are displayed.
b Select Storage adapters, then press the Insert key to add an unlisted driver from the floppy disk.
When the Device Types screen appears, check the Storage adapters list and select Modify to add another driver.
3
4
5
6
7
Select Storage adapters, then press Enter.
All recognized controllers are displayed.
If AACRAID is detected, delete it.
Press Insert to add another driver.
The available drivers are displayed.
Insert the driver floppy disk.
Press the Insert key to scan the floppy disk drive.
Once the driver is selected, the Parameter screen is displayed.
Chapter 7: Installing the Driver and an Operating System ●
49
8
9
From the lower window menu, select Continue, then press Enter.
If the driver installation process fails, the server console is displayed so you can see the cause of the failure.
To modify disk partitions, apply hot fixes, or perform volume maintenance, refer to your
NetWare documentation.
Continue with
Managing Your Storage Space on page 56
.
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.)
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 56
.
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
4
Restart your computer.
Follow the on-screen instructions to begin the UnixWare installation.
When prompted to load more HBA drivers, insert the driver disk, then select Yes. (To load more HBA drivers, repeat this step.)
5
6
7
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 56
.
Chapter 7: Installing the Driver and an Operating System ●
50
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 appears, select 6 to escape to loader prompt.
4
5
6
7
Type load kernel
.
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.
Type boot
.
Complete the FreeBSD installation, following the instructions included with your operating system.
8
9
Reboot your computer, then remove the driver disk.
Repeat Steps
3 through 6 the first time you boot the operating system to load the drivers
again for the initial bootup.
10
.
11 Continue with
Managing Your Storage Space on page 56
.
Note: Currently, ICP Storage Manager is not supported on FreeBSD. To create and manage arrays, use the ICP RAID Configuration
utility. See page 58 for more information.
Installing the Driver on an Existing
Operating System
8
In this chapter...
This chapter explains how to install your ICP 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 ●
52
Before You Begin
Before you begin, install and connect your ICP RAID controller and internal disk drives (see
You must also create a driver disk (see page 46 ) before you begin installing the controller driver.
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’s 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 ICP Start Menu.
Click Create Driver Disk(s) for Installing/Updating your OS, then select your operating system.
●
●
Windows
Linux
●
●
●
●
NetWare
UnixWare
Solaris
FreeBSD
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 53 .
For NetWare, see
●
●
●
●
.
.
For Solaris, see
.
Chapter 8: Installing the Driver on an Existing Operating System ●
53
Installing on Windows
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 56
.
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
Red Hat: mount /dev/cdrom /mnt/cdrom
SUSE: mount /dev/cdrom /media/cdrom
Install the module RPM: rpm -Uvh mount-point/xxx/yyy.rpm
3
4
5 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 56
.
Installing on NetWare
Note: Before you begin, ensure that your NetWare operating system has been upgraded to the minimum patch level specified by Novell. Refer to the Novell Web site for more information.
To install the driver on NetWare:
1 Start your computer.
2 At the NetWare server console prompt, type load hdetect
, then press Enter if it has not be loaded automatically.
3
4
5
6
7
At the Device types menu, select Continue, then press Enter.
At the Device type option, select Modify, then press Enter.
Select Storage Adapters, then press Enter.
At the Additional Driver Options menu, select Modify, then press Enter.
If aacraid.ham has already been detected, delete it.
Chapter 8: Installing the Driver on an Existing Operating System ●
54
8
9
At the Driver Name menu, press the Insert key.
Insert the driver disk, press the Insert key, then press F3.
10 At the A:\ prompt, press Enter.
The driver installs.
11 At the Additional Driver Option menu, select Return to driver summary, then press Enter.
12 At the Driver type menu, select Load on Additional Driver Options.
13 After the driver loads, select Continue.
14 Continue with
Managing Your Storage Space on page 56
.
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 56
.
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 56
.
Chapter 8: Installing the Driver on an Existing Operating System ●
55
Installing on Solaris
To install the driver on Solaris:
1
2
Start your computer.
Insert and mount the driver disk: volcheck
5
6
3
4
Change to the driver installer directory: cd /floppy/floppy0/DU/sol_210/i86pc/Tools
Start the driver installer:
./install.sh -i
Reboot your computer, then remove the driver disk.
Continue with
Managing Your Storage Space on page 56
.
Note: Currently, ICP Storage Manager is not supported on Solaris. To create and manage arrays, use the ICP RAID Configuration
utility. See page 58 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 cp /mnt/aac-02.00.00-x.tgz /tmp
Install the driver package:
5
6 pkg_add /tmp/aac-02.00.00-x.tgz
Reboot your computer, then remove the driver disk.
Continue with
Managing Your Storage Space on page 56
.
Note: Currently, ICP Storage Manager is not supported on FreeBSD. To create and manage arrays, use the ICP RAID Configuration
utility. See page 58 for more information.
Managing Your Storage Space
9
In this chapter...
Once you have installed your ICP RAID controller, disk drives (or other devices), and device driver, you can begin to build and manage your storage space.
This chapter introduces ICP Storage Manager, and describes the other utilities included with your ICP RAID controller.
Chapter 9: Managing Your Storage Space ●
57
About ICP Storage Manager
Note: Currently, ICP Storage Manager is not supported on Solaris or FreeBSD. To create and manage arrays, use the ICP RAID Configuration
for more information.
ICP Storage Manager is a full-featured software application that helps you build a storage space for your online data, using ICP RAID controllers and disk drives.
With ICP 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 ICP Storage Manager to monitor and manage all the controllers and disk drives in your storage space, including DAS and NAS.
When ICP Storage Manager is installed on a computer, the ICP 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 ICP Storage Manager online Help, or to the ICP Storage Manager
User’s Guide on the ICP Storage Manager Installation CD.
Installing ICP Storage Manager
ICP Storage Manager is included on the ICP Storage Manager Installation CD. For installation instructions, refer to the ICP Storage Manager User’s Guide, also included on the ICP 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 Command Line Interface (CLI) User’s Reference, which describes how to use
ARCCONF, are included on the ICP Storage Manager Installation CD.
Note: ICP recommends that only advanced users familiar with command line interfaces use
ARCCONF. Currently, ARCCONF is not supported on Solaris or FreeBSD. To create and manage arrays, use the ICP RAID Configuration
utility. See page 58 for more information.
Chapter 9: Managing Your Storage Space ●
58
About the ICP RAID Configuration Utility
The ICP RAID Configuration utility is a BIOS-based utility that you can use to create and manage controllers, disk drives and other devices, and arrays. The ICP RAID Configuration 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
.)
● A -Select utility—SerialSelect, SATASelect®, or SCSISelect®, for modifying your controller and disk drive settings.
Disk Utilities—For formatting or verifying disk drives.
●
The ICP RAID Configuration utility is included in your controller’s BIOS. For more information, see
Using the ICP RAID Configuration Utility on page 79
.
Note: The ICP RAID Configuration utility is primarily intended for preoperating system installation configuration.
About the ICP Flash Utility
The ICP Flash Utility (IFU) 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 IFU contains safeguards to prevent you from accidentally damaging your RAID controller’s flash contents, it is still important to use the IFU carefully and correctly to avoid rendering your RAID controller inoperable.
ICP recommends that only advanced users familiar with working in DOS use the IFU.
Which Utility Should I Use?
To create a bootable array, ICP recommends that you use the BIOS-based ACU (See Using the ICP
RAID Configuration Utility on page 79
).
For all subsequent storage management tasks, ICP recommends that you install and use ICP
). 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.
Note: Currently, ICP Storage Manager is not supported on Solaris or FreeBSD. To create and manage arrays, use the ICP RAID Configuration utility. See
Using the ICP RAID Configuration
for more information.
Solving Problems
10
In this chapter...
This chapter provides basic troubleshooting information and solutions for solving controller problems.
Chapter 10: Solving Problems ●
60
Troubleshooting Checklist
If you encounter difficulties installing or using your ICP 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 ICP RAID controller.
Check that your ICP RAID controller is installed in a compatible expansion slot (PCI, PCI-
X, or PCIe). To double-check the bus compatibility of your controller, see About Your
.
Ensure that your ICP RAID controller is firmly seated and secured in the PCI/PCI-X/PCIe expansion slot.
If your ICP RAID controller is not detected during system boot, try installing it in a different compatible expansion slot. (See
for instructions.)
● SCSI RAID controllers only—Ensure that each SCSI disk drive (or other device) on each
SCSI bus is assigned a unique SCSI ID.
Check that termination is set correctly on each SCSI bus.
Did the driver install correctly? ●
● If you have external disk drives (or other devices), are they powered on?
If you are still unable to resolve a problem, you can find additional troubleshooting information and direction on the ICP Web site at www.icp-vortex.com
or the Support
Knowledgebase at ask.adaptec.com
.
Silencing the Alarm
If your ICP RAID controller includes an alarm, the alarm will sound when an error occurs. To silence the alarm, use ICP Storage Manager (see
Managing Your Storage Space on page 56
.)
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 61 ).
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 61
).
If multiple disk drives fail within the same array (see
Note: In DAS environments, ICP Storage Manager uses the term logical drives when referring to
arrays (see
).
Chapter 10: Solving Problems ●
61
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 (following manufacturer’s instructions).
2 If copyback is not enabled—In ICP 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. Then, if necessary, use ICP Storage Manager to rebuild the array. For instructions, refer to the ICP 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
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).
Chapter 10: Solving Problems ●
62
Multiple Failures in the Same Array
Except in RAID 6 and RAID 60 arrays (see page 70
), if more than one disk drive fails at the same time in the same 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).
Note: In some instances, RAID 10 and RAID 50 arrays may survive multiple disk drive failures, depending on which disk drives fail. For more information, refer to the ICP Storage Manager
User’s Guide or online Help.
Resetting the Controller
This section explains how to reset (or flash) your ICP RAID controller. You may want to do this if the controller becomes inoperable, or if a firmware upgrade is unsuccessful.
To reset your ICP RAID controller:
1
2
Download the firmware version currently installed on your controller from www.icpvortex.com
Extract the downloaded files to a folder on your local hard drive (for example,
C:\Download\Drivers).
3
4
Create a bootable MS–DOS floppy disk and copy the IFU.exe file to it. Copy the first firmware image to the same floppy disk.
Create additional bootable MS–DOS floppy disks and copy each additional firmware image to its own floppy disk.
5
6
7
8
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 ICP RAID controller, see the figures in
About Your RAID Controller on page 16 .)
Reconnect the power cord, power on your computer, then boot to the floppy disk containing the IFU.exe file (see
At the prompt, type a: \ifu update /c x where x
is the controller number.
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 Serial Attached
SCSI
A
In this appendix...
This section provides a basic overview of the main features of Serial Attached SCSI (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 Serial Attached SCSI ●
64
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 (see page
68 ), ICP 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 65 ). Link speed is 600 MB/sec in full-duplex mode. A SAS card with eight links has a
maximum bandwidth of 4800 MB/sec in full-duplex mode.
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? on page 69 .
Appendix A: Introduction to Serial Attached SCSI ●
65
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
page 66 ), ports contain 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 66
).
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 Serial Attached SCSI ●
66
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 67
), 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 SAS
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 support up to four links.
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 Serial Attached SCSI ●
67
How are Disk Drives Identified in SAS?
In the BIOS and in the management utilities (see
), disk drives are identified with numbers in this format:
XX:YY:ZZ where XX is the disk drive count number, YY is the enclosure number, and ZZ is the slot number (within the enclosure). If the disk drive is not installed in an enclosure, a double dashes (--) appear instead of YY and ZZ (for instance, 01:--:--).
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 36
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.
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.
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.
Appendix A: Introduction to Serial Attached SCSI ●
68
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 67
), 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).
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 Serial Attached SCSI ●
69
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 600 MB/sec per phy when in fullduplex mode
Supports SATA and SAS disk drives simultaneously
More than 128 disk drives per SAS card, using an
)
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 ICP 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 ●
71
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.
Nonredundant 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 ●
72
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 ●
73
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 ●
74
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 ●
75
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
RAID 5EE Logical Drive = 750 GB plus
Parity and Spare
Appendix B: Understanding RAID ●
76
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 74 .)
Note: Because they support four disk drives only, the ICP9047MA RAID controller can’t support RAID 50 arrays.
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 ●
77
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
Disk Drive 4
400 GB
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
RAID 6 Logical Drive = 750 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.
Note: Because they support four disk drives only, the ICP9047MA RAID controller can’t support RAID 60 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 ●
78
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
RAID 1E
RAID 10
RAID 5
RAID 5EE
RAID 50
*
RAID 6
RAID 60
1
Yes
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
Minimum
Disk Drives
2
2
3
4
3
4
6
4
8
*
Because they support four disk drives only, the ICP9047MA RAID controller can’t support RAID 50 or RAID 60 arrays.
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.
Using the ICP RAID Configuration
Utility
C
In this appendix...
The ICP RAID Configuration utility is a BIOS-based utility that you can use to create and manage controllers, disk drives and other devices, and arrays.
Note: ICP recommends that only advanced users familiar with working in a computer BIOS use the ICP RAID Configuration utility tools. For more information, see
Appendix C: Using the ICP RAID Configuration Utility ●
80
Introduction to the ICP RAID Configuration Utility
The ICP RAID Configuration 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 87
.
●
●
A -Select Utility—SerialSelect, SATASelect, or SCSISelect, for modifying your controller and disk drive settings (see
Disk Utilities—For formatting or verifying disk drives (see
Running the ICP RAID Configuration Utility
If your ICP 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 the following message will display.
“ICP 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 ICP RAID Configuration Utility
All the tools within the ICP RAID Configuration 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 ICP RAID Configuration utility (see page 80
). 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 81 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 28
.
Appendix C: Using the ICP RAID Configuration Utility ●
81
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 81
).
Assign or remove hot spares.
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’s 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.
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.
!
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.
Appendix C: Using the ICP RAID Configuration Utility ●
82
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.
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 ICP 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.
Using the -Select Utility to Modify Controller Settings
Included in the ICP RAID Configuration utility is a tool for modifying the settings of your controller and the disk drives connected to it. This utility is called SerialSelect, SATASelect, or
SCSISelect, depending on what type of controller you have.
Opening a -Select Utility
To open a -Select utility, start the ICP RAID Configuration utility (see page 80
), select the
-Select utility, 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 a -Select utility, 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.
Appendix C: Using the ICP RAID Configuration Utility ●
83
Modifying Your Controller’s Configuration
Note: Default controller settings are suitable for most computers. ICP recommends that you
do not change the default setting.
To modify your controller’s settings, select Controller Configuration from the main -Select utility menu.
The following table lists controller configuration options. Some options may not be available for your controller. Additional, controller-specific options are also available:
●
●
●
For SAS controller-specific settings, see page 84
.
For SATA controller-specific settings, see
For SCSI controller-specific settings, see
General Controller Settings
Note: Default settings are shown in bold type.
Option
Drive’s Write Cache
Runtime BIOS
Automatic Failover
Array Background
Consistency Check
BBS Support
Array-based BBS
Support
Physical Drives Display
During POST
Description
When enabled, write cache is enabled on the disk drive. When disabled, write cache is not used on the disk drive. Default is the disk drive’s setting.
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 RAID controller is presented as a bootable device in the BIOS.
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, 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.
CD-ROM Boot Support 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.
Removable Media
Devices Boot Support
When enabled, removable media devices, such as CD drives, are supported. (This setting is not available on all RAID controller models.)
Alarm Control When enabled, the alarm sounds. Default is enabled.
Appendix C: Using the ICP RAID Configuration Utility ●
84
SAS-specific Controller Settings
In addition to the general settings listed on page 83 , your ICP SAS controller has SAS-specific
settings that can be modified if required. (For more information about SAS, see
.)
To modify SAS-specific settings, select PHY Configuration from the SerialSelect main menu.
Note: Default settings are shown in bold type.
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.
SATA-specific Controller Settings
In addition to the general settings listed on
page 83 , your ICP SATA controller has a SATA-
specific setting that can be modified if required.
Option
Write Cache
Description
When enabled, the controller’s write cache is enabled. Default is Yes (enabled).
Caution—When enabled, there is a potential for data loss or corruption during a power failure.
Appendix C: Using the ICP RAID Configuration Utility ●
85
SCSI-specific Controller Settings
In addition to the general settings listed on
, your ICP SCSI controller has SCSI-specific settings that can be modified if required.
To modify SCSI-specific settings, select SCSI Configuration from the SCSISelect main menu.
SCSI Device Settings
You can use SCSISelect to modify some of the settings on the SCSI devices connected to your
SCSI controller.
To modify SCSI device settings, select SCSI Configuration from the SCSISelect main menu, then select Additional Options. Devices are listed by SCSI ID. (To find the SCSI ID for a
specific device, see Formatting and Verifying Disk Drives on page 86
.)
For the best device performance, don’t change the default settings.
Note: Default settings are shown in bold type.
Option
Maximum
Transfer Rate
Enable
Disconnection
Initiate Wide
Negotiation
QAS
Packetized
Description
Shows the maximum data transfer rate that the SCSI channel supports.
When enabled, the SCSI device can disconnect from the SCSI channel. Default is
Yes (enabled).
When enabled, the SCSI channel attempts 16-bit data transfer instead of 8-bit data transfer. Default is Yes (enabled).
When enabled, QAS (Quick Arbitration and Selection) is used to eliminate overhead and speed up data transfers on the SCSI bus. Default is No (disabled).
Note—ICP recommends that you do not enable QAS if you are using an enclosure that supports Ultra320 expanders.
When enabled, SCSI packetization (encapsulation) is used to reduce overhead and speed data transfer. Default is Yes (enabled).
SCSI Channel Interface Settings
Note: Default settings are shown in bold type.
Option
Controller SCSI
Channel ID
SCSI Parity
Checking
Controller SCSI
Channel
Termination
Description
Sets the controller’s SCSI ID. ICP recommends that you leave the controller set to the default (7), which gives it the highest priority on the SCSI channel.
When enabled, the controller verifies the accuracy of data transfer on the SCSI channel. Disable only if the controller is connected to any SCSI device that does not support SCSI parity. Default is enabled.
Sets termination on the controller. ICP recommends that you retain the default setting (auto mode).
Appendix C: Using the ICP RAID Configuration Utility ●
86
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.
To format or verify a disk drive:
1
Start the ICP RAID Configuration utility (see page 80
).
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.
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 ICP RAID Configuration utility (see page 80
).
2
3
4
Select the controller you want, then press Enter.
When the ICP RAID Configuration 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: ICP 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 56
.
Appendix D: Using the Array Configuration Utility for DOS ●
88
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 ICP 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 ICP 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 ●
89
Running the ACU Using Scripts
To work in the ACU using scripts:
1
2
Insert the ACU floppy disk (see
page 88 ), 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 <file>
/L <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 89 .
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 file is 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 ●
90
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 91
)
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 ●
91
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 91
.
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. See page 92 .
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
Specifies the size of the array. Default is Maximum. See page 93 .
Specifies size of contiguous I/O, in bytes. Default is 256. See
.
Indicates the type of array to create. No default. See page 94
.
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
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.
For example:
Drives=0:0:0
Drives=0:0:0,0:1:0,0:2:0
Appendix D: Using the Array Configuration Utility for DOS ●
92
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 91
. 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:
Type=Volume
Type=RAID1
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 ●
93
Method Keyword
Method is an optional keyword, indicating which method to use when creating a redundant
(RAID 1, 5, and 10) 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.
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 MB) written to each member of a striped array (RAID 0, 5, or 10).
The possible values for StripeSize are 16, 32, 64, 128, 256, 512 and 1024 KB. Default is 256.
For example:
StripeSize=256
Appendix D: Using the Array Configuration Utility for DOS ●
94
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
Channel Definition Block Keywords—SCSI only
The channel definition block is optional. If used, it always begins with the keyword Channel and ends with the keyword End. The channel definition block keywords are listed in this table.
Keyword
Channel
ControllerID
End
Description
Used to identify the channel.
Changes the SCSI ID of the controller.
Indicates the end of a channel definition block.
Channel Keyword
Channel is an optional keyword that begins a channel definition block and specifies the channel number to which the channel keywords apply. Channels are numbered from zero to the maximum number of channels on the controller minus one.
You can include multiple channel definition blocks within a script file, each beginning with a channel keyword and value.
For example:
Channel=0
Appendix D: Using the Array Configuration Utility for DOS ●
95
ControllerID Keyword
ControllerID is an optional keyword to change the SCSI ID of the controller. Normally, the
SCSI controller is assigned SCSI ID 7 on each of its channels. You can specify any ID value between 0 and 7.
!
Caution: Do not change the SCSI ID of the controller unless directed to do so by ICP
Technical Support.
For example:
ControllerID=7
End Keyword
End is a required keyword, indicating the end of the block.
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 89 for a list of valid command-line switches.)
5 Unable to read system configuration—The ACU was unable to get the configuration information from the specified controller.
6 No drives detected.
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.
100 You ran ACU and made changes—The ACU exited with no errors (success) and you must restart the computer.
Appendix D: Using the Array Configuration Utility for DOS ●
96
Sample Scripts
This MS-DOS 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
Sample Scripts for SCSI and SAS Controllers
Note: For a sample script for a SATA controller, see
This sample script file is a sample 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:
# Script to create volume, mirror, and RAID 5 arrays
# 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
# 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=256
# 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
Appendix D: Using the Array Configuration Utility for DOS ●
97
Sample Script for SATA Controllers
This is a sample ACU file that will initialize all disk drives connected to the SATA controller and create a RAID 5 array with the disk drives on ports 0, 1, and 2.
Controller= 0,5:7:0
Controller Name=ICP ICP9087MA
Subsystem ID=0x2A1
Firmware Version=V5.1-0[6792]
Total Ports=8
Port 0 = 0:0:0 Maxtor 279.479GB 279.395GB
Port 1 = 0:1:0 Maxtor 279.479GB 279.395GB
Port 2 = 0:2:0 Maxtor 279.479GB 279.395GB
Array=MyData2
Type=RAID5
Size=Maximum
InitializeAll=Yes
Method=Build/Verify
Wait=No
Drives=0:0:0, 0:1:0, 0:2:0
End
Using the ICP Flash Utility
E
In this appendix...
This chapter describes how to use theICP Flash Utility (IFU), 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 IFU contains safeguards to prevent you from accidentally damaging your RAID controller’s flash contents, it is still important to use the IFU carefully and correctly to avoid rendering your RAID controller inoperable.
ICP recommends that only advanced users familiar with working in DOS use the IFU. For more information, see
Managing Your Storage Space on page 56 .
Appendix E: Using the ICP Flash Utility ●
99
System Requirements
● MS–DOS version 5.0 or later.
Note: You can’t run the IFU 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 a firmware kit on floppy disks (see page 100
).
There are two ways to run the IFU:
1
2
Using the IFU menus (see
From the command line (see page 101
)
Obtaining the Firmware
To obtain RAID controller firmware, go to:
●
●
The RAID Installation CD—Includes the IFU executable (IFU.exe) and a separate flash image. The flash image may comprise multiple User Flash Image (UFI) files.
The ICP Web site—Download a new firmware file to get the most recent version of IFU.
See www.icp-vortex.com
for more information.
Appendix E: Using the ICP Flash Utility ●
100
Creating the Firmware Floppy Disks
Note: You will need at least two bootable MS-DOS floppy disks to complete this task.
You can’t create a bootable floppy disk using Windows 2000.
To create the firmware floppy disks:
1 Create a bootable MS–DOS floppy disk and copy these files to it:
●
●
IFU.exe
ICxxxx01.ufi
where xxx is the model number of your controller.
Note: Most controller model numbers have a suffix (for example ICP5085AU). Check that the
.ufi file is the correct file for your controller before copying.
2
3
Create additional bootable MS–DOS floppy disks and copy each additional ICxxxx0x.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 IFU, see the following section.
To run the IFU from the command line, see page 101
.
Running the Menu-based IFU
Note: You can also run the IFU from the command line (see
).
To run the menu-based IFU:
1 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.)
2
3
4
5
At the DOS command prompt, type
IFU
with no arguments.
The IFU’s main menu is displayed.
Select Select Controllers, then select the ICP 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—Updates all the flash components on a RAID controller with the flash image data from the UFI file.
●
●
●
Save—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—Reads the contents of a RAID controller’s flash components and compares it to the contents of the specified UFI file.
Version—Displays version information about a RAID controller’s flash components.
●
List—Lists all supported RAID controllers detected on your system.
Appendix E: Using the ICP Flash Utility ●
101
6 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.)
Running the IFU from the Command Line
Note:
You can also run a menu-based IFU (see page 100 ).
To run the IFU from the command line:
1 Power off your computer, insert the first IFU floppy disk, then power on your computer.
2
If your computer isn’t set up to boot from the bootable floppy disk, enter the system setup utility to change the setting.
At the DOS command, type IFU followed by a command (see
) and any switches you want.
Note: To find a controller number, type IFU LIST, then press Enter.
The IFU 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, see
.
IFU Commands
This section lists the available IFU commands.
List
Displays the IFU-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:\> IFU LIST
ICP Flash Utility V4.0-0 B5749
(c)ICP Inc. 1999–2005. All Rights Reserved.
Controllers Detected and Recognized:
Controller #0 (03:05:00) ICP ICP9024RO
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
IFU SAVE [/C<Controller ID>] [/D <UFI File Path>]
Appendix E: Using the ICP Flash Utility ●
102
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 IFU 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 IFU 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 IFU 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 IFU saves flash contents from RAID controller 0 to a UFI file in the current default drive and directory:
A:\> IFU SAVE /C 0
In this example, the IFU saves flash contents from Controller 1 to a UFI file in
C:\UFI_FILES:
A:\> IFU 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:
IFU UPDATE [/C<Controller ID>] [/D <UFI File Path>]
You can also use the /C and /D switches (see Save on page 101
).
This example shows a typical system response after an update.
A:\> IFU UPDATE /C 0
ICP Flash Utility V4.0-0 B5749
(c)ICP Inc. 1999–2005. All Rights Reserved.
Updating Controller 0 (ICP 2820)
Reading flash image file (Build 5749)
IFU is about to update firmware on controllers ICP ICP9024RO
***PLEASE DO NOT REBOOT THE SYSTEM DURING THE UPDATE***
This might take a few minutes.
Writing ICP ICP9024RO (4MB) Flash Image to controller 0...OK. Verifying...OK
Please restart the computer to allow firmware changes to take effect.
Appendix E: Using the ICP Flash Utility ●
103
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:
IFU VERIFY [/C<Controller ID>] [/D <UFI File Path>]
You can also use the /C and /D switches. See Save on page 101
for more information.
This example shows a typical system response after a VERIFY command.
A:\> IFU VERIFY /C 0
ICP Flash Utility V4.0-0 B5749
(c)ICP Inc. 1999–2005. All Rights Reserved.
Reading flash image file (Build 5748)
Controller #0: ICP ICP9087MA
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:
IFU VERSION [/C<Controller ID>]
You can also use the /C switch. See
Save on page 101 for more information.
This example displays version information about all supported RAID controllers.
A:\> IFU VERSION /C 0
ICP Flash Utility V4.0-0 B5749
(c)ICP Inc. 1999–2005. All Rights Reserved.
Version Information for Controller #0 (ICP ICP9087MA)
ROM: Build 5748 [VALID] Fri Sep 27 13:28:40 EDT 2005
A:\> IFU VERSION /C ALL
Help
Displays a summary of IFU functions and command switches. For example:
A:\> IFU HELP
A:\> IFU /?
Appendix E: Using the ICP Flash Utility ●
104
Updating the Flash Using the IFU Command Line
1 Create the firmware floppy disks (see
).
2
3
4
5
Power off your computer, insert the first IFU floppy disk, then power on your computer.
If your computer isn’t set up to boot from the bootable floppy disk, enter the system setup utility to change the setting.
At the DOS command, if you have multiple controllers and you don’t know the number of the controller you want to update, type
IFU LIST
, then press Enter. Otherwise, skip to the next step.
At the DOS command, type IFU followed by a command (see
) and any switches you want.
Update the flash using the instructions suitable for your requirements:
●
To update a single RAID controller:
IFU 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 IFU UPDATE /C 0
To update multiple RAID controllers:
IFU UPDATE /C <cont_number_a>,<cont_number_b>
Where <controller_number_a> and <controller_number_b> are the numbers of the ICP RAID controllers whose firmware you are updating. For example, to upgrade controllers 0, 2, and 3, type
IFU UPDATE /C 0, 2, 3
To update all RAID controllers simultaneously:
IFU UPDATE /C all
Note: The UFI file identifies the RAID controllers, so you don’t have to worry about flashing the wrong controller.
6
7
8
When prompted, insert the first firmware disk into your floppy disk drive.
The IFU reads the first disk.
When prompted, remove the first firmware disk and insert the second firmware disk into your floppy disk drive.
Repeat
Step 7 as required until the flash update is complete.
Safety Information
F
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 ICP, put it back in its antistatic bag immediately.
Technical Specifications
G
In this appendix...
Appendix G: Technical Specifications ●
107
Environmental Specifications
Ambient temperature without battery backup module
Relative humidity
Altitude
0 °C to 50 ° C
10% to 90% , noncondensing
Up to 3,000 meters
ICP Model
ICP5085AU
Requirement
Forced airflow recommended but not required
ICP5445AU Forced airflow recommended but not required
ICP9014RO/ICP9024RO Forced airflow recommended but not required
ICP9047MA/ICP9087MA Forced airflow recommended but not required
ICP9085LI Forced airflow of 400 lfm (= 2.2 m/sec) required
ICP5085BR Forced airflow of 400 lfm (= 2.2 m/sec) required
DC Power Requirements
Ripple and noise
DC Voltage
50 mV peak-to-peak (max)
5 V ± 5%, 3.3 V ± 10%
Current Requirements
ICP Model
ICP5445AU
ICP5085AU
ICP9085LI
ICP5085BR
ICP9047MA
ICP9087MA
ICP9014RO
ICP9024RO
Maximum Current (A)
0.9 A @ 12 VDC; 0.77 A @ 3.3 VDC
0.61 A @ 3.3 VDC; 0.88 A @ 12 VDC
1.4 A @ 3.3 VDC; 2.4 A @ 5.0 VDC
1.5 A @ 3.3 VDC; 1.3 A @ 12.0 VDC
0.36 A @ 3.3 VDC; 2.4 A @ 5.0 VDC
0.37 A @ 3.3 VDC; 2.4 A @ 5.0 VDC
2.5 A @ 3.3 VDC; 2 A @ 5.0 VDC
2.5 A @ 3.3 VDC; 2 A @ 5.0 VDC
A
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 RAID Controller Configuration utility. See
ARCCONF
advanced data protection
Alarm Control setting
ARCCONF
Array Background Consistency Check setting
Array Configuration Utility. See ACU
array definition block
End keyword
HotspareDrives keyword
array migration
Array-based BBS Support setting
arrays creating (ACU)
creating (ICP 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
BBS Support setting
BBU
boot controller
bootable arrays
creating
C cables
CD-ROM Boot Support setting
command line interface (flash utility)
Index
Index ●
109 command line utility
contents of controller kit
Controller SCSI Channel ID setting
Controller SCSI Channel Termination setting
controllers
Alarm Control setting
Array Background Consistency Check setting
Array-based BBS Support setting
array-level features
Automatic Failover setting
BBS Support setting
cables
CD-ROM Boot Support setting
connecting external devices
data protection
descriptions
disk drives
Drive’s Write Cache setting
event log
figures
firmware
flashing
installation options
installing
modifying general settings
modifying settings with -Select utilities
Physical Drives Display During POST setting
RAID levels
Removable Media Devices Boot Support setting
resetting
Runtime BIOS setting
setting boot controller
specifications
troubleshooting
updating firmware
upgrading firmware
copyback
CRC Checking setting
D direct-attach connections
disk drives
cables
connecting to SAS controllers
connecting to SATA controllers
connecting to SCSI controllers
external
failure recovery multiple arrays
multiple disk drives
RAID 0 arrays
with hot spare
without hot spare
formatting
HVD
initializing
LVD
recovering from failure
rescanning
SAS identifiers
SE
secure erasing
stopping a secure erase
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 NetWare
installing on OpenServer
installing on Solaris
installing on UnixWare
installing on Windows
installing with FreeBSD
installing with Linux
,
installing with NetWare
installing with OpenServer
installing with UnixWare
installing with Windows
E electrostatic discharge
Enable Disconnection setting
end devices
End property
event log
expander connections
expander devices
external devices
F failed disk drives
multiple arrays
multiple disk drives
RAID 0 arrays
without hot spare
Index ●
110 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
ICP RAID Configuration utility
ICP Storage Manager
creating arrays
installing
IFU
,
to
initializing disk drives
Initiate Wide Negotiation setting
installation controllers
creating a driver disk
disk drives (SAS)
disk drives (SATA)
disk drives (SCSI)
driver
driver and FreeBSD
driver and Linux
driver and NetWare
driver and OpenServer
driver and operating system
,
driver and UnixWare
driver and Windows
existing operating system
external devices
installation options
SAS backplane
SAS direct-attach
with operating system
K kit contents
L links (SAS)
Linux driver installation
OS installation
Linux installation
M
Managing
Maximum Transfer Rate setting
mini-SAS direct connection
enclosure cable
external connector
internal cable
overview
SAS to SATA cable
mirroring
N
NCQ
NetWare driver installation
OS installation
non-redundant arrays
O online expansion
OpenServer driver installation
OS installation
operating system installation
,
operating systems
P
Packetized setting
parity
Phy Rate setting
phys
Physical Drives Display During POST setting
playback mode
Q
QAS setting
R
non-redundant arrays
RAID 0
RAID 1
RAID 10
RAID 1E
,
RAID 5
RAID 50
RAID 5EE
RAID 6
,
RAID 60
RAID controllers. 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 drive identifiers
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
Index ●
111
SAS domain
terminology
transceivers
wide connectors
wide ports
SAS Address setting
SAS controllers cables
connecting disk drives
CRC Checking setting
disk drives
modifying with -Select utilities
Phy Rate setting
SAS Address setting
SAS devices
cables
disk drives
SATA controllers cables
connecting disk drives
disk drives
modifying with -Select utilities
Write Cache setting
SATASelect
scripts in ACU for DOS
cables
comparison to SAS
disk drives
SCSI controllers cables
connecting disk drives
Controller SCSI Channel ID setting
Controller SCSI Channel Termination setting
disk drives
Enable Disconnection setting
Initiate Wide Negotiation setting
Maximum Transfer Rate setting
modifying with -Select utilities
Packetized setting
QAS setting
SCSI Parity Checking setting
SCSI Parity Checking setting
SCSISelect
secure erasing disk drives
stopping a secure erase
-Select utilities
applying changes
exiting
modifying controller settings
opening
SerialSelect
Small Computer System Interface. See SCSI
snapshot
software
Solaris driver installation
specifications
storage management
ARCCONF
ICP RAID Configuration utility
ICP Storage Manager
IFU
storage space
SUSE driver installation
SUSE installation
switches in ACU for DOS
system requirements
T technical specifications
Technical Support Identification (TSID) number
terminology
SAS
tools
ARCCONF
ICP RAID Configuration utility
ICP Storage Manager
IFU
troubleshooting tips
TSID Number
See Technical Support Identification Number
U
UnixWare driver installation
OS installation
updating firmware
upgrading firmware
utilities
ARCCONF
ICP RAID Configuration utility
IFU
V verifying disk drives
W
Windows driver installation
OS installation
Write Cache setting
Index ●
112
ICP vortex Computersysteme GmbH
Konrad-Zuse-Str.9
74172 Neckarsulm
Germany
©2005-2006 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-00166-01-A, Rev. A
JB 05/06
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project