Dell OpenManage 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. © 2013 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 . . . . . . . . . . . . . . . . . . . 23 24 . . 24 Supported Controllers . . . . . . . . . . . . . . . . . . 24 Supported Enclosures . . . . . . . . . . . . . . . . . . 26 . . . . . . 26 . . . . . . . . . . . . . . . . . . . .
Common Storage Tasks 3 . . . . . . . . . . . . . . . . . Understanding RAID Concepts What Is RAID? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 . . . . . . . . . . . . . . . . . . . . 35 Organizing Data Storage for Availability and Performance . . . . . . . . . . . . . . . . . . . . . . . 35 . . . . . . . 37 . . . . . . . . . . . . . . . . . . . 37 Choosing RAID Levels and Concatenation Concatenation RAID Level 0 (Striping) . . . . . .
4 Quick Access to Storage Status and Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 . . . . . . . . 57 . . . . . . . . . . . . . . . . . . . . . 57 Storage Dashboard and Storage Health. Storage Health . . . . . . . . . . . . . . . 58 . . . . . . . . . . . . . . . . . . . . . . 58 Hot Spare Protection Policy . Select Report. Storage Component Severity . . . . . . . . . . . . . . . . . . . . . . 59 . . . . . . . . . . . . . . . . . . . . .
Physical Device Properties . . . . . . . . . . . . . . . 67 . . . . . . . . . . . . . . . . . 70 Blink and Unblink . . . . . . . . . . . . . . . . . . 70 Full Initialization . . . . . . . . . . . . . . . . . . . 71 Physical Device Tasks . Prepare to Remove Export Log . . . . . . . . . . . . . . . . . . 71 . . . . . . . . . . . . . . . . . . . . . 71 Add PCIe SSDs to Fluid Cache Pool . . . . . . . . 72 . . . . . . . . . . . . . . 73 . . . . . . . . . . . . . . . . . . . . .
Storage Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 . . . . . . . . . . . . . . . . . . . . . . . 91 Storage Components . 8 Controllers . 87 What is a Controller? . . . . . . . . . . . . . . . . . . RAID Controller Technology: SCSI, SATA, ATA, and SAS . . . . . . . . . . . . . . . . . . . . . RAID Controller Features 91 . . . . 92 . . . . . . . . . . . . . . . . 93 Controller-supported RAID Levels . . . . . . . . . . . .
Firmware/Driver Versions . . . . . . . . . . . . . . . . . . . . . . . . . . 102 . . . . . . . . . . . . . . . . . . . 104 Firmware/Driver Properties . Controller Health . Controller Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Controller Components . . . . . . . . . . . . . . 105 . . . . . . . . . . . 106 . . . . . . . . . . . . . . . 106 . . . . . . . . . . . . . . . . . 111 Controller Properties Controller Tasks . Available Reports . Set Rebuild Rate . . .
Set Patrol Read Mode Start and Stop Patrol Read . . . . . . . . . . . . . 141 . . . . . . . . . . . . . . . 144 . . . . . . . . . . . . . 144 . . . . . . . . . . . . . . . . . 145 . . . . . . . . . . . . . . . . . . . 146 Manage Preserved Cache Manage Encryption Key Creating an Encryption Key and Enabling LKM . . . . . . . . . . . . . . . . . . . . Manage CacheCade . . . . . . 146 . . . . . . . . . . . . . . . . . . 148 Creating a CacheCade 149 . . . . . . . . . . . . . . .
Enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 . . . . . . . . . . . . . . . . . . 156 Enclosure Physical Disks Enclosure Fans Enclosure Power Supplies . . . . . . . . . . . . Enclosure Temperature Probes . . . . . . . . . . Enclosure Management Modules (EMMs) . SMART Thermal Shutdown Enclosure Management 156 157 . . . . . . . . . . . . . . 158 . . . . 159 . . . . . . . . . . . . . . . . 159 Enclosure and Backplane Health . . . . . . . . . . .
Set Temperature Probe Properties and Tasks 10 Connectors . . . . . . . . . . . . . . . . . . . . . . Channel Redundancy and Thermal Shutdown 179 . . . 181 . . . . . 181 Channel Redundancy on PERC 4/DC, 4e/DC, 4/Di, and 4e/Di Controllers . . . . . . . . . . . . . . . . 182 Creating a Channel-redundant Virtual Disk . . . . . . . 182 . . . . . . . . . . . . . . . . . . . . 184 Connector Health Connector Status . 185 . . . . . . . . . . . . . . . . . . . . . . . . . . 185 . . . . . . . . .
Physical Disks or Physical Devices . . . . 197 . . . . . . 197 . . . . . . . . . . . 198 Guidelines to Replace a Physical Disk or Physical Device . . . . . . . . . . . . . . Add a New Disk to Your System . . . . . . . . 199 . . . . . . . . . 199 . . . . . . . . . . . . . . . . 200 How to Avoid Removing the Wrong Disk Replacing a Physical Disk Receiving SMART Alerts . . . . . . . . . . . . Other Disk Procedures . Physical Disk or Physical Device Properties and Tasks . . . . . . . . . . . .
Full Initialization . . . . . . . . . . . . . . 217 . . . . . . . . . . . . . . . 217 Convert to RAID Capable Disk . Convert to Non-RAID Disk . 13 Virtual Disks 216 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Considerations Before Creating Virtual Disks . . . . . 220 . . . . . 222 Virtual Disk Considerations for PERC S100, S110, and S300 Controllers . . . . . . . . . Virtual Disk Considerations on Linux . . . . . 223 . . . . . . .
Virtual Disk Properties and Tasks . . . . . . . . . . . 235 . . . . . . . . . . . . . . 235 . . . . . . . . . . . . . . . . 239 Virtual Disk Properties Virtual Disk Tasks . Partitions of Virtual Disk . . . . . . . . . . . . . . . . Create Virtual Disk Express Wizard (Step 1 of 2) . . . . . . . . . . . . . . . . . . . . . . . 246 Create Virtual Disk Express Wizard (Step 2 of 2) . . . . . . . . . . . . . . . . . . . . . . . 249 Create Virtual Disk Advanced Wizard (Step 1 of 4) . . . . . . . .
Virtual Disk Task: Rename . . . . . . . . . . . . . 269 . . . . . . . . . . . . . . . . . . . . . . . 269 . . . . . . . . . . . . . . . . . . . . . . . . . 270 Virtual Disk Task: Change Policy Split Mirror . Unmirror 268 . . . . . . . . . . . . . . . . . . . . . 271 Virtual Disk Task: Replace Member Disk (Step 1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . 273 Virtual Disk Task: Replace Member Disk (Step 2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . 274 . . . . . . . . .
Dedicated Hot Spare Protection Policy . . . . . Resetting the Hot Spare Protection Policy . Global Hot Spare Protection Policy . . . . 282 . . . . . . . 283 Considerations for Hot Spare Protection Policy . . . . . . . . . . . . . . . . . . . Considerations for Enclosure Affinity . . . . . 283 . . . . . . 283 Considerations for Hot Spares on PERC 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, PERC 5/E, PERC 5/i, PERC 6/E, PERC 6/I, and CERC 6/I Controllers . . . . Dedicated Hot Spare Considerations . .
18 Troubleshooting . . . . . . . . . . . . . . . . . . . Common Troubleshooting Procedures 293 . . . . . . . . . 293 . . . . . . . . . . . . . 293 System Requirements. . . . . . . . . . . . . . . . 294 Drivers and Firmware . . . . . . . . . . . . . . . . 294 Cables Attached Correctly Isolate Hardware Problems . . . . . . . . . . . . Rescan to Update Information on SCSI Controllers . . . . . . . . . Replacing a Failed Disk . 294 . . . . . . . . . 294 . . . . . . . . . . . . . .
Receive a “Bad Block” Alert with “Replacement,” “Sense,” or “Medium” Error . . . . . . . . . . . 305 Read and Write Operations Experience Problems . . . . . . . . . . . . . . . . . . . . . I/O Stops When a Redundant Channel Fails A Task Menu Option is Not Displayed . . . 306 . . . . . . 306 A Corrupt Disk or Drive Message Suggests Running autocheck During a Reboot . . . . . . . Erroneous Status and Error Messages after a Windows Hibernation . . . . . . . . . . . .
A Supported Features . . . . . . . . . . . . . . . . Supported Features on the PERC 4/ Controllers . . . . . 317 . . . . . . . . . . . . . . . . . . 317 . . . . . . . . . . . . . . . . . . . 319 Controller Tasks . Battery Tasks . Connector Tasks . . . . . . . . . . . . . . . . . . Physical Disk Tasks . Virtual Disk Tasks . . . . . . . . . . . . . . . . . 320 321 Supported RAID Levels . . . . . . . . . . . . . . 323 . . . . . . . . . . . . . .
Enclosure Support . . . . . . . . . . . . . . . . Supported Features on the PERC Hardware Controllers . . . . . . . . . . . . . . . . . . . . . . . 346 . . . . . . . . . . . . . . . . . 347 . . . . . . . . . . . . . . . . . . . 350 Controller Tasks . Battery Tasks Connector Tasks . . . . . . . . . . . . . . . . . Physical Disk Tasks . Virtual Disk Tasks . . . . . . . . . . . . . . . . 351 353 Supported RAID Levels . . . . . . . . . . . . . 355 . . . . . . . . . . . . .
Supported Features on the Non-RAID Controllers . . . 372 . . . . . . . . . . . . . . . . . . 373 . . . . . . . . . . . . . . . . . . . 374 Controller Tasks . Battery Tasks . Connector Tasks 374 . . . . . . . . . . . . . . . . . . Physical Disk Tasks . . . . . . . . . . . . . . . . . 374 Virtual Disk Tasks . . . . . . . . . . . . . . . . . . 375 Enclosure Support . . . . . . . . . . . . . . . . . 376 Enclosure and Backplane Features . . . . . . . . . . .
Health Status Rollup: Unsupported Firmware Version . . . . . . . . . . . . . . . . . . . . . . . . . Health Status Rollup: Enclosure Power Supply Failed or Power Connection Removed . . . . . Health Status Rollup: One Enclosure Fan is Failed . . . . . . . . . . . . . . . . . . . . . . . . 386 . . . . . 387 Health Status Rollup: One Enclosure EMM is Failed . . . . . . . . . . . . . . . . . . . . . . . . . . Health Status Rollup: One Enclosure Temperature Probe is Failed . . . . . . . . . . . . . . .
1 Overview Dell OpenManage Server Administrator Storage Management provides enhanced features for configuring a system's locally-attached RAID and nonRAID 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.
Before Installing Storage Management The following sections describe considerations for installing Storage Management. Version Requirements for Controller Firmware and Drivers In order for Storage Management to function properly, the controllers must have the minimum required version of the firmware and drivers installed. The firmware and drivers listed in the Dell OpenManage Server Administrator Readme refer to the minimum supported version for these controllers.
• PERC 5/E • PERC 5/i Integrated and PERC 5/i Adapter • SAS 5/iR Integrated and SAS 5/iR Adapter • PERC 6/E • PERC 6/I Integrated and PERC 6/I Adapter • PERC 6/I Modular • CERC 6/I controller • SAS 6/iR controller • PERC S100, PERC S110, and S300 • PERC H200 Adapter, PERC H200 Integrated, and PERC H200 Modular • PERC H800 Adapter, PERC H700 Adapter, PERC H700 Integrated, and PERC H700 Modular • PERC H310 Adapter, PERC H310 Mini Monolithic, PERC H310 Mini Blades, PERC H710 Adapter, PER
Supported Enclosures This release of Storage Management supports the following enclosures: • Dell PowerVault 20xS and 21xS storage systems • PowerVault 220S and 221S storage systems • PowerVault MD1000 and MD1120 storage system • PowerVault MD1200 and MD1220 storage system Support for Disk and Volume Management Storage Management does not provide disk and volume management.
2 Getting Started Dell OpenManage 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 Dell OpenManage 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 Dell OpenManage Server Administrator User’s Guide.
User Privileges Server Administrator provides security through the User, Power User, and Administrator user groups. Each user group is assigned a different level of access to the Server Administrator features. 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.
Drop-down Menus and Wizards for Running Tasks Many of the storage objects displayed in the tree view have tasks. Examples of these tasks include creating virtual disks, assigning hot spares, reconditioning a battery, and so on. To access a storage object’s task, select the component in 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.
Common Storage Tasks This section provides links to information describing commonly performed storage tasks. • • Create and configure virtual disks (RAID configuration) For more information, see: – Create Virtual Disk Express Wizard (Step 1 of 2)—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.
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.
Hardware and Software RAID RAID can be implemented with either hardware or software. A system using hardware RAID has a RAID controller that implements the RAID levels and processes data reads and writes to the physical disks. When using software RAID provided by the operating system, the operating system implements the RAID levels. For this reason, using software RAID by itself can slow system performance.
• Stripe size—The total disk space consumed by a stripe not including a parity disk. 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 size is 64KB and the stripe element size is 16KB. • Stripe element—A stripe element is the portion of a stripe that resides on a single physical disk. • Stripe element size—The amount of disk space consumed by a stripe element.
When choosing concatenation or a RAID level, the following performance and cost considerations apply: • Availability or fault-tolerance—Availability or fault-tolerance refers to a system’s ability to maintain operations and provide access to data even when one of its components has failed. In RAID volumes, availability or fault-tolerance is achieved by maintaining redundant data. Redundant data includes mirrors (duplicate data) and parity information (reconstructing data using an algorithm).
Choosing RAID Levels and Concatenation You can use RAID or concatenation to control data storage on multiple disks. Each RAID level or concatenation has different performance and data protection characteristics.
When a physical disk in a concatenated or spanned volume fails, the entire volume becomes unavailable. Because the data is not redundant, it cannot be restored by rebuilding from a mirrored disk or parity information. Restoring from a backup is the only option. Because concatenated volumes do not use disk space to maintain redundant data, they are more cost-efficient than volumes that use mirrors or parity information.
Related Information: • Organizing Data Storage for Availability and Performance • Controller-supported RAID Levels • Number of Physical Disks per Virtual Disk • Maximum Number of Virtual Disks per Controller RAID Level 0 (Striping) RAID 0 uses data striping, which is writing data in equal-sized segments across the physical disks. RAID 0 does not provide data redundancy. Figure 3-2.
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.
Figure 3-3. Mirroring Disks RAID 1 Characteristics: • Groups n + n disks as one virtual disk with the capacity of n disks. The controllers currently supported by Storage Management allow the selection of two disks when creating a RAID 1. Because these disks are mirrored, the total storage capacity is equal to one disk. • Data is replicated on the two disks. • When a disk fails, the virtual disk still works. The data is read from the failed disk’s mirror.
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.
RAID 5 Characteristics: • Groups n disks as one large virtual disk with a capacity of (n-1) disks. • Redundant information (parity) is alternately stored on all disks. • 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: 44 • 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.
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 50 (Striping over RAID 5 sets) RAID 50 is striping over more than one span of physical disks.
Figure 3-6. RAID 50 RAID 50 Characteristics: 46 • 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.
NOTE: On the PERC 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, and 4e/Di controllers, there are special considerations when implementing RAID 50 on a disk group that has disks of different sizes. For more information, see Considerations for RAID 10 and 50 on PERC 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, and 4e/Di.
Figure 3-7. RAID 60 RAID 60 Characteristics: 48 • 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.
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.
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 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.
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 Considerations for RAID 10 and 50 on PERC 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, and 4e/Di On the PERC 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, and 4e/Di controllers, there are special considerations when implementing RAID 10 or RAID 50 on a disk group tha
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. For information on all RAID levels supported by Storage Management, see Choosing RAID Levels and Concatenation. Table 3-1.
Table 3-1. RAID Level and Concatenation Performance Comparison (continued) RAID Level Data Read Write Rebuild Minimum Availability Performance Performance Performance Disks Required Suggested Uses RAID 10 Excellent Very Good Fair Good 2N x X Dataintensive environment s (large records) RAID 50 Good Very Good Fair Fair N+2 (N = at least 4) Mediumsized transactional or dataintensive uses RAID 6 Excellent Sequential Fair, unless Poor 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.
• Select the controller and investigate the status of the lower-level components. For more information, see Storage Component Severity. • 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.
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.
• Power Supply Properties • 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.
Using Enclosure Temperature Probes Physical disk enclosures have temperature probes that warn you when the enclosure has exceeded an acceptable temperature range.
Related Information: • I/O and Reboot Requirements for Detecting Physical Disk Status Changes • 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.
healthy. Once the communication path is restored, reboot the system to update the disk status. If the communication path is not restored, then Storage Management does not display the storage objects after the reboot.
Quick Access to Storage Status and Tasks
PCI Express Solid-State Device Support 5 This section gives an overview of the OpenManage 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 Device Life Status Displays the life status of the PCIe SSD. The device life status is determined by the following attributes: Percent Lifetime Used — This attribute is determined by the elapsed time since the start of use (up to three years) or percentage of total bytes written (TBW). Write Protect Progress — This attribute is determined by the reduction in number of available spare sectors.
Table 5-3. Physical Device Properties Properties Description Approaching Read Only — The drive is running out of spare sectors and is reaching the read-only mode. However, the health status of the drive is good and data retention is unaffected. The drive is stated to be approaching the readonly mode if the value for percent lifetime used is less than 100 percent and that for write protect progress is greater than or equal to 90 percent. Read Only — The drive is in read-only mode.
Table 5-3. Physical Device Properties Properties Description Capable Speed Displays the highest possible speed at which the device can transfer data Fluid Cache Pool Member Indicates whether the PCIe SSD is a part of a Fluid Cache pool or not.
Full Initialization CAUTION: Performing a full initialization on a PCIe SSD overwrites all blocks and will result in permanent loss of all data on the PCIe SSD. NOTE: During full initialization, the host is unable to access the PCIe SSD. NOTE: If the system reboots or experiences a power loss during full intialization, the operation aborts. You must reboot the system and restart the process.
Add PCIe SSDs to Fluid Cache Pool You can configure or increase the capacity of the Fluid Cache pool by adding PCIe SSDs to them. To add a PCIe SSD to a cache pool: 1 On the left-hand side of the Storage Management page, click Storage PCIe SSD SubSystem Enclosure (Backplane) Physical Devices. The Physical devices on PCIe SSD SubSystem page is displayed with the available list of physical disks.
3 Click Execute to remove the PCIe SSD. The following message is displayed. Device will be removed from Fluid Cache Pool. Are you sure you want to proceed? 4 Click OK. Once the device removal is initiated from the cache pool, any dirty data is moved to the back-end disk. While the data migration is in progress, OMSS displays a transient removal state. After the device is removed from the cache pool, the Part of Cache Pool attribute is Not Enabled.
PCI Express Solid-State Device Support
6 Fluid Cache for DAS Fluid Cache is a server-side caching accelerator that makes high-speed express flash (PCIe SSD) a shared, distributed resource. Fluid Cache enables the caching of active data working sets from storage closer to the compute tier to enable accelerated response times for latency sensitive customer workloads using DAS external storage architectures. The Storage Management application facilitates addition of PCIe SSDs to the Fluid Cache pool.
Connect Fluid Cache: Click to refresh the Fluid Cache node information for Fluid Cache Disks and License. The Sub-System Information Fluid Cache page is displayed with the Fluid Cache and cache pool properties. Table 6-1. Fluid Cache Properties Properties Description Status Displays the status of the Fluid Cache. The possible options are: • OK • Non-critical • Critical License State Displays the status of the Fluid Cache license.
Table 6-2. Fluid Cache Disk Properties (continued) Properties Description Name Displays the name of the Fluid Cache disk. State Displays the state of the Fluid Cache. The possible options are: • Active • Failed Tasks Allows you to disable and discard a particular Fluid Cache disk. Click on Execute to complete this operation. Type Displays the type of device. The possible values are: • Virtual Disk • Partition Device Name Displays the device map name of the back-end disk.
Table 6-3. Cache Pool Properties Properties Description Cache Pool Size Displays the size of the cache pool in GiB. Cache Pool High Availability The possible options are: Cache Store Count • True — Indicates that the cache pool is writeback capable. This option is set to True when more than one PCIe SSDs are part of Fluid Cache pool. • False — Indicates that the cache pool is writethrough capable. This option is set to False when only one PCIe SSDs is part of Fluid Cache pool.
Table 6-4. Physical Device Properties (continued) Properties Description Failure Predicted Displays whether the physical disk has received a SelfMonitoring 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.
Table 6-4. Physical Device Properties (continued) Properties Description Vendor ID Displays the name of the physical device vendor. Product ID Displays the product ID of the device. Serial No. Displays the serial number of the device. Negotiated Speed Displays the speed of data transfer that the device negotiated during initial communication.
Table 6-5. Fluid Cache Disk Performance Properties Description Fluid Cache Disk Select the Fluid Cache disk from the drop-down option to view the performance information. The drop-down list contains the list of all Fluid Cache disks irrespective of the state (failed, active.) Time Interval Type the time interval for which you need to view the performance information. Time can be specified in Minutes, hours, days, weeks, and months. State Displays the state of the Fluid Cache Disk.
License Settings Use this page to view the digital license associated with the Fluid Cache. Table 6-6. License Settings Properties Description License Type Indicates the type of license. Possible values: • Evaluation —License expires after being active for certain number of days. The expiry time for this field is displayed in days. • Node license —License applicable for a limited number of nodes indicated by the Node Limit field.
To upgrade an existing license, use the Apply new license field. Click on Browse to select the stored license and click Apply to activate the license. You can upgrade the license from evaluation to node. Click on Exit Wizard to go back to the Information Configuration page.
Fluid Cache for DAS
Storage Information and Global Tasks 7 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 7-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.
If the enclosure has virtual disks that are channel-redundant, then the enclosure can be turned off while redundant data continues to be available on another channel. For more information, see Channel Redundancy and Thermal Shutdown. NOTE: Only SCSI controllers support Smart Thermal Shutdown. To enable or disable thermal shut down: 1 Select the Storage tree view object. 2 Click the Information/Configuration subtab.
Table 7-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 Dell OpenManage Server Administrator Readme refer to the minimum supported version for these controllers. Later versions of the firmware and drivers are also supported.
Property Definition Cluster Mode This property indicates whether the controller is part of a cluster configuration. 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.
8 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. SCSI RAID Controllers PERC 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, and 4e/Di RAID controllers use Small Computer System Interface (SCSI) technology.
• PERC H200, H700, and H800 controllers • PERC H310 Adapter, PERC H310 Mini Monolithic, PERC H310 Mini Blades, PERC H710 Adapter, PERC H710 Mini Blades, PERC H710 Mini Monolithic, PERC H710P Adapter, PERC H710P Mini Blades, PERC H710P Mini Monolithic, and PERC H810 Adapter controllers RAID Controller Features Different controllers have different features.
• Read, write, and cache policies—The manner in which a controller reads and writes data can vary. The read, write, and cache policies have implications for data encryption and system performance. See RAID Controller Read, Write, Cache, and Disk Cache Policy. • Check consistency—A check consistency determines the integrity of a virtual disk’s redundant data. When necessary, this feature rebuilds the redundant information. See Maintain Integrity of Redundant Virtual Disks.
RAID Controller Read, Write, Cache, and Disk Cache Policy When creating a virtual disk, you specify the read, write, and cache policies for the virtual disk. The following sub-section describes these policies. NOTE: Read, write, and cache policies are not supported on the CERC SATA1.5/2s controller. Read Policy Does my controller support this feature? See Supported Features The read policies indicate whether or not the controller should read sequential sectors of the virtual disk when seeking data.
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. In cluster mode, the PERC 4/DC and 4e/DC controllers only allow write-through caching.
• 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.
Updating the Display of Clustered Resources This section applies to PERC 4/DC and 4e/DC controllers After a failover of cluster resources, it is necessary to perform a rescan operation in order for Storage Management to display the most up-to-date information about shared resources.
3 Create or delete the virtual disk on system A. For more information on creating and deleting virtual disks, see: – Considerations Before Creating Virtual Disks – Creating Virtual Disks – Virtual Disk Task: Delete 4 Reboot system A. 5 Restart system B. Integrated Mirroring and the PERC 4/IM Controller The PERC 4/IM controller enables you to mirror a physical disk that resides internally in the server.
Background Initialization on PERC Controllers On PERC controllers, background initialization of a redundant virtual disk begins automatically within 0 to 5 minutes after the virtual disk is created. The background initialization of a redundant virtual disk prepares the virtual disk to maintain redundant data and improves write performance. For example, after the background initialization of a RAID 5 virtual disk completes, the parity information has been initialized.
• SAS 5/i Integrated • SAS 5/E • SAS 6Gbps Adapter Firmware/Driver Versions Use this window to view information about the controller firmware and drivers. For more information on firmware and drivers, see Before Installing Storage Management. 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.
Table 8-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 8-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 8-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 State This property displays the current status of the controller. Possible values are: Ready—The controller is functioning normally. Degraded—The controller has encountered a failure and is operating in a degraded state. Failed—The controller has encountered a failure and is no longer functioning. Firmware Version This property displays the version of the firmware that is currently installed on the controller.
Property Definition Number of Connectors This property displays the number of connectors the controller has. Each connector can be attached to physical disks or an enclosure. Depending on the controller type, the connector can be either a SCSI channel or a SAS port. 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.
Property Definition Loadbalance This property provides the ability to automatically use both controller ports or connectors connected to the same enclosure to route I/O requests. This property is available only on SAS controllers that have controller firmware version 6.1 and later. For more information, see Redundant path view. 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.
Property Definition Patrol Read Mode This property displays the Patrol Read mode setting for the controller. Possible values are: Auto—When set to Auto, a Patrol Read runs continuously on the system. When one iteration of the Patrol Read is complete, the next Patrol Read is scheduled to start within a period of time specified by the controller. You do not have the option of manually starting or stopping the Patrol Read in Auto mode.
Property Definition Cluster Mode This property indicates whether the controller is part of a cluster configuration. SCSI Initiator ID This property displays the SCSI ID of a SCSI controller. The default value is usually 7. You can change the default value in the BIOS. In cluster mode, the value is 6 or 7. The SCSI ID is not displayed on the PERC 4/IM controllers. Use the BIOS on these controllers to identify the SCSI ID.
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. If no tasks can be performed because of controller or system configuration limitations, then the Tasks drop-down menu displays No Task Available.
• 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. 4 Select a report from the Select Report drop-down menu. 5 Click Execute.
To rescan a controller: 1 Expand the tree view to display the controller object. 2 Select the Controller object. 3 Click the Configuration/Information subtab. 4 Select Rescan from the Controller 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. Create Virtual Disk Does my controller support this feature? See Supported Features.
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. NOTE: The Test Alarm task is only available on the CERC SATA1.5/6ch controller. Set Rebuild Rate Does my controller support this feature? See Supported Features. Use the Set Rebuild Rate task to change the rebuild rate. For more information, see Set Rebuild Rate.
Manage Physical Disk Power Does my controller support this feature? See Supported Features. The Manage Physical Disk Power task allows to manage the power consumed by the physical disks by spinning down the hotspares and unconfigured drives if there is no I/O activity for a specified amount of time. This option is supported with PERC H700, H800, and H310 cards. Additionally, Dell PERC H810, H710, and H710P cards support power saving configurations on unconfigured, Hot Spare, and configured disks.
To change the controller’s rebuild rate: 1 Type a numerical value in the New Rebuild Rate text box. The value must be within the 0 – 100 range. 2 Click Apply Changes. To exit and cancel your changes, click Go Back to Previous Page. 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 Rebuild Rate from the Available Tasks drop-down menu. 5 Click Execute.
To reset the controller configuration: 1 Review the virtual disks that is destroyed by resetting the controller configuration. Make backups as necessary. Click Blink at the bottom of the screen to blink the physical disks included in the virtual disks. 2 Click Reset Configuration when you are ready to erase all information on the controller. To exit without resetting the controller configuration, click Go Back to Previous Page.
To export the controller log file: Click Export Log File when ready. To exit without exporting the controller log file, click Go Back to Previous Page. 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 Export Log from the Available Tasks drop-down menu. 5 Click Execute. You can also locate this task from the Change Controller Properties drop down menu.
To avoid unlocking foreign configurations and to proceed to preview/import/clear a foreign configuration that has not been locked, click Skip or Continue. If you do not want to import/clear the foreign configurations, or in case of loss of the associated Passphrase of the corresponding Encryption Key Identifier, execute the Instant Encrypt Erase task for the physical disks. CAUTION: Executing the Instant Encrypt Erase task erases all data on the physical disk.
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 8-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 Bus Protocol This property displays the technology that the physical disk is using. Possible values are: SCSI—Small Computer System Interface SAS—Serial Attached SCSI SATA—Serial Advanced Technology Attachment (SATA) Dell Certified This property indicates that the drive has Dell firmware which has been tested and fully qualified by Dell. Drives that are not Dell certified may work but, are not supported and recommended for use in Dell servers.
Property Definition Vendor ID This property displays the disk’s hardware vendor. Product ID This property displays the disk’s product ID. Revision This property displays the drive’s firmware version. Serial No. This property displays the disk's serial number. Negotiated Speed This property displays the speed of data transfer that the disk negotiated while spinning up and upon initial communication with the controller.
Property Definition Encrypted This property displays whether the physical disk is encrypted to the controller. The possible values are Yes and No. For a non-SED the value is N/A. Part Number This property displays the unique Bill Of Materials assignment number for a physical disk. The characters 4 through 8 represent the Dell part number for that model drive. Set Background Initialization Rate Does my controller support this feature? See Supported Features.
3 Select the Information/Configuration subtab. 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.
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 Check Consistency 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.
To change the controller’s reconstruct rate: 1 Type a numerical value in the New Reconstruct Rate text box. The value must be within the 0 – 100 range. 2 Click Apply Changes. To exit and cancel your changes, click Go Back to Previous Page. 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 Reconstruct Rate from the Available Tasks drop-down menu.
PERC H800 and PERC H810 controller in a daisy-chained enclosure. For an example of a daisy chain configuration (for PERC 6/E controller.), see Figure 8-1. Figure 8-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.
Table 8-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 8-7. Table 8-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.
4 Select Manage Physical Disk Power from the Available Tasks drop-down menu. 5 Click Execute. 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.
Creating a CacheCade To create a CacheCade: 1 In the CacheCade(s) screen, click Create CacheCade. The Create CacheCade screen is displayed. 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.
Blinking and Unblinking the CacheCade In the CacheCade(s) screen, go to the CacheCade that you want to blink and select Blink... from the available Tasks. 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.
Table 8-9. CacheCade Properties Property Definition Bus Protocol This property displays the technology that the physical disk is using. Possible values are SAS and SATA. 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.
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.
Controllers 153
Controllers
Enclosures and Backplanes 9 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.
Changing the Mode on PowerVault 220S and PowerVault 221S Enclosures When toggling the bus configuration switch on a PowerVault 220S or PowerVault 221S enclosure, the enclosure should be powered off. The bus configuration switch is used to change the enclosure to split bus, joined bus, or clustered mode. If you change the PowerVault 220S or PowerVault 221S enclosure mode with the enclosure powered on, the enclosure may no longer be displayed by Storage Management and you may notice other erratic behaviors.
• If you have already removed the wrong physical disk, see Recovering from Removing the Wrong Physical Disk. • Identifying an Open Connector for the Enclosure • Checking the Enclosure’s Temperature • Verifying the Enclosure’s EMM Firmware Version 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.
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. 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 Dell 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 9-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.
Table 9-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 9-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 9-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
Connectors 10 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.
Channel Redundancy on PERC 4/DC, 4e/DC, 4/Di, and 4e/Di Controllers The following considerations apply when creating a channel-redundant virtual disk on these controllers: • It is recommended that you use a RAID 10 or RAID 50 when implementing channel redundancy on the PERC 4/DC, 4e/DC, 4/Di, and 4e/Di controllers.
Recommended RAID Levels: – PERC 4/DC, 4e/DC, 4/Di, and 4e/Di Controllers—It is recommended that you only use RAID 10 or RAID 50. 3 Complete Create Virtual Disk Advanced Wizard (Step 2 of 4). In this step, you select the channels and the disks to be used by the virtual disk. The selections you make determine whether or not the virtual disk is channelredundant. There are specific RAID level and configuration requirements for implementing channel redundancy.
6 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. 7 Repeat step 6 until you have the desired number of disks. 8 Click Continue. Connector Health This screen displays the status of the connector and the components attached to the connector. Connector Status Component status is indicated by the severity.
Table 10-1. Severity Component 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 10-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 10-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.
Connectors
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.
• Dell supports SAS and SATA drives on the same backplane but not within the same Virtual Disk. • Dell supports Solid State Disks and Hard Disk Drives on the same backplane but not within the same Virtual Disk. NOTE: With the exception of combining SAS,SATA,SCSI, and SSD drives, Dell supports upgrades and not downgrades. 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.
Related Information • If you are replacing a disk that is part of a virtual disk, see Replacing a Failed Disk. • If you want to include the new disk in a virtual disk, see Virtual Disk Considerations for Controllers or Virtual Disk Considerations for CERC SATA1.5/6ch, and CERC SATA1.5/2s 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.
2 Select the disk that is receiving SMART alerts and execute the Offline task. 3 Manually remove the 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.
Physical Disk or Physical Device Properties and Tasks Use this window to view information about physical disks or physical device and execute physical disk or physical device tasks. NOTE: Physical devices are applicable only to PCIe SSD. 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 Definition Name This property displays the name of the physical disk or device. The name is comprised of the connector number followed by the disk number. 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.
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.
On most controllers, the Blink task automatically cancels after a short duration such as 30 or 60 seconds. If you need to cancel the Blink task or if the physical disk continues to blink indefinitely, use the Unblink task. NOTE: The Blink and Unblink tasks are only supported for hotswap physical disks (disks that reside in a carrier). When using an LSI PCI-e U320 controller, the Blink and Unblink tasks apply to physical disks contained in carriers that can be inserted into a server or an enclosure.
This task causes the lights on the disk to blink. You can safely remove the disk or device under the following conditions: • Wait for about 30 seconds to allow the disk to spin down. • Wait until you notice the initial blink pattern has changed into a different pattern or the lights have stopped blinking. A physical disk or physical device is no longer in Ready state after doing a Prepare to Remove.
Rebuild Does my controller support this feature? See Supported Features. Use the Rebuild task to reconstruct data when a physical disk in a redundant virtual disk fails. For more information, see Replacing a Failed Disk that is Part of a Redundant Virtual Disk. Rebuilding a disk may take several hours. Cancel Rebuild Does my controller support this feature? See Supported Features. Use the Cancel Rebuild task to cancel a rebuild that is in progress.
NOTE: On PERC S100 and S300 controllers, if there is free space available on the global hot spare, it continues to function as a spare even after replacing a failed physical disk. See Considerations for Hot Spares on CERC SATA1.5/6ch, S100, and S300 Controllers. Global hot spares must be assigned and unassigned manually. They are not assigned to specific virtual disks.
The Online and Offline tasks only apply to physical disks that are included in a redundant virtual disk and attached to a PERC 4/SC, 4/DC, 4e/Si, 4e/Di, 4e/DC, or 4/Di controller. Use the Offline task to deactivate a disk before removing it. Use the Online task to reactivate an offline disk. In some cases, you may want to use the Online task on a failed disk in an attempt to recover data from the disk. For more information, see Using the Physical Disk Online Command on Select Controllers.
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. For more information, see Format and Initialize; Slow and Fast Initialize and Considerations for Slow Initialize. To clear the physical disk: 1 Review the physical disk to be erased by the Clear task.
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. NOTE: If the disk is not SMART-enabled or if the Auto Replace on Predictive Failure option is disabled, the failed disk is not replaced automatically.
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.
Physical Disks or Physical Devices
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.
You may also want to review the following sections: • RAID Controller Read, Write, Cache, and Disk Cache Policy • Understanding Hot Spares • Controller-supported Stripe Sizes • 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.
• Space allocation when deleting and creating virtual disks on controllers—When you delete a virtual disk, you free up or make available space on the physical disks that were being used by the deleted virtual disk. If you have created several virtual disks on a disk group, then deleting virtual disks can result in pockets of free space residing in various locations on the physical disks.
• Implementing channel redundancy—A virtual disk is channel-redundant when it maintains redundant data on more than one channel. If one of the channels fails, data is not lost because redundant data resides on another channel. For more information, see Channel Redundancy and Thermal Shutdown. • Rebuilding data—An failed physical disk that is used by both redundant and non-redundant virtual disks cannot be rebuilt.
For related information, see Considerations for CERC SATA1.5/6ch and CERC SATA1.5/2s Controllers When Physical Disks are Shared by Redundant and Non-Redundant Virtual Disks. Virtual Disk Considerations for PERC S100, S110, and S300 Controllers The following considerations apply when creating virtual disks: • Space allocation—When you create a new virtual disk, the PERC S100, PERC S110, and S300 controllers allocate the largest area of free space on the physical disks to the new virtual disk.
The support provided by your operating system depends on the version of the operating system and any updates or modifications that you have implemented. In addition, you should investigate the capacity of your peripheral devices to support a virtual disk that is larger than 1TB. For more information, see your operating system and device documentation. Number of Physical Disks per Virtual Disk There are limitations on the number of physical disks that can be included in the virtual disk.
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. This section describes how the maximum possible size for the virtual disk is calculated based on the controller type. To identify the controller type, see RAID Controller Technology: SCSI, SATA, ATA, and SAS.
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. Although a virtual disk may be created from several physical disks, it is seen by the operating system as a single disk.
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. 3 Select the Reconfigure task from the virtual disk’s drop-down menu and click Execute. 4 Complete the Reconfigure task using the Reconfigure wizard.
Table 13-1. Virtual Disk Reconfiguration and Capacity Expansion (continued) Controller Starting RAID Level Target RAID Level PERC 4/SC, 4/DC, RAID 0 Comments RAID 5 Add at least one additional disk RAID 0 With or without adding additional disks RAID 5 Add additional disks RAID 5 RAID 0 With or without adding additional disks RAID 5 RAID 5 Add additional disks PERC 4/IM N/A N/A N/A CERC SATA1.
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 Exceptions for Reconfiguring a Concatenated Virtual Disk on CERC SATA1.5/6ch and CERC SATA1.
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. • Replacing a Failed Disk describes how to replace a failed physical disk and initiate a rebuild.
The following table describes some of the possible scenarios that may/may not result in virtual disk bad blocks: 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.
Table 13-2. Sample Scenarios For Virtual Disk Bad Blocks RAID Level State Virtual Disk Scenario RAID 6 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. The problem is resolved. Ready Result Recommendations Storage Management provides the ability to clear the bad block warnings.
Virtual Disk Properties and Tasks Use this window to view information about the virtual disks and execute virtual disk tasks. From the Options menu: Refresh Partitions: Click to refresh the Virtual Disk Partitions data once the partition is created using the operating system commands for the available virtual disks. Go to the Create Virtual Disk Wizard: Launches the Create Vitrual Disk Wizard. Virtual Disk Properties The virtual disk properties can vary depending on the model of the controller.
Property Definition 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. Resynching—A consistency check is being performed on the virtual disk. On the CERC SATA1.5/6ch controllers, reconfiguring a concatenated virtual disk to a RAID 1 may cause the virtual disk to be in Resynching state.
Property Definition Background Initialization—A background initialization is being performed on the virtual disk. Formatting—The virtual disk is being formatted. Formatting applies to the CERC SATA1.5/6ch controllers. For more information, see Format and Initialize; Slow and Fast Initialize. Initializing—The virtual disk is being initialized. Initialization applies to the PERC 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, and 4e/Di controllers. For more information, see Format and Initialize; Slow and Fast Initialize.
Property Definition Associated Fluid Cache State This property displays the associated Fluid Cache state of the virtual disk. The possible values are Active— The Fluid Cache disk is active. Failed—The Fluid Cache has encountered a failure of one or more components and is no longer functioning. No— The Fluid Cache is not enabled. Disabling —In this transient state, the cache removal from the virtual disk is in process. Device Name This property displays the operating system device name for this object.
Property Definition Cache Policy This property displays the cache policy that the controller is using for this virtual disk. See RAID Controller Read, Write, Cache, and Disk Cache Policy. Stripe Size This property displays the stripe size of the virtual disk. Disk Cache Policy This property displays whether the disk cache policy of the physical disks that are part of the virtual disk is enabled or disabled. See RAID Controller Read, Write, Cache, and Disk Cache Policy.
• Pause Check Consistency • Resume Check Consistency • Blink and Unblink (Virtual Disk) • Rename • Split Mirror • Unmirror • Cancel Rebuild • Change Policy • Replace Member Disk • 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.
Cancel Background Initialization Does my controller support this feature? See Supported Features. On PERC 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, and 4e/Di controllers, background initialization of redundant virtual disks begins automatically after the virtual disk is created. Because the initialization is run in the background, other processes can continue while the initialization completes.
Assign and Unassign Dedicated Hot Spare Does my controller support this feature? See Supported Features. Use the Assign Dedicated Hot Spare task to assign a disk as a backup for a single virtual disk. For more information, see Assign and Unassign Dedicated Hot Spare. Check Consistency Does my controller support this feature? See Supported Features. Use the Check Consistency task to verify the accuracy of the redundant (parity) information. This task only applies to redundant virtual disks.
Pause Check Consistency Does my controller support this feature? See Supported Features. Use the Pause Check Consistency task to pause a check consistency while it is in progress. 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.
Rename Does my controller support this feature? See Supported Features. Use the Rename task to change the virtual disk’s name. For more information, see Virtual Disk Task: Rename. NOTE: On the CERC SATA1.5/2s controller, you cannot change the default name of a concatenated virtual disk. NOTE: Renaming a virtual disk generates alert 2159. On the CERC SATA1.5/6ch and CERC SATA1.5/2s controllers, alert 2159 displays the new virtual disk name.
Clear Virtual Disk Bad Blocks Does my controller support this feature? See Supported Features. Use the Clear Virtual Disk Bad Blocks task to clear bad blocks on your virtual disk. This feature is applicable to PERC H700, 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 family of controllers. Encrypt Virtual Disk Does my controller support this feature? See Supported Features.
Property Definition Device Name This property displays the operating system device name for this object. State This property displays the current status of the virtual disk on which the partition is created. Tasks This property displays the available tasks for the virtual disk partition. Possible tasks are: Enabling Fluid Cache on Virtual Disk Partitions and Disabling Fluid Cache on Virtual Disk Partitions. Size This property displays the total capacity of the virtual disk.
If you want to make your own selections for the virtual disk configuration, click Go To Advanced Wizard. To Create a Virtual Disk Express Wizard: Step 1 of 2 1 Click the radio button to select the correct RAID level. – Depending on the controller, Concatenated enables you to combine the storage capacity of several disks or to create a virtual disk using only a single physical disk.
– Select RAID 10 for striping over mirror sets. This selection groups n disks together as one large virtual disk with a total capacity of (n/2) disks. Data is striped across the replicated mirrored pair disks. When a disk fails, the virtual disk continues to function. The data is read from the surviving mirrored pair disk. This feature provides the best failure protection, read and write performance. Your system must have at least four disks to use RAID 10.
NOTE: When creating a virtual disk on the CERC SATA1.5/2s controller or on a controller that is in a cluster configuration, you must specify the maximum virtual disk size. 4 Click Continue to go to the next screen or Exit Wizard if you want to cancel. 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 Click Go To Create Virtual Disk Wizard.
The Physical Disk check box is not available if the controller does not have a physical disk that is a suitable hot spare for the virtual disk you are creating. For example, the available physical disks may be too small to protect the virtual disk. If the Physical Disk check box is not available, you may need to specify a smaller virtual disk, use a different RAID level, or change the disk selection using the Create Virtual Disk Advanced wizard.
If you want to have the wizard choose a recommended virtual disk configuration for you, click Go To Express Wizard. To Create a Virtual Disk Advanced Wizard: Step 1 of 4 1 Click the radio button to select the correct RAID level. – Depending on the controller, Concatenated enables you to combine the storage capacity of several disks or to create a virtual disk using only a single physical disk. For information on the number of disks supported by Concatenated, see Number of Physical Disks per Virtual Disk.
disk fails, the virtual disk continues to function. The data is read from the surviving mirrored pair disk. This feature provides the best failure protection, read and write performance. Your system must have at least four disks to use RAID 10. For PERC controllers with firmware version 6 and above, 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.
• 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 of 4) Does my controller support this feature? See Supported Features. This screen enables you to select which disks is used to create the virtual disk. The items displayed on this screen depend on the selections you made in Create Virtual Disk Advanced Wizard (Step 1 of 4). NOTE: If a physical disk is receiving a SMART alert, it cannot be used in a virtual disk. For more information on SMART alerts, see Monitoring Disk Reliability on RAID Controllers.
Physical Disks Selected The Physical Disks Selected section of the screen displays the disks you have chosen. In this example, two disks are selected. • Physical disk 0:0 • Physical disk 0:1 Each RAID level has specific requirements for the number of disks that must be selected. RAID 10, RAID 50, and RAID 60 also have requirements for how many disks must be included in each stripe or span. If the controller is a SAS controller with firmware versions 6.
you have selected RAID 10 in step 1 and the system has 22 or more than 22 physical drives. Click Continue when you have completed the disk selection. If you want to cancel the virtual disk, click Exit Wizard. If you want to return to the previous screen and change your selections, click Go Back To Previous Page.
than the size you specify. The Create Virtual Disk wizard may round up the size of the virtual disk to avoid rendering a portion of the physical disk space unusable. NOTE: When creating a virtual disk on the CERC SATA1.5/2s controller or on a controller that is in a cluster configuration, you must specify the maximum virtual disk size. 3 Select a stripe size from the Stripe Size drop-down menu. The stripe size refers to the amount of space that each stripe consumes on a single disk.
NOTE: If you have selected the Create Encrypted Virtual Disk check box in Create Virtual Disk Advanced Wizard (Step 1 of 4), then in the Summary of Virtual Disk Attributes, an Encrypted Virtual Disk attribute is displayed with a value Yes. 2 Review the Assign Dedicated Hot Spare section. A hot spare is an unused backup physical disk that can be used to rebuild data from a redundant virtual disk. For more information, see Protecting Your Virtual Disk with a Hot Spare.
Span Edit In the edit mode, you cannot alter the number of physical disks per span. If there are enough available physical disks, you can reduce or increase the number of spans. You can also alter the contents of a span by removing that span and selecting a new physical disk to comprise that span. To successfully create a virtual disk, a minimum of two spans must exist at all times. NOTE: If you click Span Edit, Intelligent Mirroring that is already been applied becomes invalid.
To Reconfigure a Virtual Disk: Step 1 of 3 1 Select the physical disks that you want to include in the virtual disk. You can expand the virtual disk’s capacity by adding additional physical disks. On some controllers, you can also remove physical disks. The changes you make to the physical disk selection are displayed in the Selected Physical Disks table. NOTE: For a controller that has more than one channel, it may be possible to configure a virtual disk that is channel-redundant.
Virtual Disk Task: Reconfigure (Step 2 of 3) Does my controller support this feature? See Supported Features. This screen enables you to select the RAID level and size for the reconfigured virtual disk. If you clicked Expand Capacity in the previous step, this screen allows you to expand the capacity of the virtual disk. The Expand Capacity option appears only for PERC H310, H700, H710, H710P, PERC H800, and H810 controllers with firmware 7.1 or above.
This feature provides better data redundancy and read performance, but slower write performance. Your system must have at least three disks to use RAID 5. – Select RAID 6 for striping with additional parity information—This selection groups n disks as one large virtual disk with a capacity of (n-2) disks. Two sets of parity information is alternately stored on all disks. The virtual disk remains functional with up to two disk failures.
Virtual Disk Task: Reconfigure (Step 3 of 3) Does my controller support this feature? See Supported Features. This screen enables you to review your changes before completing the virtual disk reconfiguration. To Reconfigure a Virtual Disk: Step 3 of 3 1 Review your changes. The New Virtual Disk Configuration table displays the changes you have made to the virtual disk. The Previous Virtual Disk Configuration displays the original virtual disk prior to reconfiguration.
Format and Initialize; Slow and Fast Initialize Does my controller support this feature? See Supported Features. The Format or Initialize task erases the files and removes the file systems on virtual disks while keeping the virtual disk configuration intact. Formatting or initializing a virtual disk destroys all data on the virtual disk. If the boot partition resides on the virtual disk, it is destroyed by the format operation. Some controllers have BIOS settings for a fast initialize or a slow initialize.
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.
Formatting or Initializing a Disk To format or initialize a disk: 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.
Virtual Disk Task: Delete Does my controller support this feature? See Supported Features. Deleting a virtual disk destroys all information including file systems and volumes residing on the virtual disk. NOTE: When deleting virtual disks, all assigned global hot spares may be automatically unassigned when the last virtual disk associated with the controller is deleted. When deleting the last virtual disk of a disk group, all assigned dedicated hot spares automatically become global hotspares.
Virtual Disk Task: Rename Does my controller support this feature? See Supported Features. Renaming a virtual disk enables you to change the virtual disk’s name. The numbering format for the virtual disk remains unchanged. Depending on the controller you have, there are different considerations regarding the controller BIOS: • On PERC 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, and 4e/Di controllers, changing the virtual disk name with Storage Management does not change the name in the BIOS. • On CERC SATA1.
Virtual Disk Task: 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. For more information, see RAID Controller Read, Write, Cache, and Disk Cache Policy. To change a virtual disk’s read, write, or disk cache policy: 1 Select the new policy from the Read Policy, Write Policy, and Disk Cache Policy drop-down menus. 2 Click Apply Changes.
concatenated virtual disks on these controllers, see Number of Physical Disks per Virtual Disk and Exceptions to One Physical Disk Limitation for Concatenated Virtual Disks on CERC SATA1.5/6ch and CERC SATA1.5/2s Controllers. NOTE: On the CERC SATA1.5/6ch controllers, this operation is not supported when using a dynamic virtual disk or for a RAID 1 virtual disk that is in a Failed Redundancy state. NOTE: On Linux, a Split Mirror cannot be performed on a mounted virtual disk.
NOTE: On the CERC SATA1.5/6ch controllers, doing an Unmirror on a RAID 1concatenated virtual disk results in a concatenated virtual disk that cannot be subjected to any further modification. You cannot reconfigure or add disks to the resulting concatenated virtual disk. If you do an Unmirror on a RAID 1 virtual disk, the resulting concatenated virtual disk can be reconfigured back to a RAID 1 virtual disk. After you have reconfigured to a RAID 1 virtual disk, further reconfiguration may be possible.
For more information on hot spares including size requirements, see Protecting Your Virtual Disk with a Hot Spare. For considerations regarding RAID 10 and RAID 50 virtual disks created using the controller BIOS, see Dedicated Hot Spare Considerations. NOTE: The CERC SATA1.5/2s controller does not support dedicated hot spares. 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.
Virtual Disk Task: Replace Member Disk (Step 1 of 2) NOTE: This feature is supported only on SAS and SATA controllers with firmware versions 6.1 and later. Does my controller support this feature? See Supported Features. 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.
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 Replace Member Disk from the Available Tasks drop-down menu. 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.
2 From the Tasks drop-down list corresponding the virtual disk for which you want to enable the cache, select Enable Fluid Cache. 3 Click Execute. 4 Select the Write cache mode. The available options are: • Write Through • Write Back 5 Click Apply for enabling the cache. After the caching is enabled, a Fluid Cache disk is created that can be viewed on the Fluid Cache Disks page.
The Partitions of Virtual Disk page is displayed with the list of available virtual disk partitions. NOTE: The Partition link is available only if the corresponding virtual disk has partitions. 3 From the Tasks drop-down list, select Enable Fluid Cache. 4 Select the Write cache mode. The available options are: • Write Through • Write Back 5 Click Apply. NOTE: This option is available for PERC H710, H710P, and H810 controllers and for Online or degraded 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 4/SC, 4/DC, 4e/DC, 4/Di, 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.
• A virtual disk cannot be migrated between the CERC SATA1.5/6ch and CERC SATA1.5/2s controller family and the PERC 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, and 4e/Di controller family. • On SCSI controllers, a virtual disk cannot be migrated from one controller to another unless the receiving controller’s configuration has been cleared. • When moving the physical disks on a SCSI controller from one enclosure to another, the SCSI ID for each disk must remain the same.
Moving the Disks 1 Turn off the system that the physical disks are being moved from. 2 If the receiving controller has a preexisting virtual disk configuration on attached physical disks, use the following procedure for clearing the configuration: – Turn off the receiving server. – Remove all the physical disks from the controller. – Start up the receiving server and clear the configuration from the controller BIOS.
5 This reads the data on the physical disks to restore the RAID controller’s proprietary configuration information. Press Esc and save the new configuration when prompted. 6 Press the Esc key and save the new configuration when prompted. 7 Reboot the system. 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.
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.
Setting Hot Spare Protection Policy The Hot Spare Protection Policy is supported only on Serial Attached SCSI (SAS) controllers. 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. Dell OpenManage Storage Management sends alerts when the hot spare protection policy is violated.
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 Dell OpenManage 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.
NOTE: For H700 and H800 controllers, you can assign a dedicated hot spare to RAID 10, RAID 50, and RAID 60. • Considerations for Multiple Dedicated Hot Spares—From Storage Management version 3.1 onwards, Storage Management enables you to assign more than one dedicated hot spare to a virtual disk. NOTE: This feature is applicable only on PERC 5 and PERC 6 family of controllers.
NOTE: When using the BIOS on a CERC SATA1.5/6ch controller, it may be possible to create a hot spare from a physical disk that is also used in a virtual disk. To avoid confusion and maximize data protection, Storage Management does not allow a physical disk to be both a hot spare and a member of a virtual disk. When assigning a hot spare, Storage Management displays the physical disks that are not being used by a virtual disk. Size Requirements for Global Hot Spares on CERC SATA1.
Global Hot Spare Considerations on a SAS 6/iR The SAS 6/iR controller enables you to assign two global hot spares. The controller firmware remembers the hot spare assignment even after the physical disks that you assigned as hot spares have been removed. In other words, in the case of a disk removal, the firmware may assume that a hot spare is present when it is not.
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 Dell 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 Dell 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.
BIOS Terminology 17 The terminology used by Storage Management can be different from the terminology used in the controller BIOS. The following sections show some of these differences. BIOS Terms and the PERC 4/SC, 4/DC, 4e/DC, and 4/Di Controllers Table 17-1.
Table 17-2. Naming convention differences between Storage Management and PERC BIOS Container Configuration Utility (CCU) (continued) Storage Management CERC SATA1.5/6ch, and CERC SATA1.
18 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 Physical Disk in a RAID 1 on a CERC SATA1.5/2s 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.
After retrieving any viable data from the disk, replace the failed disk as described previously in Replacing a Failed Disk that is Part of a Redundant Virtual Disk or Replacing a Failed Physical Disk that is Part of a NonRedundant Virtual Disk. Replacing a Failed Physical Disk in a RAID 1 on a CERC SATA1.5/2s On a CERC SATA1.5/2s controller, a rebuild may not start automatically when you replace a failed physical disk that is part of a RAID 1 virtual disk.
• Rebuild for PERC 4/SC, 4/DC, 4e/DC, 4/Di, PERC 5/E and PERC 5/i controllers You can avoid removing the wrong physical disk by blinking the LED display on the physical disk that you intend to remove. For information on blinking the LED display, see Blink and Unblink (Physical Disk). Resolving Microsoft Windows Upgrade Problems If you upgrade the Microsoft Windows operating system on a server, you may find that Storage Management no longer functions after the upgrade.
• The virtual disk is non-redundant—For example, a RAID 0 virtual disk cannot be rebuilt because RAID 0 does not provide data redundancy. • There is no hot spare assigned to the virtual disk—As long as the virtual disk is redundant, to rebuild it: – Pull out the failed physical disk and replace it. A rebuild automatically starts on the new disk. – Assign a hot spare to the virtual disk and then perform a rebuild.
• The virtual disk includes failed or corrupt physical disks—This situation may generate alert 2083. For information on Alert Messages, see the Dell OpenManage Server Administrator Messages Reference Guide at support.dell.com/manuals. • The rebuild rate setting is too low—If the rebuild rate setting is quite low and the system is processing a number of operations, then the rebuild may take an unusual amount of time to complete. For more information, see Set Rebuild Rate.
3 Restore the virtual disk from the tape onto healthy physical disks. Cannot Create a Virtual Disk You might be attempting a RAID configuration that is not supported by the controller. Check the following: • How many virtual disks already exist on the controller? Each controller supports a maximum number of virtual disks. For more information, see Maximum Number of Virtual Disks per Controller.
2 Delete the virtual disk. 3 Create one or more virtual disks that are smaller than 1TB. 4 Restore your data from backup. Irrespective of whether your Linux operating system limits the virtual disk size to 1TB, the virtual disk size depends on the version of the operating system and any updates or modifications that you have implemented. For more information, see your operating system documentation.
Resolution: Perform a Rescan Controller. When the rescan is complete, select each physical disk that is Offline and perform a Remove Dead Segments task. You must remove the dead segments before the physical disk can be brought back online. The dead segments are caused by the failure or removal of the shared physical disk. NOTE: It is recommended that you avoid using the same physical disks for both redundant and non-redundant virtual disks.
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.
Receive a “Bad Block” Alert with “Replacement,” “Sense,” or “Medium” Error The following alerts or events are generated when a portion of a physical disk is damaged: • 2146 • 2147 • 2148 • 2149 • 2150 This damage is discovered when the controller performs an operation that requires scanning the disk.
Alerts 2146 through 2150 Received while Performing I/O, Consistency Check, Format, or Other Operation If you receive alerts 2146 through 2150 while performing an operation other than a rebuild, you should replace the damaged disk immediately to avoid data loss. Do the following: 1 Back up the degraded virtual disk to a fresh (unused) tape. 2 Replace the damaged disk. 3 Do a rebuild.
A Corrupt Disk or Drive Message Suggests Running autocheck During a Reboot Let autocheck run, but do not worry about the message. The reboot completes after autocheck is finished. Depending on the size of your system, this may take about ten minutes. Erroneous Status and Error Messages after a Windows Hibernation Activating the Windows hibernation feature may cause Storage Management to display erroneous status information and error messages.
Cannot Connect to Remote System Running Windows Server 2003 When connecting to a remote system running Windows Server 2003, log into the remote system using an account that has administrator privileges. By default, Windows Server 2003 does not allow anonymous (null) connections to access the SAM user accounts. Therefore, if you are attempting to connect using an account that has a blank or null password, the connection may fail.
PCIe SSD Troubleshooting Peripheral Component Interconnect Express (PCIe) Solid-State Drive (SSD) is not seen in the operating system Probable Cause: Hardware is not installed correctly Solution: Check the following components to ensure they are plugged: • Devices: Ensure that the PCIe SSDs are installed in a PCIe SSD backplane. • Backplane: Ensure that the cables for the PCIe SSD backplane are connected. • Cables: PCIe cables are unique for the configuration.
Fluid Cache for DAS Fluid Cache tree is not seen in OMSS. Install Fluid Cache and restart the OpenManage services. Additional entries seen in the statistics chart. Upgrade the RRD tool version 1.3.7 or later. Fluid Cache device is not seen in the operating system. Configure the Fluid Cache device. For more information, refer to the Configuration section in the Dell Fluid Cache For DAS User’s Guide. On H310 I do not see any option for Fluid Cache. H310 is not a supported controller.
Blank graph or graph with minimal data is plotted The data for the duration selected has minimal samples. Select a shorter duration.
Troubleshooting
Frequently Asked Questions 19 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 by the PERC 4/ Controllers (continued) Controller Task Name PERC 4/SC PERC PERC PERC PERC PERC PERC 4/DC 4/DI 4e/SI 4e/DI 4e/DC 4/IM Set Patrol Read Yes Mode Yes Yes Yes Yes Yes No NOTE: For PERC 4 controllers, (Manual mode is not available). Start Patrol Read No No No No No No No Stop Patrol Read No No No No No No No Battery Tasks Table A-2.
Physical Disk Tasks Table A-4. Physical Disk Tasks Supported by the PERC 4/ Controllers Physical Disk Task Name PERC PERC PERC PERC PERC PERC 4/SC 4/DC 4/DI 4e/SI 4e/DI 4e/DC PERC 4/IM Blink/Unblink Yes Yes Yes Yes Yes Yes Yes Task only available when an enclosure or backplane and LEDs on the physical disks are present.
Virtual Disk Tasks Table A-5.
Table A-5.
Virtual Disk Specifications Table A-6.
Table A-6.
Table A-6.
Table A-6. Virtual Disk Specifications for the PERC 4/ Controllers (continued) PERC 4/SC PERC 4/DC PERC PERC PERC PERC PERC 4/IM Virtual Disk 4/DI 4e/SI 4e/DI 4e/DC Specification Maximum NA number of physical disks in a RAID 6 NA NA NA NA NA NA Maximum NA number of physical disks in a RAID 60 NA NA NA NA NA NA Minimum NA number of physical disks in a RAID 6 NA NA NA NA NA NA Minimum NA number of physical disks in a RAID 60 NA NA NA NA NA NA Supported RAID Levels Table A-7.
Read, Write, and Disk Cache Policy Table A-8.
Enclosure Support Table A-9. Enclosure Support on the PERC 4/ Controllers Enclosure Support PERC PERC PERC PERC PERC PERC PERC 4/SC 4/DC 4/DI 4e/SI 4e/DI 4e/DC 4/IM Can an enclosure Yes be attached to this controller? Yes Yes Yes Yes Yes No Supported Features on the CERC SATA Controllers This section identifies the controller-supported features and whether or not an enclosure can be attached to the CERC SATA 1.5/2s and CERC SATA1.5/6ch controllers.
Table A-10. Controller Tasks Supported by the CERC SATA Controllers (continued) Controller Task Name CERC SATA 1.5/2s CERC SATA 1.
Table A-11. Battery Tasks Supported by the CERC SATA Controllers (continued) Battery Task Name CERC SATA 1.5/2s CERC SATA 1.5/6ch Start Learn Cycle No No Delay Learn Cycle No No Connector Tasks Table A-12. Connector Tasks Supported by the CERC SATA Controllers Connector Task Name CERC SATA 2S CERC SATA 6ch Connector Rescan Yes Yes Physical Disk Tasks Table A-13.
Virtual Disk Tasks Table A-14.
Table A-14. Virtual Disk Tasks Supported by the CERC SATA Controllers (continued) Virtual Disk Task Name CERC SATA 2S CERC SATA 6ch Restore Dead Disk Segments No Yes Initialize Virtual Disk No No Fast Initialize Virtual Disk No No Slow Initialize Virtual Disk No No Cancel Initialize Virtual Disk No No Virtual Disk Specifications Table A-15.
Table A-15.
Table A-15. Virtual Disk Specifications for the CERC SATA Controllers (continued) Virtual Disk Specification CERC SATA 2S CERC SATA 6ch Maximum number of physical disks in a RAID 60 NA NA Minimum number of NA physical disks in a RAID 6 NA Minimum number of physical disks in a RAID 60 NA NA Supported RAID Levels Table A-16.
Table A-17. Read, Write, and Cache Policy Supported by the CERC SATA Controllers Read, Write, and Cache Policy CERC SATA 2S CERC SATA 6ch Read Ahead (Enabled) No Yes Adaptive Read Ahead No No No Read Ahead (Disabled) Yes Yes Write Policy No Yes Write Back (Enabled) No No Write Through (Disabled) Yes Yes Force Write Back (Enabled Always) No No Write Cache Enabled Protected No Yes Cache Policy No No Cache I/O No No Direct I/O No No Enclosure Support Table A-18.
• 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 PERC 5/ PERC 6/, and CERC 6/I Controllers (continued) Controller Task Name PERC 5/E PERC 5/i PERC 6/E PERC 6/I PERC 6/I Modular CERC 6/I Export Log File Yes Yes Yes Yes Yes Yes Clear Foreign Configuration Yes Yes Yes Yes Yes Yes Import Foreign Configuration Yes Yes Yes Yes Yes Yes Import/Recover Foreign Configuration Yes with firmware 5.1.x or greater. Yes with Yes firmware 5.1.x or greater.
Table A-19. Controller Tasks Supported on the PERC 5/ PERC 6/, and CERC 6/I Controllers (continued) Controller Task Name PERC 5/E PERC 5/i PERC 6/E PERC 6/I PERC 6/I Modular CERC 6/I Change Controller Properties No No Yes with firmware 6.1 and later Yes with firmware 6.1 and later Yes with No firmware 6.1 and later Intelligent Mirroring No No Yes with firmware 6.1 and later Yes with firmware 6.1 and later Yes with No firmware 6.
Table A-20. Battery Tasks Supported on the PERC 5/E, PERC 6/, and CERC 6/I Controllers (continued) Battery Task Name PERC 5/E PERC 5/i PERC 6/E PERC 6/I PERC 6/I CERC 6/I Modular Start Learn Cycle Yes Yes Yes Yes Yes No Delay Learn Cycle Yes Yes Yes Yes Yes No Connector Tasks Table A-21.
Table A-22. Physical Disk Tasks Supported by the PERC 5/E, PERC 6/, and CERC 6/I Controllers (continued) Physical Disk Task Name PERC 5/E PERC 5/I PERC 6/E PERC 6/I PERC 6/I CERC 6/I Modular Format Disk No No No No No No Clear Yes Yes Yes Yes Yes Yes Cancel Clear Yes Yes Yes Yes Yes Yes Cancel Replace Member No No Yes with firmware 6.1 and later Yes with firmware 6.1 and later Yes with No firmware 6.1 and later Virtual Disk Tasks Table A-23.
Table A-23.
Virtual Disk Specifications Table A-24.
Table A-24. Virtual Disk Specifications for the PERC 5/, PERC 6/, and CERC 6/I Controllers (continued) Virtual Disk Specification PERC 5/E PERC 5/I PERC 6/E PERC 6/I PERC 6/I CERC 6/I Modular Maximum Number of 16 Physical Disks in a RAID 10 16 256 16 with firmware version 6.
Table A-24. Virtual Disk Specifications for the PERC 5/, PERC 6/, and CERC 6/I Controllers (continued) Virtual Disk Specification PERC 5/E PERC 5/I PERC 6/E PERC 6/I PERC 6/I CERC 6/I Modular Minimum number of physical disks in a RAID 6 NA NA 4 4 4 4 Minimum number of physical disks in a RAID 60 NA NA 8 8 8 8 Supported RAID Levels Table A-25.
Table A-26.
Supported Features on the PERC Hardware Controllers This section identifies the controller-supported features and whether or not an enclosure can be attached to the following: • PERC H800 and PERC H810 Adapter Controllers • PERC H700 Adapter, PERC H700 Integrated, and PERC H700 Modular Controllers • PERC H710 Adapter, PERC H710 Mini Blades, and PERC H710 Mini Monolithic Controllers • PERC H310 Adapter, PERC H310 Mini Monolithic, and PERC H310 Mini Blades Controllers The features comprise the followi
Controller Tasks Table A-28.
Table A-28.
Table A-28.
Table A-28. 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 Patrol Read Report Yes Yes Yes Yes Yes Yes Yes Check Consistency Report Yes Yes Yes Yes Yes Yes Yes Slot Occupancy Report Yes Yes Yes Yes Yes Yes Yes Battery Tasks Table A-29.
Connector Tasks Table A-30. 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-31.
Table A-31.
Virtual Disk Tasks Table A-32.
Table A-32.
Virtual Disk Specifications Table A-33.
Table A-33.
Table A-33.
Table A-34. 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-35.
Table A-35.
• 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-37.
Table A-37. 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 Controller Reports Battery Tasks Table A-38.
Physical Disk Tasks Table A-40. 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-41.
Table A-41. 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-42. 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-43.
Table A-43.
Table A-43. 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-44.
Enclosure Support Table A-45.
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-46.
Virtual Disk Tasks Table A-48.
Table A-49.
Table A-49. 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-50.
Table A-51.
• Virtual Disk Tasks • Enclosure Support For enclosure-supported tasks, see Enclosure and Backplane Features. Controller Tasks Table A-53.
Battery Tasks Table A-54. 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-55. 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-56.
Table A-56. 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-57.
Table A-57. 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-58.
• Supported Features on the PERC H700, PERC H710 A, PERC H710 MB, PERC H710 MM, PERC H710P A, PERC H710P MB, and PERC H710P MM Controllers, see Supported Features on the PERC Hardware Controllers • Supported Features on the PERC H800 and PERC H810 A Controllers, see Supported Features on the PERC Hardware Controllers Enclosure and Backplane Tasks Table A-59.
Table A-60. Backplane Tasks for SCSI and SAS Controllers Backplane Tasks SCSI SAS Enable Alarm No No Disable Alarm No No Set Temperature Probe Values No No Set Asset Data (includes asset tag and asset name) No No Blink Enclosure No No Controller Reports No No Enclosure and Backplane Support for Smart Thermal Shutdown Table A-61.
Maximum Supported Configuration Table A-63.
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.
