JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
SPARC T5-2 Server Product Notes
Oracle Technology Network
Print View
search filter icon
search icon

Document Information

Using This Documentation

Late-Breaking Information

SPARC T5-2 Servers Available with 1 or 2 Processors

Preinstalled Software

Minimum Supported Versions of the Firmware, OS, and Software

Mandatory Oracle Solaris 11 OS Package Updates

Mandatory Oracle Solaris 10 OS Patches

Oracle Solaris 10 1/13 Mandatory Patches

Oracle Solaris 10 8/11 Mandatory Patches

Oracle Solaris 10 9/10 Mandatory Patches

Obtain Patches

Installing and Booting Oracle Solaris 11 from Devices Connected to a USB Port

Known Issues

When You Create Logical Domains, Some Memory Is Reserved By the Server

Oracle Dual Port QDR InfiniBand Adapter M3 Requires a Mimimum Firmware Level

sas2ircu Might Fail to Create a RAID Volume (15788910)

rKVMS Does Not Support Redirecting Storage From a SPARC Client (15795058)

Mouse Pointer Is Not Aligned With the Cursor in a Remote Window (15798251)

kmdb: failed to allocate xxx bytes -- recovering Error Message (15806455)

xhci Device Failed During Boot on USB Ports (15809582)

/System/Cooling Target Lists Power Supply Fans as Not Supported (15809846)

Server Does Not Support Booting Oracle Solaris From a USB Flash Drive (15810161)

File Descriptor Leakage in libldom/ldom_xmpp_client.c (15811297)

In Some Cases, Spurious Faults of Type fault.sunos.eft.unexpected_telemetry Are Reported (15820471)

ilomconfig Might Report Internal Error (15823485)

Active mempm Should Balance Cage Assignment Across All Nodes (15944881)

POST Does Not Work After a Reconfiguration Call From HC (15968276)

Some USB 3.0 Devices Cause Timeouts and Might Hang the Host (16019551 and 15985683)

Drive OK to Remove LED Might Not Illuminate When a Drive is Unconfigured (16051551)

FPGA iPOST power-on-reset, error-reset, and hw-change Triggers Do Not Work (16192025)

Oracle ILOM Gets Confused When Multiple LDOM Configuration Files Exist With the Same Name (16239544)

CPU Power Management Can Lower Disk IOPS Performance (16355418)

ldm unbind of an SDIO or SRIOV Domain Hangs (16426940)

Oracle Solaris 10 OS Does Not Display Some Fault Information (16456603)

Infrequent SAS Disconnected command timeouts Might Be Displayed (16562940)

Management of SP Does Not Display a Table as Expected (16607793)

Drive Controller Not Ready When the Driver Tries To Attach (16608475)

RAID 10 Volumes Created Instead of RAID 1e on an Even Number of Target Disks (18335578)

sas2ircu Might Fail to Create a RAID Volume (15788910)

When you use the sas2ircu command within Oracle Solaris to create a RAID volume, the command might report that volume creation has failed. For example:

# ./sas2ircu 0 create raid0 max 1:0 1:1 1:2 my-RAID0
LSI Corporation SAS2 IR Configuration Utility.
Version (2012.07.04) 
Copyright (c) 2009-2012 LSI Corporation. All rights reserved. 
You are about to create an IR volume.
WARNING: Proceeding with this operation may cause data loss or data
 corruption. Are you sure you want to proceed (YES/NO)? yes
WARNING: This is your last chance to abort this operation. Do you wish 
 to abort (YES/NO)? no 
Please wait, may take up to a minute... 
@ Nov  6 09:46:47 sys-33 scsi: /pci@300/pci@1/pci@0/pci@2/scsi@0 (mpt_sas0):
Nov  6 09:46:47 sys-33        Volume 0 is now , enabled, inactive 
@ Nov  6 09:47:45 sys-33 scsi: WARNING: /pci@300/pci@1/pci@0/pci@2/scsi@0
Nov  6 09:47:45 sys-33       passthrough command timeout@ SAS2IRCU: IocStatus = 0 IocLogInfo = 0
SAS2IRCU: Volume creation failed. 
SAS2IRCU: Error executing command CREATE 

If you retype the sas2ircu command at the Oracle Solaris prompt, the command will fail. The sas2ircu command will state that the wrong number of disks have been provided, since they had already been committed to a volume. For example:

# ./sas2ircu 0 create raid0 max 1:0 1:1 1:2 my-RAID0 
LSI Corporation SAS2 IR Configuration Utility. 
Version (2012.07.04) 
Copyright (c) 2009-2012 LSI Corporation. All rights reserved.
SAS2IRCU: Number of drives specified is higher than number of drives 
available to create a RAID volume! 
SAS2IRCU: Error executing command CREATE. 

After the initial failure of the sas2ircu command, other disk utility commands, such as format, might show disk members of the volume marked as drive not available. The format command might appear to hang and will require that you type Ctrl-C to abort the command. For example:

# format
Searching for disks...done
       0. c0t500151795955C40Ed0 <drive not available> 
@           /scsi_vhci/disk@g500151795955c40e
       1. c0t500151795955C19Ed0 <drive not available> 
@           /scsi_vhci/disk@g500151795955c19e
       2. c0t5001517959567D4Dd0 <drive not available>
@           /scsi_vhci/disk@g5001517959567d4d

Workaround: Reboot the system to restore the volume to a working state.

# reboot

Alternatively, you can use one of the other available methods to create the volume, instead of the sas2ircu command.