protected by intellectualproperty laws. Except as expresslypermitted in your license agreementor allowed by law, youmay not use, copy,
reproduce, translate, broadcast, modify, license, transmit,distribute, exhibit, perform, publish,or display any part,in any form, orby any
means. Reverseengineering, disassembly, or decompilation of thissoftware, unless required by law forinteroperability, isprohibited.
The informationcontained herein is subject tochange without notice andis not warranted tobe error-free.If you find any errors,please report
them tous in writing.
If thisis software or related software documentationthat is delivered to theU.S. Government or anyone licensingit on behalf ofthe U.S.
Government, thefollowing notice is applicable:
U.S. GOVERNMENTRIGHTS Programs, software, databases, and relateddocumentation and technical data deliveredto U.S. Government
customers are "commercial computersoftware" or "commercial technical data" pursuantto the applicable FederalAcquisition Regulation and
agency-specific supplementalregulations. As such, the use,duplication, disclosure, modification, and adaptationshall be subject tothe
restrictions and licenseterms set forth inthe applicable Government contract,and, to the extentapplicable by the termsof the Government
contract, theadditional rights set forthin FAR 52.227-19, CommercialComputer SoftwareLicense (December 2007).Oracle USA, Inc., 500
Oracle Parkway, RedwoodCity,CA 94065.
This software orhardware isdeveloped for general usein a variety ofinformation management applications. Itis not developed or intendedfor
use inany inherently dangerous applications, including applicationswhich may create arisk of personal injury. If youuse this software or
hardware in dangerous applications,then you shall be responsibleto take all appropriate fail-safe,backup, redundancy, andother measures to
ensure the safeuse. Oracle Corporation andits affiliates disclaim any liabilityfor any damages causedby use of thissoftware or hardware in
dangerous applications.
Oracle isa registeredtrademark of Oracle Corporationand/or its affiliates. Oracleand Java are registeredtrademarks of Oracleand/or its
affiliates. Other namesmay be trademarksof their respective owners.
AMD, Opteron, theAMD logo, and the AMDOpteron logo are trademarks orregistered trademarksof Advanced Micro Devices. Intel andIntel
Xeon are trademarksor registeredtrademarks of Intel Corporation.All SPARC trademarks are usedunder license and are trademarksor
registered trademarks of SPARC International, Inc. UNIX isa registeredtrademark licensed through X/Open Company, Ltd.
This software orhardware anddocumentation may provide accessto or information on content,products, and services from third parties.
Oracle Corporationand its affiliates are not responsible for andexpressly disclaimall warranties ofany kind with respect to third-party content,
products, and services.Oracle Corporation and itsaffiliates will not be responsiblefor any loss, costs, ordamages incurred due to youraccess to
or useof third-party content, products, or services.
Please
Recycle
Page 3
Contents
Prefacexi
1.HBA Overview1
Kit Contents1
HBA Features2
Array-Level Features2
Advanced Data Protection Suite3
Component Layout3
Operating System and Technology Requirements5
System Interoperability6
Host Platform Support6
Server Support7
Software Support7
2.Hardware Installation and Removal9
Observing ESD and Handling Precautions9
Preparing for Hardware Installation10
▼To Prepare for Hardware Installation10
Installation Task Map12
▼To Install the OS Onto a Bootable Array12
iii
Page 4
▼To Install on an Existing Operating System14
Installing the Battery Backup Module14
▼To Install the Battery Backup Module15
Verifying the Current Devices on a SPARC System16
▼To Verify the Current Devices17
Installing the HBA17
▼To Install the HBA17
Connecting Disk Drives19
▼To Connect Directly to the HBA19
▼To Connect to a System Backplane20
Testing the HBA Installation20
▼To Test the HBA Installation on a SPARC System20
▼To Test the HBA Installation on an x64 System23
Next Steps25
Removing the Hardware25
▼To Prepare the HBA for Removal26
▼To Remove the HBA26
3.Creating a Bootable Array on an x64 System27
Creating an Array28
▼To Create a RAID 5 Array With the ACU29
Making the Array Bootable31
▼To Make the Array Bootable31
Setting the Boot HBA31
▼To Set the Boot HBA31
Next Steps32
4.Creating a Bootable Array on a SPARC System33
Preparing to Create a Bootable Logical Drive34
ivSun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 5
▼To Prepare to Create a Bootable Logical Drive on a SPARC System34
Building a Logical Drive On Which to Install the Solaris OS34
▼To Create a Logical Drive35
▼To Delete a Logical Drive on RAID Card 137
▼To Label the Newly Created Logical Drive37
Next Steps38
5.Installing an OS Onto a Bootable Array on an x64 System39
Preparing to Install an OS40
▼To Prepare to Install an OS40
Installing the HBA Driver With an OS40
▼To Install the Driver With the Windows OS41
▼To Install the Driver With the Red Hat Linux OS41
▼To Install the Driver With the SUSE Linux OS42
▼To Install the Driver With the Solaris OS42
▼To Install the Driver With VMware Technology43
Next Steps43
6.Installing the Solaris OS on a SPARC System45
Preparing to Install the Solaris OS46
▼To Prepare to Install the Solaris OS46
Installing the Solaris OS46
▼To Install the Solaris OS46
Next Steps47
7.Installing the Driver on an Existing Operating System49
Preparing to Install the HBA Driver49
Installing the Driver on an Existing OS50
▼To Install the Driver on the Windows OS50
▼To Install the Driver on the Red Hat or SUSE Linux OS50
Contentsv
Page 6
▼To Install the Driver on the Solaris OS on an x64 System51
▼To Install the Driver on the Solaris OS on a SPARC System51
▼To Install the Driver On the VMware Technology52
Next Steps52
8.Known Issues53
Ship Kit Issues53
Some or All CDs Are Not Included in the HBA Ship Kit53
BIOS Utility Issues54
Creating an Array With the BIOS Utility Changes the BIOS Boot Order54
Hot-Plug Functionality Does Not Work in the BIOS Utility54
Performance Issues54
The System Freezes When a Sun Storage 32GB SLC SATA Solid State Drive
(SSD) is Configured In the HBA55
Cannot Access the HBA From the GUI Nor Access a LUN From the Host55
Data Miscompare With 3.5" SAS Disks55
A.Configuration Rules57
Target Devices57
Cabling58
B.HBA Specifications59
Physical Dimensions59
Environmental Specifications60
DC Power Requirements60
Current Requirements60
Performance Specifications60
Connector Pin Definitions61
SAS Pin-Out61
SATA Pin-Out62
viSun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 7
C.Using the BIOS RAID Configuration Utility65
Introduction to the BIOS RAID Configuration Utility66
Understanding Hot-Plug Limitations and Conditions Within the BIOS RAID
Configuration Utility66
Hot-Unplug Removal Conditions66
Hot-Plug Addition Conditions67
Hot-Unplug and Plug Replacement/Reinsertion Conditions67
Running the BIOS RAID Configuration Utility68
▼To Start the BIOS RAID Configuration Utility68
▼To Navigate the BIOS RAID Configuration Utility69
Using the ACU to Create and Manage Arrays69
▼To Start the ACU70
▼To Create a New Array With the ACU70
▼To Manage Existing Arrays With the ACU71
▼To Make an Array Bootable With the ACU71
▼To Initialize Disk Drives With the ACU72
▼To Rescan Disk Drives With the ACU72
▼To Perform a Secure Erase on Disk Drives With the ACU72
▼To Stop a Secure Erase in Progress With the ACU72
Using the -Select Utility to Modify HBA Settings73
▼To Start Using a -Select Utility73
▼To Apply Changes and Exit a -Select Utility73
▼To Modify General HBA Settings With a -Select Utility74
▼To Modify SAS-Specific HBA Settings With a -Select Utility75
Using the Disk Utilities to Manage Disk Drives76
▼To Format or Verify a Disk Drive With the Disk Utilities76
▼To Locate Disk Drives With the Disk Utilities76
▼To Identify Disk Drives With the Disk Utilities77
Viewing the BIOS-Based Event Log78
Contentsvii
Page 8
▼To View the Event Log78
D.Troubleshooting79
Troubleshooting Checklist79
Silencing the Alarm80
Recovering From a Disk Drive Failure80
Failed Disk Drive Protected by a Hot-Spare80
▼To Recover From a Disk Drive Failure80
Failed Disk Drive Not Protected by a Hot-Spare81
Failure in Multiple Arrays Simultaneously81
Disk Drive Failure in a RAID 0 Array81
Multiple Failures in the Same Array82
E.Best Practices83
Best Practices For Placing a New HBA in a System Running the Solaris OS83
Best Practices For Switching Cables and Making New Connections84
Switching a Cable From One Port To the Other84
Pulling a Cable and Reconnecting It To the Same Port85
Connecting a JBOD With SATA Disks85
Best Practices For Cabling to Disk Enclosures85
Best Practices For Testing Hard Drive Failure Conditions85
Best Practices For Deleting Logical Volumes Without Deleting Partitions86
Best Practices For Testing Physical Drive Failures86
Best Practices For Rescanning or Discovering Drives87
Best Practices For Controlling the Boot Order of Logical Drives87
Best Practices For Selecting Members of RAID Logical Devices88
Best Practices For Replacing an HBA88
Replacing an HBA On a SPARC System89
Replacing an HBA On an x64 System89
viiiSun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 9
F.Selecting the Best RAID Level91
Understanding Drive Segments92
Nonredundant Arrays (RAID 0)92
RAID 1 Arrays93
RAID 1 Enhanced Arrays94
RAID 10 Arrays95
RAID 5 Arrays96
RAID 5EE Arrays97
RAID 50 Arrays98
RAID 6 Arrays100
RAID 60 Arrays101
Selecting the Best RAID Level101
Migrating RAID Levels102
G.Introduction to Serial Attached SCSI103
Terminology Used in This Appendix104
About SAS104
About SAS Device Communication105
About Phys105
About SAS Ports106
About SAS Addresses106
About SAS Connectors107
About SAS Cables107
About Identifying Disk Drives in SAS107
About SAS Connection Options108
Direct-Attach Connections108
Backplane Connections108
SAS Expander Connections109
Differences Between SAS and Parallel SCSI110
Contentsix
Page 10
H.Declaration of Conformity, Safety, and Regulatory Statements113
Declaration of Conformity115
Safety Agency Compliance Statements117
Regulatory Compliance Statements129
Index131
xSun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 11
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.
This preface contains the following topics:
■ “Before You Read This Document” on page xi
■ “Related Documentation” on page xii
■ “Documentation, Drivers, Support, and Training” on page xiii
■ “Documentation Comments” on page xiii
Before You Read This Document
Familiarize yourself with computer hardware, data storage, RAID technology, and
the input/output (I/O) technology—SAS, or Serial ATA (SATA)—used by the HBA.
Also, familiarize yourself with Direct-Attached Storage (DAS) or Network-Attached
Storage (NAS)—whichever is appropriate for your storage space—and Storage Area
Network (SAN) concepts and technology.
If you are using a SPARC system with the HBA and you need to install the Solaris
OS, read the Solaris 10 10/08 Installation Guide: Basic Installations (part number: 8205236-nn) prior to installing the HBA. You can find this document by performing a
search at:
http://docs.sun.com
xi
Page 12
Related Documentation
The following table lists the documentation for this product. The online
documentation is available at:
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.com
Please include the title and part number of your document with your feedback:
Sun StorageTek SAS RAID HBA Installation Guide , part number 820-1847-20
Prefacexiii
Page 14
xivSun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 15
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.
The chapter contains the following sections:
■ “Kit Contents” on page 1
■ “HBA Features” on page 2
■ “Operating System and Technology Requirements” on page 5
■ “System Interoperability” on page 6
Kit Contents
■ Sun StorageTek SAS RAID Internal HBA
■ Full-height bracket
■ Battery backup (BBU) module and installation hardware
■ Sun StorageTek RAID Driver CD
■ Sun StorageTek RAID Manager CD (which contains the HBA documentation)
■ Live CD
Note – If a CD listed in this section is not included in the ship kit, you can obtain
the contents of the CD at:
http://
support.intel.com/support/go/sunraid.htm
1
Page 16
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.)
■ Disk drive hot-plugging (See the HDD hot-plug guidelines in “Understanding
Hot-Plug Limitations and Conditions Within the BIOS RAID Configuration
Utility” on page 66.)
■ Event logging and broadcasting, including email and SNMP messages
■ The Sun StorageTek RAID Manager GUI, a BIOS-based utility, and a command-
line interface for creating and managing RAID arrays
■ Support for disk drive enclosures with SES2 enclosure management hardware
■ A battery backup module
Array-Level 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.
■ Support for RAID levels 0, 1, 1E, 10, 5, 5EE, 50, 6, 60, simple volume, spanned
volume, and RAID volume
■ Support for hot-spares (global and dedicated)
■ Support for automatic failover, so arrays are automatically rebuilt when a failed
disk drive is replaced (applies to redundant arrays in SES2- or SAF-TE-enabled
disk drive enclosures
■ Optimized disk utilization, which ensures that the full capacity of all disk drives
can be used, even if the disk drives vary in size
■ Online capacity expansion, so you can increase the capacity of an array without
recreating it
2Sun StorageTek SAS RAID HBA Installation Guide • March 2010
only)
Page 17
■ 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.
■ Hot-Spare (RAID 5EE)—A RAID 5EE array is similar to a RAID 5 array except
that it includes a distributed spare and must be built from a minimum of four
disk drives.
■ Dual Drive Failure Protection (RAID 6)—A RAID 6 array is similar to a RAID 5
array except that it includes two independent sets of parity data instead of one.
■ Dual Drive Failure Protection (RAID 60)—A RAID 60 array is similar to a RAID
50 array except that it includes four independent sets of parity data instead of
two.
Component Layout
The Sun StorageTek SAS RAID Internal HBA is a SAS RAID HBA with these
features.
Chapter 1HBA Overview3
Page 18
FIGURE 1-1Sun StorageTek SAS RAID Internal HBA Component Layout
The following table lists the features of the HBA.
TABLE 1-1HBA Features
FeatureSpecification
Form factorLow-profile MD2
Bus compatibilityPCIe
PCIe bus widthx8
PCIe bus speed2.5 Gb/s
PHYs8
Standard cache256 MB DDR2
Connectors, internalTwo mini SAS x4 (SFF-8087)
RAID levels0, 1, 1E, 10, 5, 5EE, 50,6, 60, JBOD
Simple volume
4Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 19
TABLE 1-1HBA Features
Feature (Continued)Specification (Continued)
Disk drivesSATA, SATA II, SAS
Maximum number of disk
drives
Hot-spares
Enclosure supportI2C and SGPIO
Automatic failover
Audible alarm
Battery backup moduleABM-800
8 (or up to 100 with expanders)
Operating System and Technology
Requirements
This HBA supports the following operating system and technology versions.
TABLE 1-2Supported Operating System and Technology Versions
Operating
System/Technology
Solaris 10 OS for the
x64 and x86 (32-bit and
64-bit) platforms
Solaris 10 OS for the
SPARC (64-bit)
platform
Linux OS• RHEL 5 Server, 32-bit and 64-bit
Supported Versions
• Solaris 10 10/08 (s10u6)
• Solaris 10 5/08 (s10u5)
• Solaris 10 8/07 (s10u4)
Solaris 10 10/08 (s10u6)
• RHEL 5 Advanced Platform, 32-bit and 64-bit
• Red Hat Enterprise Linux (RHEL) 4 ES, 32-bit and 64-bit
• RHEL 4 AS Update 5, 32-bit and 64-bit
Chapter 1HBA Overview5
Page 20
TABLE 1-2Supported Operating System and Technology Versions (Continued)
Operating
System/Technology
VMware® TechnologyESX Server version 3.0.2, Update 1 (driver support only; storage
Microsoft Windows OS• Windows Server 2008 Enterprise Edition, 32-bit or 64-bit
Supported Versions
• SUSE Linux Enterprise Server (SLES) 10
• SUSE Linux Enterprise Server (SLES) 9, SP4
management must be done through the command-line interface or
the BIOS utility. For more information, see the Uniform Command-Line Interface User’s Guide at:
http://docs.sun.com/app/docs/prod/stortek.raid.hba#
hic
• Windows Server 2008 Standard Edition, 32-bit or 64-bit
• Windows Server 2003 Enterprise Edition, 32-bit or 64-bit
• Windows Server 2003 Standard Edition, 32-bit or 64-bit
Note – For up-to-date operating system version support, visit
http://
support.intel.com/support/go/sunraid.htm
.
System Interoperability
This section provides information about selected platforms and servers that are
compatible with the Sun StorageTek SAS RAID Internal HBA. This section contains
the following subsections:
■ “Host Platform Support” on page 6
■ “Server Support” on page 7
■ “Software Support” on page 7
Host Platform Support
The HBA is supported by a computer that meets the following criteria:
■ 1 GB of RAM, at minimum
■ Available compatible PCI Express x8 slot
■ 100 MB of free disk drive space
6Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 21
Server Support
TABLE 1-3 lists the servers that the HBA supports.
TABLE 1-3Server Support
ServerSupported OS/Technology
SPARC Servers
Sun SPARC Enterprise T5120 serverSolaris
Sun SPARC Enterprise T5220 serverSolaris
Sun SPARC Enterprise T5140 serverSolaris
Sun SPARC Enterprise T5240 serverSolaris
Sun SPARC Enterprise T5440 serverSolaris
Sun SPARC Enterprise M3000 serverSolaris
Sun Fire T1000 serverSolaris
Sun Ultra U45 serverSolaris
x64 Servers
Sun Fire X2250 serverSolaris, Linux, VMware, and Windows
Sun Fire X4140 serverSolaris, Linux, VMware, and Windows
Sun Fire X4150 serverSolaris, Linux, VMware, and Windows
Sun Fire X4240 serverSolaris, Linux, VMware, and Windows
Sun Fire X4250 serverSolaris, Linux, VMware, and Windows
Sun Fire X4440 serverSolaris, Linux, VMware, and Windows
Sun Fire X4450 serverSolaris, Linux, VMware, and Windows
Software Support
TABLE 1-4 lists the software applications that the HBA supports.
TABLE 1-4Software Support
SoftwareSupported OS
VERITAS Software Foundation 5.0Solaris
Sun StorEdge Enterprise Backup Software
6.0B/7.0/7.1
Solaris, Linux, and Windows
VERITAS NetBackup 6.0Solaris, Linux, and Windows
Chapter 1HBA Overview7
Page 22
8Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 23
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.
This chapter contains the following sections:
■ “Observing ESD and Handling Precautions” on page 9
■ “To Prepare for Hardware Installation” on page 10
■ “To Install the Battery Backup Module” on page 15
■ “To Install the HBA” on page 17
■ “Connecting Disk Drives” on page 19
■ “Testing the HBA Installation” on page 20
■ “Removing the Hardware” on page 25
Observing ESD and Handling
Precautions
Caution – Damage to the HBA can occur as the result of careless handling or
electrostatic discharge (ESD). Always handle the HBA with care to avoid damage to
electrostatic sensitive components.
To minimize the possibility of ESD-related damage, use both a workstation antistatic
mat and an ESD wrist strap. You can get an ESD wrist strap from any reputable
electronics store or from Sun as part number #250-1007. Observe the following
precautions to avoid ESD-related problems:
■ Leave the HBA in its antistatic bag until you are ready to install it in the system.
9
Page 24
■ 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. Familiarize yourself with the physical features of the Sun StorageTek SAS
RAID Internal HBA and the RAID levels that it supports.
See “Component Layout” on page 3.
3. Ensure you have the right quantity of initialized disk drives for the RAID level
you want to use for the arrays.
See “Selecting the Best RAID Level” on page 101.
All the disk drives must have the same performance level. You can use different-
sized disk drives in the array, but the array will be limited to the capacity of the
smallest and slowest disk drive.
For more information, refer to the Sun StorageTek RAID Manager Software User’sGuide or online Help.
The Sun StorageTek SAS RAID Internal HBA supports both SAS and SATA disk
drives.
4. Ensure that you have the proper cables for the HBA and disk drives.
You will need one SAS cable for each disk drive you are connecting to the HBA.
Use only Sun-provided SAS cables (provided to you with your Sun system at the
time of purchase). For more information or to purchase cables for your Sun
system, visit the Sun web site at http://www.sun.com. Cable connectors are
keyed so that you cannot insert them incorrectly.
10Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 25
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-1Internal Mini-SAS with Power, Which Connects to Four SAS or SATA Disk
Drives
FIGURE 2-2Internal Mini-SAS to SATA Fan-Out, Which Connects to Four SATA Disk
Drives
Chapter 2Hardware Installation and Removal11
Page 26
FIGURE 2-3Internal 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.
You can choose to create a bootable array and then install an operating system
and the HBA driver on that array, or you can complete a standard installation,
where the HBA driver is installed on an existing operating system.
Installation Task Map
You can choose either of these installation options:
■ “To Install the OS Onto a Bootable Array” on page 12
■ “To Install on an Existing Operating System” on page 14
▼ To Install the OS Onto a Bootable Array
1. Install the battery backup module (BBU).
See “Installing the Battery Backup Module” on page 14.
2. Install and connect the HBA and disk drives.
See “Installing the HBA” on page 17.
12Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 27
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. Install the Sun StorageTek RAID Manager software and begin to manage data
storage.
Use the Sun StorageTek RAID Manager CD provided in the HBA ship kit to
install the Sun StorageTek RAID Manager software. For information about
installing and using the software, see the Sun StorageTek RAID Manager SoftwareUser’s Guide. For the latest version of the software, go to:
http://
support.intel.com/support/go/sunraid.htm
.
Chapter 2Hardware Installation and Removal13
Page 28
▼ 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.
See “Installing the Driver on an Existing OS” on page 50.
5. Install the Sun StorageTek RAID Manager software and begin to manage data
storage.
Use the Sun StorageTek RAID Manager CD provided in the HBA ship kit to
install the Sun StorageTek RAID Manager software. For information about
installing and using the software, see the Sun StorageTek RAID Manager SoftwareUser’s Guide. For the latest version of the software, go to:
http://
support.intel.com/support/go/sunraid.htm
.
Installing the Battery Backup Module
Tools required:
■ Small Phillips head screw driver to tighten the screws
■ (Suggested) Small needle nose pliers or tweezers
■ ESD wrist strap
14Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 29
▼ 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. This is about 3 inches from the right edge of the HBA.
■ The bottom right hole. This is about 1 inch from the right edge of the HBA.
■ The top right hole. This is about 1 inch from the right edge of the HBA.
FIGURE 2-4Installing the Battery Backup Module
Chapter 2Hardware Installation and Removal15
Page 30
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. Obtain the three nuts from the BBU kit, and for each nut, do the following:
a. Place the nut onto the screw and hold the nut in place.
b. With the Phillips head screw driver, reach underneath the HBA and, while
holding the nut in place with your other hand (or with needle nose pliers or
tweezers), screw the plastic screw into the nut.
c. Repeat Step a - Step b for the remaining nuts.
Note – If you are unable to place a nut onto the screw that is close to the heat sink,
use a small pair of needle nose pliers or tweezers.
Caution – Do not over-tighten the screws.
Verifying the Current Devices on a
SPARC System
If you are installing on a non-SPARC system, skip to “Installing the HBA” on
page 17.
16Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 31
▼ 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.
This will help you determine which device is the HBA after you install the HBA.
Installing the HBA
Note – For the Sun SPARC Enterprise T5120, T5220, T5140, and T5240 servers,
contact Sun support to install the HBA.
▼ To Install the HBA
1. Remove the safety clip from each internal SAS connector by using your thumb
and forefinger to gently press the tabs of the safety clip and pull the clip out.
See
FIGURE 2-5.
Chapter 2Hardware Installation and Removal17
Page 32
FIGURE 2-5Removing 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.
When installed properly, the HBA will appear level with the expansion slot.
6. Secure the bracket in the x8 PCI Express slot, using the retention device (for
instance, a screw or lever) supplied with the computer.
7. Continue with the following section.
18Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 33
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. For more information or to
purchase cables, visit the Sun web site at http://www.sun.com.
▼ To Connect Directly to the HBA
In a direct-attach connection, SAS or SATA disk drives are connected directly to a
SAS card with SAS cables. The number of direct-attached disk drives is limited to
four per internal SAS connector.
1. Install the internal SAS or SATA disk drives, following the instructions in your
system documentation.
2. Use internal SAS or mini-SAS cables to attach the disk drives to the HBA.
FIGURE 2-6Attach Cables Between RAID HBA and Internal SAS or SATA Drives
Chapter 2Hardware Installation and Removal19
Page 34
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. Connect one or more internal SAS or SATA disk drives to the backplane.
Refer to your system’s documentation for more information.
2. Use an internal SAS cable, or cables, to connect the HBA to the backplane.
3. When all internal disk drives have been installed and connected, close the
computer cabinet and reattach the power cord.
Testing the HBA Installation
Note – Check all SAS cables to ensure that they are securely attached and are not
damaged or pinched anywhere along the length of cable.
This section contains the following subsections:
■ “To Test the HBA Installation on a SPARC System” on page 20
■ “To Test the HBA Installation on an x64 System” on page 23
▼ To Test the HBA Installation on a SPARC System
1. Power-up the computer and storage systems.
a. Ensure that all hard disk drives are securely installed.
b. Connect all power cords securely and plug them into the proper power
sources.
20Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 35
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.
{0} ok show-disks
a) /pci@0/pci@0/pci@8/pci@0/pci@8/scsi@0/disk
b) /pci@0/pci@0/pci@2/scsi@0/disk
c) /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: Chassis | critical: V_VCORE at /SYS/MB has
exceeded high warning threshold.
valid choice: a...c, q to quit q
Note – Device paths might vary from this example, depending on which SPARC
system you are using and into which PCI-E slot the card is plugged.
3. Use the select command to select the device node for the HBA, and follow the
on-screen instructions by pressing Enter when prompted.
Note – When you run this command, omit /disk from the HBA device path, as
shown in the following example.
{0} ok select /pci@0/pci@0/pci@8/pci@0/pci@8/scsi@0
Waiting for AAC Controller to start: . . . . . . . Started
Config Changes:
1 ->One or more device either moved or removed
or not responding or added
Press <ENTER> to accept current config changes - with in 30 seconds
(Default - Ignore changes and check the setup)
<ENTER> Pressed. Current Config is accepted
Chapter 2Hardware Installation and Removal21
Page 36
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.
6. Return to the root node by using the unselect-dev command.
{0} ok unselect-dev
22Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 37
Note – At this point, there are no volumes created and the output from a probe-
scsi-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. Connect all power cords securely and plug them into the proper power
source(s).
c. If applicable, power on the disk drive enclosure.
If the enclosure provides HDD status indicators, make sure they are normal.
d. Power-on the computer system.
If the system provides HDD status indicators, make sure they are normal.
2. Enter the BIOS RAID Configuration Utility:
a. During POST, press Ctrl + A when prompted.
b. As the computer continues its startup sequence, review the boot messages to
determine the firmware version on the HBA.
Boot messages, similar to those shown in the following example, are displayed
that indicate the firmware version (in this example, the FW build is 15815).
Adaptec RAID BIOS V5.3-0 [Build 15815]
(c) 1998-2008 Adaptec, Inc. All Rights Reserved
<<<Press <Ctrl><A> for Adaptec RAID
Adaptec RAID Configuration Utility will be invoked after initialization.
Booting the Controller Kernel....Controller started
Controller #00: Sun STK RAID INT at PCI Slot:02, Bus:04, Dev:00, Func:00
Waiting for Controller to Start....Controller started
Controller monitor V5.3-0[
Battery Backup Unit Present
Controller POST operation successful
Controller Memory Size: 256 MB
15815], Controller kernel V5.3-0[15815]
Chapter 2Hardware Installation and Removal23
Page 38
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. Press Enter as prompted.
5. Verify that all attached HDDs are detected by the HBA:
a. At the Main Menu highlight Initialize Drives and press Enter.
b. In the Select drives for initialization column, verify that all attached HDDs
are displayed.
c. Select drives to initialize them for verification.
You can initialize all of the drives now or wait until you are ready to create
your arrays.
6. Verify that all HDDs are available for array creation:
a. Return to the Main Menu page, highlight Create Array and press Enter.
b. In Select drives to create Array, verify that all the attached HDDs are
available for array creation.
c. Highlight a couple of drives and press the space bar.
Verify that the drives are moved into the right column in preparation for array
creation.
7. Press Esc and exit.
You will create the arrays later.
8. Test the alarm for the HBA:
a. Press Esc until you reach the controller Options menu.
b. Highlight Serial Select and press Enter.
c. Highlight Controller Configuration and press Enter.
d. Highlight Alarm Control… and press Enter.
24Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 39
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. If any issues are discovered, correct them and retest the HBA
before continuing.
Next Steps
If you are installing an operating system onto a bootable array, continue with one of
these sections, depending on whether you use an x64 or SPARC system:
■ “Creating a Bootable Array on an x64 System” on page 27
■ “Creating a Bootable Array on a SPARC System” on page 33.
If you are completing a standard installation onto an existing operating system,
continue with “Installing the Driver on an Existing Operating System” on page 49.
Removing the Hardware
The following instructions describe the tasks required to remove the HBA. If you
need to replace a failed HBA, remove the hardware, as described in this section, and
see “Best Practices For Replacing an HBA” on page 88.
Caution – Never remove the HBA when an attached array is in the process of
rebuilding a logical drive from a “Degraded” state.
Chapter 2Hardware Installation and Removal25
Page 40
▼ 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. Hold the upper portion of the bracket with one hand and the rear of the HBA
with the other hand.
3. Pull straight up until the HBA clears the PCI Express* expansion slot.
4. Lift the HBA from the computer chassis.
26Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 41
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.
Note – If you are a SPARC system user, and you want to create a bootable array and
then install the Solaris operating system and the HBA driver onto that array, DO
NOT complete any task in this chapter. Instead, go to “Creating a Bootable Array on
a SPARC System” on page 33.
Note – If you want to complete a standard installation onto an existing operating
system, DO NOT complete any task in this chapter. Instead, skip to “Installing the
Driver on an Existing Operating System” on page 49.
This chapter contains the following sections:
■ “Creating an Array” on page 28
■ “Making the Array Bootable” on page 31
■ “Setting the Boot HBA” on page 31
27
Page 42
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. See “To Create a RAID 5 Array With the ACU” on page 29.
■ Command Line Interface (UCLI)—Refer to the Uniform Command-Line Interface
You can use either tool, but the ACU utility is the quicker and easier tool for this
task. The ACU is menu-based and provides instructions for completing tasks onscreen. Menus can be navigated using the arrows, Enter, Esc, and other keys on your
keyboard.
Note – Do not combine SAS and SATA disk drives within the same array. The Sun
StorageTek RAID Manager software generates a warning if you try to create a logical
drive using a combination of SAS and SATA disk drives. See “Introduction to Serial
Attached SCSI” on page 103 for more information.
28Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 43
▼ 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.
During boot up, if the system has insufficient memory the following message will
be displayed.
Adaptec RAID Configuration Utility will load after system
initialization. Please wait... Or press <Enter> Key to attempt
loading the utility forcibly [Generally, not recommended]
3. If you have more than one HBA of the same model or family in the computer,
select the HBA that you want, and press Enter.
4. Select Array Configuration Utility, then press Enter.
5. Select Initialize Drives, then press Enter.
6. Select at least three disk drives for the array, press Insert for each selected disk
drive, then press Enter.
Caution – During initialization, all data is deleted from the disk. Before continuing,
back up any data you want to keep.
7. Press Y, then press Enter.
The selected disk drives are initialized, then the ACU screen is displayed.
8. Select Create Array, then press Enter.
9. Select the disk drives that were just initialized, press Insert for each selected
disk drive, and press Enter.
Chapter 3Creating a Bootable Array on an x64 System29
Page 44
10. When the Array Properties screen is displayed, follow the instructions in the
following table.
TABLE 3-1Filling in Array Properties Screen
Property Line
Array Type
Array Label
Array Size
Stripe Size
Read Caching
Write Caching
Entry or Selection
Select RAID 5, then press Enter.
Type a name, then press Enter.
Press Enter, then press Enter again to use the default granularity of GB.
Press Enter to use the default (256 KB).
Press Enter to use the default (Yes).
Press Enter to use the default (Disable).
Caution - When write cache is enabled, there is a slight possibility of
data loss or corruption during a power failure.
Create RAID via
[Done]
11. If a cache warning message is displayed, type
Press Enter to use the default (Build/Verify).
Press Enter.
Y
.
12. After the array is created, a message is displayed telling you that the array can
now be used.
13. Press any key to return to the ACU Menu.
You can start using the array immediately. However, performance is reduced until
the build process is complete.
14. Press Esc until the Exit utility window is displayed.
15. Select Yes, then press Enter.
The computer restarts.
16. Continue with “Installing an OS Onto a Bootable Array on an x64 System” on
page 39.
30Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 45
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.
Note – You cannot make an array bootable while it is building, verifying, or
rebuilding.
The number of the array changes to Array 00, which makes this array the boot
array for the Sun StorageTek SAS RAID Internal HBA.
3. Restart the computer.
Setting the Boot HBA
The Sun StorageTek SAS RAID Internal HBA supports bootable disk drives and
bootable arrays. You can configure the computer system to boot from either a disk
drive or an array connected to the HBA.
▼ To Set the Boot HBA
Note – For more information about completing these steps, refer to your computer
documentation.
Chapter 3Creating a Bootable Array on an x64 System31
Page 46
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.
32Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 47
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.
Note – If you are an x64 system user, and you want to create a bootable array and
then install an operating system and the HBA driver onto that array, DO NOT
complete any task in this chapter. Instead, go to “Creating a Bootable Array on an
x64 System” on page 27.
Note – If you want to complete a standard installation onto an existing operating
system, DO NOT complete any task in this chapter. Instead, skip to “Installing the
Driver on an Existing Operating System” on page 49.
Note – The procedures in this chapter do not require the use of a network install
server. If you prefer to create RAID volumes from a network install server, do not
follow the procedures in this chapter. Instead, add the command-line interface (CLI),
shown in the examples in this chapter, to the miniroot image on the network install
server. To obtain the CLI, install the Sun StorageTek RAID Manager software
package for SPARC, located on the Sun StorageTek RAID Manager CD in the HBA
ship kit or go to:
http://support.intel.com/support/go/sunraid.htm
For more information about modifying the miniroot image, see “Patching the
Miniroot Image” in the Solaris 10 10/08 Installation Guide: Network-Based Installations
document, located at http://docs.sun.com..
33
Page 48
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. Obtain the Live CD for SPARC from the HBA ship kit or go to:
http://support.intel.com/support/go/sunraid.htm
.
Building a Logical Drive On Which to
Install the Solaris OS
In order to install the Solaris 10/08 OS, you need to build the logical drive (array) on
which to install it. This section contains the following subsections:
■ “To Create a Logical Drive” on page 35
■ “To Delete a Logical Drive on RAID Card 1” on page 37
■ “To Label the Newly Created Logical Drive” on page 37
Note – The following procedures provide basic examples of the command-line
interface (CLI). For detailed information about using the CLI, see the Uniform
Command-Line Interface User’s Guide, located at:
34Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 49
▼ 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.
In the following example, note that the CLI is located in the /opt/StorMan
directory, and the name of the CLI is arcconf. All commands must start with
unless you have altered the path to include /opt/StorMan in it.
# cd /opt/StorMan
# ./arcconf GETCONFIG 1
./
Note – Ignore any “failing to write to log files” messages that might be displayed
after running the command. The command will run successfully and will provide a
list of physical disks, card status, and logical disks. The list might be long if you
have many physical disks. If you have multiple RAID cards, you can specify them
with different numbers, starting from 1.
Chapter 4Creating a Bootable Array on a SPARC System35
Page 50
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.
# ./arcconf CREATE 2 LOGICALDRIVE MAX 1 0 0 0 1
■ To create a logical drive on the RAID card 1, using RAID 5 and all space on
disks 0,2 0,3 and 0,4, run the CREATE command as shown in the following
example.
Note – After using the CREATE command, you will see error messages like the one
shown in the next example. This is because you are working on a read-only file
system and certain links cannot be created. However, if the last message says
“Command completed successfully”, the logical drive is created.
Creating logical device: Device 2
devfsadm: mkdir failed for /dev 0x1ed: Read-only file system
WARNING: /pci@7c0/pci@0/pci@8/scsi@0/sd@2,0 (sd2):
Corrupt label; wrong magic number
devfsadm: inst_sync failed for /etc/path_to_inst.117: Read-only file system
devfsadm: WARNING: failed to update /etc/path_to_inst
Command completed successfully.
36Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 51
▼ 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.
In this example, x is the number of the logical drive that you want to delete.
# ./arcconf DELETE 1 LOGICALDRIVE x
▼ To Label the Newly Created Logical Drive
Before the Solaris OS can install software onto the newly created logical drive, you
must label the drive.
1. Use the ./arcconf GETCONFIG card-number LD command to display the logical
drives on RAID card 1.
# ./arcconf GETCONFIG 1 LD
2. Use the devfsadm command to find the newly created drive and load its
drivers.
# devfsadm
3. To label the newly created drive, use the format command and select the
logical drive.
You can distinguish the logical RAID card drives in the output by looking at the
vendor/product ID string. The Sun StorageTek SAS RAID HBA card is displayed
as “Sun-STKRAID.” The last part of the string will display “EXT” (for external) or
“INT” (for internal), depending on the type of card you have.
Chapter 4Creating a Bootable Array on a SPARC System37
Page 52
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@780/pci@0/pci@9/scsi@0/sd@0,0
1. c0t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@780/pci@0/pci@9/scsi@0/sd@1,0
2. c2t0d0 <Sun-STKRAIDINT-V1.0 cyl 17818 alt 2 hd 255 sec 63>
/pci@7c0/pci@0/pci@8/scsi@0/sd@0,0
3. c2t1d0 <Sun-STKRAIDINT-V1.0 cyl 8907 alt 2 hd 255 sec 63>
/pci@7c0/pci@0/pci@8/scsi@0/sd@1,0
Specify disk (enter its number): 2
4. When the format process displays the Disk not labeled. Label it now?
prompt, type y and press Enter.
5. Exit the format process by typing quit and pressing Enter.
You now have a labeled logical drive.
6. Use the init 0 command, switch to the ok prompt, and use the boot net
command to reboot the system for normal network-based installation.
# init 0
# syncing file systems... done
Program terminated
r)eboot, o)k prompt, h)alt?
ok boot net
o
Next Steps
Install the Solaris OS and the HBA driver onto the bootable array, as described in
“Installing the Solaris OS on a SPARC System” on page 45.
38Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 53
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.
Note – If you are using a SPARC system and you chose to create a bootable array as
part of your installation (“Creating a Bootable Array on a SPARC System” on
page 33), DO NOT perform any steps in this chapter. Instead, skip to “Installing the
Solaris OS on a SPARC System” on page 45.
Note – If you want to perform a standard installation on an existing operating
system, DO NOT perform the procedures in this chapter. Instead, go to “Installing
the Driver on an Existing Operating System” on page 49.
Note – Each computer system is different. The instructions in this chapter might
need to be modified, depending on your actual system configuration. See your
system documentation for more information.
This chapter contains the following sections:
■ “Preparing to Install an OS” on page 40
■ “Installing the HBA Driver With an OS” on page 40
39
Page 54
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
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
http://support.intel.com/support/go/sunraid.htm
.
.
Installing the HBA Driver With an OS
The HBA driver can be installed with various operating systems and technology on
an x64 system. This section contains the following subsections:
■ “To Install the Driver With the Windows OS” on page 41
■ “To Install the Driver With the Red Hat Linux OS” on page 41
■ “To Install the Driver With the SUSE Linux OS” on page 42
■ “To Install the Driver With the Solaris OS” on page 42
■ “To Install the Driver With VMware Technology” on page 43
40Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 55
▼ 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. Insert the driver CD, and then wait until you are prompted to install a driver.
5. Press S to specify that the driver is on the installed medium, then press Enter.
The computer reads the medium.
6. When the driver is found, press Enter.
7. Follow the on-screen instructions to complete the installation.
8. To configure and manage the hard disks, see the Sun StorageTek RAID ManagerSoftware User’s Guide at:
Note – You will need the SUSE installation media to perform this task.
1. Insert the SUSE Installation medium.
2. Restart the computer.
3. When the SUSE installation selection screen is displayed, choose the type of
installation you want, then press the F6 key to indicate the use of a driver
medium, such as a USB thumb key or a CD-ROM / DVD-ROM drive.
If F6 is not shown on the screen, you may have an older version of SUSE; press
the Alt key instead.
4. When prompted, insert the driver CD, and then press any key to continue.
5. Follow the prompts to set up the environment you want.
6. If you are installing other third-party devices, install them now.
Otherwise, select Back.
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 ManagerSoftware User’s Guide at:
This HBA supports, at a minimum, the Solaris 10 8/07 (s10u4) OS on an x64-based
system. The Solaris 10 8/07 OS requires nothing from the user. However, install the
latest patches from the http://www.sunsolve.sun.com website after installing
the Solaris OS.
42Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 57
▼ 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.
Note – The Sun StorageTek RAID Manager GUI is not supported with VMware
technology. To create and manage arrays, use the command-line interface and the
BIOS utility. See the Uniform Command-Line Interface User’s Guide for more
information at:
■ Use the BIOS utility to create arrays on the disk enclosure. See “Using the BIOS
RAID Configuration Utility” on page 65.
Chapter 5Installing an OS Onto a Bootable Array on an x64 System43
Page 58
44Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 59
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.
Note – If you are using an x64 system and you chose to create a bootable array as
part of your installation (“Creating a Bootable Array on an x64 System” on page 27),
DO NOT perform any steps in this chapter. Instead, skip to “Installing an OS Onto a
Bootable Array on an x64 System” on page 39.
This chapter contains the following sections:
■ “Preparing to Install the Solaris OS” on page 46
■ “Installing the Solaris OS” on page 46
■ “Next Steps” on page 47
45
Page 60
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. Obtain the Solaris 10 10/08 OS, at minimum, from the Sun download site:
http://www.sun.com/software/solaris
2. Perform a normal installation, as described in the Solaris 10 10/08 Installation
Guide: Basic Installations (part number: 820-5236-nn).
You can obtain this document by performing a search at:
http://docs.sun.com
3. Apply any patches that are specifically required for the system.
4. Reboot the system.
# reboot
The system will now be able to see, and boot from, the logical drive on which you
installed the Solaris OS.
46Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 61
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:
Chapter 6Installing the Solaris OS on a SPARC System47
Page 62
48Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 63
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.
Instead, see “Creating a Bootable Array on an x64 System” on page 27 or “Creating
a Bootable Array on a SPARC System” on page 33.
This chapter contains the following sections:
■ “Preparing to Install the HBA Driver” on page 49
■ “Installing the Driver on an Existing OS” on page 50
Preparing to Install the HBA Driver
Before you begin, prepare to install the HBA driver by doing the following:
1. Install and connect the HBA and disk drives.
See “Hardware Installation and Removal” on page 9.
Note – For up-to-date operating system version support, visit
http://
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
support.intel.com/support/go/sunraid.htm.
.
49
Page 64
Installing the Driver on an Existing OS
The driver can be installed on various operating systems. This section contains the
following subsections:
■ “To Install the Driver on the Windows OS” on page 50
■ “To Install the Driver on the Red Hat or SUSE Linux OS” on page 50
■ “To Install the Driver on the Solaris OS on an x64 System” on page 51
■ “To Install the Driver on the Solaris OS on a SPARC System” on page 51
■ “To Install the Driver On the VMware Technology” on page 52
▼ To Install the Driver on the Windows OS
1. Start or restart Windows.
The Found New Hardware Wizard opens and searches for the driver.
2. Insert the driver CD.
3. Select the source, and click Next.
4. Click Next, and click Next again.
5. Follow the on-screen instructions to complete the driver installation.
6. Remove the driver CD and restart the computer.
7. To configure and manage the hard disks, see the Sun StorageTek RAID ManagerSoftware User’s Guide at:
▼ To Install the Driver on the Solaris OS on an x64
System
This HBA supports, at a minimum, the Solaris 10 8/07 (s10u4) OS on an x64-based
system. The Solaris 10 8/07 OS requires nothing from the user. However, install the
latest patches from the http://www.sunsolve.sun.com website after installing
the Solaris OS.
To configure and manage the hard disks, see the Sun StorageTek RAID ManagerSoftware User’s Guide at:
This HBA supports, at a minimum, the Solaris 10/08 (s10u6) OS on a SPARC system.
The Solaris 10 8/07 OS requires nothing from the user. However, install the latest
patches from the http://www.sunsolve.sun.com website after installing the
Solaris OS.
To configure and manage the hard disks, see the Sun StorageTek RAID ManagerSoftware User’s Guide at:
■ 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.
■ If you are using an x64 system, you can also use the BIOS utility to create arrays
on the disk enclosure. See “Using the BIOS RAID Configuration Utility” on
page 65.
52Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 67
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.
Some or All CDs Are Not Included in the HBA
Ship Kit
Workaround: You can obtain the latest drivers and software at:
http://
support.intel.com/support/go/sunraid.htm
53
Page 68
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. For more information, see “Best Practices
For Controlling the Boot Order of Logical Drives” on page 87.
Hot-Plug Functionality Does Not Work in the
BIOS Utility
Workaround: 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.
Performance Issues
This section contains the known performance issues:
■ “The System Freezes When a Sun Storage 32GB SLC SATA Solid State Drive (SSD)
is Configured In the HBA” on page 55
■ “Cannot Access the HBA From the GUI Nor Access a LUN From the Host” on
page 55
■ “Data Miscompare With 3.5" SAS Disks” on page 55
54Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 69
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. Upgrade the SSD to firmware version 8850, at minimum.
You can obtain the latest SSD firmware at: http://www.sunsolve.sun.com
4. Power cycle the SSD.
Cannot Access the HBA From the GUI Nor Access
a LUN From the Host
CR 6820225
Workaround: Reboot the host system on which the HBA resides.
Data Miscompare With 3.5" SAS Disks
CR 6822080
Issue: After repeatedly scanning a Seagate SAS Cheetah 15K disk, inconsistent data
is reported, even though nothing has changed on the disk. This is due to an old
firmware version (prior to 0A1C) on the Seagate SAS Cheetah 15K disk, model
ST3450856SS (Sun part number: 390-0424-03).
Workaround: Upgrade the firmware on the Seagate SAS Cheetah 15K disk to version
0A1C, at minimum.
Chapter 8Known Issues55
Page 70
56Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 71
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.
The appendix contains the following sections:
■ “Target Devices” on page 57
■ “Cabling” on page 58
Target Devices
The following rules apply for supported target devices:
■ Internal Enclosures:
■ SAS/SATA backplane
■ SASA/SATA backplane with SES-2 enclosure management support
Note – Enclosure cascading is not supported.
■ SAS/SATA HDDs:
■ Eight direct-attached per HBA (128 HDDs maximum via backplane SAS
expander)
57
Page 72
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. For more information about cabling for these servers, see the server-specific
installation documentation listed in “Related Documentation” on page xii.
■ SAS internal 4-lane cable with SFF-8087 host-side connector
■ Maximum recommended length of 6 meters
■ SATA internal x4 cable with mini-SAS
■ Maximum length of 1 meter
58Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 73
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.
■ Height: 67 mm
■ Length: 167 mm
59
Page 74
Environmental Specifications
Note – With a Battery Backup Unit (BBU), the ambient temperature must not exceed
40 ˚C.
TABLE B-1Environmental Specifications
Ambient temperature without forced airflow0 ˚C to 40 ˚ C
Ambient temperature with forced airflow0 ˚C to 55 ˚ C
Relative humidity10% to 90%, noncondensing
AltitudeUp 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.0 VDC
Performance Specifications
The Serial Attached SCSI [SAS] bus defines these layers:
60Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 75
■ 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. Internal connectors are defined and two data rates are defined:
1.5 Gbps and 3.0 Gbps over a 100 ohm [+ 15 ohm] differential impedance cable.
SAS uses the Serial ATA physical interface, including the connector receptacle and
connector plugs. SAS transmits data using 8B/10B at a maximum level of 1.2 volts
[Tx voltage = 800-1600mV], [Rx voltage = 275-1600mV]. SAS uses big-endian, while
SATA uses little-endian byte ordering. SAS uses a 32 bit CRC. SAS uses LVDS.
Connector Pin Definitions
SAS Pin-Out
Two types of ports are defined: A Narrow Port communicates over a narrow link and
contains only one transmit/receive pair, and a Wide Port communicates over a wide
link and contains more than one transmit/receive pair. The ports reside in the PHY
layer, and the link resides in the physical layer.
TABLE B-2SAS Pin-Out
Signal Name1 Physical Link2 Physical Links3 Physical Links4 Physical Links
Rx 0+S1S1S1S1
Rx 0-S2S2S2S2
Rx 1+N/AS3S3S3
Rx 1-N/AS4S4S4
Rx 2+N/AN/AS5S5
Rx 2-N/AN/AS6S6
Appendix BHBA Specifications61
Page 76
TABLE B-2SAS Pin-Out
Signal Name
(Continued)
1 Physical Link
(Continued)
2 Physical Links
(Continued)
3 Physical Links
(Continued)
4 Physical Links
(Continued)
Rx 3+N/AN/AN/AS7
Rx 3-N/AN/AN/AS8
Tx 3-N/AN/AN/AS9
Tx 3+N/AN/AN/AS10
Tx 2-N/AN/AS11S11
Tx 2+N/AN/AS12S12
Tx 1-N/AS13S13S13
Tx 1+N/AS14S14S14
Tx 0-S15S15S15S15
Tx 0+S16S16S16S16
Signal GroundG1 - G9G1 - G9G1 - G9G1 - G9
Chassis GroundHousingHousingHousingHousing
SATA Pin-Out
The Serial ATA [SATA] bus is defined over two separate connectors, one connector
for the data lines and one for the power lines. A SATA hard drive may also have a
third connector for legacy PATA power connections. The PATA power connector may
be used in instead of the SATA power to supply a connection which is more rugged
and reliable then the SATA-1 power connection.
TABLE B-3SATA Data Pin-Out
Pin #Signal NameSignal Description
1GNDGround
2A+Transmit +
3A-Transmit -
4GNDGround
5B-Receive -
6B+Receive +
7GNDGround
62Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 77
TABLE B-4SATA Power Pin-Out
Pin#Signal NameSignal Description
1V333.3v Power
2V333.3v Power
3V333.3v Power, Pre-charge, 2nd mate
4Ground1st Mate
5Ground2nd Mate
6Ground3rd Mate
7V55v Power, pre-charge, 2nd mate
8V55v Power
9V55v Power
10Ground2nd Mate
11Reserved-
12Ground1st Mate
13V1212v Power, Pre-charge, 2nd mate
14V1212v Power
15V1212v Power
Appendix BHBA Specifications63
Page 78
64Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 79
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 SoftwareUser’s Guide at:
Note – If you are not an advanced user familiar with working in a computer BIOS,
do not use the BIOS RAID Configuration utility tools. Instead, use the Sun
StorageTek RAID Manager graphical user interface.
This appendix contains the following sections:
■ “Introduction to the BIOS RAID Configuration Utility” on page 66
■ “Understanding Hot-Plug Limitations and Conditions Within the BIOS RAID
Configuration Utility” on page 66
■ “Running the BIOS RAID Configuration Utility” on page 68
■ “Using the ACU to Create and Manage Arrays” on page 69
■ “Using the -Select Utility to Modify HBA Settings” on page 73
■ “Using the Disk Utilities to Manage Disk Drives” on page 76
■ “Viewing the BIOS-Based Event Log” on page 78
65
Page 80
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,orSATASelect, for modifying the HBA and disk
drive settings. See “Using the -Select Utility to Modify HBA Settings” on page 73.
■ Disk Utilities—For formatting or verifying disk drives. See “Using the Disk
Utilities to Manage Disk Drives” on page 76.
Understanding Hot-Plug Limitations
and Conditions Within the BIOS RAID
Configuration Utility
Hot-plugging of hard disk enclosures is not supported from within the BIOS RAID
Configuration utility. However, hot-plugging of SAS/SATA hard disk drives (HDDs)
is supported, but only within hard disk enclosures and under the following
conditions:
■ “Hot-Unplug Removal Conditions” on page 66
■ “Hot-Plug Addition Conditions” on page 67
■ “Hot-Unplug and Plug Replacement/Reinsertion Conditions” on page 67
Note – Hot-plugging of hard disk drives is NOT supported during periods when the
controller is busy performing actions on logical drives (building, rebuilding, or
migrating RAID volumes).
Hot-Unplug Removal Conditions
Hot-unplug, removal, of HDDs is supported under the following conditions:
66Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 81
■ 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.
Hot-Plug Addition Conditions
Hot-plug, add, of HDDs is supported under the following conditions:
■ After the hard disk drive is added to the enclosure, you must perform a bus scan
by using the Rescan Drives option from the main menu of the ACU.
■ You must confirm that the Disk Utility reports the correct configuration of the
attached target devices.
Hot-Unplug and Plug Replacement/Reinsertion
Conditions
Hot unplug and plug, replace/reinsert, of HDDs is supported under the following
conditions:
■ The hard disk drive to be removed must not be a part of a logical device (its status
must be ‘available’).
■ If a hard disk drive is to be removed and replaced either into the same slot or a
different unused slot using the same disk drive or a new disk drive, you must
perform a bus scan between the removal and the replacement steps, as follows:
a. Remove the selected hard disk drive.
b. Complete a bus scan by using the Rescan Drives option in the ACU.
c. Confirm that the Disk Utility reports the correct configuration of attached
target devices
d. Replace/reinsert the hard disk (new or same) into the enclosure slot (same or
another unused slot).
e. Complete a bus scan by using the Rescan Drives option in the ACU.
f. Confirm that Disk Utility reports the correct configuration of attached target
devices.
Appendix CUsing the BIOS RAID Configuration Utility67
Page 82
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. If the Sun StorageTek SAS RAID Internal HBA is connected to a RAID
enclosure, power on the enclosure (or enclosures) before you power on the
computer.
2. Start or restart the computer.
3. When prompted, press Ctrl+A.
During boot up, if your system has insufficient memory the following message will
be displayed.
BIOS RAID Configuration Utility will load after system
initialization. Please wait... Or press <Enter> Key to attempt
loading the utility forcibly [Generally, not recommended]
Note – The first time you power on the computer after you install a new HBA, the
BIOS may display a configuration that doesn’t match the system’s configuration. This
is normal behavior.
68Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 83
▼ 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. This section contains the following subsections:
■ “To Start the ACU” on page 70
■ “To Create a New Array With the ACU” on page 70
■ “To Manage Existing Arrays With the ACU” on page 71
■ “To Make an Array Bootable With the ACU” on page 71
■ “To Initialize Disk Drives With the ACU” on page 72
■ “To Rescan Disk Drives With the ACU” on page 72
■ “To Perform a Secure Erase on Disk Drives With the ACU” on page 72
■ “To Stop a Secure Erase in Progress With the ACU” on page 72
Appendix CUsing the BIOS RAID Configuration Utility69
Page 84
▼ 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 Create a New Array With the ACU
Note – You can create an array with the ACU and the Sun StorageTek RAID
Manager graphical user interface (GUI). However, it is a much quicker process to
create an array through the GUI than the ACU. Creating an array with the ACU
might take two to three times longer than creating an array with the GUI. For more
information, see the Sun StorageTek RAID Manager Software User’s Guide.
1. Select Create Arrays from the main ACU menu.
Only disk drives that can be used in a new array are available for selection. (Disk
drives must be initialized before they can be used in an array. See “To Initialize
Disk Drives With the ACU” on page 72 for more information.)
2. Use the Array Properties menu to modify the RAID level, size, name, stripe
size, and caching settings of the array.
Note – For more information about RAID levels and using disk drives to create
arrays, see “Selecting the Best RAID Level” on page 91.
Note – Creating a new array might change the BIOS boot order. Check the BIOS
settings to verify the correct boot order. For more information, see “Best Practices For
Controlling the Boot Order of Logical Drives” on page 87.
70Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 85
▼ 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 Make an Array Bootable With the ACU
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.
1. Select Manage Arrays from the main ACU menu.
2. Select the array that you want to make bootable, then press Ctrl+B.
Note – You cannot make an array bootable while it is building, verifying, or
rebuilding.
The array number changes to Array 00, which makes the array the boot array for
the HBA.
3. Restart the computer.
Appendix CUsing the BIOS RAID Configuration Utility71
Page 86
▼ 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.
▼ To Perform a Secure Erase on Disk Drives With
the ACU
When you perform a secure erase on a disk drive, all data on that disk drive is
completely and irretrievably eradicated. Secure erase performs three distinct writing
passes to the disk drive being erased—it does not just write zeros.
Performing a secure erase takes up to six times longer than clearing (or zeroing) a
disk drive. You may want to perform a secure erase only on disk drives that contain
confidential or classified information.
Note – To erase (or zero) a disk drive with non-classified information, you may
choose to format it (see “Using the Disk Utilities to Manage Disk Drives” on page 76)
instead, or clear it using Sun StorageTek RAID Manager graphical user interface
(GUI)—both options take much less time than the secure erase option.
● Select Secure Erase from the main ACU menu, then select Y (yes).
To return to the main ACU menu once the secure erase has begun, press Esc. The
selected disk drive(s) cannot be used until the erase is complete.
▼ To Stop a Secure Erase in Progress With the ACU
1. From the main ACU window, select Secure Erase.
72Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 87
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. This section contains the following subsections:
■ “To Start Using a -Select Utility” on page 73
■ “To Apply Changes and Exit a -Select Utility” on page 73
■ “To Modify General HBA Settings With a -Select Utility” on page 74
■ “To Modify SAS-Specific HBA Settings With a -Select Utility” on page 75
▼ To Start Using a -Select Utility
1. Start the BIOS RAID Configuration utility (see “To Start the BIOS RAID
Configuration Utility” on page 68), select the -Select utility, and press Enter.
2. Follow the on-screen instructions to modify the settings of the HBA and
connected disk drives, as required.
▼ To Apply Changes and Exit a -Select Utility
1. Press Esc until you are prompted to exit.
If you modified any settings, you are prompted to save the changes before you
exit.
2. Select Yes to exit, then press any key to restart your computer.
Any changes you made take effect after the computer restarts.
Appendix CUsing the BIOS RAID Configuration Utility73
Page 88
▼ 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-1General HBA Settings
OptionDescription
Drive’s Write CacheWhen enabled, write cache is enabled on the disk drive. When
disabled, write cache is not used on the disk drive. It is
recommended that you disable write cache on the disk drive.
Caution - When write cache is enabled, there is a slight possibility
of data loss or corruption during a power failure.
Runtime BIOSWhen enabled, the HBA BIOS allows the HBA to act as a bootable
device. Disabling the BIOS allows another HBA to act as a
bootable device.
Automatic FailoverWhen enabled, the HBA automatically rebuilds an array when a
failed disk drive is replaced. When disabled, the array must be
rebuilt manually.
Array Background
Consistency Check
BBS SupportWhen enabled in systems that support BBS, the HBA is presented
Array-based BBS
Support
Physical Drives
Display During
POST
CD-ROM Boot
Support
When enabled, the HBA constantly verifies a redundant array.
Note that there may be a significant performance reduction.
Default is disabled.
as a bootable device in the BIOS.
When enabled in systems that support BBS, the HBA presents
attached bootable devices up to the BIOS for boot device selection.
This is relevant for logical arrays. Default is disabled.
When enabled, connected disk drives are displayed during system
Power On Self Test (POST). Displaying the disk drives adds a few
seconds to the overall POST time. Default is disabled.
When enabled, the system can be booted from a bootable CD.
Note—CDs are not supported by current software.
74Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 89
TABLE C-1General HBA Settings
Option (Continued)Description (Continued)
Removable Media
Devices Boot
Support
Alarm ControlWhen enabled, the alarm sounds. Default is enabled.
SATA Native
Command Queuing
(NCQ)
When enabled, removable media devices, such as CD drives, are
supported.
Note—When the alarm is turned off (disabled), it will
automatically turn back on after a reboot.
When enabled, NCQ is enabled. Disable this feature if you want
to attach more than 48 SATA II disk drives. Only available with
SATA II disk drives.
▼ To Modify SAS-Specific HBA Settings With a -
Select Utility
In addition to the general settings listed on“To Modify General HBA Settings With a
-Select Utility” on page 74, the Sun StorageTek SAS RAID Internal HBA has SAS-
specific settings that can be modified if required. (For more information about SAS,
see “Introduction to Serial Attached SCSI” on page 103.)
● Select PHY Configuration from the SerialSelect main menu and change the
settings listed in the following table.
Note – Default settings are shown in bold type.
TABLE C-2SAS-Specific HBA Settings
OptionDescription
PHY RateThe data transfer rate between the HBA and devices. The default setting is
Auto, which allows the SAS card to adjust the data transfer rate as
required.
CRC
Checking
SAS
Address
When enabled, determines whether the HBA verifies the accuracy of data
transfer on the serial bus. Default setting is Yes (enabled). Set to No
(disabled) only if the HBA is connected to a device that does not support
CRC Checking.
In a situation where you want each phy on a HBA to be in a different SAS
domain, this setting specifies a unique world-wide name for each phy.
Default is 0.
Note: This setting is for SAS address conflict resolution only and must
otherwise remain at its default value.
Appendix CUsing the BIOS RAID Configuration Utility75
Page 90
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.
This section contains the following subsections:
■ “To Format or Verify a Disk Drive With the Disk Utilities” on page 76
■ “To Locate Disk Drives With the Disk Utilities” on page 76
■ “To Identify Disk Drives With the Disk Utilities” on page 77
▼ To Format or Verify a Disk Drive With the Disk
Utilities
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 Format Disk or Verify Disk Media.
▼ To Locate Disk Drives With the Disk Utilities
Note – This feature is only available with disk drives that have an activity LED.
You can use the Identify Drive feature to physically locate a disk drive by blinking
the LED.
76Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 91
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. Only
physical drives that display during POST are shown.
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.
The Disk Utilities view will provide you with the following information:
TABLE C-3Information Provided by Disk Utilities
LocationModelRev#SpeedSize
CN1=DEV1
Box0=Slot0
Exp0=phy0
The
manufacturer
information.
The revision
number of the
disk drive.
The speed of
the disk drive.
The size of the
disk drive.
The location information of a disk drive is determined by three types of connections:
■ Direct attached drives—The connection is determined by the cable connected
to a device, for example CN1 (connector 1) is connected to DEV1 (device 1).
For more information, see “Direct-Attach Connections” on page 108.
■ Storage Enclosure Processor (SEP) managed devices—The connection is
determined by an active backplane. Box0 (enclosure 0) is connected to slot0
(disk drive slot 0 in the enclosure). For more information, see “Backplane
Connections” on page 108.
Appendix CUsing the BIOS RAID Configuration Utility77
Page 92
■ 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.
Some events are not stored indefinitely—the event log is cleared of any nonpersistent events each time you restart your computer; additionally, once the log is
full, new events overwrite old events.
▼ To View the Event Log
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. When the BIOS RAID Configuration utility menu is displayed, then press
Ctrl+P.
4. Select Controller Log Information, then press Enter.
The current event log opens.
78Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 93
APPENDIX
D
Troubleshooting
This appendix provides basic troubleshooting information and solutions for solving
HBA problems. The appendix contains the following sections:
■ “Troubleshooting Checklist” on page 79
■ “Silencing the Alarm” on page 80
■ “Recovering From a Disk Drive Failure” on page 80
Troubleshooting Checklist
If you encounter difficulties installing or using the Sun StorageTek SAS RAID
Internal HBA, check these items first:
■ With the computer powered off, check the connections to each disk drive, power
supply, LED connector, and so on.
Try disconnecting and reconnecting disk drives from the HBA.
■ Check that the HBA is installed in a compatible expansion slot (x8 PCI Express).
■ Ensure that the HBA is firmly seated and secured in the expansion slot.
■ If the HBA is not detected during system boot, try installing it in a different
compatible expansion slot.
■ Did the driver install correctly?
■ If you have external disk drives (or other devices), are they powered on?
If you are still unable to resolve a problem, you can find additional troubleshooting
information and direction at http://www.sun.com.
79
Page 94
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 there is a disk drive failure in more than one array simultaneously (see “Failure
in Multiple Arrays Simultaneously” on page 81).
■ If it is a RAID 0 array (see “Disk Drive Failure in a RAID 0 Array” on page 81).
■ If multiple disk drives fail within the same array (see “Multiple Failures in the
Same Array” on page 82).
Failed Disk Drive Protected by a Hot-Spare
When an array is protected by a hot-spare, if a disk drive in that array fails the hotspare is automatically incorporated into the array and takes over for the failed drive.
▼ To Recover From a Disk Drive Failure
1. Remove and replace the failed disk drive (following manufacturer’s
instructions).
2. Choose the correct step:
■ If copyback is not enabled—In the Sun StorageTek RAID Manager graphical user
interface (GUI), remove the ‘hot-spare’ designation from the original hot-spare
(the disk drive that was built into the array). Then, designate a new hot-spare to
protect the arrays on that HBA.
80Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 95
■ 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.
If the HBA fails to rebuild the array, check that the cables, disk drives, and HBAs are
properly installed and connected. Then, if necessary, use Sun StorageTek RAID
Manager GUI to rebuild the array. For instructions, refer to the Sun StorageTek RAIDManager Software User’s Guide or online Help.
Failure in Multiple Arrays Simultaneously
If there is a disk drive failure in more than one array at the same time (one failure per
array), and the arrays have hot-spares protecting them, the HBA rebuilds the arrays
with these limitations:
■ A hot-spare must be of equal or greater size than the failed disk drive it’s
replacing.
■ Failed disk drives are replaced with hot-spares in the order in which they failed.
(The array that includes the disk drive that failed first is rebuilt first, assuming an
appropriate hot-spare is available—see bullet above.)
If there are more disk drive failures than hot-spares, see “Failed Disk Drive Not
Protected by a Hot-Spare” on page 81.
If copyback is enabled, data is moved back to its original location once the HBA
detects that the failed drive has been replaced.
Disk Drive Failure in a RAID 0 Array
Because RAID 0 volumes do not include redundancy, if a disk drive fails in a RAID 0
array, the data can’t be recovered.
Correct the cause of the failure or replace the failed disk drives. Then, restore your
data (if available).
Appendix DTroubleshooting81
Page 96
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. For more information, refer to the
Sun StorageTek RAID Manager Software User’s Guide or online Help.
82Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 97
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. The appendix contains the
following sections:
■ “Best Practices For Placing a New HBA in a System Running the Solaris OS” on
page 83
■ “Best Practices For Switching Cables and Making New Connections” on page 84
■ “Best Practices For Cabling to Disk Enclosures” on page 85
■ “Best Practices For Testing Hard Drive Failure Conditions” on page 85
■ “Best Practices For Deleting Logical Volumes Without Deleting Partitions” on
page 86
■ “Best Practices For Testing Physical Drive Failures” on page 86
■ “Best Practices For Rescanning or Discovering Drives” on page 87
■ “Best Practices For Controlling the Boot Order of Logical Drives” on page 87
■ “Best Practices For Selecting Members of RAID Logical Devices” on page 88
■ “Best Practices For Replacing an HBA” on page 88
Best Practices For Placing a New HBA in
a System Running the Solaris OS
If you install a new HBA into a system that is running the Solaris OS, the system
might not detect the newly installed HBA.
To confirm whether the system has detected the HBA, do the following:
83
Page 98
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.
■ If the output displays 0 adapters, run the /usr/sbin/devfsadm command to
force the system to detect the HBA, and then continue to the next step.
3. Repeat Step 1 to confirm that the system has detected the HBA.
Best Practices For Switching Cables and
Making New Connections
This section contains the following topics:
■ “Switching a Cable From One Port To the Other” on page 84
■ “Pulling a Cable and Reconnecting It To the Same Port” on page 85
■ “Connecting a JBOD With SATA Disks” on page 85
Switching a Cable From One Port To the Other
If you need to switch a cable from one port to the other port on the same HBA or on
the same JBOD, wait long enough after the initial cable pull for all the physical hard
drives to be removed from the displays of the graphical user interface (GUI) and
command-line interface (CLI). Waiting after the initial pull prevents the controller
from trying to remove drives at the same time as it is re-adding those same drives on
the other port. If no display is available, wait at least two minutes between pulling
the cable and reconnecting it to the other port.
84Sun StorageTek SAS RAID HBA Installation Guide • March 2010
Page 99
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. An affiliation is used by the SAS protocol to prevent
multiple SAS initiators (HBAs) from walking on each other when communicating
with SATA drives. To avoid these connection problems, remove the affiliation by
power cycling the JBOD prior to connecting the JBOD to the new HBA.
Best Practices For Cabling to Disk
Enclosures
The HBA supports using a single connection, or path, between a RAID card and a
JBOD. Therefore, when connecting a RAID card to a disk enclosure, be sure to use
only one cable. Using more than one cable does NOT provide redundancy.
Best Practices For Testing Hard Drive
Failure Conditions
When hot-plugging hard drives to test failure conditions, wait at least one minute
between removing the drive and re-inserting it. Waiting one minute gives the
controller time to recognize the removal of the hard drive. In a true failure situation,
a removed drive is replaced with a different hard drive. In testing situations where
the same drive is re-inserted, a one-minute waiting period before re-insertion is
required.
Appendix EBest Practices85
Page 100
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.
If you need to remove a logical volume without first deleting partitions from the OS,
you can do so by using the arcconf command-line interface (CLI) instead of the
GUI. The CLI allows the deletion of logical volumes without requiring the removal of
partitions first.
To delete a logical volume through the CLI without deleting partitions, type the
following at the command prompt:
You will receive a warning message, as shown in the following example.
WARNING: Logical device z may contain a partition.
All data in logical device z will be lost.
Delete the logical device?
Press y, then ENTER to continue or press ENTER to abort:
Best Practices For Testing Physical Drive
Failures
If, for testing purposes, you use the Sun StorageTek RAID Manager GUI to fail a
physical drive, the drive will not return to a ready state without you replacing the
drive. In a test scenario, you may not need to physically replace the drive as you are
only performing a test.
In this scenario, you can use the arcconf CLI to return the drive to its ready state
without actually having to replace the drive.
To do so, type the following at the command prompt: