LSI SAS2 manual Interface Description Commands, Efi

Page 32
Format commands as follows for the SAS2IRCU command-line interface: sas2ircu <controller_#> <command> <parameters>
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 the SAS2IRCU through the command line, the standard output and standard error interfaces, and the program return value. You can 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 RAID command fails, the SAS2IRCU prints the IOCStatus and IOCLogInfo on the console. You can use this information to analyze the cause of the failure.
The following table shows which commands the SAS2IRCU supports on each operating system.
Table 1: SASIRCU Commands
SAS2 Integrated RAID Solution User Guide
SAS2IRCU requires PCI™ 2.x or PCI 3.0 firmware and MPI v2.0. SAS2IRCU supports the following operating systems:

Appendix A: Interface Description

A.1.2 Operating System and Software

Support

WinPE 1.x (Server 2003/XP), WinPE 2.0 (Vista), WinPE 2.1 (Server 2008) Requires Windows® driver v2.00.00.17 or greater.

UEFI 2.1

Linux® 2.6 Kernel - Red Hat® Enterprise Linux (RHEL) 5, SUSE® Linux Enterprise Server (SLES) 10

Requires Linux driver v00.255.04.00 or greater.

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 locate the controller and its interface registers because it must directly access the controller chip’s interface registers.

A.2 Interface Description

A.3 Commands

SAS2IRCU

 

Operating System

 

 

 

 

 

Command

DOS

Linux

EFI

WinPE

 

 

 

 

 

 

CREATE

X

X

X

X

 

 

 

 

 

DELETE

X

X

X

X

 

 

 

 

 

DISPLAY

X

X

X

X

 

 

 

 

 

HOTSPARE

X

X

X

X

 

 

 

 

 

LIST

X

X

X

X

 

 

 

 

 

STATUS

X

X

X

X

 

 

 

 

 

MFGPAGE

X

 

 

 

 

 

Page 32

LSI Corporation Confidential August 2010

Image 32
Contents SAS2 Integrated RAID Solution Revision History Table of Contents Table of Contents Introduction to the Integrated RAID Solution FeaturesOverview Enhanced RAID 1EBenefits and Features Types of mirrored arrays Overview of Integrated RAID Mirrored VolumesIntroduction Operation of Mirrored Volumes Typical Integrated Mirroring Implementation Integrated Mirroring Enhanced with Three Disks Mirrored Volume Features SAS2 Integrated RAID Solution User Guide Creating Mirrored Volumes Mirrored VolumeConfiguration Overview Please wait, invoking SAS Configuration UtilitySelect Create RAID 1 Volume Create New Array window appearsSelect Create RAID 1E Volume Expanding an Integrated Mirroring Volume with OCE Manage Array window appears Select New Array Type window appearsArray on this adapter Following figureManage Hot Spares window appears Smart supportHot Spare status changes to Yes Press C to create the hot spare diskOther Configuration Tasks Follow these steps to activate a selected volume Currently inactivePress Enter Select RAID Properties, and then press EnterFollow these steps to select a boot disk SAS2 Bios CU, select an adapter from the Adapter ListHighlight SAS Topology, and press Enter SAS Topology window appearsBoot Device on SAS Topology Window Overview of Integrated Striping Boot disk or as a data diskVolumes can consist of two-to-ten disks Integrated Striping Description Integrated Striping ExampleCreating Integrated Striping Volumes Creating Integrated Striping VolumesSelect Create RAID 0 Volume Viewing Volume Properties Activating an Array Select Delete Array Alternate device Following figure showsSAS2 Integrated RAID Solution User Guide Requirements Using the SAS2 Integrated RAID Configuration UtilityHardware and Software Interface Description Commands EFICommand to get the enclosure and slot numbers of a drive GB of capacity on the disk driveFollowing fields of IOC Page 6 specify the configuration MPI2 specification and is specific for SSD drives only VolumeName a user-specified string to identify the volume Appearing while the command is runningSas2ircu controller# delete noprompt Sas2ircu controller# display filename112 Initiator IDDrive Type Enclosure information Enclosure# Logical IDConfiguration has changed or a drive has failed Failed FLD The volume has failedMissing MIS The volume is missing Initializing Init The volume is initializingSas2ircu controller# hotspare delete EnclosureBay Sas2ircu controller# status Volume status Enabled or Disabled  Physical disk I/Os Quiesced or Not quiescedSas2ircu list NoneSas2ircu controller# constchk volumeId noprompt Sas2ircu controller# activate volumeIdSas2ircu controller# logir action filename noprompt