Server Administrator Storage Management User’s Guide
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed. ____________________ Information in this publication is subject to change without notice. © 2012 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . What’s New in this Release? . . . . . . . . . . . . . . Before Installing Storage Management . . . . . . . . . Version Requirements for Controller Firmware and Drivers . . . . . . . . . . . . . . . . . . . 21 22 . . 22 Supported Controllers . . . . . . . . . . . . . . . . . . 23 Supported Enclosures . . . . . . . . . . . . . . . . . . 24 . . . . . . 24 . . . . . . . . . . . . . . . . . . . .
Common Storage Tasks 3 . . . . . . . . . . . . . . . . . Understanding RAID Concepts What Is RAID? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 . . . . . . . . . . . . . . . . . . . . 33 Organizing Data Storage for Availability and Performance . . . . . . . . . . . . . . . . . . . . . Choosing RAID Levels and Concatenation Concatenation 34 . . . . . . . . . . . . . . . . . . . 35 . . . . . . . . . . . . . . . RAID Level 1 (Mirroring) .
Storage Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 . . . . . . . . . . . . . . . . . . . . . . 54 Hot Spare Protection Policy . Select Report. Storage Component Severity . . . . . . . . . . . . . . Alerts or Events 54 . . . . . . . . 55 . . . . . . . . . . . . . . . . . . . . . 56 Storage Properties and Current Activity Monitoring Disk Reliability on RAID Controllers Using Alarms to Detect Failures . . . . . 56 . . . . . . . . . . . .
Export Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 . . . . . . . . . . . . . . . . . . . . . 64 PCIe SSD Sub System Health Backplanes Backplane Firmware Version . 6 . . . . . . . . . . . 64 . . . . . . . . . . . . . 65 . . . . . . . . . . . . . . . . . . . 65 . . . . . . . . . . . . . . . . . . . . . . . 65 Storage Information and Global Tasks . . . . . . . . . Storage Properties . Global Tasks Global Rescan . . . . . . . . . . . . . . . . . . . .
Disk Cache Policy. . . . . . . . . . . . . . . . . . . . . . 78 . . . . . . . . . . . . 79 . . . . . . . . . . . . . . . 79 Background Initialization on PERC Controllers . Non-RAID Controller Description Firmware/Driver Versions . . . . . . . . . . . . . 80 . . . . . . . . . . . . . . . . . . . . 82 Firmware/Driver Properties Controller Health . Controller Severity . . . . . . . . . . . . . . . . . Controller Information . . . . . . . . . . . . . . . Controller Components . . . . . . . . .
Set Reconstruct Rate . . . . . . . . . . . . . . . . . . Redundant Path Configuration . . . . . . . . . . . . . . . . . . . . 115 115 Set Patrol Read Mode . . . . . . . . . . . . . . . . . Start and Stop Patrol Read . . . . . . . . . . . . . . . 117 . . . . . . . . . . . . . 118 Manage Physical Disk Power . . . . . . . . . . . . . 119 . . . . . . . . . . . . . . . 123 . . . . . . . . . . . . 123 . . . . . . . . . . . . . . . . 124 . . . . . . . . . . . . . . . . . .
Physical Disk Firmware Version Report. 8 Enclosures and Backplanes 132 . . . . . . . . . . . . . . . . . 135 Backplanes . . . . . . . . . . . . . . . . . . . . . . . 135 Enclosures . . . . . . . . . . . . . . . . . . . . . . . . 135 . . . . . . . . . . . . . 136 . . . . . . . . . . . . . . . . . . . 136 Enclosure Physical Disks . Enclosure Fans Enclosure Power Supplies . . . . . . . . . . . . . Enclosure Temperature Probes . . . . . . . . . . Enclosure Management Modules (EMMs) .
Fan Properties . . . . . . . . . . . . . . . . . . . . . Power Supply Properties . . . . . . . . . . . . . . . Temperature Probe Properties and Tasks . . . . . . . Temperature Probe Properties and Tasks . . . . Set Temperature Probe Properties and Tasks 9 Connectors . 157 . . . . . . . . . . . . . . . . . . . . . . 161 Connector Health. . . . . 161 . . . . . 161 . . . . . . . . . . . . . . . . . . . 163 Connector Status . . . . . . . . . . . . . . . . . Connector Information . . . .
RAID Controller Batteries Battery Properties and Tasks . . . . . . . . . . . . . . 171 171 . . . . . . . . . . . . . . . . . . . 173 12 Physical Disks or Physical Devices . Guidelines to Replace a Physical Disk or Physical Device . . . . . . . . . . . . . . Add a New Disk to Your System . 177 177 . . . . . . . . . . . . 178 . . . . . . . . 179 . . . . . . . . . 179 . . . . . . . . . . . . . . . . . 180 Replacing a Physical Disk Receiving SMART Alerts . . . . . . . . . . . . .
Clear Physical Disk and Cancel Clear . . . . . . . . . 192 Revertible Hot Spare . . . . . . . . . . . . . . . . . . 193 Instant Encrypt Erase. . . . . . . . . . . . . . . . . . 194 . . . . . . . . . . . . . . . . . . . 195 Full Initialization . . . . . . . . . . . . . 196 . . . . . . . . . . . . . . . 196 . . . . . . . . . . . . . . . . . . . . . 197 Convert to RAID Capable Disk . Convert to Non-RAID Disk 13 Virtual Disks . Considerations Before Creating Virtual Disks . . . .
What is a Virtual Disk Bad Block? Recommendations . . . . . . . . . 208 . . . . . . . . . . . . . . . . . 210 Virtual Disk Properties and Tasks . . . . . . . . . . . . 210 . . . . . . . . . . . . . . . 210 . . . . . . . . . . . . . . . . . 214 Virtual Disk Properties Virtual Disk Tasks . Create Virtual Disk Express Wizard . . . . . . . . . . . . . . . . . 221 . . . . . . . . . 222 Create Virtual Disk Express Wizard (Step 2) Create Virtual Disk Advanced Wizard .
Assign and Unassign Dedicated Hot Spare . . . . . . 240 Virtual Disk Task: Replace Member Disk (Step 1 of 2) . . . . . . . . . . . . . . . . . . . . . . . 241 Virtual Disk Task: Replace Member Disk (Step 2 of 2) . . . . . . . . . . . . . . . . . . . . . . . 243 14 Moving Physical and Virtual Disks from One System to Another . . . . . Required Conditions . . . . 245 . . . . . . . . . . . . . . . . . . 245 . . . 246 . . . . . 247 . . . . . . . . . . . . . .
Size Requirements for Global Hot Spares on S100, and S300 Controllers . . . . . . . . . . Global Hot Spare Considerations on a SAS 6/iR 16 CacheCade Using Solid State Drives . . . . . . . . . . . . . . . . . . 17 Troubleshooting . . . . 252 . . . . 252 . . . . . . . . 255 . . . . . . . . . . . . . . . . . . 257 Common Troubleshooting Procedures . . . . . . . . . 257 . . . . . . . . . . . . . 257 System Requirements. . . . . . . . . . . . . . . . 258 Drivers and Firmware . . . . . . . . .
Specific Problem Situations and Solutions . Physical Disk is Offline or Displays an Error Status . . . . . . . . . . . . . . . . . . . 265 . . . . . . 266 Receive a “Bad Block” Alert with “Replacement,” “Sense,” or “Medium” Error . . . . . . . . . . . . . . . . . . . . . . . . 266 Read and Write Operations Experience Problems . . . . . . . . . . . . . . . . . . . . . 267 . . . . . .
How Can I Safely Remove or Replace a Physical Disk? . . . . . . . . . . . . . . How do I Recover from Removing the Wrong Physical Disk? . . . . . . . . . . . . . . . . . . . . . . 274 . . . . . . 274 . . . . . . . . . . . . . 274 . . . . . . . . . . . . . . 275 How do I Identify the Firmware Version that is installed? . . . . . . . . . . . . . . . . . Which Controllers do I Have? . How do I Turn off an Alarm? . Which RAID level is Best for me? . A Supported Features . . . . . . . . . . . . . .
Virtual Disk Specifications Supported RAID Levels . . . . . . . . . . . . . 297 . . . . . . . . . . . . . 299 Read, Write, Cache and Disk Cache Policy. Enclosure Support . . . 300 . . . . . . . . . . . . . . . . 301 Supported Features on the SAS 5/iR, SAS 6/iR, and PERC H200 Controllers . . . . . . . . . . . . . . 301 . . . . . . . . . . . . . . . . . 302 . . . . . . . . . . . . . . . . . . . 303 Controller Tasks . Battery Tasks Connector Tasks . . . . . . . . . . . . . . . . .
Enclosure and Backplane Features . . . . . . . . . . . 318 Enclosure and Backplane Tasks . . . . . . . . . . 319 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Maximum Supported Configuration . 319 . . . . . . . . . . 19 Determining the Health Status for Storage Components . . . . . . . . . . . . . . . 321 Health Status Rollup: Battery is Charging or Dead . . . . . . . . . . . . . . . . . . . . . . . . . .
Health Status Rollup: One Enclosure EMM is Failed . . . . . . . . . . . . . . . . . . . . . . . . . . Health Status Rollup: One Enclosure Temperature Probe is Failed . . . . . . . . . . . . . . . . . . . . . Health Status Rollup: Lost Both Power Connections to the Enclosure . . . . . . . . . . . . . . . . . . . 20 Contents 327 328 . 328 Health Status Rollup: One or More Physical Disks are Failed . . . . . . . . . . . . . . . . . . . . . . . .
1 Overview Server Administrator Storage Management provides enhanced features for configuring a system's locally-attached RAID and non-RAID disk storage. Storage Management enables you to perform controller and enclosure functions for all supported RAID and non-RAID controllers and enclosures from a single graphical or command-line interface without requiring use of the controller BIOS utilities. The graphical interface is wizard-driven with features for novice and advanced users.
• Added support for mapping Enhanced Error Message Initiative (EEMI) messages. • Added support for debranding.
Supported Controllers This release of Storage Management supports the following controllers. The firmware and drivers listed in the Server Administrator Readme refer to the minimum supported version for these controllers. Later versions of the firmware and drivers are also supported. For the most recent driver and firmware requirements, contact your service provider. Supported RAID Controllers Storage Management supports the following RAID controllers.
• SAS 5/i Integrated • SAS 5/E • SAS 6Gbps Adapter Supported Enclosures This release of Storage Management supports the following enclosures: • 20xS and 21xS storage systems • 220S and 221S storage systems • MD1000 and MD1120 storage system • MD1200 and MD1220 storage system Support for Disk and Volume Management Storage Management does not provide disk and volume management.
2 Getting Started Server Administrator Storage Management is designed for system administrators who implement hardware RAID solutions and understand corporate and small business storage environments. Storage Management enables you to configure the storage components attached to your system. These components include RAID and non-RAID controllers and the channels, ports, enclosures, and disks attached to them.
Launching Storage Management Storage Management is installed as a Server Administrator service. All Storage Management features are accessible by selecting the Storage object in the Server Administrator tree view. For more information on starting Server Administrator, see the Server Administrator User’s Guide.
Administrator privileges are required to access all Storage Management features. Administrator privilege allows you to execute the drop-down menu tasks, launch wizards, and use the omconfig storage command line interface commands. Without Administrator privileges, you cannot manage and configure the storage component. User and Power User privileges allow you to view storage status, but not manage or configure storage.
the tree view and then select the Information/Configuration subtab. The Information/Configuration subtabs have task drop-down menus or buttons for launching a task. Using the Storage Management Command Line Interface Storage Management has a fully-featured command line interface (CLI). For more information, see the Server Administrator Command Line Interface User’s Guide. Displaying the Online Help Storage Management provides extensive online help.
• – Create Virtual Disk Express Wizard—This sub-section describes using the Express Wizard to create a virtual disk. Using the Express Wizard is the quickest method for creating a virtual disk. The Express Wizard is appropriate for novice users. – Create Virtual Disk Advanced Wizard—This sub-section describes using the Advanced Wizard to create a virtual disk. The Advanced Wizard requires a good knowledge of RAID levels and hardware and is appropriate for advanced users.
Getting Started
Understanding RAID Concepts 3 Storage Management uses Redundant Array of Independent Disks (RAID) technology to provide Storage Management capability. Understanding Storage Management requires an understanding of RAID concepts, as well as some familiarity with how your system’s RAID controllers and operating system view disk space. This sub-section describes basic storage concepts including What Is RAID?, Organizing Data Storage for Availability and Performance, and Choosing RAID Levels and Concatenation.
the RAID levels. For this reason, using software RAID by itself can slow system performance. You can, however, use software RAID on top of hardware RAID volumes to provide better performance and variety in the configuration of RAID volumes. For example, you can mirror a pair of hardware RAID 5 volumes across two RAID controllers to provide RAID controller redundancy. RAID Concepts RAID uses particular techniques for writing data to disks.
• Stripe element size—The amount of disk space consumed by a stripe element. For example, consider a stripe that contains 64KB of disk space and has 16KB of data residing on each disk in the stripe. In this case, the stripe element size is 16KB and the stripe size is 64KB. • Parity—Parity refers to redundant data that is maintained using an algorithm in combination with striping. When one of the striped disks fails, the data can be reconstructed from the parity information using the algorithm.
fault-tolerance is achieved by maintaining redundant data. Redundant data includes mirrors (duplicate data) and parity information (reconstructing data using an algorithm). • Performance—Read and write performance can be increased or decreased depending on the RAID level you choose. Some RAID levels may be more appropriate for particular applications. • Cost efficiency—Maintaining the redundant data or parity information associated with RAID volumes requires additional disk space.
• RAID Level 5 (Striping with distributed parity) • RAID Level 6 (Striping with additional distributed parity) • RAID Level 50 (Striping over RAID 5 sets) • RAID Level 60 (Striping over RAID 6 sets) • RAID Level 10 (Striping over mirror sets) • RAID Level 1-Concatenated (Concatenated mirror) • Comparing RAID Level and Concatenation Performance • No-RAID Concatenation In Storage Management, concatenation refers to storing data on either one physical disk or on disk space that spans multiple p
Figure 3-1. Concatenating Disks • Concatenates n disks as one large virtual disk with a capacity of n disks. • Data fills up the first disk before it is written to the second disk. • No redundancy data is kept. When a disk fails, the large virtual disk fails. • No performance gain. • No redundancy.
Figure 3-2. Striping Disks RAID 0 Characteristics: • Groups n disks as one large virtual disk with a capacity of (smallest disk size)*n disks. • Data is stored to the disks alternately. • No redundancy data is kept. When a disk fails, the large virtual disk fails with no means of rebuilding the data. • Better read and write performance.
RAID Level 1 (Mirroring) RAID 1 is the simplest form of maintaining redundant data. In RAID 1, data is mirrored or duplicated on one or more physical disks. If a physical disk on one side of the mirror fails, then the data can be rebuilt using the physical disk on the other side of the mirror. Figure 3-3. Mirroring Disks RAID 1 Characteristics: 38 • Groups n + n disks as one virtual disk with the capacity of n disks.
Related Information: • Organizing Data Storage for Availability and Performance • Comparing RAID Level and Concatenation Performance • Controller-supported RAID Levels • Number of Physical Disks per Virtual Disk • Maximum Number of Virtual Disks per Controller RAID Level 5 (Striping with distributed parity) RAID 5 provides data redundancy by using data striping in combination with parity information.
• When a disk fails, the virtual disk still works, but it is operating in a degraded state. The data is reconstructed from the surviving disks. • Better read performance, but slower write performance. • Redundancy for protection of data.
Figure 3-5. RAID 6 RAID 6 Characteristics: • Groups n disks as one large virtual disk with a capacity of (n-2) disks. • Redundant information (parity) is alternately stored on all disks. • The virtual disk remains functional with up to two disk failures. The data is reconstructed from the surviving disks. • Better read performance, but slower write performance. • Increased redundancy for protection of data. • Two disks per span are required for parity.
• Number of Physical Disks per Virtual Disk • Maximum Number of Virtual Disks per Controller RAID Level 50 (Striping over RAID 5 sets) RAID 50 is striping over more than one span of physical disks. For example, a RAID 5 disk group that is implemented with three physical disks and then continues on with a disk group of three more physical disks would be a RAID 50. It is possible to implement RAID 50 even when the hardware does not directly support it.
Figure 3-6. RAID 50 RAID 50 Characteristics: • Groups n*s disks as one large virtual disk with a capacity of s*(n-1) disks, where s is the number of spans and n is the number of disks within each span. • Redundant information (parity) is alternately stored on all disks of each RAID 5 span. • Better read performance, but slower write performance. • Requires as much parity information as standard RAID 5. • Data is striped across all spans. RAID 50 is more expensive in terms of disk space.
Related Information: • Organizing Data Storage for Availability and Performance • Comparing RAID Level and Concatenation Performance • Controller-supported RAID Levels • Number of Physical Disks per Virtual Disk • Maximum Number of Virtual Disks per Controller RAID Level 60 (Striping over RAID 6 sets) RAID 60 is striping over more than one span of physical disks that are configured as a RAID 6.
Figure 3-7. RAID 60 RAID 60 Characteristics: • Groups n*s disks as one large virtual disk with a capacity of s*(n-2) disks, where s is the number of spans and n is the number of disks within each span. • Redundant information (parity) is alternately stored on all disks of each RAID 6 span. • Better read performance, but slower write performance. • Increased redundancy provides greater data protection than a RAID 50. • Requires proportionally as much parity information as RAID 6.
• Two disks per span are required for parity. RAID 60 is more expensive in terms of disk space. Related Information: • Organizing Data Storage for Availability and Performance • Comparing RAID Level and Concatenation Performance • Controller-supported RAID Levels • Number of Physical Disks per Virtual Disk • Maximum Number of Virtual Disks per Controller RAID Level 10 (Striping over mirror sets) The RAB considers RAID Level 10 to be an implementation of RAID level 1.
Figure 3-8. Striping Over Mirrored Disk Groups RAID 10 Characteristics: • Groups n disks as one large virtual disk with a capacity of (n/2) disks, where n is an even integer. • Mirror images of the data are striped across sets of physical disks. This level provides redundancy through mirroring. • When a disk fails, the virtual disk still works. The data is read from the surviving mirrored disk. • Improved read performance and write performance. • Redundancy for protection of data.
• Comparing RAID Level and Concatenation Performance • Controller-supported RAID Levels • Number of Physical Disks per Virtual Disk • Maximum Number of Virtual Disks per Controller RAID Level 1-Concatenated (Concatenated mirror) RAID 1-concatenated is a RAID 1 disk group that spans across more than a single pair of physical disks. This combines the advantages of concatenation with the redundancy of RAID 1. No striping is involved in this RAID type.
• Number of Physical Disks per Virtual Disk • Maximum Number of Virtual Disks per Controller Comparing RAID Level and Concatenation Performance The following table compares the performance characteristics associated with the more common RAID levels. This table provides general guidelines for choosing a RAID level. Evaluate your specific environment requirements before choosing a RAID level. NOTE: The following table does not show all RAID levels supported by Storage Management.
Table 3-1. RAID Level and Concatenation Performance Comparison (continued) Suggested Uses RAID Level Data Read Write Rebuild Minimum Availability Performance Performance Performance Disks Required RAID 5 Good Sequential Fair, unless Fair reads: good.
No-RAID In Storage Management, a virtual disk of unknown metadata is considered a No- RAID volume. Storage Management does not support this type of virtual disks. These must either be deleted or the physical disk must be removed. Storage Management allows Delete and Rename operation on No-RAID volumes.
Understanding RAID Concepts
4 Quick Access to Storage Status and Tasks This section describes various methods to determine the status or health of your system’s storage components and how to quickly launch available controller tasks. Storage Dashboard and Storage Health For each controller, the Storage Health tab or Storage Dashboard displays a summary of the controller severity (health or status) and a task menu for launching the controller tasks. A link is provided to access virtual disk status and tasks.
• Click the virtual disk that is in degraded state to display the Physical Disk Properties page. NOTE: The virtual disk link is displayed only if the physical disks that are part of the virtual disk, are in a Warning or Critical state. For more information on how the status of lower-level components is rolled up into the status displayed for the controller, see Determining the Health Status for Storage Components.
Table 4-1. Component Severity Severity Component Status Normal/OK—The component is working as expected. Warning/Non-critical—A probe or other monitoring device has detected a reading for the component that is above or below the acceptable level. The component may still be functioning, but it could fail. The component may also be functioning in an impaired state. Data loss is possible. Critical/Failure/Error—The component has either failed or failure is imminent.
• Temperature Probe Properties and Tasks • Virtual Disk Properties and Tasks Alerts or Events Storage activity generates alerts or events that are displayed in the Alert Log. Some alerts indicate normal activity and are displayed for informational purposes only. Other alerts indicate abnormal activity which should be addressed immediately. For more information about alerts and their corrective actions, see the Server Administrator Messages Reference Guide.
Using Enclosure Temperature Probes Physical disk enclosures have temperature probes that warn you when the enclosure has exceeded an acceptable temperature range.
Related Information: • Time Delay in Displaying Configuration Changes Time Delay in Displaying Configuration Changes When you change the storage configuration, Storage Management quickly generates SNMP traps in response to the configuration changes. The Storage Management MIB (Management Information Base) is also updated to reflect storage configuration changes. However, it may take up to five minutes to update the MIB with the most recent storage configuration.
PCI Express Solid-State Device Support 5 This section gives an overview of the Storage Management (OMSM) device management support for Peripheral Component Interconnect Express (PCIe) Solid-State Drive (SSD) and its associated devices like the backplane and extender card. In OMSS, PCIe SSD appears under the storage management. OMSM reports the PCIe SSD devices and its various properties. NOTE: OMSM does not support RAID management or configuration on PCIe SSD sub systems.
PCIe Sub System Properties The PCIe SSD sub system comprises of the following components: • Backplane • Extender Card • PCIe Solid State Device Table 5-1 lists the PCIe Sub System Properties. Table 5-1. PCIe Sub System Properties Properties Description ID This property displays the Sub System ID assigned to the PCIe sub system by Storage Management. Storage Management numbers the controllers and PCIe sub systems attached to the system starting with zero.
PCIe Extender Cards The PCIe Extender Card is attached to the backplane of the system and provides PCIe connectivity for upto four PCIe SSD devices at the front of the chassis. NOTE: The PCIe Extender Card does not have any properties or tasks. Table 5-2 lists the PCIe Extender Card Properties. Table 5-2. PCIe Extender Card Properties Properties Description Name This property displays the name of the Extender Card. State This property displays the current status of the Extender Card.
Table 5-3. Physical Device Properties Properties Description Read Only Displays if the PCIe SSD is write-protected. Possible values are: Yes and No. Driver Version Displays the version of the driver that is currently installed on the sub system. NOTE: On some sub systems, Storage Management may not be able to obtain the driver version. In this case, Storage Management displays Not Applicable. Device Life Remaining Displays the warranted wearout level of the PCIe SSD (in percentage).
• Prepare to Remove • Export Log To run a physical device task: 1 Expand the Storage tree object to display the storage component objects. 2 Expand the PCIe-SSD SubSystem object. 3 Expand the Connector object. 4 Expand the Enclosure (Backplane) object. 5 Select the Physical Devices object. 6 Select a task from the Available Tasks drop-down menu. 7 Click Execute. Blink and Unblink The Blink task allows you to find a device within a system by blinking one of the LEDs on the device.
CAUTION: The identify LED pattern (blink operation) is the same LED pattern as safe to remove. When you initiate a prepare to remove operation, ensure that your PCIe SSD is no longer accessible by the system before you physically remove the PCIe SSD. CAUTION: To prevent data loss, it is mandatory that you use the Prepare to Remove task before physically removing a device. Use the Prepare to Remove task to safely remove a PCIe SSD from the system. This task causes the status LEDs on the device to blink.
Storage Information and Global Tasks 6 Use this window to view high-level information about your system’s storage. This window also enables you to launch global tasks that affect all controllers attached to the system. Storage Properties The Storage tree-view object has the following properties. Table 6-1. Storage Properties Property Definition Status These icons represent the severity or health of the storage component. For more information, see Storage Component Severity.
Global Tasks: • Global Rescan • Enable/Disable Smart Thermal Shutdown • Setting Hot Spare Protection Policy Global Rescan A global rescan updates configuration changes (such as new or removed devices) for all SCSI controllers and their attached components. For information on when you may want to do a rescan, see Rescan to Update Storage Configuration Changes. NOTE: Global Rescan is not supported on non-RAID controllers.
To enable or disable thermal shut down: 1 Select the Storage tree view object. 2 Click the Information/Configuration subtab. 3 From the Global Tasks drop-down menu, select Enable Smart Thermal Shutdown or Disable Smart Thermal Shutdown. Depending on the option that is currently selected, the Available Tasks drop-down menu displays only one of these tasks at a time. 4 Click Execute. Storage Controllers The information displayed for each controller can vary depending on the controller characteristics.
Table 6-2. Controller Properties Property Definition Status This property displays the controller status. ID This property displays the controller ID as reported by the omreport CLI command. Name This property displays the name of the controller. For more detailed information on a controller, click its name. Slot ID This property displays the slot to which the controller is attached. On some controllers, Storage Management is unable to display the slot ID.
Property Definition Minimum Required This property displays the minimum firmware version that Firmware Version is required by Storage Management. This property is only displayed if the controller firmware does not meet the minimum requirement. The firmware and drivers listed in the Server Administrator Readme refer to the minimum supported version for these controllers. Later versions of the firmware and drivers are also supported.
Property Definition SCSI Initiator ID This property displays the SCSI ID of a SCSI controller. The default value is 7. You can change the default value in the BIOS. Controllers in a cluster configuration should not have duplicate SCSI Initiator IDs. For a list of acceptable SCSI Initiator ID values, refer to SCSI documentation. On some controllers, this property is not available. In this case, this property displays as Not Applicable.
7 Controllers This section describes the controllers supported by Storage Management as well as the different controller features. What is a Controller? Most operating systems do not read and write data directly from the disks, but instead send read and write instructions to a controller. The controller is the hardware in your system that interacts directly with the disks to write and retrieve data.
RAID Controller Technology: SCSI, SATA, ATA, and SAS Storage Management supports RAID controllers using SCSI, SATA, ATA, and SAS technology. This section indicates which technology the supported RAID controllers use. For more information on these controllers, see Supported Features and the controller hardware documentation. SAS RAID Controllers The following RAID controllers use Serial Attached SCSI (SAS) technology.
The following describes some of the RAID controller features and provides links to a more detailed explanation. For information on which controllers support which features, see Supported Features. • Hot spares—On RAID controllers, a hot spare is a backup for a disk that fails. See the Protecting Your Virtual Disk with a Hot Spare. • Rebuilding data. You can rebuild data from a failed physical disk if the disk is a member of a redundant virtual disk. See Rebuilding Redundant Information.
Controller-supported RAID Levels RAID controllers support different RAID levels. For information on which RAID levels a controller supports, see the supported RAID levels section for the controller in Supported Features. Controller-supported Stripe Sizes When creating a virtual disk, you must specify the stripe size for the virtual disk. Different controllers have different limitations on the stripe sizes they can support.
• Read Cache Enabled—When the read cache is enabled, the controller reads the cache information to see if the requested data is available in the cache before retrieving the data from the disk. Reading the cache information first can provide faster read performance because the data (if available in the cache) can more quickly be retrieved from the cache than from the disk. • Read Cache Disabled—When the read cache is disabled, the controller retrieves data directly from the disk and not from the cache.
Write Policy Does my controller support this feature? See Supported Features The write policies specify whether the controller sends a write-request completion signal as soon as the data is in the cache or after it has been written to disk. • Write-Back—When using write-back caching, the controller sends a write-request completion signal as soon as the data is in the controller cache but has not yet been written to disk.
• Write-Through—When using write-through caching, the controller sends a write-request completion signal only after the data is written to the disk. Write-through caching provides better data security than write-back caching, since the system assumes the data is available only after it has been safely written to the disk. NOTE: Write-through is the default write policy setting when cluster mode is enabled.
• Direct I/O—Specifies that reads are not buffered in cache memory. When using direct I/O, data is transferred to the controller cache and the host system simultaneously during a read request. If a subsequent read request requires data from the same data block, it can be read directly from the controller cache. The direct I/O setting does not override the cache policy settings. Direct I/O is also the default setting. NOTE: Cache policy is not supported on any controller that does not have a battery.
The background initialization process helps the controller identify and correct problems that may occur with the redundant data at a later time. In this regard, the background initialization process is similar to a check consistency. The background initialization should be allowed to run to completion. If cancelled, the background initialization automatically restarts within 0 to 5 minutes. Some processes such as read and write operations are possible while the background initialization is running.
Firmware/Driver Properties The firmware and driver properties can vary depending on the model of the controller. On some controllers, Storage Management may not be able to obtain the driver or firmware version. In this case, Storage Management displays Not Applicable.
Table 7-1. Firmware and Driver Properties Property Definition Firmware Version This property displays the version of the firmware that is currently installed on the controller. NOTE: On some controllers, Storage Management may not be able to obtain the firmware version. In this case, Storage Management displays Not Applicable. Minimum This property displays the minimum firmware version that is Required required by Storage Management.
Property Definition Minimum This property displays the minimum storport driver version Required Storport required by Storage Management. This property is displayed if Driver Version the operating system storport driver does not meet the minimum requirement. This is applicable for Windows operating system only. NOTE: To download the latest storport driver, see the Microsoft Knowledge Base article 943545 at support.microsoft.com.
Table 7-2. Component Severity Severity Component Status Normal/OK. The component is working as expected. Warning/Non-critical. A probe or other monitoring device has detected a reading for the component that is above or below the acceptable level. The component may still be functioning, but it could fail. The component may also be functioning in an impaired state. Data loss is possible. Critical/Failure/Error. The component has either failed or failure is imminent.
Controller Properties and Tasks Use this window to view information about the controller and execute controller tasks. Controller Properties The controller properties can vary depending on the model of the controller. Controller properties may include: Table 7-3. Controller Properties Property Definition Status These icons represent the severity or health of the storage component. For more information, see Storage Component Severity.
Property Definition Firmware Version This property displays the version of the firmware that is currently installed on the controller. NOTE: On some controllers, Storage Management may not be able to obtain the firmware version. In this case, Storage Management displays Not Applicable. Minimum Required This property displays the minimum firmware version that is Firmware Version required by Storage Management.
Property Definition Rebuild Rate The rebuild rate is the percentage of the system’s resources dedicated to rebuilding a failed disk when a rebuild is necessary. For more information, see Set Rebuild Rate. NOTE: Revertible Hot Spare operation has the same rebuild rate that you set here. BGI Rate The background initialization (BGI) rate is the percentage of the system’s resources dedicated to performing the background initialization of a virtual disk after it is created.
Property Definition Auto replace member In case of predictive failure, this property enables the on predictive failure automatic copying of data from a physical disk to a hot spare. Use this property in conjunction with the Allow Revertible Hot Spare and Replace Member property. Redundant path view Indicates whether Storage Management has detected a redundant path configuration.
Property Definition Patrol Read State This property displays the current state of the Patrol Read process. Possible values are: Ready—The Patrol Read process is enabled and runs when next scheduled or when manually initiated. Active—The Patrol Read process is currently running. Stopped—The Patrol Read has been stopped. For more information about Patrol Read, see Set Patrol Read Mode.
Property Definition Available Reports Enables you to view Patrol Read report, Check Consistency report, Slot Occupancy report, and Physical Disk Firmware Version Report. For more information, see Available Reports. Controller Tasks To execute a controller task: 1 Expand the Storage tree object to display the controller objects. 2 Select a controller object. 3 Select the Information/Configuration subtab. 4 Select a task from the Available Tasks drop-down menu. 5 Click Execute.
• Set Background Initialization Rate • Set Check Consistency Rate • Set Reconstruct Rate • Set Patrol Read Mode • Start and Stop Patrol Read • Manage Preserved Cache • Change Controller Properties • Manage Physical Disk Power • Manage Encryption Key • Convert to RAID Capable Disks • Convert to Non-RAID Disks Available Reports To view a report: 1 Expand the Storage tree object to display the controller objects. 2 Select a controller object. 3 Select the Information/Configuration subtab.
On SCSI controllers, a rescan updates configuration changes (such as new or removed devices) for all components attached to the controller. For information on when you may want to do a rescan, see Rescan to Update Storage Configuration Changes. NOTE: Rescan Controller is not supported on non-RAID SCSI controllers. You must reboot the system before Storage Management can see configuration changes on non-RAID SCSI controllers.
Quiet Alarm (Controller) Does my controller support this feature? See Supported Features. Use the Quiet Alarm task to quiet the controller’s alarm when it is sounding. After it is quieted, the alarm is still enabled in the event of a future device failure. Test Alarm (Controller) Does my controller support this feature? See Supported Features. Use the Test Alarm task to test whether the controller alarm is functional. The alarm sounds for about 2 seconds.
The Foreign Configuration Operations task provides a preview of the foreign configurations that you can import. This task is available on PERC 6 controllers with firmware version 6.1 and later. For more information, see Foreign Configuration Operations. Manage Physical Disk Power Does my controller support this feature? See Supported Features.
Set Rebuild Rate Does my controller support this feature? See Supported Features. The Set Rebuild Rate task changes the controller’s rebuild rate. During a rebuild, the complete contents of a physical disk are reconstructed. The rebuild rate, configurable between 0% and 100%, represents the percentage of the system resources dedicated to rebuilding failed physical disks.
5 Click Execute. You can also locate this task from the Change Controller Properties drop down menu. For more information, see Change Controller Properties. Reset Configuration Does my controller support this feature? See Supported Features. Use the Reset Configuration task to erase all information on the controller so that you can perform a fresh configuration. This operation destroys all data and virtual disks on the controller and unassigns any hot spares.
To locate this task in Storage Management: 1 Expand the Storage tree object to display the controller objects. 2 Select a controller object. 3 Select the Information/Configuration subtab. 4 Select Reset Configuration from the Available Tasks drop-down menu. 5 Click Execute. You can also locate this task from the Change Controller Properties drop down menu. For more information, see Change Controller Properties. Export Log Does my controller support this feature? See Supported Features.
5 Click Execute. You can also locate this task from the Change Controller Properties drop down menu. For more information, see Change Controller Properties. Foreign Configuration Operations NOTE: Foreign Configuration Operations is available only on SAS controllers with firmware versions 6.1 and later. A foreign configuration is data residing on physical disks that has been moved from one controller to another.
Foreign Configuration Properties The following table describes the properties that are displayed for the Foreign Disks and Global Hot Spares. Table 7-4. Foreign Configuration Properties Property Definition Status These icons represent the severity or health of the storage component. Normal/OK Warning/Non-critical Critical/Fatal For more information, see Storage Component Severity. Name 98 This property displays the name of the foreign configuration and is available as a link.
Property Definition State This property displays the current state of the foreign configuration. Ready—The foreign disk can be imported and functions normally after import. Degraded—The foreign disk is in degraded state and rebuilds after import. Failed—The foreign disk has encountered a failure and is no longer functioning. You cannot import the foreign configuration.
Property Definition Remarks This property gives more information about the foreign virtual disk. If the virtual disk cannot be imported, the reason for failure is displayed. • Exceeded Maximum—The number of virtual disks selected for import has exceeded the maximum number of supported disks. • Missing physical disk or missing span—One or more physical disks or spans in the virtual disk to be imported is missing. • Unsupported—The selected RAID level is not supported on this controller.
Importing Foreign Configurations Some controllers enable you to import a foreign configuration so that virtual disks are not lost after moving the physical disks. You can import a foreign configuration only if it contains a virtual disk that is in either Ready or Degraded state. In other words, all of the virtual disk data must be present, but if the virtual disk is using a redundant RAID level, the additional redundant data is not required.
Importing/Recovering Foreign Configurations The recover operation attempts to restore degraded, failed, or missing virtual disks to a healthy state. A virtual disk may be in a degraded, failed, or missing state after losing communication with the controller due to a power loss, faulty cable connection, or other failure. A rebuild or background initialization may automatically initiate after the recover operation completes. The virtual disk data may be inconsistent after recovery.
Clear Foreign Configuration Does my controller support this feature? See Supported Features. After moving a physical disk from one controller to another, you may find that the physical disk contains all or some portion of a virtual disk (foreign configuration). You can identify whether or not a previously used physical disk contains a foreign configuration (virtual disk) by checking the physical disk state.
4 Select Clear Foreign Configuration from the Controller tasks. Physical Disks in Foreign Virtual Disks The Physical Disks in Foreign Virtual Disks page displays the physical disks and the dedicated hot spare, if any, included in the foreign configuration. The following table describes properties for physical disks in the foreign configuration. Table 7-5. Physical Disk Properties Property Definition Status These icons represent the severity or health of the storage component.
Property Definition After Import State This property displays the after-import state of the physical disk. The physical disk can be imported in any of the following states. Online—The physical disk is part of the imported virtual disk and functions normally. Offline—The physical disk is offline after import to the virtual disk. Foreign—The virtual disk containing the physical disk cannot be imported and the physical disk remains in foreign state.
Property Definition Failure Predicted This property displays whether or not the physical disk has received a Self-Monitoring Analysis and Reporting Technology (SMART) alert and is therefore predicted to fail. For more information on SMART predictive failure analysis, see Monitoring Disk Reliability on RAID Controllers. For information on replacing the physical disk, see Replacing a Physical Disk Receiving SMART Alerts.
Property Definition Media This property displays the media type of the physical disk. The possible values are: HDD—Hard Disk Drive. A HDD is a non-volatile storage device which stores digitally-encoded data on rapidly rotating platters with magnetic surfaces. SSD—Solid State Drive. An SSD is a data storage device that uses solid-state memory to store persistent data. Unknown—Storage Management is unable to determine the media type of the physical disk.
Property Definition Negotiated Speed This property displays the speed of data transfer that the disk negotiated while spinning up and upon initial communication with the controller. This speed is dependent on the speed of the disk, the capable speed of the controller, the current speed of the controller on that connector, and the speed of the Enclosure Management Module (EMM) on the enclosure. Capable Speed This property displays the highest possible speed with which the device can transfer data.
Property Definition Part Number This property displays the unique Bill Of Materials assignment number for a physical disk. The characters 4 through 8 represent the service provider’s part number for that model drive. Set Background Initialization Rate Does my controller support this feature? See Supported Features. The Set Background Initialization Rate task changes the amount of system resources dedicated to the background initialization task.
4 Select Set Background Initialization Rate from the Available Tasks drop-down menu. 5 Click Execute. You can also locate this task from the Change Controller Properties drop down menu. For more information, see Change Controller Properties. Set Check Consistency Rate Does my controller support this feature? See Supported Features. The Set Check Consistency Rate task changes the amount of system resources dedicated to the check consistency task.
You can also locate this task from the Change Controller Properties drop down menu. For more information, see Change Controller Properties. Related Information: • Check Consistency • Cancel Check Consistency Set Reconstruct Rate Does my controller support this feature? See Supported Features. The Set Reconstruct Rate task changes the amount of system resources dedicated to the reconstruct task.
You can also locate this task from the Change Controller Properties drop down menu. For more information, see Change Controller Properties. Related Information: Virtual Disk Task: Reconfigure (Step 1 of 3) Redundant Path Configuration Does my Controller Support This Feature? See Supported Features. Redundant path is supported only on external PERC cards that use firmware version 6.1 and later. A redundant path internal to the system is not supported. MD1xxx enclosures are supported.
Figure 7-1. Daisy Chain Configuration SAS Controller C0 C1 C0 C1 E1 C0 C1 C0 C1 E2 C0 C1 C0 C1 E3 If the communication channel between the connector and the first enclosure is lost, the redundant path configuration itself is lost. In this case, the health of the logical connector is displayed as critical. Navigate to the Information/Configuration subtab of the logical connector to view details of the Path Health.
Table 7-6. Component Health Health of Logical Path between Controller and Enclosure 1 Connector Connector 0 (C0) Connector 1 (C1) Available Available Available Disconnected Disconnected Available However, if the communication channel between any two enclosures is lost, the redundant path configuration is degraded and the health of the logical connector is displayed as degraded. For a brief outline of this scenario, see Table 7-7. Table 7-7.
Clearing the Redundant Path View Consider a case where you reboot your system and Storage Management, displays the Logical Connector with a path failure message. It is possible that you may have intentionally unplugged the second connector. In this case, the path failure message is not relevant. Else, there could be a fault in the connected cable or the cable may not be connected properly to the controller.
The Patrol Read does not run on a physical disk in the following circumstances: • The physical disk is not included in a virtual disk or assigned as a hot spare. • The physical disk is included in a virtual disk that is currently undergoing one of the following: – A rebuild – A reconfiguration or reconstruction – A background initialization – A check consistency In addition, the Patrol Read suspends during heavy I/O activity and resumes when the I/O is finished.
To locate this task in Storage Management: 1 Expand the Storage tree object to display the controller objects. 2 Select a controller object. 3 Select the Information/Configuration subtab. 4 Select Set Patrol Read Mode from the Available Tasks drop-down menu. 5 Click Execute. You can also locate this task from the Change Controller Properties drop down menu. For more information, see Change Controller Properties.
Related Information: Set Patrol Read Mode Change Controller Properties Does my controller support this feature? See Supported Features. The Change Controller Properties task provides you the option to change multiple controller properties simultaneously. This task is available only on SAS controllers with firmware version 6.1 and later.
2 Select a controller object. 3 Select the Information/Configuration subtab. 4 Select Change Controller Properties... from the Controller Tasks drop down menu. 5 Click Execute.
• Customized Power Savings Mode—provides the option for you to customize the power savings settings. The default values are populated when you select this power mode. You can select or deselect the features you want to enable. To enable the Quality of Service (QoS) feature, select the Customized Power Savings Mode and then select Enable for the Spin Down Configured Drives option.
Property Definition Time Interval for Spin Up(in Hours) The spin up time interval for the battery learn cycle. The time interval can range from 1-24 hours. To manage physical disk power on unconfigured drives and hot spares: 1 Select Enabled for the Spin Down Unconfigured Drives and Spin Down Hot Spares options. 2 Click Apply Changes. To exit and cancel your changes, click Go Back to Previous Page.
To manage physical disk power through the Customized Power Savings Mode: 1 Select the Customized Power Save Mode option. 2 Edit the remaining parameters on the Manage Physical Disk Power screen. Configure the options in the QOS section as described below. To manage physical disk power through the QOS option: 1 Select the Customized Power Save Mode option. 2 In the Spin Down Configured Drives drop-down menu, select Enabled. 3 The Quality of Service (QOS) option is enabled.
Manage Preserved Cache The Managed Preserved Cache feature provides you the option to ignore or restore the controller cache data. In the write-back policy, data is written to the cache before being written to the physical disk. If the virtual disk goes offline or is deleted for any reason, the data in the cache is lost. Data in the cache may also be lost in case of unintended cable or power failure.
Manage Encryption Key NOTE: To configure encryption, you do not require an SED. However, to create a secure virtual disk, you require an SED. The encryption settings are then used to configure the virtual disk and the SED. NOTE: The Encryption must be manually enabled for any virtual disk that was created using SED drives on a controller for which the Encryption was not enabled earlier.
Encryption Key The controller uses the Encryption Key to lock or unlock access to Self Encryption Disks (SEDs). You can create only one Encryption Key for each encryption-capable controller. If you are using Local Key Management (LKM) you must create the Encryption Key by providing the Encryption Key Identifier and the Passphrase. Encryption Key Identifier An Encryption Key Identifier is a user-supplied text label for the Passphrase.
NOTE: Server Administrator Storage Management provides a suggested Passphrase below the Passphrase text box. 4 If you want to save the Encryption Key credentials in a file on the system where Distributed Web Server is running, select the Escrow check box. The Path field is displayed. Enter the path where you want to save the file. The path should contain a file name with an .xml extension. The saved file contains this information: SAS address, Encryption Key Identifier, Passphrase, and modified date.
When changing the Encryption Key, you can also save or update the new Encryption Key credentials to a file in the system where Distributed Web Service is running. Select the Escrow check box. If you have already saved the Encryption Key credentials for a controller, providing the path of the file updates credentials for that controller. If the credentials are for a new controller, the details are appended in the same file.
2 In the CacheCade Group section, select SATA SSD or SAS SSD if your system contains both SAS and SATA SSDs. 3 Enter a name for the CacheCade. The size is calculated as follows: CacheCade size = capacity of the smallest SSD * the number of SSDs 4 From the available free disks that are displayed, select the SSDs that you would like to include in the CacheCade. The selected disks are displayed in the Physical Disks Selected section. 5 Click Finish.
The LED of the physical disk(s) participating in the CacheCade glows. To unblink the physical disk in the CacheCade(s) screen, go to the CacheCade Disk that you want to unblink and select Unblink... from the available Tasks. Deleting the CacheCade To delete the CacheCade: 1 In the CacheCade(s) screen, go to the CacheCade that you want to delete and select Delete... from the available Tasks. The following warning is displayed: Warning! CacheCade pool size will be reduced.
Table 7-9. CacheCade Properties Property Definition Disk Cache Policy This property displays whether the disk cache policy of the physical disks that are part of the CacheCade is Enabled or Disabled. See RAID Controller Read, Write, Cache, and Disk Cache Policy. Convert to Non-RAID Disks On PERC H310 adapters, in the controller tasks drop-down menu select the task Convert to Non-RAID disks: 1 The disks in Ready state are displayed. Select the drives that you want to convert. 2 Click Apply.
Patrol Read Report Does my controller support this feature? See Supported Features. This report provides information on all the Patrol Reads done on the controller in the chronological order. It provides information such as last run time and result. If the Patrol Read fails, it provides the reason for the failure. To locate this task in Storage Management: 1 Click Storage to view the dash board. 2 Select View Patrol Read Report from the Select Report drop-down menu. 3 Click Execute.
Physical Disk Firmware Version Report Does my controller support this feature? See Supported Features. The Physical Disk Firmware Version Report compares the current firmware against a list of currently available firmware and legacy driver models. NOTE: To generate the HDD firmware version report, negotiable speed and the model number of the drives are used as keys for indexing entries in the hddfwver.csv file.
Table 7-10. Physical Disk Firmware Version Report Properties Property Definition Name The nexus or location of each drives that has to be updated. This nexus is represented as a two or three-digit mapping of the drive location. Example: Two digit mapping: 0:1 = Controller 0: Slot 1 Three digit mapping: 1:0:4 = Controller 1: Connector 0: Slot 4 Model Number The unique number associated with a specific OEM Vendor's drives and drive capacity.
Table 7-10. Physical Disk Firmware Version Report Properties Nautilus DOS Nautilus is the tool that is used for offline firmware updates. Nautilus DOS is the version of the tool that works on 9th (x9xx) - 11th (yx1x) generation of supported servers with SAS and SATA drives. This tool updates multiple drive types with a single scan and updates procedure boot and runs from a USB key, Preboot Execution Environmen (PXE), or CD-ROM.
Enclosures and Backplanes 8 Physical disks can be contained in an enclosure or attached to the system’s backplane. An enclosure is attached to the system externally while the backplane and its physical disks are internal. Backplanes You can view the Backplane object by expanding the controller and Connector object in the Storage Management tree view. Storage Management displays the status of the backplane and attached physical disks.
Storage Management displays the properties of the enclosure’s fans, power supply, and temperature probes. Storage Management also notifies you of enclosure status changes through alerts that are displayed in the Alert Log.
The Failure threshold has a default value that cannot be changed. You can set the Warning threshold, however. For information on setting the warning threshold, see Set Temperature Probe Values.
SMART Thermal Shutdown Does my enclosure support this feature? See Supported Features. Enclosure management provides a feature which automatically shuts down the operating system, the server, and the enclosure when the enclosure’s temperature reaches dangerous extremes. The temperature, when shutdown occurs, is determined by the enclosure temperature probe’s Minimum Failure Threshold and the Maximum Failure Threshold. These thresholds are default settings that cannot be changed.
enclosure may no longer be displayed by Storage Management and you may notice other erratic behaviors. In addition, the bus configuration switch on these enclosures is not rated for frequent toggling. Enclosure Management In addition to the drop-down menu Enclosure Tasks, the following activities may be required for enclosure management. • Identifying the service tag of the enclosure—To identify the enclosure’s service tag, select the enclosure in the tree view and click the Information/Configuration tab.
Enclosure and Backplane Health This screen displays the status of the enclosure or backplane and the components attached to the enclosure or backplane. Enclosure and Backplane Status Component status is indicated by the severity. A component with a Warning or Critical/Failure status requires immediate attention to avoid data loss if possible. A component’s status may indicate the combined status of the component and its lower-level objects.
Enclosure and Backplane Components For information on attached components, see Physical Disks or Physical Devices. Enclosure and Backplane Properties and Tasks Use this window to view information about the enclosure or backplane and execute enclosure tasks. Enclosure and Backplane Properties The enclosure or backplane properties can vary depending on the model of the controller.
Table 8-2. Enclosure and Backplane Properties Property Definition These icons represent the severity or health of the storage component. For more information, see Storage Component Severity. NOTE: If the enclosure is connected to the controller in redundant path mode (for more information, see Redundant Path Configuration), the loss of connection to any one EMM may cause the enclosure status to be displayed as degraded. Name This property displays the name of the enclosure or backplane.
Property Definition Configuration This property displays the mode in which the enclosure is operating. Possible values are: Joined—Indicates that the enclosure is operating in joinedbus mode. Split—Indicates that the enclosure is operating in split-bus mode. Unified—Indicates that enclosure is operating in unified mode. Clustered—Indicates that the enclosure is operating in cluster mode. Clustered mode is only available on clusterenabled RAID controllers.
Property Definition Express Service Code The Express Service Code is a numeric function of your service tag. You can key in the numeric Express Service Code for automated call-routing while calling technical support. You can use this number to identify a specific enclosure in your environment by matching this number with the number on the Express Service Code affixed to the enclosure. Asset Tag This property displays the asset tag information for the enclosure.
Drop-down Menu Enclosure Tasks: • Enable Alarm (Enclosure) • Disable Alarm (Enclosure) • Set Asset Data • Blink • Set Temperature Probe Values Available Reports To view a report: 1 Expand the Storage tree object to display the controller objects. 2 Expand a controller object. 3 Expand a Connector object. 4 Select the enclosure object. 5 Select the Information/Configuration subtab. 6 Select a report from the Select Report drop-down menu. 7 Click Execute.
Disable Alarm (Enclosure) Does my enclosure support this feature? See Supported Features. Use the Disable Alarm task to disable the enclosure alarm. When disabled, the alarm does not sound when the enclosure exceeds a warning threshold for temperature or experiences other error conditions such as a failed fan, power supply, or controller. If the alarm is already sounding, you can turn it off with this task. Set Asset Data Does my enclosure support this feature? See Supported Features.
Identifying an Open Connector for the Enclosure Does my controller support this feature? See Supported Features. If you have not yet attached the enclosure to an open connector, you may need to identify a connector on the controller that can be used for this purpose. To identify an open connector: 1 Expand the Storage Management tree view until the controller object is expanded. When the controller object is expanded, the tree view displays the controller’s connectors.
Verifying the Enclosure’s EMM Firmware Version Does my controller support this feature? See Supported Features. The firmware for the Enclosure Management Modules (EMMs) must be at the same level. The status of the EMMs is displayed as degraded if there is a mismatch between the EMM firmware. To verify the EMM firmware version: 1 Expand the tree view until the EMMs object is displayed. 2 Select the EMMs object. The firmware version for each EMM is displayed in the Firmware Version column in the right pane.
2 Type the new asset name in the New asset name text box. You can specify a name useful to you for organizing your storage environment. For example, the asset name could refer to the type of data stored on the enclosure or to the enclosure’s location. 3 Click Apply Changes. To exit and cancel your changes, click Go Back To Enclosure Information Page. To locate this task in Storage Management: 1 Expand the Storage tree object to display the controller objects. 2 Expand a controller object.
3 Type the lowest acceptable temperature in Celsius for the enclosure in the Minimum Warning Threshold text box. The text box label indicates the range that you can specify. 4 Type the highest acceptable temperature in Celsius for the enclosure in the Maximum Warning Threshold text box. The text box label indicates the range that you can specify. 5 Click Apply Changes.
To locate this task in Storage Management: 1 Expand the Storage tree object to display the controller objects. 2 Expand a controller object. 3 Expand a Connector object. 4 Select the enclosure object. 5 Select the Information/Configuration subtab. 6 Select View Slot Occupancy Report from the Available Tasks drop-down menu. 7 Click Execute. EMM Properties Use this window to view information about the Enclosure Management Modules (EMMs).
Table 8-3. EMM Properties Property Definition Status These icons represent the severity or health of the storage component. Normal/OK Warning/Non-critical Critical/Fatal For more information, see Storage Component Severity. Name This property displays the name of the EMM. State This property displays the current state of the EMMs. • Ready—The EMM is functioning normally. • Degraded—The EMM has encountered a failure and is operating in a degraded state.
Property Definition Type This property indicates whether the EMM is a SCSI SES Module or a SCSI Terminator. SCSI SES Module—A SCSI SES Module provides SES and SAFTE reporting to the host server, control of all system LED indicators, and monitoring of all environmental elements, such as temperature sensors, cooling modules, and power supplies. SCSI Terminator—The SCSI Terminator card is only used if the 220S or 221S enclosure is not configured with a redundant SCSI SES Module type of EMM.
Table 8-4. Fan Properties Property Definition Status These icons represent the severity or health of the storage component. Normal/OK Warning/Non-critical Critical/Fatal For more information, see Storage Component Severity. Name This property displays the name of the fan. State This property displays the current status of the fan. Ready—The fan is functioning normally. Degraded—The fan has encountered a failure and is operating in a degraded state.
Power Supply Properties Use this window to view information about the enclosure’s power supplies. Table 8-5. Power Supply Properties Property Definition Status These icons represent the severity or health of the storage component. Normal/OK Warning/Non-critical Critical/Fatal For more information, see Storage Component Severity. Name This property displays the name of the power supply. State This property displays the current status of the power supply. Ready—The power supply is functioning normally.
Property Definition Firmware Version This property displays the firmware version number of the power supply. The firmware version of power supply is available only in MD12XX boxes with enclosure firmware version 1.04 and later.
Temperature Probe Properties and Tasks Does my enclosure support this feature? See Supported Features. Use this window to view information about the enclosure’s temperature probes. Temperature Probe Properties and Tasks Table 8-6. Temperature Probe Properties Property Definition Status These icons represent the severity or health of the storage component. For more information, see Storage Component Severity.
Property Definition State This property displays the current status of the temperature probe. Ready—The temperature probe is functioning normally. Degraded—The temperature probe has encountered a failure and is operating in a degraded state. Failed—The temperature probe has encountered a failure and is no longer functioning. Storage Management may also be unable to communicate with the enclosure using SES commands.
Set Temperature Probe Properties and Tasks Click the Set Temperature Probe button to launch the wizard for changing the temperature probe’s Warning threshold. You can change the Warning threshold for each of the temperature probes included in the enclosure. For more information, see Set Temperature Probe Values. To launch the Set Temperature Probe wizard: 1 Expand the Storage tree object to display the controller objects. 2 Expand a controller object. 3 Expand a Connector object.
Enclosures and Backplanes
9 Connectors A controller contains one or more connectors (channels or ports) to which you can attach disks. A connector is externally accessible for attaching an enclosure (with external disks) to the system. A connector may also be attached to the system’s backplane (for internal disks). The controller’s connectors are displayed by expanding the controller object in the tree view. NOTE: For PCIe SSD, connectors are referred to as PCIe SSD extenders.
NOTE: Channel redundancy only applies to controllers that have more than one channel and that attach to an external disk enclosure. 1 Launch the Create Virtual Disk Advanced Wizard by doing the following: a Locate the controller on which you are creating a channel-redundant virtual disk Expand the controller object until the Virtual Disks object is displayed. b Select the Virtual Disks object and click Go To Create Virtual Disk Wizard. c Click Virtual Disk Advanced Wizard.
4 Click Continue. RAID 50 1 Select one physical disk on each of three channels. (In other words, each of the three channels select a single disk.) 2 Select an additional disk on each of the three channels. You have now selected the minimum number of disks for a RAID 50. Continue selecting a disk on each channel until you have selected the desired number of disks. 3 Repeat step 2 until you have the desired number of disks. 4 Click Continue.
Table 9-1. Component Severity Severity Component Status Normal/OK. The component is working as expected. Warning/Non-critical. A probe or other monitoring device has detected a reading for the component that is above or below the acceptable level. The component may still be functioning, but it could fail. The component may also be functioning in an impaired state. Data loss is possible. Critical/Failure/Error. The component has either failed or failure is imminent.
Table 9-2. Connector Properties Property Definition These icons represent the severity or health of the storage component. For more information, see Storage Component Severity. A Warning or Critical severity may indicate that the connector is unable to communicate with attached devices such as an enclosure. Check the status of attached devices. For more information, see Cables Attached Correctly and Isolate Hardware Problems. Name This property displays the connector number.
Connector Tasks: Rescan Connector Does my controller support this feature? See Supported Features. On a SCSI controller, this task rescans the controller connectors to verify the currently connected devices or to recognize new devices that have been added to the connectors. Performing a rescan on a connector is similar to performing a rescan on the controller. For information on scheduling a rescan, see Rescan to Update Storage Configuration Changes.
Table 9-3. Logical Connector Properties Property Definition These icons represent the severity or health of the storage component. For more information, see Storage Component Severity. A Warning or Critical severity may indicate that the connector is unable to communicate with attached devices such as an enclosure. Check the status of attached devices. For more information, see Cables Attached Correctly and Isolate Hardware Problems. Name This property displays the connector number, usually 0.
Selecting this option clears the redundant path view and the connectors are represented on the user interface as Connector 0 and Connector 1. Related Tasks • Redundant Path Configuration Logical Connector Components For information on attached components, see Enclosure and Backplane Properties and Tasks.
10 Tape Drives Tape drives contain several tape back up units (TBUs) on which data can be backed up. Storage Management enumerates the TBUs that are used for data back up. You can view the tape drives associated with a particular controller on the Tape Drives on page. Tape Drive Properties Table 10-1. Property Tape Drive Properties Definition ID Displays the ID of the tape drive. Name Displays the name of the tape drive.
Tape Drives
RAID Controller Batteries 11 Some RAID controllers have batteries. If the controller has a battery, Storage Management displays the battery under the controller object in the tree view. In the event of a power outage, the controller battery preserves data that is in the volatile cache memory (SRAM) but not yet written to disk. The battery is designed to provide a minimum of 24 hours back up. When a RAID controller is first installed in a server, the battery may need charging.
Table 11-1. Battery Properties Property Definition Status These icons represent the severity or health of the storage component. Normal/OK Warning/Non-critical Critical/Fatal For more information, see Storage Component Severity. Name This property displays the name of the battery. State This property displays the current status of the battery. Possible values are: Charging—The battery is undergoing the recharge phase of the battery learn cycle. For more information, see Start Learn Cycle.
Battery Tasks To execute a drop-down menu battery task: 1 Expand the Storage tree object to display the controller objects. 2 Expand a controller object. 3 Select the Battery object. 4 Select a task from the Available Tasks drop-down menu. 5 Click Execute. Drop-Down Menu Battery Tasks: • Start Learn Cycle • Battery Delay Learn Cycle Related information: • Battery Properties Start Learn Cycle Does my controller support this feature? See Supported Features.
The controller firmware automatically initiates the Learn cycle every 90 days. You can, however, delay the start time of the Learn cycle for a further seven days, after which the firmware automatically initiates the Learn cycle. For more information, see Battery Delay Learn Cycle. NOTE: The Learn cycle cannot be performed while the battery is charging. If either a user or the controller firmware initiate the Learn cycle while the battery is charging, then the battery Learn State displays Requested.
To locate this task in Storage Management: 1 Expand the Storage tree object to display the controller objects. 2 Expand the controller object. 3 Select the Battery object. 4 Select Delay Learn Cycle from the Available Tasks drop-down menu. 5 Click Execute.
RAID Controller Batteries
12 Physical Disks or Physical Devices Physical disks or physical devices reside within an enclosure or are attached to the controller. On a RAID controller, physical disks or devices are used to create virtual disks. Guidelines to Replace a Physical Disk or Physical Device A replacement disk may not always be the same model as the physical disks or devices in the storage enclosure.
NOTE: With the exception of combining SAS,SATA,SCSI, and SSD drives, only upgrades are supported. Add a New Disk to Your System 1 Install or attach the new physical disk (or disks) or physical devices. For more information, see the documentation that came with the disk. 2 Do one of the following depending on the controller technology. For more information, see RAID Controller Technology: SCSI, SATA, ATA, and SAS.
• If you want to include the new disk in a virtual disk, see Virtual Disk Considerations for Controllers. How to Avoid Removing the Wrong Disk You can avoid removing the wrong disk by blinking the LED display on the disk that you want to remove. For information on blinking the LED display: • See Blink and Unblink (Physical Disk) to blink the LED display on a physical disk. • See Blink and Unblink (Virtual Disk) to blink the LED display on all physical disks included in a particular virtual disk.
4 Insert a new disk. Make sure that the new disk is the same size or larger as the disk you are replacing. On some controllers, you may not be able to use the additional disk space if you insert a larger disk. For more information, see Virtual Disk Considerations for Controllers. After you complete this procedure, a rebuild is automatically initiated because the virtual disk is redundant. If the disk is not part of a redundant virtual disk: 1 Back up data from the virtual disk. 2 Delete the virtual disk.
Physical Disk or Physical Device Properties The following table describes properties that may be displayed for physical disks or devices depending on the controller. Table 12-1. Property Physical Disk Properties Definition Status These icons represent the severity or health of the storage component. Normal/OK Warning/Non-critical Critical/Fatal For more information, see Storage Component Severity. Power Status The following status of the physical drives.
Property Definition State This property displays the current state of the physical disk or device. Ready—The physical disk or device is functioning normally. If the disk is attached to a RAID controller, Ready state indicates that the disk is available to be used by a virtual disk. When the physical disk or device is used in a virtual disk, the state changes to Online. Online—The physical disk is part of a virtual disk and is functioning normally. For more information, see Online and Offline.
Property Definition Rebuilding—Data from a redundant virtual disk is currently being rebuilt onto the physical disk or device. Incompatible—The physical disk or device is not suitable for a rebuild. The physical disk or device may be too small or it may be using an incompatible technology. For example, you cannot rebuild a SAS disk with a SATA disk or a SATA disk with a SAS disk. Removed—The physical disk or device has been removed. This state only applies to physical disks that are part of a virtual disk.
Property Definition Replacing—A Replace Member Disk task is being performed on the physical disk or device. For more information, see Replace Member Disk and Revertible Hot Spare. NOTE: You can cancel the copying of data at any time during the execution of this task. Non-RAID—Non-RAID disks are exposed to the operating system unlike unconfigured good disks and this enables usage of disk in direct pass-through mode. Maximum number of non-RAID disks that can be supported on H310 controller are 64.
Property Definition Failure Predicted This property displays whether or not the physical disk or device has received a SMART alert and is therefore predicted to fail. For more information on SMART predictive failure analysis, see Monitoring Disk Reliability on RAID Controllers. For information on replacing the physical disk, see Replacing a Physical Disk Receiving SMART Alerts.
Property Definition Bus Protocol This property displays the technology that the physical disk or device is using. Possible values are: SCSI—Small Computer System Interface SAS—Serial Attached SCSI SATA—Serial Advanced Technology Attachment (SATA) Media This property displays the media type of the physical disk or device. The possible values are: HDD—Hard Disk Drive. A HDD is a non-volatile storage device which stores digitally-encoded data on rapidly rotating platters with magnetic surfaces.
Property Definition Serial No. This property displays the disk's serial number. Part Number This property displays the Piece Part Identification (PPID) of the physical drive. Negotiated Speed This property displays the speed of data transfer that the disk negotiated while spinning up and upon initial communication with the controller.
NOTE: Different controllers support different features. For this reason, the tasks displayed on the Tasks drop-down menu can vary depending on which controller is selected in the tree view. If no tasks can be performed because of controller or system configuration limitations, then the Tasks drop-down menu displays No Task Available.
into a server or an enclosure. If the physical disk is not contained in a carrier but is instead designed to be connected with a SCSI cable (typically a ribbon cable), then the Blink and Unblink tasks are disabled. Remove Dead Segments Does my controller support this feature? See Supported Features. The Remove Dead Segments task recovers disk space that is currently unusable.
In some cases, a rescan is required for the controller to recognize configuration changes such as the removal of a disk or device. For more information, see Rescan to Update Storage Configuration Changes. NOTE: This procedure is not available for physical disks or devices that have been assigned as a hot spare or physical disks or devices that are part of a virtual disk. In addition, this procedure is only supported for hotswap physical disks or devices (disks that reside in a carrier).
without interrupting the system or requiring your intervention. When a hot spare is activated, it rebuilds the data for all redundant virtual disks that were using the failed physical disk. You can change the hot spare assignment by unassigning a disk and choosing another disk as needed. You can also assign more than one physical disk as a global hot spare. NOTE: On SAS 6/iR controllers, you cannot assign physical disks that have boot partitions, as hot spares.
• Considerations for Hot Spares on S100, and S300 Controllers • Global Hot Spare Considerations on a SAS 6/iR Online and Offline Does my controller support this feature? See Supported Features. The Online and Offline tasks only apply to physical disks that are included in a redundant virtual disk and attached to a PERC controller. Use the Offline task to deactivate a disk before removing it. Use the Online task to reactivate an offline disk.
Use the clear physical disk task to erase data residing on a physical disk. The Clear task applies to physical disks that are in Ready state and that contain data or that are in Clear state. NOTE: A physical disk may display the Clear state if it is a member of a virtual disk that is being slow initialized. Performing a Cancel Clear task on the physical disk causes the Slow Initialize task to be cancelled for the entire virtual disk.
You can also use the Revertible Hot Spare task to copy data from a physical disk to the hot spare on a predictive failure event. If Revertible Hot Spare is enabled and the physical disk is SMART-enabled, the controller firmware automatically starts copying data from the SMARTenabled disk in the virtual disk to the hot spare. NOTE: To use the Revertible Hot Spare task, you should have assigned a hot spare to the virtual disk.
To locate this task in Storage Management: 1 Expand the Storage tree object to display the controller objects. 2 Expand a controller object. 3 Expand a Connector object. 4 Expand the enclosure or Backplane object. 5 Select the Physical Disks object. 6 Select Instant Encrypt Erase from the Available Tasks drop-down menu of the physical disk you want to clear. 7 Click Execute. Full Initialization Does my controller support this feature? See Supported Features.
Convert to RAID Capable Disk This task enables a disk for all RAID operations. This task is supported on H310 controllers. Convert to Non-RAID Disk This task converts a disk to Non-RAID disk. After converting a disk to nonRAID, the disk is exposed to the operating system unlike unconfigured good disks and this enables usage of disk in direct pass-through mode. This task is supported on H310 controllers.
13 Virtual Disks In order to implement RAID functions, RAID controllers must create a virtual disk. A virtual disk refers to storage created by a RAID controller from one or more physical disks. Although a virtual disk may be created from several physical disks, it is seen by the operating system as a single disk. Depending on the RAID level used, the virtual disk may retain redundant data in case of a disk failure or have particular performance attributes.
• Rescan to Update Storage Configuration Changes • Time Delay in Displaying Configuration Changes NOTE: In addition to this document, review the hardware documentation that is provided with the controllers. Reviewing the hardware documentation along with this document may provide a better understanding of the controller limitations.
must decide which free space on the physical disks to allocate to the new virtual disk. The PERC controllers look for the largest area of free space and allocate this space to the new virtual disk. • SCSI limitation of 2TB—Virtual disks created on a PERC controller cannot be created from physical disks with an aggregate size greater than 2TB. This is a limitation of the controller implementation.
• Rebuilding data—An failed physical disk that is used by both redundant and non-redundant virtual disks cannot be rebuilt. Rebuilding a failed physical disk in this situation requires deleting the non-redundant virtual disk. • Disk Group Concept Consideration for S110—Disk grouping is a logical grouping of disks attached to a RAID controller on which one or more virtual disks are created, such that all virtual disks in the disk group use all of the physical disks in the disk group.
Virtual Disk Considerations on Linux On some versions of the Linux operating system, the virtual disk size is limited to 1TB. Before creating a virtual disk that is larger than 1TB, you should make sure that your operating system supports this virtual disk size. The support provided by your operating system depends on the version of the operating system and any updates or modifications that you have implemented.
Maximum Number of Virtual Disks per Controller Controllers have limitations on how many virtual disks can be created on the controller. For information on how many virtual disks the controller supports, see the virtual disk specifications for the controller in Supported Features. Calculation for Maximum Virtual Disk Size and the Create Virtual Disk Express Wizard The Create Virtual Disk Express Wizard displays the minimum and maximum values for the virtual disk size.
• SMART Thermal Shutdown • Channel Redundancy and Thermal Shutdown NOTE: Channel redundancy only applies to controllers that have more than one channel and that attach to an external disk enclosure. Creating Virtual Disks Does my controller support this feature? See Supported Features. In order to implement RAID functions, you need to create a virtual disk. A virtual disk refers to storage created by a RAID controller from one or more physical disks.
Reconfiguring/Migrating Virtual Disks Does my controller support this feature? See Supported Features. You can reconfigure or migrate a virtual disk in order to increase the disks capacity or change its RAID level. To reconfigure a virtual disk: 1 Review the information in Starting and Target RAID Levels for Virtual Disk Reconfiguration and Capacity Expansion. 2 Locate the controller on which the virtual disk resides in the tree view. Expand the controller object until the Virtual Disks object is displayed.
Table 13-1.
Table 13-1. Virtual Disk Reconfiguration and Capacity Expansion (continued) Controller Starting RAID Level Target RAID Level Comments RAID 0 RAID 6 requires a minimum of 4 disks. RAID 6 Reconfiguration from RAID 0 to RAID 6 requires at least 2 additional disks even when this exceeds the 4disk minimum required by RAID 6. RAID 1 RAID 0 With or without adding additional disks RAID 1 RAID 5, RAID 6 Add at least one additional disk. RAID 6 requires a minimum of 4 disks.
Table 13-1. Controller Virtual Disk Reconfiguration and Capacity Expansion (continued) Starting RAID Level Target RAID Level Comments PERC S100, S110, RAID 0 and S300 RAID 0 With or without additional disks RAID 1 RAID 1 Without additional disks RAID 5 RAID 5 With or without additional disks RAID 10 RAID 10 Without additional disks Maintain Integrity of Redundant Virtual Disks Does my controller support this feature? See Supported Features.
Rebuilding Redundant Information Does my controller support this feature? See Supported Features. If you have a redundant virtual disk, you can reconstruct the contents of a failed physical disk onto a new disk or a hot spare. A rebuild can take place during normal operation, but it degrades performance. The following sections provide additional information on rebuilding disks.
Table 13-2. Sample Scenarios For Virtual Disk Bad Blocks RAID Level State Virtual Disk Scenario Result RAID 0 Degraded One bad block on a The controller cannot regenerate physical disk. data from peer disks as there is no redundancy. This results in a virtual disk bad block. RAID 5 Ready One bad block on a The controller regenerates data physical disk. from peer disks and sends a Write to the bad block. The disk then re-maps the Logical Block Addressing (LBA) to another physical location.
Recommendations Storage Management provides the ability to clear the bad block warnings. To clear bad blocks, the following procedure is recommended: 1 Perform a backup of the virtual disk with the Verify option selected. One of the two following scenarios can occur: – Backup operation fails on one or more files. In this case, restore the file from a previous backup. After restoring the file, proceed to step 2. – Backup operation completes without error.
Table 13-3. Virtual Disk Properties Property Definition Status These icons represent the severity or health of the storage component. Normal/OK Warning/Non-critical Critical/Fatal For more information, see Storage Component Severity. Name This property displays the virtual disk name. State This property displays the current status of the virtual disk. Possible values are: Ready—The virtual disk is functioning normally. Degraded—A physical disk in a redundant virtual disk is not online.
Property Definition Background Initialization—A background initialization is being performed on the virtual disk. Degraded Redundancy—This state is applicable to RAID 6 only in which a physical disk in a redundant virtual disk is not online, but the virtual disk is still accessible and functioning. Virtual Disk Bad Block This property displays whether the virtual disk has bad blocks. Encrypted This property displays whether the virtual disk is encrypted. The possible values are Yes and No.
Property Definition Media This property displays the media type of the physical disks present in the virtual disk. The possible values are: HDD—Hard Disk Drive. A HDD is a non-volatile storage device which stores digitally-encoded data on rapidly rotating platters with magnetic surfaces. SSD—Solid State Drive. An SSD is a data storage device that uses solid-state memory to store persistent data. Unknown—Storage Management is unable to determine the media type of the physical disk.
Virtual Disk Tasks To execute a virtual disk drop-down menu task: 1 Expand the Storage tree object to display the controller objects. 2 Expand a controller object. 3 Select the Virtual Disks object. 4 Select a task from the Available Tasks drop-down menu. 5 Click Execute. NOTE: Different controllers support different features. For this reason, the tasks displayed on the Tasks drop-down menu can vary depending on which controller is selected in the tree view.
• Clear Virtual Disk Bad Blocks • Encrypt Virtual Disk Reconfigure Does my controller support this feature? See Supported Features. Use the Reconfigure task to change the virtual disks properties. For example, you can use this task to add physical disks or change the RAID level. For more information, see Virtual Disk Task: Reconfigure (Step 1 of 3). Format, Initialize, Slow and Fast Initialize Does my controller support this feature? See Supported Features.
Use the Restore Dead Segments task to recover data from a RAID-5 virtual disk that has been corrupted. The Restore Dead Segments task attempts to reconstruct data from a corrupt portion of a physical disk included in a RAID5 virtual disk. The Restore Dead Segments task uses the parity or redundant information to reconstruct the lost data. This task is not always able to recover lost data. Delete Does my controller support this feature? See Supported Features.
NOTE: The Pause Check Consistency task updates the virtual disk State property to Resynching Paused immediately. The Progress property may continue to increment for up to three seconds. This time delay occurs because the polling task may take up to three seconds to query the task information and update the display. Resume Check Consistency Does my controller support this feature? See Supported Features. Use the Resume Check Consistency task to resume a check consistency after it has been paused.
Change Policy Does my controller support this feature? See Supported Features. Use the Change Policy task to change a virtual disk’s read, write, or cache policy. Changes to the read, write, and cache policy only apply to the virtual disk that you have selected. This task does not change the policy for all virtual disks on the controller. For more information, see RAID Controller Read, Write, Cache, and Disk Cache Policy. You can also modify the physical disk cache policy using this command.
Create Virtual Disk Express Wizard Does my controller support this feature? See Supported Features. The Create Virtual Disk Wizard allows you to select the wizard type and the RAID level. The Create Virtual Disk Express Wizard calculates the appropriate virtual disk configuration based on the available space and controller considerations. To make your own selections for the virtual disk configuration, select the Advanced Wizard option. For more information, see Create Virtual Disk Advanced Wizard.
continues to function. This feature provides data redundancy and good read performance, but slightly slower write performance. Your system must have at least two disks to use RAID 1. – Select RAID 5 for striping with distributed parity. This selection groups n disks together as one large virtual disk with a total capacity of (n-1) disks. When a disk fails, the virtual disk continues to function. This feature provides better data redundancy and read performance, but slower write performance.
Create Virtual Disk Express Wizard (Step 2) The Create Virtual Disk Express Wizard - page displays the summary of attributes of the selected RAID level. The attributes include Bus Protocol, Stripe Element Size, Read Policy, and the selected physical disk. The default values of the virtual disk attributes excluding the RAID level are recommended for the selected RAID level. 1 Enter a name for the virtual disk in the Name text box.
takes additional time, because the drive(s) need to spun up. The message displays the ID(s) of the spun down drive(s). Click Go Back To Previous Page to return to Create Virtual Disk Express Wizard page, if you want to change your selections. Click Exit Wizard to cancel the virtual disk creation. Create Virtual Disk Advanced Wizard Does my controller support this feature? See Supported Features.
If you select No, the RAID levels are available based on the total number of physical disks present on the system. 5 Select the required RAID level from the from the drop-down list. – Depending on the controller, Concatenated enables you to combine the storage capacity of several disks or to create a virtual disk using a single physical disk. For more information on the number of supported physical disks supported by Concatenated, see Number of Physical Disks per Virtual Disk.
protection and read/write performance. Your system must have at least four disks to use RAID 10. For PERC controllers with firmware version 6 and later, RAID 10 also allows to create a single span virtual disk with 22 or 26 physical drives. – Intelligent Mirroring—Automatically calculates the span composition based on the physical disks you select. Spans are not displayed on this screen. Select Continue to view the span grouping on the Summary screen. Click Exit Wizard to cancel the virtual disk creation.
• Across connectors in the enclosure that are not at the same level of the enclosure but with a physical disk of acceptable size difference If the size difference is not acceptable, the disk is not mirrored and hence dropped from the span, and number of span and disk in the span is recalculated. NOTE: It is recommended that you use Intelligent Mirroring to create RAID 10 across enclosures for simple and optimum configuration.
Create Virtual Disk Advanced Wizard (Step 2) Depending on the RAID level you selected in the Create Virtual Disk Wizard (Step 1) page, the Create Virtual Disk Advanced Wizard (Step 2 of 3) - page displays the disks and connectors (channels or ports) available for configuring the virtual disk. NOTE: If you are creating an encrypted virtual disk, only the encrypted physical disks are displayed. Else, both encrypted and unencrypted physical disks are displayed.
• Select All Disks check box — Enables you to select all the physical disks in all the enclosures. • Enclosure check box — Enables you to select all physical disks in the enclosure. NOTE: The Select All and Enclosure check boxes enable you to edit spans after selecting the physical disks that comprise them. You can remove a span and specify a span again with different physical disks before proceeding.
Create Virtual Disk Advanced Wizard (Step 3) The Create Virtual Disk Advanced Wizard (Step 3 of 3) - page is displays the summary of attributes of the selected RAID level. The attributes include Bus Protocol, Stripe Element Size, Read Policy and the selected physical disk. The default values of the virtual disk attributes excluding the RAID level are recommended for the selected RAID level. 1 Enter a name for the virtual disk in the Name text box.
displayed near the Size text box. In some cases, the virtual is slightly larger than the size you specify. The Create Virtual Disk Wizard adjusts the size of the virtual disk to avoid rendering a portion of the physical disk space unusable. 3 Select a stripe size from the Stripe Element Size drop-down list. The stripe size refers to the amount of space that each stripe consumes on a single disk.
The message displays the ID(s) of the spun down drive(s). Click Go Back To Previous Page to return to Create Virtual Disk Advanced Wizard page, if you want to change your selections. Click Exit Wizard to cancel the virtual disk creation. The Create Virtual Disk Advanced Wizard (Step 3 of 3) - page displays a check box next to each physical disk that is suitable as a dedicated hot spare. Select a Physical Disk check box if you want to assign a dedicated hot spare.
The Reconfigure task enables you to change the virtual disk configuration. Using this task, you can change the RAID level and increase the virtual disk size by adding physical disks. On some controllers, you can also remove physical disks. Before continuing with the virtual disk reconfiguration, you should be familiar with the information in Starting and Target RAID Levels for Virtual Disk Reconfiguration and Capacity Expansion and Choosing RAID Levels and Concatenation.
NOTE: For PERC H310 Adapter, PERC H310 Mini Monolithic, PERC H310 Mini Blades, PERC H700, PERC H710 Adapter, PERC H710 Mini Blades, PERC H710 Mini Monolithic, PERC H710P Adapter, PERC H710P Mini Blades, PERC H710P Mini Monolithic, PERC H800, and PERC H810 Adapter controllers, if the disk group has free space available, you can expand the virtual disk capacity. To expand virtual disk capacity, click Expand Capacity. 2 Click Continue to go to the next screen or Exit Wizard if you want to cancel.
Concatenated, see Number of Physical Disks per Virtual Disk. Using Concatenated does not provide data redundancy nor does it affect the read and write performance. – Select RAID 0 for striping—This selection groups n disks together as one large virtual disk with a total capacity of n disks. Data is stored to the disks alternately so that they are evenly distributed. Data redundancy is not available in this mode. Read and write performance is enhanced.
NOTE: The PERC S100 and S300 controllers do not allow you to change the RAID level. 3 Click Continue to go to the next screen or Exit Wizard if you want to cancel. To Reconfigure a Virtual Disk (Expand Virtual Disk Capacity): Step 2 of 3 1 Enter the percentage of the free disk size available by which you want to expand the virtual disk capacity. The screen displays the maximum free size available and the description of the selected RAID level.
initialize can be completed quickly because existing information on the physical disks is not erased, although future write operations overwrite any information that remains on the physical disks. NOTE: Doing a Fast Initialize causes existing data to be inaccessible. This task should be considered data destructive. In comparison with the Slow Initialize task, the Fast Initialize task has the following advantages: • The Fast Initialize task takes less time to complete.
1 Review the virtual disk that is destroyed by the Format or Initialize and make sure that vital data is not lost. Click Blink at the bottom of the screen to blink the physical disks included in the virtual disk. 2 Depending on the task you are initiating, click the following button when ready: – Format – Initialize – Slow Initialize – Fast Initialize To exit without formatting or initializing the virtual disk, click Go Back To Virtual Disk Page.
To delete a virtual disk: To identify which physical disks are included in the virtual disk, click Blink. The LED lights on the physical disks blink for 30 to 60 seconds. When deleting a virtual disk, the following considerations apply: • There are particular considerations for deleting a virtual disk from a cluster-enabled controller. • It is recommended that you reboot the system after deleting the virtual disk.
To rename a virtual disk: 1 Type the new name in the text box. 2 Click Rename. To exit without renaming the virtual disk, click Go Back To Virtual Disk Page. To locate this task in Storage Management: 1 Expand the Storage tree object to display the controller objects. 2 Expand a controller object. 3 Select the Virtual Disks object. 4 Select Rename from the Available Tasks drop-down menu. 5 Click Execute. Virtual Disk Task: Change Policy Does my controller support this feature? See Supported Features.
Split Mirror Does my controller support this feature? See Supported Features. Use the Split Mirror task to separate mirrored data originally configured as a RAID 1, RAID 1-concatenated, or RAID 10 virtual disk. Splitting a RAID 1 or RAID 1-concatenated mirror creates two concatenated non-redundant virtual disks. Splitting a RAID 10 mirror creates two RAID 0 (striped) non-redundant virtual disks. Data is not lost during this operation.
Use the Unmirror task to separate mirrored data and restore one half of the mirror to free space. Unmirroring a RAID 1 or RAID 1-concatenated virtual disk results in a single, non-redundant concatenated virtual disk. Unmirroring a RAID 10 virtual disk results in a single, non-redundant RAID 0 (striped) virtual disk. Data is not lost during this operation. NOTE: On Linux, an Unmirror cannot be performed on a mounted virtual disk. To Unmirror: Click Unmirror.
To assign a dedicated hot spare: 1 Select the disk in the Connector (channel or port) table that you want to use as the dedicated hot spare. On some controllers, more than one disk can be selected. The disks you have selected as dedicated hot spares are displayed in the Disks currently configured as dedicated hot spare table. 2 Click Apply Changes when ready.
You can copy data from a physical disk, which is a member of a virtual disk, to another physical disk by providing a Replace Member Configuration option. You can initiate multiple copies of data from different array groups. The source physical disk should be part of a virtual disk and in the Online state. Also, the virtual disk should not be fully degraded. NOTE: You must also enable the Revertible Hot Spare option to use Replace Member Disk task.
5 Click Execute. Virtual Disk Task: Replace Member Disk (Step 2 of 2) This screen displays the summary of the attributes of the virtual disk in which you replaced the member disk. Use this screen to review your changes before completing the virtual disk replace member task. To Replace a Member Disk: Step 2 of 2 1 Review your changes. The source Physical Disk table displays details of the source physical disk. The destination Physical Disk table displays details of the destination physical disk.
Virtual Disks
14 Moving Physical and Virtual Disks from One System to Another This section describes how to move physical and virtual disks from one system to another. Required Conditions This section applies to PERC 5/E and PERC 5/i, and SAS 5/iR Controllers After some planning and preparation, it is possible to migrate physical and virtual disks from one controller, enclosure or server to another.
Migrating SAS Virtual Disks to Another System The following describes how to migrate virtual disks and volumes from one system to another. 1 Turn off the system that the physical disks are being moved from. 2 If the receiving controller does not have a preexisting virtual disk configuration, then turn off its server. 3 Place the physical disks into the new enclosure. 4 Start up the system connected to the receiving controller.
15 Protecting Your Virtual Disk with a Hot Spare When you create a redundant virtual disk using a RAID controller, you have the opportunity to maintain system operations even when a disk fails. To do so, you would assign a hot spare to the virtual disk. When a disk fails, the redundant data is rebuilt onto the hot spare without interrupting system operations. Understanding Hot Spares A hot spare is an unused backup physical disk that can be used to rebuild data from a redundant virtual disk.
The Hot Spare Protection Policy provides you with a higher protection level for the virtual disks by enabling you to specify the number of dedicated/global hot spares to be assigned to the virtual disks/controller. You can also specify the severity levels for the protection policy. Storage Management sends alerts when the hot spare protection policy is violated. Storage Management does not provide a default policy; however, you can determine the hot spare protection policy best suited for your environment.
Global Hot Spare Protection Policy Table 15-2. Property Global Hot Spare Properties Definition Enable Global Hot Spare Enables the Global Hot Spare Protection Policy. Minimum Number of Disks Displays the minimum number of physical disks to be assigned as global hot spares for the controller. Severity Level Displays the severity level that you must assign to the generated alert, if the Global Hot Spare policy is violated.
• Enclosure affinity settings for a global/dedicated hot spare are not automatically set when you upgrade to version 6.1. Enclosure affinity settings for a global/dedicated hot spare are not automatically set when you import a foreign virtual disk.
A dedicated hot spare can only be assigned to the set of virtual disks that share the same physical disks. A global hot spare is assigned to all redundant virtual disks on the controller. A global hot spare must be the same size (or larger) as the smallest physical disk included in any virtual disk on the controller.
Considerations for Hot Spares on S100, and S300 Controllers For the S100, and S300 controllers, a hot spare is assigned to a virtual disk. When a physical disk fails, only the portion of the physical disk containing the virtual disk is rebuilt onto the hot spare. Data or space on the physical disk not included in the virtual disk are not rebuilt. On the S100, and S300 controllers, individual physical disks may be included in more than one virtual disk.
• When removing a physical disk that is assigned as a global hot spare, unassign the hot spare before removal and reassign another physical disk as the global hot spare. • Immediately replace any physical disk that has failed or been removed. This ensures that a healthy disk resides in a slot that the controller firmware assumes is a hot spare.
Protecting Your Virtual Disk with a Hot Spare
CacheCade Using Solid State Drives 16 CacheCade is used to improve random read performance of the Hard Disk Drive (HDD) based Virtual Disks. A solid-state drive (SSD) is a data storage device that uses solid-state memory to store persistent data. SSDs significantly increase the I/O performance (IOPS) and/or write speed in Mbps from a storage device. With Storage Controllers, you can create a CacheCade using SSDs. The CacheCade is then used for better performance of the storage I/O operations.
• The total amount of cache pool with a CacheCade is 512 GB. If you create a CacheCade which is larger than 512 GB, the storage controller still uses only 512 GB. • The CacheCade is supported only on H710P, H800, and H810 controllers with 1 GB NVRAM. • In a storage enclosure, the total number of logical devices including virtual disks and CacheCade(s) cannot exceed 64.
17 Troubleshooting This section contains troubleshooting procedures for common situations as well as for specific problems. Common Troubleshooting Procedures This section describes commands and procedures that can be used in troubleshooting.
System Requirements Make sure that the system meets all system requirements. In particular, verify that the correct levels of firmware and drivers are installed on the system. For more information on drivers and firmware, see Drivers and Firmware. Drivers and Firmware Storage Management is tested with the supported controller firmware and drivers. In order to function properly, the controller must have the minimum required version of the firmware and drivers installed.
Replacing a Failed Disk You may need to replace a failed disk in the following situations: • Replacing a Failed Disk that is Part of a Redundant Virtual Disk • Replacing a Failed Physical Disk that is Part of a Non-Redundant Virtual Disk Replacing a Failed Disk that is Part of a Redundant Virtual Disk If the failed disk is part of a redundant virtual disk, then the disk failure should not result in data loss.
Replacing a Failed Physical Disk that is Part of a Non-Redundant Virtual Disk If the failed physical disk is part of a non-redundant virtual disk (such as RAID 0), then the failure of a single physical disk causes the entire virtual disk to fail. To proceed, you need to verify when your last backup was, and if there is any new data that has been written to the virtual disk since that time. If you have backed up recently and there is no new data on the disks that would be missed, you can restore from backup.
Recovering from Removing the Wrong Physical Disk If the physical disk that you mistakenly removed is part of a redundant virtual disk that also has a hot spare, then the virtual disk rebuilds automatically either immediately or when a write request is made. After the rebuild has completed, the virtual disk no longer has a hot spare since data has been rebuilt onto the disk previously assigned as a hot spare. In this case, you should assign a new hot spare.
• Cannot Create a Virtual Disk • Virtual Disk Errors on Linux • Problems Associated With Using the Same Physical Disks for Both Redundant and Non-Redundant Virtual Disks A Rebuild Does Not Work A rebuild does not work in the following situations: 262 • The virtual disk is non-redundant—For example, a RAID 0 virtual disk cannot be rebuilt because RAID 0 does not provide data redundancy.
A Rebuild Completes with Errors In some situations, a rebuild may complete successfully while also reporting errors. This may occur when a portion of the disk containing redundant (parity) information is damaged. The rebuild process can restore data from the healthy portions of the disk but not from the damaged portion. When a rebuild is able to restore all data except data from damaged portions of the disk, it indicates successful completion while also generating alert 2163.
• The controller may be performing other tasks, such rebuilding a physical disk, that must run to completion before the controller can create the new virtual disk. A Virtual Disk of Minimum Size is Not Visible to Windows Disk Management If you create a virtual disk using the minimum allowable size in Storage Management, the virtual disk may not be visible to Windows Disk Management even after initialization.
Problems Associated With Using the Same Physical Disks for Both Redundant and Non-Redundant Virtual Disks When creating virtual disks, you should avoid using the same physical disks for both redundant and non-redundant virtual disks. This recommendation applies to all controllers. Using the same physical disks for both redundant and non-redundant virtual disks can result in unexpected behavior including data loss.
Physical Disk is Offline or Displays an Error Status A physical disk may display an error status if it has been damaged, taken offline, or was a member of a virtual disk that has been deleted or initialized. The following actions may resolve the error condition: • If a user has taken the disk offline, then return the disk to Online status by executing the Online disk task. • Rescan the controller. This action updates the status of storage objects attached to the controller.
• I/O If you receive an alerts 2146 through 2150 as the result of doing a rebuild or while the virtual disk is in a degraded state, then data cannot be recovered from the damaged disk without restoring from backup. If you receive alerts 2146 through 2150 under circumstances other than a rebuild, then data recovery may be possible. The following describes each of these situations.
A Task Menu Option is Not Displayed You may notice that the task menus do not always display the same task options. This is because Storage Management only displays those tasks that are valid at the time the menu is displayed. Some tasks are only valid for certain types of objects or at certain times. For example, a Check Consistency task can only be performed on a redundant virtual disk. Similarly, if a disk is already offline, the Offline task option is not displayed.
Storage Management May Delay Displaying Storage Devices After Reboot Storage Management requires time after a reboot to find and inventory all attached storage devices. You may experience a delay in storage controllers being displayed until this operation has completed. You are Unable to Log into a Remote System Access can be denied here if you do not enter a user name and password that match an administrator account on the remote computer or if you mistype the login information.
Physical Disks Display Under Connector Not Enclosure Tree Object Storage Management polls the status of physical disks at frequent intervals. When the physical disk is located in an enclosure, Storage Management uses the data reported by the SCSI Enclosure Processor (SEP) to ascertain the status of the physical disk.
Device driver is not installed Solution: 1 Contact your service provider for downloading the latest PCIe SSD driver. 2 Open Device Manager and double-click on Other Devices where the PCIe device is seen with a yellow mark. 3 Right-click and install the driver on the instance. For more information on possible error conditions with your PCIe SSD, see the system specific Owner's Manual.
Troubleshooting
Frequently Asked Questions 18 This section provides frequently asked questions that address situations commonly experienced in a storage environment. Why is a Rebuild not Working? For more information, see A Rebuild Does Not Work.
How do I Recover from Removing the Wrong Physical Disk? For more information, see Recovering from Removing the Wrong Physical Disk. How do I Identify the Firmware Version that is installed? The controller’s properties information displays the firmware version that is installed on the controller. From the Storage tree view object, you can display the firmware version for all controllers attached to the system.
3 To display more information about a particular controller including its tasks, click the controller’s name in the Name column on the Information/Configuration subtab. This action displays the controller’s Information/Configuration subtab. The Information/Configuration subtab displays information about the controller’s components and enables you to execute the controller tasks.
Frequently Asked Questions
A Supported Features Different controllers support different features. The tasks displayed by the Storage Management menus and other features vary depending on whether the controller supports the feature. This appendix identifies the features that each controller supports. For more information, see your hardware documentation.
Table A-1.
Table A-1. Controller Tasks Supported on the PERC 5/ PERC 6/, and CERC 6/I Controllers Controller Task Name PERC 5/E PERC 5/i PERC 6/E PERC 6/I PERC 6/I Modular CERC 6/I Foreign Configuration No No Yes with firmware 6.1 and later Yes with firmware 6.1 and later Yes with No firmware 6.1 and later Import Preview of Foreign Configuration No No Yes with firmware 6.1 and later Yes with firmware 6.1 and later Yes with No firmware 6.
Table A-1. Controller Tasks Supported on the PERC 5/ PERC 6/, and CERC 6/I Controllers Controller Task Name PERC 5/E PERC 5/i PERC 6/E PERC 6/I PERC 6/I Modular CERC 6/I Slot Occupancy Report Yes Yes Yes Yes Yes Yes Physical Disk Firmware Version Report Yes Yes Yes Yes Yes Yes Battery Tasks Table A-2.
Physical Disk Tasks Table A-4.
Virtual Disk Tasks Table A-5.
Table A-5.
Table A-6.
Table A-6.
Supported RAID Levels Table A-7.
Table A-8.
• PERC H310 Adapter, PERC H310 Mini Monolithic, and PERC H310 Mini Blades Controllers The features comprise the following: • Controller Tasks • Battery Tasks • Connector Tasks • Physical Disk Tasks • Virtual Disk Tasks • Virtual Disk Specifications • Supported RAID Levels • Read, Write, Cache and Disk Cache Policy • Enclosure Support For enclosure-supported tasks, see Enclosure and Backplane Features. Controller Tasks Table A-10.
Table A-10.
Table A-10.
Table A-10.
Table A-10. Controller Tasks Supported on the PERC Hardware Controllers (continued) Controller Task PERC Name H800 PERC H810 Adapter PERC PERC H700 H700 Adapter/I Modular ntegrated PERC PERC H710 H710P Adapter/ Adapter Mini Monolithi c/Mini Blade PERC H310 Adapter/ Mini Blade/ Mini Monolithi c Physical Disk Yes Firmware Version Report Yes Yes Yes Yes Yes Yes Battery Tasks Table A-11.
Connector Tasks Table A-12. Controller Tasks Supported by the PERC Hardware Controllers Controller Task Name PERC PERC PERC PERC H800 H810 H700 H700 Adapter Adapter/ Modular Integrated PERC PERC H710 H710P Adapter Adapter /Mini Blade/ Mini Monolit hic PERC H310 Adapter/Mini Blade/Mini Monolithic Connector Rescan No No No No No No No Physical Disk Tasks Table A-13.
Table A-13.
Virtual Disk Tasks Table A-14.
Table A-14.
Virtual Disk Specifications Table A-15.
Table A-15.
Table A-15.
Table A-16. RAID Levels Supported by the PERC H800, PERC H700 Adapter, PERC H700 Integrated, and PERC H700 Modular Controllers RAID Level PERC PERC PERC H800 H810 H700 Adapter Adapter/I ntegrated /Modular PERC H710 Mini Blade PERC H710 PERC PERC H310 Adapter/Mini H710P Adapter/Mini Monolithic Adapter Blade/Mini Monolithic RAID 6 Yes Yes Yes Yes Yes Yes No RAID 60 Yes Yes Yes Yes Yes Yes No Read, Write, Cache and Disk Cache Policy Table A-17.
Table A-17.
• Controller Tasks • Battery Tasks • Connector Tasks • Physical Disk Tasks • Virtual Disk Tasks • Virtual Disk Specifications • Supported RAID Levels • Read, Write, Cache and Disk Cache Policy • Enclosure Support For enclosure-supported tasks, see Enclosure and Backplane Features. Controller Tasks Table A-19.
Table A-19. Controller Tasks Supported on the SAS 5/iR, SAS 6/iR, and H200 Controllers Controller Task Name SAS 5/iR SAS 6/iR PERC H200 Import/Recover Foreign Configuration No Yes Yes Set Patrol Read Mode No No No Start Patrol Read No No No Stop Patrol Read No No No Patrol Read Report No No No Check Consistency Report No No No Slot Occupancy Report Yes Yes Yes Physical Disk Firmware Version Report Yes Yes Yes Controller Reports Battery Tasks Table A-20.
Physical Disk Tasks Table A-22. Physical Disk Tasks Supported on the SAS 5/iR, SAS 6/iR, and H200 Controllers Physical Disk Task Name SAS 5/IR SAS 6/iR PERC H200 Blink/Unblink Yes Yes Yes Task only available when an enclosure or backplane and LEDs on the physical disks are present.
Virtual Disk Tasks Table A-23.
Table A-23. Virtual Disk Tasks Supported by the SAS 5/iR, SAS 6/iR, and H200 Controllers (continued) Virtual Disk Task Name SAS 5/IR SAS 6/iR PERC H200 Slow Initialize Virtual Disk No No No Cancel Initialize Virtual Disk No No No Supported RAID Levels Table A-24. RAID Levels Supported by the SAS 5/iR, SAS 6/iR, and H200 Controllers RAID Level SAS 5/IR SAS 6/iR PERC H200 RAID 0 Yes Yes Yes RAID 1 Yes Yes Yes RAID 10 No No Yes Virtual Disk Specifications Table A-25.
Table A-25.
Table A-25. Virtual Disk Specifications for the SAS 5/iR, SAS 6/iR, and PERC H200 Controllers (continued) Virtual Disk Specification SAS 5/IR SAS 6/iR PERC H200 Minimum number of physical disks in a RAID 6 NA NA NA Minimum number of physical disks in a RAID 60 NA NA NA 8 14 Maximum number of disks in 8 configured state (part of a virtual disk or hot spares) Read, Write, Cache and Disk Cache Policy Table A-26.
Enclosure Support Table A-27.
Supported Features on the PERC S100, PERC S110, and S300 Controllers This section identifies the controller-supported features and whether or not an enclosure can be attached to the controller. • Controller Tasks • Physical Disk Tasks • Virtual Disk Tasks • Virtual Disk Specifications • Supported RAID Levels • Read, Write, Cache and Disk Cache Policy • Enclosure Support Controller Tasks Table A-28.
Virtual Disk Tasks Table A-30.
Table A-31.
Table A-31. Virtual Disk Specifications for the PERC S100, PERC S110, and S300 Controllers Virtual Disk Specification PERC S100 PERC S110 PERC S300 Minimum Number of 3 Physical Disks in a RAID 5 3 3 Minimum Number of Physical Disks in a RAID 10 4 4 4 Supported RAID Levels Table A-32.
Table A-33.
• Virtual Disk Tasks • Enclosure Support For enclosure-supported tasks, see Enclosure and Backplane Features. Controller Tasks Table A-35.
Battery Tasks Table A-36. Battery Tasks Supported on the Non-RAID Controllers Battery Task Name Non-RAID SCSI Non-RAID SAS Recondition Battery No No Start Learn Cycle No No Delay Learn Cycle No No Connector Tasks Table A-37. Connector Tasks Supported on the Non-RAID Controllers Connector Task Name Non-RAID SCSI Non-RAID SAS Connector Rescan No No Physical Disk Tasks Table A-38.
Table A-38. Physical Disk Tasks Supported on the Non-RAID Controllers (continued) Physical Disk Task Name Non-RAID SCSI Non-RAID SAS Cancel Clear No No Virtual Disk Tasks Table A-39.
Table A-39. Virtual Disk Tasks Supported by the Non-RAID Controllers (continued) Virtual Disk Task Name Non-RAID SCSI Non-RAID SAS Restore Dead Disk Segments No No Initialize Virtual Disk No No Fast Initialize Virtual Disk No No Slow Initialize Virtual Disk No No Cancel Initialize Virtual Disk No No Enclosure Support Table A-40.
Enclosure and Backplane Tasks Table A-41. Enclosure Tasks for controllers Enclosure Tasks MD1000 Storage MD1120 MD1200 Storage MD1220 Enable Alarm Yes Yes Yes Yes Disable Alarm Yes Yes Yes Yes Set Temperature Probe Values Yes Yes Yes Yes Set Asset Data (includes asset tag and asset name) Yes Yes Yes Yes Blink Enclosure Yes Yes Yes Yes Yes Yes Yes Yes Controller Reports Slot Occupancy Report Maximum Supported Configuration Table A-42.
Supported Features
B Determining the Health Status for Storage Components The tables in this appendix indicate how the status of lower-level storage components is “rolled up” into the combined status displayed for the controller or other higher-level component. The examples provided by these tables do not cover all scenarios, but they do indicate how status is rolled up when a particular component is in a healthy, degraded, or failed state. Health Status Rollup: Battery is Charging or Dead Table B-1.
Health Status Rollup: Physical Disks in a Virtual Disk are Failed or Removed Table B-2. Health Status Rollup: Physical Disks in a Virtual Disk are Failed or Removed (Enclosures Not Included) Storage Controlle Battery Subsyste r m Connect Physical Firmwar Virtual or Disk(s) e/ Disk(s) Driver Compon ent Status Health Rollup Health Status Rollup: Physical Disks in a Virtual Disk are Unsupported, Partially or Permanently Degraded Table B-3.
Table B-3. Health Status Rollup: Physical Disks in a Virtual Disk are Unsupported, Partially or Permanently Degraded (Enclosures Not Included) Storage Controlle Battery Subsyste r m Connect Physical Firmwar Virtual or Disk(s) e/ Disk(s) Driver Health Rollup Health Status Rollup: All Physical Disks in a Virtual Disk are in Foreign State Table B-4.
Health Status Rollup: Some Physical Disks in a Virtual Disk are in Foreign State Table B-5. Health Status Rollup: Some Physical Disks in a Virtual Disk are in Foreign State (Enclosures Not Included) Storage Controlle Battery Subsyste r m Connect Physical Firmwar Virtual or Disk(s) e/ Disk(s) Driver Compon ent Status Health Rollup Health Status Rollup: Virtual Disk is Degraded; Physical Disks are Failed or Rebuilding Table B-6.
Table B-6. Health Status Rollup: Virtual Disk is Degraded; Physical Disks are Failed or Rebuilding (Enclosures Not Included) Storage Controlle Battery Subsyste r m Connect Physical Firmwar Virtual or Disk(s) e/Driver Disk(s) Health Rollup Health Status Rollup: Virtual Disk is Failed Table B-7.
Health Status Rollup: Unsupported Firmware Version Table B-8. Health Status Rollup: Unsupported Firmware Version (Enclosures Not Included) Storage Controlle Battery Subsyste r m Connect Physical Firmwar Virtual or Disk(s) e/Driver Disk(s) Compon ent Status Health Rollup Health Status Rollup: Enclosure Power Supply Failed or Power Connection Removed Table B-9.
Health Status Rollup: One Enclosure Fan is Failed Table B-10. Health Status Rollup: One Enclosure Fan is Failed Storage Controlle Connect Enclosur Enclosur Virtual Subsyste r or e e Fan Disks m Physical Disks Compon ent Status Health Rollup NA NA NA Health Status Rollup: One Enclosure EMM is Failed Table B-11.
Health Status Rollup: One Enclosure Temperature Probe is Failed Table B-12. Health Status Rollup: One Enclosure Temperature Probe is Failed Storage Controlle Connect Enclosur Enclosur Virtual Subsyste r or e e Disks m Temperat ure Probe Physical Disks Compon ent Status Health Rollup NA Health Status Rollup: Lost Both Power Connections to the Enclosure Table B-13.
Table B-13. Health Status Rollup: Lost Both Power Connections to the Enclosure Storage Controlle Connect Enclosur All Virtual Subsyste r or e Enclosur Disks m e Compone nts Health Rollup NA NA Physical Disks NA Health Status Rollup: One or More Physical Disks are Failed Table B-14.
Health Status Rollup: Physical Disk is Rebuilding Table B-15.
