Sun StorageTek SAS RAID HBA Installation Guide For The Eight-Port, Internal HBA Model SG-XPCIESAS-R-INT-Z Part No.
Copyright © 2010, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.
Contents Preface 1. xi HBA Overview Kit Contents HBA Features 1 1 2 Array-Level Features 2 Advanced Data Protection Suite Component Layout 3 3 Operating System and Technology Requirements System Interoperability 6 Host Platform Support Server Support 6 7 Software Support 2.
▼ To Install on an Existing Operating System Installing the Battery Backup Module ▼ 14 14 To Install the Battery Backup Module 15 Verifying the Current Devices on a SPARC System ▼ To Verify the Current Devices Installing the HBA ▼ To Install the HBA 17 19 ▼ To Connect Directly to the HBA ▼ To Connect to a System Backplane Testing the HBA Installation 19 20 20 ▼ To Test the HBA Installation on a SPARC System ▼ To Test the HBA Installation on an x64 System Next Steps 25 Removing the H
▼ To Prepare to Create a Bootable Logical Drive on a SPARC System Building a Logical Drive On Which to Install the Solaris OS ▼ To Create a Logical Drive ▼ To Delete a Logical Drive on RAID Card 1 37 ▼ To Label the Newly Created Logical Drive 37 Next Steps 5. 38 Preparing to Install an OS 40 Installing the HBA Driver With an OS 6.
▼ To Install the Driver on the Solaris OS on an x64 System ▼ To Install the Driver on the Solaris OS on a SPARC System ▼ To Install the Driver On the VMware Technology Next Steps 8.
C.
▼ D. To View the Event Log Troubleshooting 78 79 Troubleshooting Checklist Silencing the Alarm 79 80 Recovering From a Disk Drive Failure 80 Failed Disk Drive Protected by a Hot-Spare ▼ 80 To Recover From a Disk Drive Failure 80 Failed Disk Drive Not Protected by a Hot-Spare Failure in Multiple Arrays Simultaneously Disk Drive Failure in a RAID 0 Array Multiple Failures in the Same Array E.
F. Selecting the Best RAID Level 91 Understanding Drive Segments 92 Nonredundant Arrays (RAID 0) 92 RAID 1 Arrays 93 RAID 1 Enhanced Arrays RAID 10 Arrays RAID 5 Arrays 94 95 96 RAID 5EE Arrays 97 RAID 50 Arrays 98 RAID 6 Arrays 100 RAID 60 Arrays 101 Selecting the Best RAID Level Migrating RAID Levels G.
H.
Preface This installation guide explains how to install Oracle’s eight-port, internal Sun StorageTek SAS RAID HBA (referred to as Sun StorageTek SAS RAID Internal HBA in this document), which uses Adaptec technology. It also provides a basic overview of Serial Attached SCSI (SAS) and Redundant Array of Independent Disk (RAID) technology.
Related Documentation The following table lists the documentation for this product. The online documentation is available at: http://docs.sun.com/app/docs/prod/stortek.raid.
Documentation, Drivers, Support, and Training Sun Function URL Documentation http://docs.sun.com Drivers (not including Solaris) http://support.intel.com/support/go/sunraid.htm Support http://www.sun.com/support/ Training http://www.sun.com/training/ Documentation Comments We are interested in improving our documentation and welcome your comments and suggestions. Submit comments about this document by clicking the Feedback[+] link at: http://docs.sun.
xiv Sun StorageTek SAS RAID HBA Installation Guide • March 2010
CHAPTER 1 HBA Overview This chapter provides a basic overview of Oracle’s eight-port, internal Sun StorageTek SAS RAID HBA (referred to as Sun StorageTek SAS RAID Internal HBA in this document), which uses Adaptec technology. This chapter describes the various operating systems, host platforms, storage, and infrastructure configurations that support the HBA.
HBA Features The Sun StorageTek SAS RAID Internal HBA (SG-XPCIESAS-R-INT-Z) has the following features: Note – These features are supported by some operating systems but not others. For more information, refer to the Sun StorageTek RAID Manager Software User’s Guide or online Help. ■ Flash ROM to update the HBA firmware and BIOS using the BIOS Configuration utility or the Sun StorageTek RAID Manager graphical user interface (For more information, see the Sun StorageTek RAID Manager Software User’s Guide.
■ Support for array migration from one RAID level to another Advanced Data Protection Suite ■ Copyback Hot-Spare—You can use this feature to move data from a hot-spare back to its original location after a failed disk drive is replaced. ■ Striped Mirror (RAID 1E)—A RAID 1 Enhanced array is similar to a RAID 1 array except that data is both mirrored and striped, and more disk drives can be included.
FIGURE 1-1 Sun StorageTek SAS RAID Internal HBA Component Layout The following table lists the features of the HBA. TABLE 1-1 HBA Features Feature Specification Form factor Low-profile MD2 Bus compatibility PCIe PCIe bus width x8 PCIe bus speed 2.
TABLE 1-1 HBA Features Feature (Continued) Specification (Continued) Disk drives SATA, SATA II, SAS Maximum number of disk drives 8 (or up to 100 with expanders) Hot-spares Enclosure support I2C and SGPIO Automatic failover Audible alarm Battery backup module ABM-800 Operating System and Technology Requirements This HBA supports the following operating system and technology versions.
TABLE 1-2 Supported Operating System and Technology Versions (Continued) Operating System/Technology Supported Versions • SUSE Linux Enterprise Server (SLES) 10 • SUSE Linux Enterprise Server (SLES) 9, SP4 VMware® Technology ESX Server version 3.0.2, Update 1 (driver support only; storage management must be done through the command-line interface or the BIOS utility. For more information, see the Uniform CommandLine Interface User’s Guide at: http://docs.sun.com/app/docs/prod/stortek.raid.
Server Support TABLE 1-3 lists the servers that the HBA supports.
8 Sun StorageTek SAS RAID HBA Installation Guide • March 2010
CHAPTER 2 Hardware Installation and Removal This chapter explains how to install and remove the HBA, and how to install and connect internal disk drives.
■ Always use a properly fitted and grounded wrist strap or other suitable ESD protection when handling the HBA and observe proper ESD grounding techniques. ■ Hold the HBA by the edge of the PCB, not the connectors. ■ Place the HBA on a properly grounded antistatic work surface pad when it is out of its protective antistatic bag. Preparing for Hardware Installation ▼ To Prepare for Hardware Installation 1. Read “Safety Agency Compliance Statements” on page 117. 2.
Note – If you are installing the HBA in a Sun SPARC Enterprise T5120, T5220, T5140, or T5240 server, see the server-specific installation documents listed in “Related Documentation” on page xii. These documents provide detailed cabling information for the servers. The following figures depict the SAS cables.
FIGURE 2-3 Internal Mini-SAS, Which Connects to SAS or SATA Disk Drives on a Backplane 5. If you are installing the HBA into a full-height computer chassis, replace the original low-profile bracket with the full-height bracket included in the HBA ship kit. Caution – Handle the HBA by its bracket or edges only. 6. Choose your installation option.
3. Create a bootable array. See “Creating a Bootable Array on an x64 System” on page 27 or “Creating a Bootable Array on a SPARC System” on page 33. 4. Set the boot controller. See “Creating a Bootable Array on an x64 System” on page 27 or “Creating a Bootable Array on a SPARC System” on page 33. 5. Install the operating system and the HBA driver. See “Installing an OS Onto a Bootable Array on an x64 System” on page 39 or “Installing the Solaris OS on a SPARC System” on page 45. 6.
▼ To Install on an Existing Operating System 1. Install the battery backup module (BBU). See “Installing the Battery Backup Module” on page 14. 2. If you are installing on an x64 system, skip to the next step. If you are installing on a SPARC system, use the Open Boot Prompt (OBP) to make note of the current devices on the system. See “Verifying the Current Devices on a SPARC System” on page 16. 3. Install and connect the HBA and disk drives. See “Installing the HBA” on page 17. 4. Install the HBA driver.
▼ To Install the Battery Backup Module 1. Attach an ESD wrist strap. See “Observing ESD and Handling Precautions” on page 9. 2. Lay the top square piece of packing foam from the ship kit on your work surface, smooth side up. 3. Take the HBA out of the antistatic bag and set it on the packing foam with the heat sink facing up. 4. Slightly lift the HBA, and from underneath it, insert three plastic screws from the BBU kit through the following three mounting holes in the HBA: ■ The bottom left hole.
5. Place a spacer over each screw. The BBU connector on the HBA is just below the screw closest to the right edge of the HBA. 6. Line up the BBU connector on the BBU module with the connector on the HBA. The screws you inserted will line up with matching holes in the BBU. 7. Gently press down on the right edge of the BBU module until the connectors click into place. Caution – DO NOT force the connection. If a gentle push does not mate the connectors, realign the components and try again. 8.
▼ To Verify the Current Devices 1. Enter the Open Boot Prompt (OBP) and use the show-disks command to list the current devices. {0} ok show-disks a) /pci@0/pci@0/pci@2/scsi@0/disk b) /pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,2/storage@2/disk q) NO SELECTION Enter Selection, q to quit: q {0} ok Note – Device paths might vary from this example, depending on the SPARC system you are using and into which PCI-E slot the card is plugged. 2. Take note of the devices.
FIGURE 2-5 Removing the Safety Clips From the SAS Connectors 2. Turn off the computer and disconnect the power cord. 3. Open the cabinet, following the manufacturer instructions. 4. Select an available x8 PCI Express expansion slot that is compatible with the HBA and remove the slot cover. Caution – Touch a grounded metal object before handling the HBA. 5. Insert the HBA into the PCI Express expansion slot and press down gently but firmly until it clicks into place.
Connecting Disk Drives You can connect SAS disk drives, SATA disk drives, or a combination of both to the HBA. There are no jumpers or switches to set before installation. In a direct-attach connection, the SAS or SATA disk drives are connected directly to the HBA with SAS cables. The number of direct-attached disk drives is limited to four per internal SAS connector. Use high-quality cables to connect the HBA to the internal device(s), such as disk drives or backplanes. Use only Sun-supplied cables.
3. Close the computer cabinet, and reattach the power cord. ▼ To Connect to a System Backplane In a backplane connection, disk drives and SAS cards are attached to and communicate with each other through a system backplane. The number of disk drives is limited to the number of slots available on the backplane. Some backplanes have embedded SAS expanders and can support up to 128 end devices. (For more information about backplane and expander connections, see “Backplane Connections” on page 108.) 1.
c. Power-on the disk drive enclosure, and verify that all available HDD status indicators are normal for the storage enclosure(s) that they are in. d. Power-on the computer system. 2. Enter the Open Boot Prompt (OBP) and use the show-disks command to list the current devices. In the following example, the HBA is the first device that is listed.
4. To display the firmware version on the HBA, use the show-version command. {0} ok show-version AAC Kernel Version: 15815 {0} ok 5. To display additional configuration information, list the device properties by using the .properties command. {0} ok .properties firmware-version 15815 assigned-addresses 820f0010 00000000 00e00000 00000000 00200000 820f0030 00000000 00d00000 00000000 00080000 compatible pciex9005,285.108e.286.9 pciex9005,285.108e.286 pciex9005,285.
Note – At this point, there are no volumes created and the output from a probescsi-all command will not display any drives. If no errors or issues are discovered, continue to “Next Steps” on page 25 to complete the installation process. If any issues are discovered, correct them and retest the HBA before continuing. ▼ To Test the HBA Installation on an x64 System 1. Power-up the computer and storage systems: a. Ensure that all hard disk drives are securely installed. b.
Controller Serial Number: 00721EC0006 Controller WWN: 5000E0CE21907000 No Logical Drives Found c. When the utility starts, review the list of HBAs installed on the computer. d. If more than one HBA is listed, select the one you wish to test and press Enter. 3. Enter the Array Configuration Utility (ACU) by highlighting Array Configuration Utility and then pressing Enter. You might see a screen next indicating Configuration Change. This is normal for a newly installed HBA and targets. 4.
e. Highlight Test and press Enter. Verify a 3-second audible alarm. 9. Verify that all target devices are present: a. Press Esc until you reach the controller Options menu. b. Highlight Disk Utilities and press Enter. You will see an indication that the HBA is scanning SAS devices. c. After the scanning completes, verify that all attached target devices are displayed. d. Press Esc to exit. If no errors or issues are discovered, continue to the next section to complete the installation process.
▼ To Prepare the HBA for Removal 1. If the computer is running the OS, halt all I/O activity to the HBA. 2. Complete all transactions being done by the HBA such as migrations, rebuilds, verifications, and so on. 3. Properly log out of the OS and shut down the computer. 4. Unplug the computer. 5. Open the computer chassis and disconnect the SAS/SATA cable(s) from the HBA. ▼ To Remove the HBA 1. Remove the retention mechanism (screw, clip, and so on) that is securing the HBA bracket to the chassis. 2.
CHAPTER 3 Creating a Bootable Array on an x64 System As an installation option, you can choose to create a bootable array and then install an operating system and the HBA driver onto that array. This chapter describes how to set the Sun StorageTek SAS RAID Internal HBA to be the boot controller, and how to create a bootable array on an x64 system.
Creating an Array A RAID 5 array is created in the examples shown in this section because RAID 5 provides the most security and best performance with a minimum of three disk drives. However, you can choose to create an array with a different RAID level; you can also change array level later, after the operating system is installed. You can create an array using either of these tools: ■ Array Configuration Utility (ACU)—BIOS-based menus and keyboard navigation.
▼ To Create a RAID 5 Array With the ACU Note – Hot-plugging of enclosures is not supported in the BIOS RAID Configuration utility. Hot-plugging of SAS/SATA hard disk drives (HDDs) is supported only within hard disk enclosures and only under the conditions specified in “Understanding Hot-Plug Limitations and Conditions Within the BIOS RAID Configuration Utility” on page 66. 1. Power on the computer. 2. When prompted, press Ctrl+A to enter the BIOS RAID Configuration utility.
10. When the Array Properties screen is displayed, follow the instructions in the following table. TABLE 3-1 Filling in Array Properties Screen Property Line Entry or Selection Array Type Select RAID 5, then press Enter. Array Label Type a name, then press Enter. Array Size Press Enter, then press Enter again to use the default granularity of GB. Stripe Size Press Enter to use the default (256 KB). Read Caching Press Enter to use the default (Yes).
Making the Array Bootable Note – You may need to change the system BIOS to modify the boot order. For more information, refer to your computer documentation or see “Best Practices For Controlling the Boot Order of Logical Drives” on page 87. The Sun StorageTek SAS RAID Internal HBA always uses the lowest numbered array as its bootable array. ▼ To Make the Array Bootable 1. Select Manage Arrays from the main ACU menu. 2. Select the array that you want to make bootable, then press Ctrl+B.
1. Enter the system setup. 2. Navigate to the drive boot sequence. 3. Move the boot HBA to the top of the list. Next Steps Install an operating system (OS) onto the bootable array and then install the HBA driver on the array, as described in “Installing an OS Onto a Bootable Array on an x64 System” on page 39.
CHAPTER 4 Creating a Bootable Array on a SPARC System As an installation option, you can choose to create a bootable array (bootable logical drive) and then install the Solaris 10 10/08 operating system, which contains the required HBA driver, onto that array (logical drive). This chapter describes how to set the Sun StorageTek SAS RAID Internal HBA to be the boot controller, and how to create a bootable array on a SPARC system.
The chapter contains the following sections: ■ “Preparing to Create a Bootable Logical Drive” on page 34 ■ “Building a Logical Drive On Which to Install the Solaris OS” on page 34 ■ “Next Steps” on page 38 Preparing to Create a Bootable Logical Drive ▼ To Prepare to Create a Bootable Logical Drive on a SPARC System 1. Install and connect the HBA and disk drives, ensuring that the physical drives are cabled to the HBA. See “Hardware Installation and Removal” on page 9. 2.
▼ To Create a Logical Drive 1. Prepare to create the logical drive, as described in “To Prepare to Create a Bootable Logical Drive on a SPARC System” on page 34. 2. From the system console, boot from the Live CD. ok boot cdrom 3. At the system prompt, access the command-line interface (CLI), and use the ./arcconf GETCONFIG command to print a list of the complete configuration of card 1 on the system.
4. Do one of the following: ■ To create a logical drive on the RAID card 2, using RAID level 1 (a mirror) and using all the space on physical drives 0,0 and 0,1, run the CREATE command as shown in the following example. Note that in this example, the RAID card number follows the CREATE command, and the RAID level follows the keyword, MAX. Drives are listed in a space-separated fashion, with the channel number followed by the ID number. # .
▼ To Delete a Logical Drive on RAID Card 1 You might need to free up some space in order to create the logical drive on which the Solaris OS will be installed. You can do so by deleting existing logical drives. Caution – Using the command in this procedure will destroy all data on the specified logical drive. Be very careful when using this command to prevent unintentional data loss. ● To delete a logical drive on RAID card 1, use the DELETE card-number LOGICALDRIVE drive-number command.
# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t0d0 /pci@780/pci@0/pci@9/scsi@0/sd@0,0 1. c0t1d0 /pci@780/pci@0/pci@9/scsi@0/sd@1,0 2. c2t0d0 /pci@7c0/pci@0/pci@8/scsi@0/sd@0,0 3. c2t1d0 /pci@7c0/pci@0/pci@8/scsi@0/sd@1,0 Specify disk (enter its number): 2 4.
CHAPTER 5 Installing an OS Onto a Bootable Array on an x64 System If you chose to create a bootable array on an x64 system as part of your installation (see “Creating a Bootable Array on an x64 System” on page 27), you can install an operating system and the HBA driver on that bootable array. This chapter explains how to install an operating system (OS) onto a bootable array and then install the HBA driver on the array.
Preparing to Install an OS ▼ To Prepare to Install an OS 1. Install and connect the HBA and disk drives. See “Hardware Installation and Removal” on page 9. 2. Obtain the driver CD from the HBA ship kit or obtain the latest version of the driver at http://support.intel.com/support/go/sunraid.htm. 3. Create a bootable array. See “Creating a Bootable Array on an x64 System” on page 27. Note – For up-to-date operating system version support, go to http://support.intel.com/support/go/sunraid.htm.
▼ To Install the Driver With the Windows OS Note – You will need the Windows Installation media to complete this task. 1. Insert the Windows installation medium, then restart the computer. 2. Follow the on-screen instructions to begin the Windows installation. 3. When prompted to install a third-party driver, press F6. Note – When F6 is active, a prompt is displayed at the bottom of the screen for only 5 seconds. If you miss your chance to press F6, restart the computer. 4.
7. Complete the Linux installation, following the instructions included with the operating system. 8. To configure and manage the hard disks, see the Sun StorageTek RAID Manager Software User’s Guide at: http://docs.sun.com/app/docs/prod/stortek.raid.hba#hic ▼ To Install the Driver With the SUSE Linux OS Note – You will need the SUSE installation media to perform this task. 1. Insert the SUSE Installation medium. 2. Restart the computer. 3.
▼ To Install the Driver With VMware Technology Note – You will need the VMware Installation media to complete this task. 1. Insert the VMware Installation medium. 2. Restart the computer. 3. Follow the on-screen instructions to begin the VMware installation. Note – The VMware ESX Server embedded driver will see the device and install. 4. Complete the VMware installation, following the instructions included with your operating system.
44 Sun StorageTek SAS RAID HBA Installation Guide • March 2010
CHAPTER 6 Installing the Solaris OS on a SPARC System If you chose to create a bootable array on a SPARC system as part of your installation (see “Creating a Bootable Array on a SPARC System” on page 33), you can install the Solaris 10/08 (s10u6) operating system (OS), at minimum, on that bootable array. Starting with the Solaris 10/08 OS, the driver required by the HBA is provided with the Solaris OS.
Preparing to Install the Solaris OS Before you begin, prepare to install the Solaris 10/08 OS. ▼ To Prepare to Install the Solaris OS ● Complete the procedures in “Creating a Bootable Array on a SPARC System” on page 33. Note – For up-to-date Sun StorageTek SAS RAID HBA support, go to http://support.intel.com/support/go/sunraid.htm. Installing the Solaris OS ■ “To Install the Solaris OS” on page 46 ▼ To Install the Solaris OS 1.
Next Steps You can optionally install and use the Sun StorageTek RAID Manager GUI to create arrays on the disk enclosure. See the Sun StorageTek RAID Manager User’s Guide at: http://docs.sun.com/app/docs/prod/stortek.raid.
48 Sun StorageTek SAS RAID HBA Installation Guide • March 2010
CHAPTER 7 Installing the Driver on an Existing Operating System As an installation option, you can choose to perform a standard installation by installing the HBA driver on an existing operating system. This chapter describes how to perform this operation. Note – If you want to create a bootable array and install an operating system and the HBA driver on that array, DO NOT perform the procedures in this chapter.
Installing the Driver on an Existing OS The driver can be installed on various operating systems.
2. Mount the CD. For example: Red Hat: mount /dev/cdrom /mnt/cdrom SUSE: mount /dev/cdrom /media/cdrom 3. Install the module RPM. rpm -Uvh mount-point/xxx/yyy.rpm Where mount-point is the specific mount point on the Linux system, xxx is the driver path, and yyy.rpm is the rpm file. 4. Reboot the computer to ensure the driver loaded correctly. 5. Run fdisk, mkfs, and create mount points for any new disk drives. 6.
▼ To Install the Driver On the VMware Technology Note – The embedded driver provided by VMware ESX Server is suitable for most applications. If an updated driver is needed, use the following procedure. 1. Start the computer, then insert the driver CD. 2. At the console screen of the VMware ESX Server, mount the CD. For example: mount –r /dev/cdrom /mnt/cdrom. 3. Install the module RPM: rpm –ivh /mnt/cdrom/xxx/yyy.rpm where xxx is the driver path, and yyy.rpm is the rpm file. 4.
CHAPTER 8 Known Issues This chapter contains the latest supplementary information for the preceding chapters in this guide.Specific Change Request (CR) identification numbers are provided for service personnel, when necessary. The chapter contains the following sections: ■ “Ship Kit Issues” on page 53 ■ “BIOS Utility Issues” on page 54 ■ “Performance Issues” on page 54 Ship Kit Issues This section describes the known ship kit issue.
BIOS Utility Issues This section contains the known issues related to the BIOS RAID Configuration Utility: ■ “Creating an Array With the BIOS Utility Changes the BIOS Boot Order” on page 54 ■ “Hot-Plug Functionality Does Not Work in the BIOS Utility” on page 54 ■ “Performance Issues” on page 54 Creating an Array With the BIOS Utility Changes the BIOS Boot Order Workaround: After creating the array, check the BIOS settings to verify the correct boot order and make changes as necessary.
The System Freezes When a Sun Storage 32GB SLC SATA Solid State Drive (SSD) is Configured In the HBA CR 6806467 Issue: This occurs because the HBA has firmware prior to version 16732 installed on it and the Sun Storage 32GB SLC SATA SSD has firmware version 8626 or earlier installed on it. Workaround: Do the following: 1. Upgrade the HBA to firmware version 16732, at minimum. You can obtain the latest HBA firmware at: http://support.intel.com/support/go/sunraid.htm 2. Power cycle the HBA host system. 3.
56 Sun StorageTek SAS RAID HBA Installation Guide • March 2010
APPENDIX A Configuration Rules This appendix lists the configuration rules for the Sun StorageTek SAS RAID Internal HBA. Note – Use only Sun-approved devices and cabling with the HBA.
Note – Mixing SATA and SAS HDDs in the same logical RAID array is not supported. Although it is not an unsupported configuration, SAS and SATA HDDs must not be mixed in the same enclosure. Cabling Note – If you are installing the HBA on a Sun SPARC Enterprise T5120, T5220, T5140, or T5240 server, you will need different cables than the ones listed in this section.
APPENDIX B HBA Specifications This appendix provides information about the HBA specifications. The appendix contains the following sections: ■ “Physical Dimensions” on page 59 ■ “Environmental Specifications” on page 60 ■ “DC Power Requirements” on page 60 ■ “Current Requirements” on page 60 ■ “Performance Specifications” on page 60 ■ “Connector Pin Definitions” on page 61 Physical Dimensions Meets PCI low-profile MD2 specification.
Environmental Specifications Note – With a Battery Backup Unit (BBU), the ambient temperature must not exceed 40 ˚C. TABLE B-1 Environmental Specifications Ambient temperature without forced airflow 0 ˚C to 40 ˚ C Ambient temperature with forced airflow 0 ˚C to 55 ˚ C Relative humidity 10% to 90%, noncondensing Altitude Up to 3,000 meters Note – Forced airflow is recommended. DC Power Requirements PCI Express, DC Voltage 3.3 V 9%, 12 V 8% Current Requirements 1.0 A @ 3.3 VDC; 1.0 A @ 12.
■ Physical layer: Consists of two sets of differential lines, one receive set and one transmit set [4-wire total]. This layer defines the cable, connector, and transceiver [Transmitter / Receiver] characteristics. ■ PHY layer: Connects the differential Transmitter and Receiver circuits [ICs] to the Physical Layer. ■ Link layer ■ Port layer ■ Application layer The external connector accepts 4 physical links and the cable may hold between 1 and 4 physical links.
TABLE B-2 SAS Pin-Out Signal Name (Continued) 1 Physical Link (Continued) 2 Physical Links (Continued) 3 Physical Links (Continued) 4 Physical Links (Continued) Rx 3+ N/A N/A N/A S7 Rx 3- N/A N/A N/A S8 Tx 3- N/A N/A N/A S9 Tx 3+ N/A N/A N/A S10 Tx 2- N/A N/A S11 S11 Tx 2+ N/A N/A S12 S12 Tx 1- N/A S13 S13 S13 Tx 1+ N/A S14 S14 S14 Tx 0- S15 S15 S15 S15 Tx 0+ S16 S16 S16 S16 Signal Ground G1 - G9 G1 - G9 G1 - G9 G1 - G9 Chassis Ground Housing H
TABLE B-4 SATA Power Pin-Out Pin# Signal Name Signal Description 1 V33 3.3v Power 2 V33 3.3v Power 3 V33 3.
64 Sun StorageTek SAS RAID HBA Installation Guide • March 2010
APPENDIX C Using the BIOS RAID Configuration Utility The BIOS RAID Configuration utility is a BIOS-based utility that you can use to create and manage controllers, disk drives and other devices, and arrays. Note – If you are using a SPARC system, you cannot use the BIOS RAID Configuration utility. Instead, use the Sun StorageTek RAID Manager graphical user interface (GUI). For more information, see the Sun StorageTek RAID Manager Software User’s Guide at: http://docs.sun.com/app/docs/prod/stortek.raid.
Introduction to the BIOS RAID Configuration Utility The BIOS RAID Configuration utility comprises these tools: ■ The Array Configuration Utility (ACU)—For creating and managing arrays and initializing and rescanning disk drives. See “Using the ACU to Create and Manage Arrays” on page 69. ■ A -Select Utility—SerialSelect, or SATASelect, for modifying the HBA and disk drive settings. See “Using the -Select Utility to Modify HBA Settings” on page 73.
■ The hard disk drive to be removed must not be a part of a logical device (its status must be ‘available’). ■ After the hard disk drive is removed from the enclosure, you must perform a bus scan by using the Rescan Drives option from the main menu of the Array Configuration Utility (ACU). ■ You must confirm that the Disk Utility reports the correct configuration of the attached target devices.
Running the BIOS RAID Configuration Utility This section describes how to start and navigate through the BIOS RAID Configuration utility. The section contains the following subsections: ■ “To Start the BIOS RAID Configuration Utility” on page 68 ■ “To Navigate the BIOS RAID Configuration Utility” on page 69 ▼ To Start the BIOS RAID Configuration Utility 1.
▼ To Navigate the BIOS RAID Configuration Utility ● Use the arrows, Enter, Esc, and other keys on your keyboard to navigate through the utility menus. All the tools within the BIOS RAID Configuration utility are menu-based and instructions for completing tasks are displayed on-screen. Using the ACU to Create and Manage Arrays You can use the ACU, a tool of the BIOS RAID Configuration utility, to create and manage arrays.
▼ To Start the ACU 1. Start the BIOS RAID Configuration utility. See “To Start the BIOS RAID Configuration Utility” on page 68. 2. If you have more than one HBA, select the HBA that you want to manage and press Enter. 3. Select Array Configuration Utility and press Enter. 4. Follow the on-screen instructions to create and manage arrays, and initialize, rescan, and erase disk drives.
▼ To Manage Existing Arrays With the ACU 1. Select Manage Arrays from the main ACU menu. 2. From the Manage Arrays menu, do any of the following: ■ View the properties of an array. Note – Failed drives are displayed in a different text color. ■ Make an array bootable. See “To Make an Array Bootable With the ACU” on page 71. ■ Assign or remove hot-spares. ■ Delete an array. Caution – Before deleting an array, back up the data to avoid permanently losing it.
▼ To Initialize Disk Drives With the ACU If a disk drive is displayed grayed-out (unavailable for use in a new array), it may need to be initialized. ● Select Initialize Drives from the main ACU menu. Caution – Do not initialize a disk drive that is part of an array. Initializing a disk drive that is part of an array may make the array unusable. Back up all data from your disk drive before you initialize it. ▼ To Rescan Disk Drives With the ACU ● Select Rescan Drives from the main ACU menu.
2. Select the disk drive being secure erased, then press Ctrl+Q. The secure erase stops and the ACU returns to its main window. Using the -Select Utility to Modify HBA Settings Included in the BIOS RAID Configuration utility is a tool for modifying the settings of the HBA and the disk drives connected to it. This utility is called SerialSelect or SATASelect.
▼ To Modify General HBA Settings With a -Select Utility Note – Default HBA settings are suitable for most computers. Do not change the default settings. ● Select Controller Configuration from the main -Select utility menu and change the settings listed in the following table. Some options may not be available for the HBA. Note – Default settings are shown in bold type. TABLE C-1 General HBA Settings Option Description Drive’s Write Cache When enabled, write cache is enabled on the disk drive.
TABLE C-1 General HBA Settings Option (Continued) Description (Continued) Removable Media Devices Boot Support When enabled, removable media devices, such as CD drives, are supported. Alarm Control When enabled, the alarm sounds. Default is enabled. Note—When the alarm is turned off (disabled), it will automatically turn back on after a reboot. SATA Native Command Queuing (NCQ) When enabled, NCQ is enabled. Disable this feature if you want to attach more than 48 SATA II disk drives.
Using the Disk Utilities to Manage Disk Drives You can use the disk utilities, another tool in the BIOS RAID Configuration utility, to low-level format or verify your disk drives. (New disk drives are low-level formatted at the factory and do not need to be low-level formatted again.) Caution – Before you format a disk drive, back up all data. Formatting destroys all data on a disk drive.
1. Start the BIOS RAID Configuration utility. See “To Start the BIOS RAID Configuration Utility” on page 68. 2. Select the HBA you want, then press Enter. 3. Select Disk Utilities. 4. Select the disk drive you want, then press Enter. 5. Select Identify Drive, then press Enter. 6. When you have finished locating your disk drive, press any key to stop the blinking. ▼ To Identify Disk Drives With the Disk Utilities You can identify disk drives by viewing the list of disk drives on your system.
■ Expanders—The connections is determined by an expander. Exp0 (expander 0) is connected to phy0 (phy 0 within a connector). For more information, see “SAS Expander Connections” on page 109. Note – Devices other than disk drives (CDROM, tape drives, and so on) are listed in order after your system disk drives. Viewing the BIOS-Based Event Log The BIOS-based event log records all firmware events, such as configuration changes, array creation, and boot activity.
APPENDIX D Troubleshooting This appendix provides basic troubleshooting information and solutions for solving HBA problems.
Silencing the Alarm An alarm will sound when an error occurs. To silence the alarm, use BIOS RAID Configuration utility. See “Using the BIOS RAID Configuration Utility” on page 65. Recovering From a Disk Drive Failure This section explains how to recover when a disk drive fails: ■ If the array was protected by a hot-spare (see “Failed Disk Drive Protected by a Hot-Spare” on page 80). ■ If the array was not protected by a hot-spare (see “Failed Disk Drive Not Protected by a Hot-Spare” on page 81).
■ If copyback is enabled—Data is automatically moved back to its original location once the HBA detects that the failed drive has been replaced. No action is required. Failed Disk Drive Not Protected by a Hot-Spare When an array is not protected by a hot-spare, if a disk drive in that array fails, remove and replace the failed disk drive. The HBA detects the new disk drive and begins to rebuild the array.
Multiple Failures in the Same Array Except in RAID 6 and RAID 60 arrays (see “Selecting the Best RAID Level” on page 91), if more than one disk drive fails at the same time in the same array, the data cannot be recovered. Correct the cause of the failure or replace the failed disk drives. Then, restore your data (if available). Note – In some instances, RAID 10 and RAID 50 arrays may survive multiple disk drive failures, depending on which disk drives fail.
APPENDIX E Best Practices This appendix provides information about how to best use the Sun StorageTek SAS RAID HBA to improve your overall user experience.
1. Run the arcconf getversion command at a terminal window. Assuming the newly installed HBA is the sole HBA installed in the system, the output of the arcconf getversion command will display 1 adapter. 2. Review the output of the arcconf getversion command and do one of the following: ■ If the output displays 1 adapter, the system has detected the HBA and you do not need to perform any further action.
Pulling a Cable and Reconnecting It To the Same Port Wait at least two minutes between pulling a cable and reconnecting it to the same port on an HBA or JBOD. To avoid confusing the controller, wait until the physical drives are removed from the display of the GUI and CLI. Connecting a JBOD With SATA Disks When connecting a JBOD with SATA disks to an HBA, connection problems might occur if the JBOD was previously connected to a different HBA. This is due to a SAS feature called, affiliation.
Best Practices For Deleting Logical Volumes Without Deleting Partitions When attempting to delete a logical volume, the Sun StorageTek RAID Manager graphical user interface (GUI) might require you to remove any partitions on the logical drive before it allows drive deletion. This is a safety feature designed to prevent accidental deletion of drives that contain valid data.
Typing this command causes the failed drive to return to a ready state in the GUI. Best Practices For Rescanning or Discovering Drives If you add a new enclosure to an existing card, or if you initiate a card rescan and the rescan finds a new physical disk drive on the card, the newly discovered drive might be displayed as failed in the Sun StorageTek RAID Manager GUI (with a red X over the drive).
2. Verify whether the logical drive of the RAID card is the first drive in the list. 3. If the first drive listed is the original system boot drive, you do not need to perform any further action. If the first drive listed is the logical drive of the RAID card, change the list so that the original boot drive is listed first. 4. To save the settings, do one of the following: ■ If you are working on an ILOM Remote Console, go to the ILOM Keyboard menu at the top of the window and choose F10.
Replacing an HBA On a SPARC System Upon replacing an existing HBA card with a new card on a SPARC system, the new card automatically detects the existing configuration upon installation and no further action is required. However, if the new HBA is not seeing one or more volumes in the existing configuration, rescan those volumes to enable their detection.
90 Sun StorageTek SAS RAID HBA Installation Guide • March 2010
APPENDIX F Selecting the Best RAID Level When you create arrays (or logical drives) for the Sun StorageTek SAS RAID Internal HBA, you can assign a RAID level to protect your data. Each RAID level offers a unique combination of performance and redundancy. RAID levels also vary by the number of disk drives they support.
Understanding Drive Segments A drive segment is a disk drive or portion of a disk drive that is used to create an array. A disk drive can include both RAID segments (segments that are part of an array) and available segments. Each segment can be part of only one logical device at a time. If a disk drive is not part of any logical device, the entire disk is an available segment.
FIGURE F-1 Nonredundant Arrays (RAID 0) RAID 1 Arrays A RAID 1 array is built from two disk drives, where one disk drive is a mirror of the other (the same data is stored on each disk drive). Compared to independent disk drives, RAID 1 arrays provide improved performance, with twice the read rate and an equal write rate of single disks. However, capacity is only 50 percent of independent disk drives.
FIGURE F-2 RAID 1 Arrays RAID 1 Enhanced Arrays A RAID 1 Enhanced (RAID 1E) array—also referred to as a striped mirror—is similar to a RAID 1 array except that data is both mirrored and striped, and more disk drives can be included. A RAID 1E array can be built from three or more disk drives. In this figure, the large bold numbers represent the striped data, and the smaller, non-bold numbers represent the mirrored data stripes.
FIGURE F-3 RAID 1 Enhanced Arrays RAID 10 Arrays A RAID 10 array is built from two or more equal-sized RAID 1 arrays. Data in a RAID 10 array is both striped and mirrored. Mirroring provides data protection, and striping improves performance. Drive segment size is limited to the size of the smallest disk drive in the array.
FIGURE F-4 RAID 10 Arrays RAID 5 Arrays A RAID 5 array is built from a minimum of three disk drives, and uses data striping and parity data to provide redundancy. Parity data provides data protection, and striping improves performance. Parity data is an error-correcting redundancy that’s used to re-create data if a disk drive fails. In RAID 5 arrays, parity data (represented by Ps in the next figure) is striped evenly across the disk drives with the stored data.
FIGURE F-5 RAID 5 Arrays RAID 5EE Arrays A RAID 5EE array—also referred to as a hot-spare—is similar to a RAID 5 array except that it includes a distributed spare drive and must be built from a minimum of four disk drives. Unlike a hot-spare, a distributed spare is striped evenly across the disk drives with the stored data and parity data, and can’t be shared with other logical disk drives. A distributed spare improves the speed at which the array is rebuilt following a disk drive failure.
In this example, S represents the distributed spare, P represents the distributed parity data. FIGURE F-6 RAID 5EE Arrays RAID 50 Arrays A RAID 50 array is built from at least six disk drives configured as two or more RAID 5 arrays, and stripes stored data and parity data across all disk drives in both RAID 5 arrays. (For more information, see “RAID 5 Arrays” on page 96.) The parity data provides data protection, and striping improves performance. RAID 50 arrays also provide high data transfer speeds.
Drive segment size is limited to the size of the smallest disk drive in the array. For example, three 250 GB disk drives and three 400 GB disk drives comprise two equalsized RAID 5 arrays with 500 GB of stored data and 250 GB of parity data. The RAID 50 array can therefore contain 1000 GB (2 x 500 GB) of stored data and 500 GB of parity data. FIGURE F-7 RAID 50 Arrays In this example, P represents the distributed parity data.
RAID 6 Arrays A RAID 6 array—also referred to as dual drive failure protection—is similar to a RAID 5 array because it uses data striping and parity data to provide redundancy. However, RAID 6 arrays include two independent sets of parity data instead of one. Both sets of parity data are striped separately across all disk drives in the array. RAID 6 arrays provide extra protection for your data because they can recover from two simultaneous disk drive failures.
RAID 60 Arrays Similar to a RAID 50 array (see “RAID 50 Arrays” on page 98), a RAID 60 array—also referred to as dual drive failure protection— is built from at least eight disk drives configured as two or more RAID 6 arrays, and stripes stored data and two sets of parity data across all disk drives in both RAID 6 arrays. Two sets of parity data provide enhanced data protection, and striping improves performance. RAID 60 arrays also provide high data transfer speeds.
Migrating RAID Levels As your storage space changes, you can migrate existing RAID levels to new RAID levels that better meet your storage needs. You can perform these migrations through the Sun StorageTek RAID Manager software. For more information, see the Sun StorageTek RAID Manager Software User’s Guide. TABLE F-2 lists the supported RAID level migrations.
APPENDIX G Introduction to Serial Attached SCSI This section provides a basic overview of the main features of Serial Attached SCSI (SAS), introduces some common SAS terms, and explains how SAS differs from parallel SCSI. Note – This section is not specific to the Sun StorageTek SAS RAID Internal HBA. Instead, this appendix provides general information. Diagrams are for reference purposes only and do not represent any specific configurations supported by the Sun StorageTek SAS RAID Internal HBA.
Terminology Used in This Appendix For convenience, SAS HBAs and SAS RAID HBAs are referred to generically in this appendix as SAS cards. HBAs, RAID controllers, disk drives, and external disk drive enclosures are referred to as end devices and expanders are referred to as expander devices. For convenience, this appendix refers to end devices and expander devices collectively as SAS devices.
About SAS Device Communication SAS devices communicate with each other through links. A link is a physical connection between two phys. As shown in the following figure, SAS devices contain ports (see “About SAS Ports” on page 106), ports contain phys, and each phy contains one transmitter and one receiver—one transceiver. A phy can belong to one port only. FIGURE G-1 SAS Device Communication About Phys Phys are part of the physical communication connection between SAS devices.
When a connection is formed between two end devices, a link is established from a phy in one port to a phy in the other port. As shown in the figure above, a wide port can support multiple independent links simultaneously. Phys are internal, within SAS connectors (see “About SAS Connectors” on page 107). SAS cables physically connect one or more phys on one SAS device to one or more phys on another SAS device.
About SAS Connectors A SAS or mini-SAS connector is the physical plug or receptacle that you see on a SAS device. It’s what you plug a SAS cable into, or the end of the SAS cable that’s being plugged in. (See “Preparing for Hardware Installation” on page 10.) A connector is what forms physical links between phys. Some SAS connectors can support multiple links. The number of links a SAS connector can support is referred to as its width.
■ ExpX:PhyX = Expander X is attached to Phy X (see “SAS Expander Connections” on page 109 below for more information) where X is the count number. Note – Devices other than disk drives (CDROM, tape drives, and so on) are listed in order after your system disk drives. In parallel SCSI, XX is the disk drive’s channel number, YY is the target number, and ZZ is the logical unit number (LUN).
When connecting to a backplane, the Sun StorageTek RAID Manager GUI enables you to manage your system disk drives, see the Sun StorageTek RAID Manager Software User’s Guide. The number of end devices is limited to the number of slots available on the backplane. For example, the Sun S50 enclosure, which contains an expander, is a backplane connection that supports up to 12 SAS or SATA disk drives. Some backplanes support daisy-chain expansion to other backplanes.
FIGURE G-2 SAS Expander Connections Differences Between SAS and Parallel SCSI In summary, although SAS and parallel SCSI both use the SCSI command set, how they move data from one place to another is very different. To support point-to-point serial data transport, SAS introduces new types of connectors, cables, connection options, and terminology. Generally speaking, SAS is faster and more flexible than parallel SCSI, and provides more options for building your storage space.
This table describes many of the main differences between the two interfaces.
112 Sun StorageTek SAS RAID HBA Installation Guide • March 2010
APPENDIX H Declaration of Conformity, Safety, and Regulatory Statements This appendix provides Declaration of Conformity, safety, and regulatory statements for the product.
114 Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Declaration of Conformity To receive a copy of the latest Declaration of Conformity (DoC) for the product, either contact your local Sun sales representative, or create an online request at: https://www2.sun.de/dct/forms/reg_us_1607_755_0.
116 Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Safety Agency Compliance Statements Read this section before beginning any procedure. The following text provides safety precautions to follow when installing a Sun Microsystems product. Depending on the type of power switch your device has, one of the following symbols may be used: On – Applies AC power to the system. Off – Removes AC power from the system.
Caution – Not all power cords have the same current ratings. Do not use the power cord provided with your equipment for any other products or use. Household extension cords do not have overload protection and are not meant for use with computer systems. Do not use household extension cords with your Sun product. The following caution applies only to devices with a Standby power switch: Caution – The power switch of this product functions as a standby type device only.
System Unit Cover Laser Compliance Notice You must remove the cover of your Sun computer system unit to add cards, memory, or internal storage devices. Be sure to replace the cover before powering on your computer system. Sun products that use laser technology comply with Class 1 laser requirements. Class 1 Laser Product Luokan 1 Laserlaite Klasse 1 Laser Apparat Laser Klasse 1 Caution – Do not operate Sun products without the cover in place.
■ Ce produit est destiné à être utilisé dans des zones à accès limité, dans lesquelles les accès sont contrôlés au moyen de systèmes de sécurité (par exemple, à clé, verrou, dispositif ou badge). Le personnel autorisé à accéder à ces zones doit avoir été préalablement informé des raisons justifiant la limitation des accès et de toutes les précautions à prendre. Positionnement d’un produit Sun Attention – Evitez d'obstruer ou de recouvrir les orifices de votre produit Sun.
système. Assurez-vous de le brancher dans une prise d'alimentation mise à la terre près du système et facile d'accès. Ne le branchez pas lorsque l'alimentation électrique ne se trouve pas dans le châssis du système.
Attention – L'utilisation de contrôles et de réglages ou l'application de procédures autres que ceux spécifiés dans le présent document peuvent entraîner une exposition à des radiations dangereuses. Einhaltung sicherheitsbehördlicher Vorschriften Lesen Sie vor dem Ausführen von Arbeiten diesen Abschnitt. Im folgenden Text werden Sicherheitsvorkehrungen beschrieben, die Sie bei der Installation eines Sun Microsystems-Produkts beachten müssen. Achtung – Heiße Oberfläche.
Anschluss des Netzkabels Warnung bezüglich Batterien Achtung – Sun-Geräte sind für Stromversorgungssysteme mit einem geerdeten neutralen Leiter (geerdeter Rückleiter bei gleichstrombetriebenen Geräten) ausgelegt. Um die Gefahr von Stromschlägen zu vermeiden, schließen Sie das Gerät niemals an andere Stromversorgungssysteme an.
■ Reduzierter Luftstrom - Die Installation des Geräts in einem Rack sollte so erfolgen, dass die Luftstrommenge, die für den sicheren Betrieb des Geräts erforderlich ist, nicht beeinträchtigt wird. ■ ■ Mechanische Belastung - Die Montage des Geräts im Rack sollte so erfolgen, dass bei einer ungleichmäßigen mechanischen Belastung keine gefährliche Betriebsbedingung entstehen kann.
Encendido – Suministra alimentación de CA al sistema. Apagado – Corta la alimentación de CA del sistema. Espera – El interruptor de encendido/espera está en la posición de espera. Modificaciones en el equipo No realice modificaciones de tipo mecánico ni eléctrico en el equipo. Sun Microsystems no se hace responsable del cumplimiento de normativas en caso de que un producto Sun se haya modificado. Colocación de un producto Sun Precaución – No obstruya ni tape las rejillas del producto Sun.
descritas en el manual de servicio del producto. No desmonte las baterías ni intente recargarlas fuera del sistema. No intente deshacerse de las baterías echándolas al fuego. Deshágase de las baterías correctamente de acuerdo con las instrucciones del fabricante y las normas locales. Tenga en cuenta que en las placas CPU de Sun, hay una batería de litio incorporada en el reloj en tiempo real. Los usuarios no deben reemplazar este tipo de baterías.
Danmark Advarsel! – Litiumbatteri — Eksplosionsfare ved fejlagtig håndtering. Udskiftning må kun ske med batteri af samme fabrikat og type. Levér det brugte batteri tilbage til leverandøren. Norge Advarsel – Apparatet må tilkoples jordet stikkontakt. Sverige Varning – Apparaten skall anslutas till jordat uttag. Suomi Varoitus – Paristo voi räjähtää, jos se on virheellisesti asennettu. Vaihda paristo ainoastaan laitevalmistajan suosittelemaan tyyppiin.
128 Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Regulatory Compliance Statements Your Sun product is marked to indicate its compliance class: • Federal Communications Commission (FCC) — USA • Industry Canada Equipment Standard for Digital Equipment (ICES-003) — Canada • Voluntary Control Council for Interference (VCCI) — Japan • Bureau of Standards Metrology and Inspection (BSMI) — Taiwan Please read the appropriate section that corresponds to the marking on your Sun product before attempting to install the product.
GOST-R Certification Mark 130 Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Index A C ACU creating arrays, 70 creating bootable arrays, 71 initializing disk drives, 72 managing arrays, 71 rescanning disk drives, 72 secure erasing disk drives, 72 advanced data protection, 3 Alarm Control setting, 75 Array Background Consistency Check setting, 74 Array Configuration Utility.
connections, 77 failure recovery multiple arrays, 81 multiple disk drives, 82 RAID 0 arrays, 81 with hot spare, 80 without hot spare, 81 formatting, 76 identifying, 77 initializing, 72 recovering from failure, 80 rescanning, 72 SAS, 107 SAS identifiers, 107 secure erasing, 72 types of connections, 77 verifying, 76 distributed spare drives, 97 drive requirements, 10 Drive’s Write Cache setting, 74 driver and operating system installation, 39, 45 driver installation, 49 to 52 drivers installing on Linux, 50 i
mirroring, 93 N non-redundant logical drives, 92 O online expansion, 2 operating system installation, 39, 45 P parity, 96 Phy Rate setting, 75 phys, 105 Physical Drives Display During POST setting, 74 R RAID, 3 distributed spare drives, 97 mirrored data, 93 non-redundant logical drives, 92 parity, 96 RAID 0, 92 RAID 1, 93 RAID 10, 95 RAID 1E, 3, 94 RAID 5, 96 RAID 50, 98 RAID 5EE, 3, 97 RAID 6, 3, 100 RAID 60, 3, 101 striping data, 92 RAID controllers.
Serial ATA. See SATA serial attached SCSI.
