![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Solution Type Technical Instruction Sure Solution 1005358.1 : Hardware RAID usage on X64 based systems with the LSI SAS1064
PreviouslyPublishedAs 207472
Applies to:Sun Fire X4100 M2 ServerSun Fire X4100 Server Sun Fire X4200 M2 Server Sun Fire X4200 Server Sun Fire X4600 M2 Server All Platforms GoalDescriptionThis document contains information related to configuration of the LSI SAS1064 disk controller IC on Sun X64 based systems & information related to its hardware RAID feature. To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Sun x86 Systems SolutionSteps to FollowThe Sun Fire [tm] X4100, Sun Fire [tm] X4100 M2, Sun Fire [tm] X4200, Sun Fire [tm] X4200 M2, Sun Fire [tm] X4600, Sun Fire [tm] X4600 M2 servers contain the LSI Logic Serial Attached SCSI (SAS) SAS1064 disk controller IC. It is based on the Fusion-MPT (Message Passing Technology) architecture. The LSISAS1064 four-port controller key features include a 133MHz bus, PCI-X host interface, 3Gb/s data transfer rates per port, hot plug/hot swap capability, and Integrated RAID for enhanced data protection. SAS controllers support command queuing to maximize drive performance. Interrupt coalescing is another advanced feature of the controllers that improves system performance by reducing the number of interrupts per I/O to less than one. Additional information regarding this controller can be found in the product brief at the LSI website This controller provides for the creation of as many as two hardware RAID volumes for a 4 disk system. It supports either two-disk RAID 1 integrated mirror (IM) volumes or two-, three-, or four-disk RAID 0 integrated stripe (IS) volumes. OS based RAID control software is Sun's supported control of the RAID volumes. The LSI firmware is contained within the server's firmware & driver download. This can be found at the Sun System Firmware Release page. If HW RAID is used, the LSI firmware version should track the SP firmware's version, as shown in the table below. The LSI firmware version is displayed during boot. The SP firmware version can be derived from the SP's firmware build # from the CLI's version command, as follows: -> version SP firmware 1.0.7 SP firmware build number: 12513 <========== SP firmware date: Wed Aug 2 15:03:28 PDT 2006 SP filesystem version: 0.1.13
LSI Firmware Requirements & Information: The LSI RAID controller FW requires 64MB unpartitioned disk space at the end of the disk for volume management (Bug ID 6312581). Creation of any RAID volume could possibly result in the data on ALL disks in the volume being lost, so it is recommended that a backup be performed prior creation. The disks within all RAID volumes must be of the same size. It is recommended that the LSI firmware of replacement motherboards be moved to the revision of the failed motherboard. Migration of disk volumes from one system to another is not supported by Sun. RAID configuration via the LSI BIOS utility is discussed in the Sun LSI 106x RAID User’s Guide, document number 820-4933. Issues related to LSI firmware are as follows:
Solaris uses the mpt driver to access the internal disks, and provides the raidctl utility to control & monitor internal RAID volumes. raidctl has the following functionality (see the Solaris raidctl(1M) manpage for full command details): Create a mirror: raidctl -c primary secondary Create a stripe: raidctl -c -r 0 disk1 disk2 [disk3] . . . Delete a RAID volume: raidctl -d volume Display RAID volume information: # /usr/sbin/raidctl -l RAID Volume RAID RAID Disk Volume Type Status Disk Status ------------------------------------------------------ c1t0d0 IM OK c1t0d0 OK c1t1d0 OK Output similar to the above will be seen with the raidctl command in Solaris 10 Update 3 and earlier. From Solaris 10 Update 4 the command arguments and display format changed, below is an example: # /usr/sbin/raidctl -l Controller: 0 Volume:c1t0d0 Disk: 0.0.0 Disk: 0.1.0 # /usr/sbin/raidctl -l c1t0d0 Volume Size Stripe Status Cache RAID Sub Size Level Disk ---------------------------------------------------------------- c1t0d0 67.9G N/A OPTIMAL N/A RAID1 0.0.0 67.9G GOOD 0.1.0 67.9G GOOD The volume (RAID) status can be one of four possible: OK / OPTIMAL: Volume is optimal. DEGRADED: Volume contains a failed disk (mirror) or at reduced functionality. RESYNCING / SYNC: Volume is synchronizing (mirror), disks are sync'ing. FAILED: Volume is non-functional/offline. The Disk status can be one of three possible: OK / GOOD: Disk is operating normally. MISSING: Disk is removed or otherwise offline. FAILED: Disk is in a failed state and needs service. After RAID volume creation: Member disk drives are no longer visible, only the RAID volume is presented. The RAID volume may be addressed just as any other LUN in Solaris. After RAID volume creation a valid Solaris label must be applied so that the new volume can be accessed correctly by the OS. Solaris based issues are as follows:
Windows and Linux operating systems use LSI Logic's MegaRAID Storage manager (MSM-IR) to monitor & control internal RAID volumes. Instructions for use of MSM-IR can be found in the LSI 106x RAID User’s Guide, document number 820-4933. MSM-IR issues are as follows:
Linux & MyStorage issues (included for legacy installations):
Internal Comments This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the Document Feedback alias(es) listed below: Normalization team alias: [email protected] X64, RAID, LSI, SAS1064 Previously Published As 89505 Attachments This solution has no attachment |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|