SAS-2 Integrated RAID Configuration Utility (SAS2IRCU) User Guide
November 2012
Revision History
Version and DateDescription of Changes
Version 1.1, November 2012
Version 1.0, February 2012Initial release of this document.
Added information about new commands DELETEVOLUME, BOOTIR, BOOTENCL, and HELP.
Added support for 4-KB sector disk drives.
Updated information about supported operating system architecture, supported LSI
controller chips, and supported operating systems.
LSI and the LSI & Design logo are registered trademarks of LSI Corporation or its subsidiaries. All other brand and product names may be trademarks of their respective companies.
!LSI Corporation reserves the right to make changes to the product(s) or information disclosed herein at any time without notice. LSI Corporation does not assume any responsibility or liability arising out of
the application or use of any product or service described herein, except as expressly agreed to in writing by LSI Corporation; nor does the purchase, lease, or use of a product or service from LSI Corporation
convey a license under any patent rights, copyrights, trademark rights, or any other of the intellectual property rights of LSI Corporation or of third parties. LSI products are not intended for use in life-support
appliances, devices, or systems. Use of any LSI product in such applications without written consent of the appropriate LSI officer is prohibited.
SAS-2 Integrated RAID Configuration Utility (SAS2IRCU) User Guide
November 2012
Hardware and Software Requirements
SAS-2 Integrated RAID Configuration Utility (SAS2IRCU) User Guide
This document explains how to use the command-line-driven SAS-2 Integrated RAID configuration utility (SAS2IRCU)
to create Integrated RAID volumes on LSI SAS-2 controllers.
You execute SAS2IRCU commands from a command-line prompt or a shell script. When you use a SAS2IRCU
command, the program returns a status value to the operating system when it exits.
You can use SAS2IRCU to quickly and efficiently configure Integrated RAID devices on LSI SAS-2 controllers.
NOTE In this document, the term disk means hard disk drive (HDD) and solid state drive (SSD), and the HDDs
or SSDs can support either SAS or SATA protocol.
1Hardware and Software Requirements
SAS2IRCU runs on the following operating system architecture:
Windows®: x86, x64 (AMD64)
Linux®: x86, x86_64 (supported with x86 build), PPC64
UEFI: EFI Byte Code (EBC)
Solaris®: x86 (or compatible), SPARC®
FreeBSD®: x86 (or i386), AMD64 (or compatible)
SAS2IRCU operates with storage devices that are compliant with existing SCSI standards.
1.1Controller Support
SAS2IRCU supports the following LSI SAS-2 controllers and the host bus adapters based on these controllers:
SAS2IRCU requires PCI 2.x or PCI 3.0 firmware and MPI v2.0. SAS2IRCU supports the following operating systems.
NOTE LSI® recommends that you use the latest version of the driver for any operating system.
Windows Server® 2003, Windows XP, Windows Vista®, Windows Server 2008 R2, Windows 7, Windows 8,
Windows Server 2012
UEFI 2.1, UEFI 2.3
LSI Corporation
- 3 -
SAS-2 Integrated RAID Configuration Utility (SAS2IRCU) User Guide
November 2012
Linux 2.6 Kernel - Red Hat® Enterprise Linux (RHEL) 5 and higher, SUSE® Linux Enterprise Server (SLES) 10 and higher
Requires the Linux driver v00.255.04.00 or greater. LSI recommends that you use the latest version of the driver
available on the LSI website.
MS-DOS® 6.22 and FreeDOS 1.0
SAS2IRCU runs on DOS only if the system BIOS supports 32-bit BIOS services, including the PCI BIOS services.
SAS2IRCU uses these services to directly access the controller and its interface registers.
Solaris 10 update 10, Solaris 11 express (CPU – x86 and x64)
Oracle® provides a built-in Solaris 10 driver for the LSI 3Gb/s and 6Gb/s SAS and SCSI adapters. Installation of an
LSI driver is not required. For information about installing the Oracle Solaris 10 driver, refer to the Oracle website.
Contact Oracle directly if you have questions about the Oracle driver.
FreeBSD 7.2 and higher in both 32-bit and 64-bit architecture
VMware® ESXi 5.0
2Interface Description
Use this syntax for SAS2IRCU commands:
sas2ircu <controller_#> <command> <parameters>
Interface Description
Use a space to separate the program name, the controller number, the command, and the parameters fields. The
format of <parameters> is command specific.
Information passes between the user environment and SAS2IRCU through the command line, the standard output
and standard error interfaces, and the program return value. It is possible to redirect the output streams as permitted
by the operating system. When the program exits, it returns a value of 0 if the command is successful. Otherwise, it
returns a value of 1.
If a command fails, SAS2IRCU prints the IOCStatus and IOCLogInfo on the console. This information is useful in
determining the cause of the failure.
3Commands
The following table lists the SAS2IRCU commands and shows which commands are supported on each operating
system. Click the hyperlinks to view information about the commands.
Table 1 SASIRCU Commands
SAS2IRCU
Command
CREATEXXXXX
DELETEXXXXX
DOSLinuxEFISolarisFreeBSD
Operating System
DELETEVOLUMEXXXXX
DISPLAYXXXXX
HOTSPAREXXXXX
LISTXXXXX
STATUSXXXX X
LSI Corporation
- 4 -
SAS-2 Integrated RAID Configuration Utility (SAS2IRCU) User Guide
November 2012
Table 1 SASIRCU Commands (Continued)
Commands
SAS2IRCU
Command
CONSTCHKXXXXX
ACTIVATEXXXXX
LOCATEXXXXX
LOGIRXXXXX
BOOTIRXXXXX
BOOTENCLXXXXX
HELPXXXXX
DOSLinuxEFISolarisFreeBSD
The commands are not case sensitive. The individual command descriptions that follow use the following
conventions:
Replace text enclosed in < > with a required parameter, such as a controller number or a volume type.
Replace text enclosed in [ ] with an optional parameter.
Enter parameters enclosed in { } one or more times, as required for the command.
Do not use the command-line definition characters < >, [ ], and { } on the command line.
3.1Common Command-Line Parameters
Operating System
This section describes command-line parameters that are common to more than one command.
<controller_#>
The unique controller number that the program assigns to each PCI function found on supported controller chips
in the system, starting with controller # 0. For example, in a system containing two LSISAS2008 controllers,
controller # 0 references the first controller and controller # 1 references the other controller. Use the LIST
command to view a list of controllers connected to the system and the controller number for each controller.
Valid controller number values are 0 to 255 (decimal).
<Enclosure:Bay>
The enclosure and bay (or slot) of a peripheral device attached to the bus. The argument must use a colon ( : ) as a
separator and must follow the Enclosure:Bay format. Enclosure is a 16-bit EnclosureHandle value set by the I/O
controller (IOC). A value of 0 is invalid. Bay/Slot is a 16-bit slot value set by the IOC. Use the DISPLAY command to
determine the enclosure number and slot number of a drive.
3.2CREATE
The CREATE command creates Integrated RAID volumes on LSI SAS-2 controllers.
When you add a disk to an Integrated RAID volume, the volume might not use all of the disk’s storage capacity. For
example, if you add a 300-GB disk drive to a volume that only uses 200 GB of capacity on each disk drive, the volume
does not use the remaining 100 GB of capacity on the disk drive.
The disk identified by the first Enclosure:Bay on the command line becomes the primary disk drive when you create an
Integrated Mirroring (RAID 1) volume. If the controller resynchronizes the disk drives, the data on the primary disk
drive becomes available when you access the newly created volume.
When the Integrated RAID firmware creates a RAID 1 volume, it starts a background initialization of the volume. Use
the STATUS command to monitor the status of the initialization.
LSI Corporation
- 5 -
Loading...
+ 11 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.