adaptec_raid_controller_iug_10_2012
adaptec_raid_controller_iug_10_2012
In no event will PMC-Sierra, Inc. be liable for any direct, indirect, special,
incidental or consequential damages, including, but not limited to, lost profits,
lost business or lost data resulting from any use of or reliance upon the
information, whether or not PMC-Sierra, Inc. has been advised of the
possibility of such damage.
Other product and company names mentioned herein may be the trademarks
of their respective owners.
Revision History
Issue Issue Date Details of Change
1.0 September 27, Firmware/BIOS/Drivers/Utilities Version 8.0
2012
Contents
Adaptec by PMC Product Support..............................................................................................................................8
Limited 3-Year Hardware Warranty............................................................................................................................9
Regulatory Compliance Statements..........................................................................................................................10
4 Getting Started......................................................................................................................................................23
Choosing a RAID Level..................................................................................................................................23
Selecting Disk Drives and Cables .................................................................................................................23
Disk Drives.......................................................................................................................................23
Cables..............................................................................................................................................23
Replacing the Full-Height Bracket with a Low-Profile Bracket.....................................................................24
Installation Options......................................................................................................................................25
Basic Installation Steps.................................................................................................................................25
Installing with an Operating System................................................................................................26
Installing on an Existing Operating System......................................................................................26
• It's recommended that you register your product so that you have easy access to your TSID when
contacting product support.
Note: The phone numbers below are subject to change. Please visit the Support
section of www.adaptec.com for the most up to date contact information.
North America
• Visit our Web site at www.adaptec.com.
• Search the Adaptec Support Knowledgebase (ASK) at ask.adaptec.com for articles, troubleshooting
tips, and frequently asked questions for your product.
• For support via e-mail, submit your question at ask.adaptec.com.
• To speak with a Technical Support Specialist, call +1 408 934 7274 or +49 89 4366 5544 or +44 845
266 8773.
Europe
• Visit our Web site at www.adaptec-europe.com.
• German: Call +49 89 43 66 55 22. For support via e-mail, submit your question at ask-de.adaptec.com.
• French: Call +49 89 43 66 55 33. For support via e-mail, submit your question at ask-fr.adaptec.com.
• English: Call +49 89 43 66 55 44. For support via e-mail, submit your question at ask.adaptec.com.
Japan
• Visit our Web site at www.adaptec.co.jp.
• Call 03-3367-3970 (fax). For support via e-mail, submit your question at ask.adaptec.co.jp
Australia
• Call +61-2-9503-1555.
Russia
• Visit our Web site at www.adaptec.com/ru-ru/.
• Call +7 499 918 7200 or +49 89 4366 5555. For support via e-mail, submit your question at
ask-ru.adaptec.com.
UL Compliance Statement
Adaptec by PMC products are tested and listed by Underwriters Laboratories, Inc. to UL 60950
-1 Second Edition and IEC-60950-1 Second Edition standards, file numbers E175975. Adaptec
by PMC products are for use only with UL listed ITE.
PMC-Sierra, Inc. Use only with the listed ITE:
ASR-7805/ASR-7805Q/ASR-71605/
ASR-71605E/ASR-71605Q/ASR-71685/
ASR-72405/AFM-700
This Information Technology Equipment has been tested and found to comply with EMC
Directive 89/336/EEC, as amended by 92/31/EEC and 93/68/EEC, in accordance with:
• EN55022 (1998+A1:2000+A2:2007) Emissions
∘ Class B ITE radiated and conducted emissions
• EN55024 (1998+A1:2001+A2:2010) Immunity:
∘ EN61000-4-2 (2009) Electrostatic discharge: ±4 kV contact, ±8 kV air
∘ EN61000-4-3 (2010) Radiated immunity: 3V/m
∘ EN61000-4-4 (2004) Electrical fast transients/burst: ±1 kV AC, ±0.5 kV I/O
∘ EN61000-4-5 (2006) Surges: ±1 kV differential mode, ±2 kV common mode
∘ EN61000-4-6 (2009) Conducted immunity: 3 V
∘ EN61000-4-11 (2004) Supply dips and variations: 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.
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.
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.
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.
This equipment is home use (Class B) electromagnetic wave suitability equipment and to be used mainly
at home and it can be used in all areas.
• Adaptec RAID Controller Command Line Utility User’s Guide—Describes how to use the included
Adaptec RAID Controller Configuration (ARCCONF) command line utility (see About the Adaptec
RAID Controller Configuration Utility on page 54) to perform basic array and configuration
management functions; located on the Adaptec Installation DVD.
Kit Contents
• Adaptec RAID controller
• Adaptec Installation DVD (bootable), including controller drivers, Adaptec maxView Storage Manager,
ARCCONF command line utility, and documentation
• Cables (Not included in Adaptec 'Single' product. If your kit includes cables, the type and quantity
vary—for more information, see Cables on page 23.)
• (Select models only) Low-profile bracket
• Adaptec Serial Attached SCSI RAID Controllers Quick Start Guide (Not included in Adaptec 'Single'
product)
System Requirements
• PC-compatible computer with Intel Pentium, or equivalent, processor
• Motherboard with these features:
∘ Support for multi-function devices where one of the devices is a PCI bridge
∘ Large memory-mapped address ranges
Refer to the Readme file on the Adaptec Installation DVD for additional motherboard compatibility
information.
• One of these operating systems:
Note: For up-to-date operating system version support check the readme on the
Adaptec Installation DVD or visit the Adaptec Web Site at www.adaptec.com. To
download Linux driver sources, visit the Support area of the Adaptec Web site at
www.adaptec.com/en-us/support.
∘ Microsoft® Windows® Server 2012 (32-bit and 64-bit), Windows Server 2008 (32-bit and 64-bit),
Windows Server 2008 R2 (64-bit), Windows SBS 2011, Windows Storage Server 2008 R2, Windows
Storage Server 2011, Windows 7 and Windows 8 (32-bit and 64-bit)
∘ Red Hat® Enterprise Linux 6.2, 5.8 (32-bit and 64-bit)
∘ SuSE Linux Enterprise Server 11, 10 (32-bit and 64-bit)
∘ FreeBSD 9, 8.2
∘ Debian Linux 6 (32-bit and 64-bit)
∘ Ubuntu Linux 12, 11, 10 (32-bit and 64-bit)
∘ Fedora Linux 16, 15, 14 (32-bit and 64-bit)
∘ CentOS 6.2, 5.8
∘ Solaris 10, Solaris 11 Express
∘ VMware ESXi 5.0, VMware ESX 4.1 Classic
• 2 GB of RAM minimum
• Available compatible PCIe slot (depending on your controller model—see the descriptions in About
Your RAID Controller on page 16)
• 350 MB of free disk drive space
• 16-bit SVGA color monitor with a resolution of at least 800 x 600
• DVD-ROM drive
• USB flash drive or CD burner, for creating driver disks and bootable media
Array-level Features
• Support for RAID 0, RAID 1, RAID 5, RAID 10, RAID 50, and simple volumes
• Support for hybrid RAID 1 and RAID 10 arrays comprised of hard drives and Solid State Drives (SSDs)
• Support for hot spares (global and dedicated)
• Support for automatic failover, so arrays are automatically rebuilt when a failed 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
Adaptec RAID 7805/Adaptec RAID 71605/Adaptec RAID 71685/ Adaptec Flash Backup Module AFM-
Adaptec RAID 72405 700 with Supercapacitor Card
(optional)
Adaptec RAID 7805Q/Adaptec RAID 71605Q Adaptec Flash Backup Module AFM-
700 with Supercapacitor Card (pre-
installed)
Daughterboard
connector
PCIe x8 connector
Mounting bracket
maxCache SSD support 7805Q: Up to 8 solid state drives, 2TB capacity, max. See the maxCache
compatibility list at www.adaptec.com/compatibility.
Zero Maintenance Cache Protection Adaptec Flash Backup Module AFM-700 (7805: optional, sold separately;
Module 7805Q: standard, pre-installed)
CN0
CN1
CN2
CN3
Daughterboard
connector
PCIe x8 connector
Mounting bracket
maxCache SSD support 71605Q: Up to 16 solid state drives, 2TB capacity, max. See the
maxCache compatibility list at www.adaptec.com/compatibility.
Zero Maintenance Cache Protection Adaptec Flash Backup Module AFM-700 (71605: optional, sold
Module separately; 71605Q: standard, pre-installed)
CN0
CN1
CN2
CN3
PCIe x8 connector
Mounting bracket
2 external
mini-SAS HD
connectors
Daughterboard
connector
PCIe x8 connector
Mounting bracket
Zero Maintenance Cache Protection Adaptec Flash Backup Module AFM-700 (optional, sold separately)
Module
HDA mode
connector
Ext. Alarm
connector
Daughterboard
connector
PCIe x8 connector
Mounting bracket
Zero Maintenance Cache Protection Adaptec Flash Backup Module AFM-700 (optional, sold separately)
Module
4 Getting Started
This chapter provides the basic information you need to set up your disk drives and arrays the way you
want them. It describes the options you have for installing your Adaptec RAID controller and disk drives
and creating arrays for storage. It also describes how to prepare your controller for installation into a
low-profile computer cabinet.
Disk Drives
Your SAS controller supports SAS disk drives, SATA disk drives, and SATA and SAS Solid State Drives
(SSDs). When selecting disk drives for your RAID array, ensure that all the disk drives have the same
performance level. You can use different-sized disk drives in the array, but the array will be limited to
the capacity of the smallest and slowest disk drive. For more information about arrays, refer to the
maxView Storage Manager User’s Guide or online Help. For more information about compatible disk
drives, refer to the Adaptec Web site at www.adaptec.com/compatibility.
Cables
Depending on your requirements, you can use any of the cables listed below. Cable connectors are
keyed so that you can't insert them incorrectly. For more information about cabling options for your
RAID controller, visit the Adaptec Web site at www.adaptec.com.
Note: We recommend using only Adaptec SAS cables.
Full-height bracket
Low-profle bracket
Back of board
Front of board
Remove mounting
screws with Phillips
screw driver
Back of board
Front of board
Figure 1
Figure 2
2. Attach the low-profile bracket to the controller board. The low-profile bracket is installed on the
back side of the controller, with the mounting screws inserted from the front of the controller, as
shown the Figure 3.
Insert the screws through the holes on the front of the controller, then fasten the screws to the
bracket with a Phillips screw driver.
Caution: The mount points on the low-profile bracket have a smooth or flat side
and a raised side that looks like a spacer (see Figure 3). Be sure to install the bracket
with the flat side against the controller PCB and the raised side facing away from
the PCB.
Front of board
Figure 3
Installation Options
When you install your Adaptec RAID 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.
3. Insert the RAID controller into the expansion slot and press down gently but firmly until it clicks into
place. When installed properly, the RAID controller should appear level with the expansion slot.
Caution: Touch a grounded metal object before handling the RAID controller.
4. Secure the bracket in the expansion slot, using the retention device (for instance, a screw or lever)
supplied with your computer.
5. Prepare and install your internal disk drives, following the instructions in Connecting Disk Drives to
Your Controllers on page 31.
If you are not installing internal disk drives, close your computer cabinet, reattach the power cord,
then continue with Connecting External Devices on page 33.
Recessed side
b) Thread the cable-ties through the slots on the supercapacitor module and affix to the mounting
plate, as shown in the next figure. The cable-ties should completely encircle the supercapacitor
module and mounting plate to ensure that it is held in place securely.
c) Set the mounting plate aside; continue with the steps below.
2. Turn off your computer and disconnect the power cord. Open the cabinet, following the
manufacturer's instructions.
3. Select an available PCIe expansion slot that's compatible with your RAID controller and remove the
slot cover, as shown in the figure below. (PCIe bus compatibility is marked on the controller figures
in About Your RAID Controller on page 16.) Be sure to choose a slot next to an empty slot in the
backplane; you will use the empty slot to install the supercapacitor mounting plate, after you install
the controller. Remove the slot cover for the mounting plate, then continue with the next step.
4. Insert the RAID controller into the expansion slot and press down gently but firmly until it clicks into
place. When installed properly, the RAID controller should appear level with the expansion slot.
Caution: Touch a grounded metal object before handling the RAID controller.
5. Secure the bracket in the expansion slot, using the retention device (for instance, a screw or lever)
supplied with your computer.
6. Attach the supercapacitor module to the RAID controller by inserting the connector into the socket
on the flash module daughterboard, as shown in the figure below. The connector attaches to the
socket in only one direction.
7. Install the mounting plate in the empty slot next to the controller, as shown in the next figure. After
securing the mounting plate to the card cage, verify that the supercapacitor module and mounting
plate sit above (and do not touch) the PCIe slot.
Gap
8. 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.
9. Prepare and install your internal disk drives, following the instructions in Connecting Disk Drives to
Your Controllers on page 31.
If you are not installing internal disk drives, close your computer cabinet, reattach the power cord,
then continue with Connecting External Devices on page 33.
10. Restart your computer.
The supercapacitor starts charging automatically. It should reach full charge in 3-4 minutes.
Note: Although you can connect both SAS and SATA disk drives to your SAS controller,
we recommend that you do not combine SAS and SATA disk drives within the same
array. See What is SAS? on page 59 for more information.
You have two connection options:
• To connect directly to the controller, see the following section.
• To connect to a backplane, see Connecting Drives to a System Backplane on page 32.
To connect Solid State Drives to your controller, see Connecting Solid State Drives (SSDs) on page 32.
2. Use an internal mini-SAS HD to SATA cable to attach the SSD(s) to the controller, as shown in the
example below.
To other SSDs
Internal x4 mini-SAS HD connector Single-port connector
3. When all SSDs have been installed and connected, close your computer cabinet, reattach the power
cord, then continue with Connecting External Devices on page 33.
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 35.
If you are completing a standard installation onto an existing operating system, continue with Installing
the Driver on an Existing Operating System on page 50.
Creating an Array
This section explains how to create an array.
A RAID 5 array is created in the examples shown in this section because RAID 5 provides the most security
and best performance with a minimum of three disk drives. However, you can choose to create an array
with a different RAID level; you can also change array level later, after the operating system is installed.
You can create an array using any of these tools:
• Adaptec RAID Configuration Utility (ARC)—BIOS-based menus and keyboard navigation (see the
following section).
• maxView Storage Manager—Graphical software application (running from a bootable installation
DVD) that you can navigate with your mouse (see About maxView Storage Manager on page 54).
• ARCCONF—Command line utility. For instructions, refer to the Adaptec RAID Controller Command
Line Utility User’s Guide.
You can use any of these tools, but the ARC utility is the quickest and easiest tool for this task.
Note: We recommend that you do not combine SAS and SATA disk drives within the
same array. maxView Storage Manager displays a warning if you try to create a logical
drive using a combination of SAS and SATA disk drives. See What is SAS? on page 59
for more information.
2. If you have more than one controller of the same model or family in your computer, select your
controller, then press Enter .
Array Size Press Enter , then press Enter again to use the default granularity of GB.
Write Caching Press Enter to use the default (Enable always), then press Y to confirm.
6. When the wizard opens, ensure that Express Configuration is selected, then click Next.
8. Click Finish.
maxView Storage Manager builds the logical drives.
9. Partition and format your logical drive.
The logical drives you created appear as a physical disk drives on your operating system. You must
partition and format these logical drives before you can use them to store data.
10. Close all windows, then click Reboot to restart your system.
11. Remove the Adaptec Installation DVD.
For information on installing and using maxView Storage Manager as a full software application,
refer to the maxView Storage Manager User's Guide.
12. Continue with the following section.
linux dd
5. Select Yes to indicate that you have a driver disk, then select the driver image from the USB drive
(typically, /dev/sda1).
6. Complete the Linux installation, following the on-screen instructions.
7. Continue with Managing Your Storage Space on page 54.
4. Make sure that "Install a new system or upgrade an existing system" is highlighted, then, at the end
of the "vmlinuz initrd=initrd.img" line press Space, type the following command, and press Enter:
linux dd
5. Select Yes to indicate that you have a driver disk, then select the driver image from the USB drive
(typically, /dev/sda1).
6. Complete the Linux installation, following the on-screen instructions, then reboot.
7. Assuming the USB driver disk is /dev/sda1, type the following commands to ensure that the driver
remains installed when you update the OS:
Red Hat Linux 6, Cent OS 6, Fedora Linux without Dynamic Kernel Module Support
Note: You will need the Installation CD for your operating system to complete this
task. You must have root privileges to install the driver image.
To install the Adaptec RAID controller driver while installing Red Hat 6, Cent OS 6, or Fedora Linux:
1. Insert your installation CD.
2. Restart your computer.
3. When the Welcome screen appears, press Enter at the boot prompt, type CTRL+ALT+F2 to switch
to the shell, then continue the installation by selecting your language and keyboard.
4. Insert the USB driver disk.
5. Assuming the USB drive is assigned to /dev/sda1, type the following commands to load the
controller driver:
6. Press ALT+F6 to switch back to the installation screen, then click Next.
7. Follow the on-screen prompts to continue the installation. When prompted to reboot the system,
press CTRL+ALT+F2 to switch to the console. Do not reboot before completing Step 8!
8. Type the following commands to complete the driver installation:
mkdir /mnt/sysimage/tmp/AACRAID
cp -r /AACRAID/* /mnt/sysimage/tmp/AACRAID
chroot /mnt/sysimage/
cd /tmp/AACRAID
sh ./fc-post-install.sh
exit
9. Press ALT+F6 to switch back to the installation screen, finish the installation, then reboot.
10. Continue with Managing Your Storage Space on page 54.
linux dd
6. When prompted to "Please choose the Driver Update medium," highlight the USB partition, then
select OK.
If the "choose Driver Update medium" screen is displayed again, assume that the driver was accepted
and select Back.
7. Follow the prompts to continue the installation.
Note: For SuSE Linux 11, switch to the console by typing CTRL+ALT+F2 when the
installation is between 50%-90% complete, type this command:
cp -a /update/install /mnt/tmp
...then press CTRL+ALT+F7 to return to the installation screen and complete the
installation as usual.
mkdir /AACRAID
mount /dev/sda1 /mnt
cp -R /mnt/* /AACRAID
umount /mnt
Note: The following steps assume you are installing Debian 6 using kernel 2.6.32-5.
cp -f /AACRAID/aacraid.ko-PRE_MOD
/lib/modules/2.6.32-5-486/kernel/drivers/scsi/aacraid/aacraid.ko
Debian 64-bit:
cp -f /AACRAID/aacraid.ko
/lib/modules/2.6.32-5-amd64/kernel/drivers/scsi/aacraid/aacraid.ko
6. Remove the USB drive.
7. Install the loadable module:
Debian 32-bit:
insmod /lib/modules/2.6.32-5-486/kernel/drivers/scsi/aacraid/aacraid.ko
Debian 64-bit:
insmod /lib/modules/2.6.32-5-amd64/kernel/drivers/scsi/aacraid/aacraid.ko
8. Press CTRL+ALT+F5 to switch back to the installation screen, then follow the on-screen prompts
to continue the installation.
Note: Do not press Continue at the end of the installation until you complete Step
9!
9. When prompted to reboot the system, press CTRL+ALT+F2 to switch to the console.
10. Type the following commands to complete the driver installation:
Debian 32-bit:
cp -f /AACRAID/aacraid.ko-POST_MOD
/target/lib/modules/2.6.32-5-486/kernel/drivers/scsi/aacraid/aacraid.ko
chroot /target
/sbin/depmod -a 2.6.32-5-486
update-initramfs -u -v
exit
Debian 64-bit:
cp -f /AACRAID/aacraid.ko
/target/lib/modules/2.6.32-5-amd64/kernel/drivers/scsi/aacraid/aacraid.ko
chroot /target
/sbin/depmod -a 2.6.32-5-amd64
update-initramfs -u -v
exit
11. Press CTRL+ALT+F5 to switch back to the installation screen, then reboot.
12. Continue with Managing Your Storage Space on page 54.
4. Assuming the USB drive is assigned to /dev/sda1, type the following commands to begin loading
the driver:
mkdir /AACRAID
mount /dev/sda1 /mnt
cp -R /mnt/* /AACRAID
umount /mnt
Note: The following steps assume you are installing Ubuntu 10 or 11, using kernel
2.6.32-28. For Ubuntu 12 or higher, the driver files aacraid.ko-PRE_MOD and
aacraid.ko-POST_MOD are both replaced by the single file aacraid.ko.
cp -f /AACRAID/aacraid.ko-PRE_MOD
/lib/modules/2.6.32-28-generic/kernel/drivers/scsi/aacraid/aacraid.ko
9. When prompted to reboot the system, press CTRL+ALT+F2 to switch to the console.
10. Type the following commands to complete the driver installation:
Ubuntu 32-bit:
cp -f /AACRAID/aacraid.ko-POST_MOD
/target/lib/modules/2.6.32-28-generic-pae/kernel/drivers/scsi/aacraid/aacraid.ko
chroot /target
/sbin/depmod -a 2.6.32-28-generic-pae
update-initramfs -u -v
exit
Ubuntu 64-bit:
cp -f /AACRAID/aacraid.ko-POST_MOD
/target/lib/modules/2.6.32-28-server/kernel/drivers/scsi/aacraid/aacraid.ko
chroot /target /sbin/depmod -a 2.6.32-28-server
update-initramfs -u -v
exit
11. Press CTRL+ALT+F1 to switch back to the installation screen, then reboot.
12. Continue with Managing Your Storage Space on page 54.
2. Interrupt the autoboot, press the ESC key. The Device Configuration Assistant (DCA) Utility will open.
3. Select Apply driver updates.
4. Insert the driver disk or other update media, then press Return.
5. Complete the Solaris installation, following the instructions included with your operating system.
10. To ensure that the driver is loaded automatically as a module at boot time, repeat Steps 4-7, then
complete the steps below.
11. Type this command to boot to the kernel: boot
12. Login as root, then type:
dmesg
13. Assuming the USB drive is da1s1, type this command to mount the drive:
mount -t msdosfs /dev/da1s1 /mnt
14. Install the driver package:
pkg_add /mnt/aac9x-amd64.tgz
Note: The distribution also includes driver packages for FreeBSD 8.
2. Download and install vSphere PowerCLI on your Windows build machine. You can download PowerCLI
from the VMware Download Center at www.vmware.com/downloads (for example,
VMware-PowerCLI-5.0.0-374833.exe).
3. Run PowerShell as Administrator, then set the execution policy to Remote Signed:
# Set-ExecutionPolicy RemoteSigned
4. Download the VMware ESXi5.0 Standard Software Depot (for example,
vmware-ESXi-5.0.0-469512-depot.zip) and store in a temporary location on your Windows
build machine. You can download the software depot from the VMware Download Center at
www.vmware.com/downloads. When you start the download, be sure to choose “ESXi Offline
Bundle”.
Note: You may need to provide account credentials to download the software
depot from the VMware Web site.
5. Insert the Adaptec Installation DVD, navigate to the Linux driver folder, then copy the Adaptec
AACRAID driver binary to a temporary location on the Windows build machine:
Options Description
ESXi 5.0 aacraid-esxi5.0-1.2.1.xxxxx.zip
where xxxxx is the build number.
After you copy the file, remove the Adaptec Installation DVD.
6. Launch vSphere PowerCLI, then follow the steps below to create the custom boot image:
a) At the PowerCLI prompt, add the VMware Image Builder snap-in by running the following cmdlet:
# Add-PSSnapIn VMware.ImageBuilder
Note: You will see a message if the Image Builder snap-in is already installed.
You can ignore this message.
Note: Continue using PowerCLI in Steps 6.b through 6.j.
where C:\ESXi5.0-PMC-CustomISO is the temporary folder on your build machine where the
software depot is stored.
c) Add the AACRAID driver binary as a software depot (where xxxxx is the build number):
# Add-EsxSoftwareDepot
C:\ESXi5.0-PMC-CustomISO\aacraid-esxi5.0-1.1.7.xxxxx.zip
where C:\ESXi5.0-PMC-CustomISO is the temporary folder on your build machine where the
software depot is stored.
d) Verify that the software depots are added:
# $DefaultSoftwareDepots
e) List ESX Image Profiles:
# Get-EsxImageProfile
You should see a display like this:
ESXi-5.0.0-469512-no-tools
ESXi-5.0.0-469512-standard
f) Create a copy of the standard image profile, using the -CloneProfile option:
# New-EsxImageProfile -CloneProfile ESXi-5.0.0-469512-standard -Name
"ESXi 5.0 Adaptec Series 7"
g) Change the vendor and acceptance level of the new image profile:
# Set-EsxImageProfile -ImageProfile "ESXi 5.0 Adaptec Series 7" -vendor
PMC-Sierra -AcceptanceLevel VMwareCertified
h) Check if the new driver package is available:
# Get-EsxSoftwarePackage
You should see a line like this:
Installing on Windows
Note: The following instructions apply to all supported Windows operating systems.
To install the driver on Windows:
1. Start or restart Windows.
The Found New Hardware Wizard opens and searches for the driver.
2. Insert the driver disk, then select Locate and Install Driver Software.... and Don't Search Online.
3. Click Next, then click Close.
4. When the installation is complete, remove the driver disk and restart your computer.
5. Continue with Managing Your Storage Space on page 54.
where mount-point is the mount point on the Linux system, xxx is the driver path, and yyy.rpm is
the rpm file.
3. Reboot your computer to ensure the driver loaded correctly.
4. Continue with Managing Your Storage Space on page 54.
Installing on Solaris
To install the driver on Solaris:
1. Start your computer.
2. (Solaris 10 only) Check for any pre-existing Adaptec driver by running pkginfo SUNWaac in a
terminal window . If there is no pre-existing Adaptec driver on your computer, continue with Step
3. If an Adaptec driver is already installed on your computer, run pkgrm SUNWaac to remove it.
Caution: If your operating system currently boots from the Adaptec controller,
do not reset your computer after you remove the pre-existing Adaptec driver.
Instead, follow the steps in this section to install a new driver before rebooting
your computer.
Solaris 11:
cd /rmdisk/aacraid/DU/sol_211/i86pc/Tools
5. Start the driver installer:
./install.sh -i
6. Remove the driver disk, then reboot your computer.
7. Continue with Managing Your Storage Space on page 54.
Installing on FreeBSD
To install the driver on FreeBSD:
1. Start your computer.
2. Insert and mount the driver disk:
mount -t msdos /dev/fd1 /mnt
3. Copy the driver package to the /tmp directory:
cp /mnt/aac8x-i386.tgz /tmp
4. Install the driver package:
pkg_add /tmp/aac8x-i386.tgz
5. Remove the driver disk, then reboot your computer.
6. Continue with Managing Your Storage Space on page 54.
Installing on VMware
Note: You must remove the old driver before you can install the new one. You must
have root privilege to install the new driver.
Note: To copy the driver VIB file to the VMware ESX/ESXi server (in Step 2 below),
you must have access to a remote copy utility, such as WinSCP, putty, or Linux scp.
To install the driver on VMware:
1. At the VMware console screen, type these commands to remove the old driver:
VMware ESX 4.1:
2. Using a remote copy utility, copy the driver VIB file for your operating system version from the Linux
driver folder on the installation DVD to a local directory on the ESX server. This example uses Linux
scp to copy the driver to /tmp/aacraid (where xxxxx is the build number):
VMware ESX 4.1:
scp
/mnt/cdrom/linux/driver/vmware-esx-drivers-scsi-aacraid-400.4.2.1.xxxxx-1.0.4.260247.x86_64.vib
root@<esx-server-ip>:/tmp/aacraid
Note: The ARC utility is primarily intended for pre-operating system installation
configuration.
10 Solving Problems
This chapter provides basic troubleshooting information and solutions for solving controller problems.
Troubleshooting Checklist
If you encounter difficulties installing or using your Adaptec RAID controller, check these items first:
• With your computer powered off, check the connections to each disk drive, power supply, LED
connector, and so on.
Try disconnecting and reconnecting disk drives from the Adaptec RAID controller.
• Check that your Adaptec RAID controller is installed in a compatible PCIe expansion slot. To
double-check the bus compatibility of your controller, see About Your RAID Controller on page 16.
• Ensure that your Adaptec RAID controller is firmly seated and secured in the PCIe expansion slot.
• If your Adaptec RAID controller is not detected during system boot, try installing it in a different
compatible expansion slot. (See Installing the Controller on page 27 for instructions.)
• Did the driver install correctly?
• If you have external disk drives (or other devices), are they powered on?
• Check the Readme on the installation DVD for compatibility issues and known problems.
If you are still unable to resolve a problem, you can find additional troubleshooting information and
direction on the Adaptec Web site at www.adaptec.com or the Support Knowledgebase at
ask.adaptec.com.
For more information about using maxView Storage Manager to monitor your disk drives, refer to the
maxView Storage Manager User’s Guide or the online Help.
• If it is a RAID 0 array, see Disk Drive Failure in a RAID 0 Array on page 57.
• If multiple disk drives fail within the same array, see Multiple Failures in the Same Array on page
57.
• If the drive is part of the maxCache Container, see Failed SSD in maxCache Container on page 58.
Note: maxView Storage Manager uses the term logical drives or logical devices when
referring to arrays (see Terminology Used in this Guide on page 13).
Note: In some instances, RAID 10 and RAID 50 arrays may survive multiple disk drive
failures, depending on which disk drives fail.
A Introduction to SAS
This section provides a basic overview of the main features of SAS, introduces some common SAS terms,
and explains how SAS differs from parallel SCSI.
Note: For technical articles and tutorials about SAS, refer to the SCSI Trade Association
(STA™) Web site at www.scsita.org.
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 expanders. See SAS Expander
Connections on page 62.)
Note: Although you can use both SAS and SATA disk drives in the same SAS domain
(see SAS Expander Connections on page 62), we recommend that you do 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 How Do
SAS Devices Communicate? on page 59). Link speed is 300 MB/sec in half-duplex mode. Therefore, a
SAS card with eight links has a bandwidth of 2400 MB/sec.
Although they share the SCSI command set, SAS is conceptually different from parallel SCSI physically,
and has its own types of connectors, cables, connection options, and terminology, as described in the
rest of this chapter.
To compare SAS to parallel SCSI, see How is SAS Different from Parallel SCSI? on page 63.
Receiver Transmitter
Phy Transmitter Receiver
Phy
Receiver Transmitter
Phy Transmitter Receiver
Phy
Wide Wide
Port Receiver Transmitter Port
Phy Transmitter Receiver
Phy
Receiver Transmitter
Phy Transmitter Receiver
Phy
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 What’s a SAS Connector? on page 61).
SAS cables physically connect one or more phys on one SAS device to one or more phys on another SAS
device.
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
in Connecting Drives Directly to the Controller on page 32 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 SAS Expander Connections on page
62.)
Backplane Connections
In a backplane connection, disk drives and SAS cards are attached to and communicate with each other
through a system backplane.
There are two types of backplane connections, passive and active. When connecting to either backplane,
it’s important to properly connect your disk drive LEDs in order to identify disk drive conditions. See
About Your RAID Controller on page 16 for your RAID controller Activity LED connections and locations.
Once you have connected to a backplane, use maxView Storage Manager to manage your disk drives.
For more information, refer to the maxView Storage Manager User’s Guide on the Adaptec Installation
DVD.
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.
Maximum speed 320 MB/sec shared by all devices Maximum speed 300 MB/sec per phy when in half-duplex
on the bus mode
Supports SCSI devices only Supports SATA and SAS disk drives simultaneously
Up to 16 devices per SCSI channel More than 100 disk drives per SAS card, using an expander
(see SAS Expander Connections on page 62) or 50 SATAII
disk drives.
Uses SCSI IDs to differentiate between devices Uses unique SAS addresses to differentiate between devices
connected to the same adapter
User intervention required to set SCSI IDs SAS addresses self-configured by SAS devices
B Understanding RAID
When you create arrays (or logical drives), you can assign a RAID level to protect your data.
Each RAID level offers a unique combination of performance and redundancy. RAID levels also vary by
the number of disk drives they support.
This appendix describes the RAID levels supported by your Adaptec RAID controller, and provides a basic
overview of each to help you select the best level of protection for your data storage.
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.
Disk Drive 1 3 6
Disk Drive 2 400 GB
Disk Drive 2 1 4
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.
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 1 4 .. . P
Disk Drives in Logical Drive RAID 5 Logical Drive = 750 GB plus Parity
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 67.)
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 3, P, 9 P, 7, 11 2, 6, P 4, P, 10 P, 8, 12 Total Unused
Space = 150 GB
Drive 1 Drive 2 Drive 3
250 GB 250 GB 250 GB Drive 4 Drive 5 Drive 6
400 GB 400 GB 400 GB
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 1 P1 . . . P2
Disk Drive 3 P1 3 . . . P1
Unused Space = 150 GB
Disk Drives in Logical Drive Based on the drive segment sizes used:
RAID 6 Logical Drive = 500 GB plus parity
(P1 & P2)
RAID 60 Arrays
Similar to a RAID 50 array (see RAID 50 Arrays on page 68), a RAID 60 array—also known as dual drive
failure protection—is built from eight disk drives configured as two or more RAID 6 arrays, and stripes
stored data and two sets of parity data across all disk drives in both RAID 6 arrays.
Two sets of parity data provide enhanced data protection, and striping improves performance. RAID 60
arrays also provide high data transfer speeds.
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.
Ctrl-A or uEFI/HII?
Your Adaptec RAID controller supports two interfaces to the BIOS-level RAID configuration options of
the ARC utility: Ctrl-A and uEFI/HII. On servers that support the Unified Extensible Firmware Interface,
or uEFI (version 2.10 or higher), the BIOS-level RAID configuration options are presented with a HII
interface, or Human Interaction Infrastructure, rather than the Adaptec Ctrl-A interface described in
this chapter. uEFI/HII provides an architecture-independent mechanism for initializing add-in cards, like
the Adaptec RAID controller, and rendering contents to the screen in a uniform way.
In the HII interface, access to the RAID configuration options is provided through the server's standard
BIOS. How you access the BIOS varies, depending on the manufacturer, but typically it's started by simply
pressing DEL. Once you enter setup, navigate to the "PMC maxView Storage Manager" option, typically
on the BIOS' "Advanced" menu, then scan for and select a controller.
From that point on, the HII menus and the Ctrl-A menus for configuring your RAID controller are almost
identical. For example, the top-most menu contains the same three choices: Logical Device Configuration,
Controller Settings, Disk Utilities (described above). Options in the lower-level menus are also similar.
In both interfaces, all the tools 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.
This chapter provides instructions for navigating and completing tasks with the Ctrl-A interface. To
complete tasks with the HII interface:
• Refer to the on-screen instructions for keyboard navigation and selection options.
• Refer to the option descriptions in this chapter for details about individual RAID configuration settings
and tasks.
Option Description
Power Management When enabled, switches the array to low power state, when the array/
drive is inactive.
Slow Down Drive After The duration of inactive state of the array/drive after which it is slowed
down to low power mode. This is an optional setting.
Note: The disk drive should support low power mode.
Power Off Drive After The duration of inactive state of the array/drive after which it is powered
off. This is an optional setting.
Note: Power Off Drive After duration should be greater
than Slow Down Drive After Duration.
Verify Drive After The regular time interval at which the system performs a health check
of the array/drive.
6. Press Tab.
7. Select the maxCache Read Cache setting (Enable/Disable).
8. Select the maxCache Write Cache setting (Enable/Disable).
9. Press Enter to accept the values.
Option Description
Drive's Write Cache When set to Enable All, write cache is enabled on all disk drives on the controller.
(Enabling the write cache overrides any individual drive settings in maxView Storage
Manager.) When set to Disable All, write cache is not used on the disk drives. When
set to Drive Specific, write cache is enabled/disabled on a per-drive basis in maxView
Storage Manager.
Caution: When write cache is enabled, there is a slight possibility
of data loss or corruption during a power failure.
Runtime BIOS 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.
Automatic Failover When enabled, the controller automatically rebuilds an array when a failed disk
drive is replaced. When disabled, the array must be rebuilt manually.
Array Background When enabled, the controller constantly verifies a redundant array. Note that there
Consistency Check may be a significant performance reduction. Default is disabled.
Array-based BBS Support 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.
SATA Native Command When enabled, NCQ is enabled. Disable this feature if you want to attach more than
Queuing (NCQ) 48 SATA II disk drives. Only available with SATA II disk drives.
Physical Drives Display When enabled, connected disk drives are displayed during system Power On Self
During POST Test (POST). Displaying the disk drives adds a few seconds to the overall POST time.
Default is disabled.
DVD/CD-ROM Boot Support When enabled, the system can be booted from a bootable DVD/CD. (This setting is
not available on all RAID controller models.)
Option Description
Removable Media Devices When enabled, removable media devices, such as CD drives, are supported. (This
Boot Support setting is not available on all RAID controller models.)
Default Background Task Sets the default priority for background tasks on the controller (such as logical drive
Priority creation) to High, Medium, or Low. Default is High.
Note: This setting applies to new tasks. It does not affect
currently running tasks.
LED Indication Mode When set to Activity and Fault, the drive activity LEDs blink to indicate I/O activity
(randomly depending on I/O load) and fault (steady 1Hz). When set to Fault Only,
the drive activity LEDs blink to indicate fault state only. For Series 6/6E controllers,
default is Fault Only.
Backplane Mode When set to Default, controller automatically sets the backplane mode to IBPI. To
set the backplane mode explicitly, select IBPI, SGPIO, or Disabled. Default is IBPI.
Note: With the default IBPI setting, the firmware sends
a SGPIO "Backplane_TYPE" signal if it recognizes that a
SGPIO Backplane is connected. If any connected SGPIO
backplane does not support the "Backplane_TYPE" signal,
or it does not support the IBPI protocol, you can manually
set the Backplane Mode to "SGPIO".
Selectable Performance When set to Dynamic, performance criteria adjusts automatically based on controller
Mode usage, RAID level, and disk drive type. When set to OLTP/Db, performance criteria
is optimized for transaction-oriented applications, such as data entry and retrieval.
When set to Big Block Bypass, DRAM write cache is bypassed based on I/O write
size; performance criteria is optimized for serving Web pages, file serving, and data
retrieval. When set to User Defined, you are prompted to use the OS tools to set
individual parameters (contact Adaptec support for more information). Default is
Dynamic.
Controller Mode When set to RAID Mode, all RAID functions of the controller are enabled. When set
to Auto Volume Mode, RAID functions of the controller are enabled. Attached drives
without Adaptec meta-data, but with an OS partition, are surfaced to the host
operating system as Pass Through devices, where the RAID layer of the controller
firmware is bypassed when the host issues commands to the device. Attached drives
without Adaptec meta-data and without OS partitions, are automatically configured
as Simple Volumes. When set to HBA Mode, attached drives are surfaced as Pass
Through devices. Changing into HBA mode is allowed only if there are no drives with
Adaptec meta-data attached to the controller (see Uninitializing Disk Drives on page
74 for more information). Default is RAID Mode.
Note: Make sure the operating system driver supports power management.
Option Description
Power Management When enabled, switches the system to low power state, based on the specified
Settings settings.
Option Description
Time Zone The time zone of the place in which the system is located. Time specific power
management settings are implemented based on the set time zone. By default, it is
set to 00:00.
The valid range for the time zone settings is -12:00 to +12:00.
Stay Awake Start The time from which the system should operate in the full power mode, irrespective
of other power management settings, daily. By default it is set to 00:00.
The valid range is 00:00 to 23:59.
Stay Awake End The time until which the system should operate in the full power mode, irrespective
of other power management settings, daily. By default it is set to 00:00.
The valid range is 00:00 to 23:59.
Spin Up Limit (Internal) The number of internal drives to be spun up at any given moment. By default it is
set to 0. In the default setting, all the internal drives will spin up.
Spin Up Limit (External) The number of external drives to be spun up at any given moment. By default it is
set to 0. In the default setting, all the external drives will spin up.
CN1=DEV1 The manufacturer The revision The speed of the The size of the disk
Box0=Slot0 information. number of the disk disk drive. drive.
Exp0=phy0 drive.
System Requirements
• DOS version 5.0 or later.
Note: You can’t run the AFU from a DOS command prompt window under any
version of Windows.
• At least 8 MB of extended memory.
Compatibility Notes
• Supports HIMEM.SYS; compatible with other DOS drivers running under HIMEM.SYS (for example,
SMARTDRV.SYS and SETVER.SYS).
• Does not support DOS extenders installed in memory, such as EMM386.SYS and DOS4GW.
7. Complete the flash operation and restart your computer before trying to use the RAID controller
again. (You can not use your RAID controller while you are updating its flash.)
The AFU processes the selected command, prompts you to insert additional floppy disks as needed,
and reports either success or an error message code.
The AFU processes the command, prompts you to insert additional floppy disks as needed, exits,
and reports either success or an error message code.
To update a RAID controller’s flash using the command line utility ARCCONF, see Updating the Flash
Using the AFU Command Line on page 83.
AFU Commands
This section lists the available AFU commands.
List
Displays the AFU-supported RAID controllers installed on your computer. Also displays the ID numbers
assigned to each controller.
You don’t have to restart the computer after completing this command.
Save
Saves the contents of a RAID controller's flash in a UFI file. The name of the UFI file is based on the
controller type and can't be changed.
You must restart the computer following a SAVE command.
The command syntax for the SAVE command is:
AFU SAVE [/C<Controller ID>] [/D <UFI File Path>]
These switches are available:
• /C <Controller ID>—One or more RAID controller IDs representing the set of RAID controllers on
which to perform the specified command. The default is 0; if the computer has multiple RAID
controllers, the AFU defaults to controller 0 unless you specify otherwise.
For example:
To specify a single RAID controller ID: /C 0
To specify multiple IDs separated by commas: /C 0,2
To indicate all RAID controllers:ALL
If you are using multiple RAID controllers, you must specify the controller you want by using the /C
switch; otherwise, the AFU displays an error message and exits.
• /D <UFI File Path>—Specifies the path where the UFI files are located. If you do not specify the /D
switch, the AFU looks for (or creates) its UFI files in the default location.
You cannot specify the name of a UFI file, only its path. UFI filenames are predefined, based on the
RAID controller type.
In this example, the AFU saves flash contents from RAID controller 0 to a UFI file in the current
default drive and directory:
A:\> AFU SAVE /C 0
In this example, the AFU saves flash contents from Controller 1 to a UFI file in C:\UFI_FILES:
A:\> AFU SAVE /C 1 /D C:\UFI_FILES
Update
Updates the flash components of one or more RAID controllers on your computer from the flash image
data in a UFI file. You must restart the computer following an UPDATE command.
The command syntax for the UPDATE command is:
AFU UPDATE [/C<Controller ID>] [/D <UFI File Path>]
Verify
Compares the contents of each of the flash components on a RAID controller to the corresponding
image in a UFI file, and indicates whether they match. After using the VERIFY command, you must restart
the computer.
The command syntax for the VERIFY command is as follows:
AFU VERIFY [/C<Controller ID>] [/D <UFI File Path>]
Version
Displays version information about the flash components on a RAID controller. After using the VERSION
command, restart your computer.
The command syntax for the VERSION command is:
AFU VERSION [/C<Controller ID>]
This example displays version information about all supported RAID controllers.
Help
Displays a summary of AFU functions and command switches.
For example:
A:\> AFU HELP
A:\> AFU /?
7. When prompted, insert the first firmware disk into your floppy disk drive.
The AFU reads the first disk.
8. When prompted, remove the first firmware disk and insert the second firmware disk into your floppy
disk drive.
9. Repeat Step 8 as required.
1 +3.3V —
1 +3.3V —
F Safety Information
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.
G Technical Specifications
Environmental Specifications
Note: Adaptec RAID controllers require adequate airflow to operate reliably. The
recommended airflow is 200 LFM (linear feet per minute), minimum. Forced airflow
is required.
DC Power Requirements
Bus Type Description Requirements
Current Requirements
Adaptec Model Typical Current
Index
A B
activity LED connector specifications 84 backplane connections 32, 61, 62, 78
Adaptec Flash Utility, See AFU batteryless backup 27, 28
Adaptec RAID Configuration utility 54 Big Block Bypass mode 76
Adaptec RAID Controller Configuration utility, See boards, See controllers
ARCCONF boot controller 26, 35
adapters, See controllers bootable arrays 16, 34, 35, 36, 38, 39, 72, 73
advanced data protection 16 creating 16, 34, 35, 38, 39, 72, 73
AFU 55, 79
Alarm Control setting 76
ARC 16, 35, 38, 56, 72, 73, 74, 75, 76, 77
C
checking flash backup unit 77 cards, See controllers
creating arrays 35, 72 CD-ROM Boot Support setting 75
creating bootable arrays 16, 38, 72, 73 checking flash backup unit 77
HII interface 35 command line interface (flash utility) 79, 80
initializing disk drives 72, 74 command line utility 54
managing arrays 72 concept 13, 14, 35, 54, 55, 57
modifying controller settings 56, 75 connectors 61, 78
opening Controller Settings tool 75 contents of controller kit 15
rescanning disk drives 74 Controller Mode 76
secure erasing disk drives 74 Auto Volume Mode 76
stopping a secure erase 74 HBA Mode 76
uninitializing disk drives 74, 76 RAID Mode 76
ARC Controller Settings 75 controllers 13, 15, 16, 17, 23, 25, 26, 27, 28, 29, 31, 32,
applying changes 75 33, 35, 56, 58, 61, 62, 63, 71, 72, 74, 75, 76,
exiting 75 77, 78, 79, 84, 86
ARCCONF 16, 54 alarm connector specifications 84
Array Background Consistency Check setting 75, 77 Alarm Control setting 76
array migration 16 Array Background Consistency Check setting 75, 77
Array-based BBS Support setting 75 Array-based BBS Support setting 75
arrays 16, 23, 35, 36, 38, 64, 65, 67, 68, 69, 72, 73 array-level features 16
creating (ARC) 35, 72 Automatic Failover setting 75
creating (maxView Storage Manager) 36 CD-ROM Boot Support setting 75
creating bootable arrays 16, 38, 72, 73 connecting disk drives 28, 31
making an array bootable 36, 38 connecting external devices 28, 31, 32, 33
managing with ARC 72 data protection 16
non-redundant 23, 64 descriptions 13, 15, 16, 27, 29, 31, 32, 56, 58, 62
RAID 1 23, 65 disk drives 23, 27
RAID 10 23, 65 Drive's Write Cache setting 75
RAID 1E 23, 65 event log 78
RAID 5 23, 67, 68 figures 13, 15, 16, 27, 29, 31, 32, 56, 58, 62
RAID 50 23, 68, 69 firmware 79
RAID 6 23, 69 flashing 58
RAID 60 23, 69 installation options 25
arrays (bootable) 34, 35, 39 installing 27, 56
audible alarm 56 modifying general settings 74, 75
Auto Volume Mode 76 modifying settings with ARC 71, 74
automatic failover 16 Physical Drives Display During POST setting 75
Automatic Failover setting 75 RAID levels 23, 31, 72
Removable Media Devices Boot Support setting 76
resetting 58
Runtime BIOS setting 75
Z
U
zero maintenance cache protection 16, 27, 28
uEFI 35, 71