To Complete the Installation

Language:

Replace the system cover and reconnect the AC power cords, as described in the system documentation.

If you needed to turn the system power off as part of the installation, turn power on to the system.
Note - Ensure that the power is turned on to the SAS devices, SATA II devices, or both before or at the same time that the power is turned on to the host system. If the system is powered up before these devices, the devices might not be recognized.

If you need to install an OS on your system, complete the procedures in Creating a Bootable Drive in a Preboot Environment and then go to the next step.

If you already have an OS installed on an x86 system, review the BIOS bootup messages to ensure that you see the LSI BIOS initialization banner and that you are prompted for the BIOS utility (by pressing Ctrl+C).
If you see the banner and are prompted for the utility, it means the BIOS has detected the HBA card.

If you already have an OS installed on a SPARC system, during the power-up process of the system, use the probe-scsi-all command at the Open Boot Prompt (OBP) ok prompt to verify that the system recognizes the HBA.

The probe-scsi-all command displays the SCSI devices that are connected to the host, as shown in the following example.

{0} ok probe-scsi-all
/pci@0/pci@0/pci@8/pci@0/pci@a/LSI,sas@0 
MPT Version 2.00, Firmware Version 4.00.00.00 
Target 9
  Unit 0   Disk     SEAGATE ST914602SSUN146G0603    286739329 Blocks, 146 GB 
  SASAddress 5000c5000b305b4d  PhyNum 0
Target a
  Unit 0   Disk     SEAGATE ST914602SSUN146G0603    286739329 Blocks, 146 GB 
  SASAddress 5000c5000b304cad  PhyNum 1
Target b
  Unit 0   Disk     HITACHI H101414SCSUN146GSA23    286739329 Blocks, 146 GB 
  SASAddress 5000cca000310015  PhyNum 2
Target c
  Unit 0   Disk     HITACHI H101414SCSUN146GSA23    286739329 Blocks, 146 GB 
  SASAddress 5000cca0002cf035  PhyNum 3
{0} ok

This example shows a SAS 2 controller (LSI,sas@0) connected to four physical drives.

(Optional) If you would like to create additional RAID volumes on the system (maximum of two RAID 0, 1, and 10 volumes per system), follow either or , then continue with :
1. (SPARC only) During the power-up process of the system, access the OBP and create RAID volumes for the HBA by issuing the appropriate FCode commands.
  For more information about the different FCode commands that you can use to create RAID volumes, see Creating a Bootable Drive in a Preboot Environment .
2. (x86 only) During the power-up process of the system, review the BIOS bootup messages, access the BIOS Configuration utility by pressing Ctrl+C, when prompted, and create volumes for the HBA through the BIOS utility.
  For more information about creating volumes through the BIOS utility, see Creating a Bootable Drive in a Preboot Environment .
3. Go to the Oracle support area of the LSI web site (http://www.lsi.com/sep/Pages/oracle/index.aspx), download the SAS2IRCU utility, and issue the sas2ircu command, with no options, at the command-line or at a terminal window.
  Issuing the sas2ircu command, with no options, produces a list of SAS2IRCU utility commands that you can use to create RAID volumes for the HBA. Upon reviewing the list of commands, use the appropriate commands to create the RAID volumes.
  
  Note - With version 04.250.04.02 of the SAS2IRCU utility, be careful when using the DELETE command. The DELETE command can take no arguments or a single argument. Issuing the DELETE command with no arguments deletes all RAID volumes. Issuing the command with a single argument deletes only the RAID volume that you specify in the argument. With version 6.250.02.00 of the SAS2IRCU utility or later, use the DELETEVOLUME command to delete a single RAID volume.
  
  For more information about the RAID configuration utilities, see Installing the RAID Configuration Utility.
After you initiate the creation of a RAID 1 or RAID 10 volume, the HBA performs a background initialization task that synchronizes untouched blocks of each side of the mirror for the entire volume. This background task operates transparently, and does not prevent normal communication with the volume or immediate mirroring of new data written to the volume. However, applications might experience performance degradation until the background initialization task is complete.