Dell EMC Server Administrator Storage Management 10.0.1 May 2021 Rev.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2021 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Chapter 1: Overview.....................................................................................................................12 What is new in this release.............................................................................................................................................. 12 OMSA Customer Survey..................................................................................................................................................
Storage Properties And Current Activity.................................................................................................................... 30 Alerts Or Events................................................................................................................................................................ 30 Monitoring Disk Reliability On RAID Controllers........................................................................................................
Disk Cache Policy........................................................................................................................................................ 49 Background Initialization On PERC Controllers......................................................................................................... 50 Non-RAID Controller Description..................................................................................................................................
Physical Disk Firmware Version Report Properties..............................................................................................81 Chapter 8: Support For PERC 9, PERC 10, and PERC 11 Hardware Controllers.............................83 Support For RAID Level 10 Virtual Disk Creation On PERC Hardware Controllers...........................................83 RAID Level 10 Virtual Disk Creation With Uneven Span....................................................................................
Battery — Available Tasks............................................................................................................................................ 106 Starting A Learn Cycle................................................................................................................................................... 106 Battery Transparent Learn Cycle.................................................................................................................................
Virtual Disk Properties.............................................................................................................................................. 127 Virtual Disk Tasks.......................................................................................................................................................129 Virtual Disk — Available Tasks.....................................................................................................................................
Assigning A Dedicated Hot Spare.......................................................................................................................... 143 Unassigning A Dedicated Hot Spare..................................................................................................................... 143 To Locate Assign Or Unassign Dedicated Hot Spare In Storage Management..........................................144 Virtual Disk Task - Replace Member Disk Step 1 of 2................................
A Task Menu Option Is Not Displayed.................................................................................................................. 155 A Corrupt Disk Or Drive Message Suggests Running Autocheck During A Reboot..................................155 Erroneous Status And Error Messages After A Windows Hibernation.........................................................156 Storage Management May Delay Before Updating Temperature Probe Status........................................
Enclosure Support On The PERC Software RAID Controllers........................................................................175 Supported Features On The Non-RAID Controllers................................................................................................ 176 Controller Tasks Supported On The Non-RAID Controllers............................................................................ 176 Battery Tasks Supported By Non-RAID Controllers....................................................
1 Overview Server Administrator Storage Management provides enhanced features for configuring the locally attached RAID and non-RAID disk storage on a system. Storage Management enables you to perform controller and enclosure functions for all supported RAID and non-RAID controllers and enclosures from a single graphical user interface (GUI) or command-line interface (CLI). The GUI is wizard-driven and includes features for novice and advanced users. The CLI is fully featured and scriptable.
Version Requirements For Controller Firmware And Drivers 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 Server Administrator Release Notes refer to the minimum supported version for these controllers. Later versions of the firmware and drivers are also supported. For the most recent driver and firmware requirements, contact your service provider.
Support For Disk And Volume Management Storage Management does not provide disk and volume management. To implement disk and volume management, you must use the native disk and volume management utilities provided by your operating system.
2 Getting Started Server Administrator Storage Management is designed for system administrators who implement hardware RAID solutions and understand corporate and small business storage environments. Storage Management enables you to configure the storage components attached to your system. These components include RAID and non-RAID controllers and the channels, ports, enclosures, and disks attached to them.
where is the assigned name for the managed system and 1311 is the default port. or https://:1311 where is the IP address for the managed system and 1311 is the default port. NOTE: Type https:// (not http://) in the address field to receive a valid response in your browser. User Privileges Server Administrator provides security through the User, Power User, and Administrator user groups.
The online Help is available as: ● Context-sensitive Help — Each Storage Management page has a icon. Click this icon to display the context-sensitive online Help that describes the contents of the displayed page. ● Table of Contents — The table of contents is available in the page that displays the information when you access the context-sensitive Help. Common Storage Tasks This section provides information on commonly performed storage tasks: ● Create and configure virtual disks (RAID configuration).
3 Understanding RAID concepts Storage Management uses the 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 the RAID controllers and operating system view disk space on your system.
● 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.
● ● ● ● ● ● RAID Level 6 (Striping With Additional Distributed Parity) RAID Level 50 (Striping Over RAID 5 Sets) RAID Level 60 (Striping Over RAID 6 Sets) RAID Level 10 (Striping Over Mirror Sets) Comparing RAID Level And Concatenation Performance No-RAID Concatenation In Storage Management, concatenation refers to storing data on either one physical disk or on disk space that spans multiple physical disks.
RAID 0 characteristics: ● ● ● ● Groups n disks as one large virtual disk with a capacity of (smallest disk size) *n disks. Data is stored to the disks alternately. No redundant data is stored. When a disk fails, the large virtual disk fails with no means of rebuilding the data. Better read and write performance. RAID level 1 - mirroring RAID 1 is the simplest form of maintaining redundant data. In RAID 1, data is mirrored or duplicated on one or more physical disks.
● Redundancy for protection of data. ● RAID 1 is more expensive in terms of disk space since twice the number of disks are used than required to store the data without redundancy. RAID level 5 -striping with distributed parity RAID 5 provides data redundancy by using data striping in combination with parity information. Rather than dedicating a physical disk to parity, the parity information is striped across all physical disks in the disk group.
RAID 6 characteristics: ● ● ● ● ● ● Groups n disks as one large virtual disk with a capacity of (n-2) disks. Redundant information (parity) is alternately stored on all disks. The virtual disk remains functional with up to two disk failures. The data is reconstructed from the surviving disks. Better read performance, but slower write performance. Increased redundancy for protection of data. Two disks per span are required for parity. RAID 6 is more expensive in terms of disk space.
RAID 50 characteristics: ● Groups n*s disks as one large virtual disk with a capacity of s*(n-1) disks, where s is the number of spans and n is the number of disks within each span. ● Redundant information (parity) is alternately stored on all disks of each RAID 5 span. ● Better read performance, but slower write performance. ● Requires as much parity information as standard RAID 5. ● Data is striped across all spans. RAID 50 is more expensive in terms of disk space.
RAID 60 characteristics: ● Groups n*s disks as one large virtual disk with a capacity of s*(n-2) disks, where s is the number of spans and n is the number of disks within each span. ● Redundant information (parity) is alternately stored on all disks of each RAID 6 span. ● Better read performance, but slower write performance. ● Increased redundancy provides greater data protection than a RAID 50. ● Requires proportionally as much parity information as RAID 6. ● Two disks per span are required for parity.
RAID 10 characteristics: ● ● ● ● ● Groups n disks as one large virtual disk with a capacity of (n/2) disks, where n is an even integer. Mirror images of the data are striped across sets of physical disks. This level provides redundancy through mirroring. When a disk fails, the virtual disk still works. The data is read from the surviving mirrored disk. Improved read performance and write performance. Redundancy for protection of data.
Comparing RAID Level And Concatenation Performance 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 supported RAID levels in Storage Management. For information on all supported RAID levels in Storage Management, see Choosing RAID Levels And Concatenation. Table 1.
Table 1. RAID Level and Concatenation Performance Comparison (continued) RAID Level Data Availability Read Performance Write Performance Rebuild Performance Minimum Disks Required Suggested Uses data intensive uses. RAID 6 Excellent Sequential reads: good. Transactional reads: Very good Fair, unless using writeback cache Poor N + 2 (N = at least two disks) Critical information. Databases and other read intensive transactional uses.
4 Quick Access To Storage Status And Tasks This section describes various methods to determine the status or health of the storage components on your system and how to quickly launch the available controller tasks.
Table 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/Fatal — The component has either failed or failure is imminent.
NOTE: You may not receive SMART alerts when the I/O of a controller is paused. Using Alarms To Detect Failures Certain storage components have alarms which when enabled, alert you when the component fails. Using Enclosure Temperature Probes Physical disk enclosures have temperature probes that warn you when the enclosure has exceeded an acceptable temperature range.
5 PCI Express Solid-State Device Support This section provides an overview of the Storage Management device management support for Peripheral Component Interconnect Express (PCIe) Solid-State Drive (SSD) and its associated devices like the backplane and extender card. In Storage Management, PCIe SSD appears under Storage in the tree view. Storage Management reports the PCIe SSD devices and its various properties.
● PCIe Solid-State Device Table 3. PCIe SSD Subsystem Properties Properties Description ID Displays the subsystem ID assigned to the PCIe SSD subsystem by Storage Management. Storage Management numbers the controllers and PCIe SSD subsystems attached to the system starting with zero. This number is the same as the PCIe SSD subsystem ID number reported by the omreportcommand. For information on Command Line Interface, see the Server Administrator Command Line Interface User's Guide.
Table 4. PCIe Extender Card Properties Description ID Displays the ID assigned to the PCIe extender card by Storage Management. Status These icons represent the severity or health of the PCIe extender card. — Normal/OK — Warning/Non-critical — Critical/Failure/Error Name Displays the name of the extender card. State Displays the status of the extender card. Possible values are: Ready — The extender card is functioning normally.
Table 5. Physical Device Properties (continued) Properties Description spare sectors are less than 10 percent of the original pool, the drive enters read-only mode. Possible values for the device life status are: Drive Health Good — The drive is used within the TBW specification. The drive health is good as sufficient spare blocks are available. The drive health status is good if the values for percent lifetime used and write protect progress is less than 100 percent.
Table 5. Physical Device Properties (continued) Properties Description Firmware Revision Displays the firmware version of the physical device. NOTE: The updated firmware version reflects on the Storage Management page after a service restart for the NVMe drives which supports firmware update without reset. Model Number Displays the Piece Part Identification (PPID) of the PCIe SSD. Capacity Displays the capacity of the device. Vendor ID Displays the hardware vendor of the device.
Blinking And Unblinking A PCIe SSD The Blink task allows you to find a device within a system by blinking one of the LEDs on the device. You can use this task to locate a failed device. Select Unblink to cancel the Blink task or to stop the LED on a physical device that is blinking indefinitely. Enabling Full Initialization On A Micron PCIe SSD Does my controller support this feature? See Supported Features. CAUTION: Full Initialization permanently erases all data present on the disk.
NOTE: Orderly hot swap is only supported when the PCIe SSDs are installed in a supported system running a supported operating system. To ensure that you have the correct configuration for your PCIe SSD, see the system-specific Owner's Manual. NOTE: The Prepare to Remove task for PCIe SSDs is supported on systems running the VMware vSphere (ESXi) 6.0 and above operating system. However, this task is not supported on prior versions of VMware vSphere (ESXi) operating system.
4. Select the Physical Devices object. 5. Select Cryptographic Erase from the Tasks drop-down menu of the physical device you want to clear. 6. Click Execute. PCIe SSD In Slot Card Tasks You can perform the following tasks on the PCIe SSD in slot card: To perform a PCIe SSD in slot card task: 1. In the Server Administrator window, under the System tree, expand the Storage tree object to display the storage component objects. 2. Expand the PCIe SSD Subsystem object. 3. Select the PCIe SSD in Slot object. 4.
Table 6. PCIe SSD in Slot Card Properties (continued) Properties Description State Displays the status of the PCIe SSD in slot card. Possible values are: Ready — The PCIe SSD in slot card is functioning normally. Degraded — The PCIe SSD in slot card has encountered a failure and is operating in a degraded state. Failed — The PCIe SSD in slot card has encountered a failure and is no longer functioning. Device Name Displays the name of the PCIe SSD in slot card.
Table 6. PCIe SSD in Slot Card Properties (continued) Properties Description Add-in Card — For HHHL devices 2.5 inches — For physical devices other than a HHHL device. Sub Vendor Displays the vendor name of the device. Available Spare Displays the available spare value set for all PCIe SSDs. The new disk has 100% spare which will comes down as per the usage. Exporting The Log For A PCIe SSD In Slot Card The export log contains debug information for the PCIe SSD and can be useful when troubleshooting.
CAUTION: Cryptographic Erase permanently erases all data present on the disk. Performing a Cryptographic Erase on an NVMe PCIe SSD overwrites all blocks and results in permanent loss of all data on the NVMe PCIe SSD. During Cryptographic Erase, the host is unable to access the NVMe PCIe SSD. The following error messages will be displayed based on the actions performed while performing Crytographic erase NOTE: The error messages will not be displayed in CLI mode.
6 Storage Information And Global Tasks Use the Storage information and Global Tasks window to view high-level information about the storage components or devices on your system. These windows also allow you to launch global tasks that affect all controllers attached to the system. Topics: • • • Storage Properties Global Tasks Storage Controller Properties Storage Properties The Storage tree-view object has the following properties. Table 7.
NOTE: You can also click the Set Remaining Rated Writer Endurance Threshold link available on the Storage Dashboard to access this operation. 4. Click Execute. The Set Threshold for Remaining Rated Write Endurance window is displayed with the following options: ● Set Threshold for PCIe SSD (1–100) — Displays the default threshold value for all PCIe SSDs ● Set Threshold for SAS/SATA SSD (1–100) — Displays the default threshold value for all SAS/SATA SSDs 5.
4. In Set Threshold for PCIe SSD (1-99), enter the appropriate threshold value. NOTE: If available spare threshold value is set an alert message is generated. NOTE: The threshold value cannot be set to 100%. 5. Click Apply Changes. NOTE: If you click Apply Changes without entering a new threshold value for either of the available options an error message is displayed. Enter a new threshold value and then click Apply Changes to successfully complete the task. 6.
Table 9. Controller Properties (continued) Property Definition Minimum Required Firmware Version Displays the minimum firmware version that is required by Storage Management. This property is displayed only if the controller firmware does not meet the minimum requirement. Driver Version Displays the version of the drivers installed on the controller. Minimum Required Driver Version Displays the minimum driver version that is required by Storage Management.
7 Controllers This chapter provides information about the supported controllers and controller features in Storage Management.
● PERC H345 Frnt / Adapter ● PERC H745P MX, PERC H755 MX on MX 750c RAID Controller Features Different controllers have different features. If you have more than one controller attached to your system, you may notice that the tasks displayed on the Information/Configuration page of the controller are different for each controller. Controllers may also have differences in their read, write, and cache policies as well as how they handle hot spares.
● Read Ahead — The controller reads sequential sectors of the virtual disk when seeking data. Read ahead policy may improve system performance if the data is written to the sequential sectors of the virtual disk. ● No Read Ahead — Selecting no read ahead policy indicates that the controller should not use read ahead policy. Write Policy Does my controller support this feature? See Supported Features.
NOTE: The default setting for Disk Cache Policy for virtual disks based on SATA drives is Enabled, and for virtual disks based on SAS drives is Disabled. NOTE: For SAS 6i/R and PERC H200 family of controllers, the Disk Cache Policy setting is available only after creating the virtual disk.
Firmware Or Driver Versions Use the firmware or driver versions window to view information about the controller firmware and drivers. For more information on firmware and drivers, see Before Installing Storage Management. Related concepts Firmware Or Driver Properties Firmware Or Driver Properties The firmware and driver properties can vary depending on the model of the controller. The firmware and driver properties are listed in the table below.
NOTE: If you have connected the enclosure in Redundant path mode, the connectors are represented as Logical Connector. ● Virtual Disks Controllers Properties And Tasks Use the controllers properties and tasks window to view information about the controller and perform controller tasks. NOTE: The firmware and drivers listed in the Server Administrator Release Notes, see the minimum supported version for these controllers. Later versions of the firmware and drivers are also supported.
Table 11. Controller Properties (continued) Property Definition ● 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 Displays the version of the firmware that is installed on the controller. NOTE: Storage Management displays Not Applicable on some controllers for which the firmware version cannot be obtained.
Table 11. Controller Properties (continued) Property Definition Load Balance 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. Auto Replace Member on Predictive Failure Enables the automatic copying of data from a physical disk to a hot spare in case of predictive failure.
Table 11. Controller Properties (continued) Property Definition Patrol Read Iterations Displays the number of Patrol Read Iterations. For more information about patrol read, see Setting The Patrol Read Mode. Cluster Mode Indicates whether the controller is part of a cluster configuration. Persistent Hot Spare Displays if the hot spare is persistent. The possible values are: ● Enabled — The slot corresponding to the hot spare drive is persistent.
● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Turning Off The Controller Alarm Testing The Controller Alarm Setting The Rebuild Rate Resetting Configuration Exporting The Controller Log File Foreign Configuration Operations Importing Foreign Configurations Importing Or Recovering Foreign Configurations Clearing Foreign Configuration Setting Background Initialization Rate Setting Check Consistency Rate Setting The Reconstruct Rate Setting The Patrol Read Mode Starting And Stopping Patrol Read Managing The Pre
Setting The Rebuild Rate Does my controller support this feature? See Supported Features. The Set Rebuild Rate task allows you to change the rebuild rate for a controller. During a rebuild, the complete contents of a physical disk are reconstructed. The rebuild rate, configurable between 0% and 100%, represents the percentage of the system resources dedicated for rebuilding failed physical disks.
1. Review the virtual disks that are destroyed by resetting the controller configuration. Make backups as necessary. Click Blink at the bottom of the page 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 Locate Reset Configuration In Storage Management 1.
A foreign configuration is data residing on physical disks that have been moved from one controller to another. Virtual disks residing on physical disks that have been moved are considered to be a foreign configuration. NOTE: It is not recommended to remove an external enclosure cable while the operating system is running on the system. Removing the cable could result in a foreign configuration when the connection is re-established.
Table 12. Foreign Configuration Properties (continued) Property Definition ● Incompatible physical disks — Configuration on the physical disks is not recognized by the RAID firmware. ● Orphan drive — A physical disk in the foreign configuration has configuration information that matches another physical disk that is already a part of an array (either a foreign or a native array).
state. If the physical disk state is Foreign, then the physical disk contains all or some portion of a virtual disk or has a hot spare assignment. If you have an incomplete foreign configuration which cannot be imported, you can use the Clearing Foreign Configuration option to erase the foreign data on the physical disks. NOTE: The task of importing foreign configuration imports all virtual disks residing on physical disks that have been added to the controller.
1. In the Server Administrator window, under the system tree, expand Storage to display the controller objects. 2. Select a controller object. 3. Click Information/Configuration on the controller Properties page. 4. Select Foreign Configuration Operations from the Controller Tasks drop-down menu. 5. Click Execute. 6. In the Foreign Configuration Preview page, click Clear. For SAS controllers with firmware version 6.0 and earlier, select Clear Foreign Configuration from the Controller Tasks drop-down menu.
Table 13. Physical Disk Properties (continued) Property Definition ● 2110 ● 2111 For information on alert messages, see the Server Administrator Messages Reference Guide. Progress Displays the progress of an operation being performed on the physical disk. Bus Protocol Displays the technology that the physical disk is using.
Table 13. Physical Disk Properties (continued) Property Definition After Import Status Displays the status of the physical disk after importing the foreign configuration. Possible values are: ● Foreign ● Online ● Offline ● Replaced ● Rebuild Encryption Capable Displays whether the physical disk is a Self Encryption Disk (SED). The possible values are Yes and No. Encrypted Displays whether the physical disk is encrypted to the controller. The possible values are Yes and No.
time to complete, and has least impact to system performance. A check consistency rate of 0% does not mean that the check consistency is stopped or paused. At 100%, the check consistency is the highest priority for the controller. The check consistency time is minimized and has most impact to system performance. To Change The Check Consistency Rate For A Controller 1. Type a numerical value in the Set New Check Consistency Rate (0-100) field. The value must be within the 0–100 range. 2.
For redundant paths, the enclosure must be in the Unified mode however specific port connections are not required. A connection from either controller ports to either EMM In ports creates the redundant path as long as two cables are used. But, Redundant Path continues to appear in the field even as the redundant path is removed. The redundant path ceases to appear only when it is cleared in the storage management.
In the above scenario, the enclosure status is displayed as Warning. Clicking Information/Configuration in the Enclosures page displays all enclosure components (EMMs, Fans, Physical Disks, Power Supplies, and Temperature) in normal condition. The Path Failure message indicates that the enclosure has lost a communication path to the controller and the enclosure is no longer in redundant path mode. Set up single and multiple multipath connections On OpenManage 10.0.
Figure 2. Connecting a 4-port controller to enclosures in Multiple Multipath Similarly, you can connect a maximum of two Array584EMM enclosures to a 4-port HBA355e adapter. NOTE: MD14xx and Array584EMM enclosures cannot be connected to the same HBA355e adapter. 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 the following table: Table 16.
Does my controller support this feature? See Supported Features. Patrol read identifies disk errors in order to avoid disk failures and data loss or corruption. The Set Patrol Read task is applicable only for disks used as virtual disks or hot spares. The Set Patrol Read task runs in the background and corrects, when possible. When the Set Patrol Read mode is set to Auto, patrol read is initiated when the controller is idle for a period of time and when no other background tasks are active.
Click Start Patrol Read or Stop Patrol Read. NOTE: On PERC 9 family and later of hardware controllers, the Stop Patrol Read task displays: Patrol Read Aborted or Manually Stopped. On controllers prior to PERC 9, the Stop Patrol Read task displays: Patrol Read is Completed. To exit without starting or stopping the Patrol Read, click Go Back to Previous Page. Locate Start Stop Patrol Read In Storage Management 1.
Managing The Physical Disk Power Does my controller support this feature? See Supported Features. The Manage Physical Disk Power task allows you to manage the power consumed by the physical disks. NOTE: The Manage Physical Disk Power task is provided with H330 cards by spinning down the hot spares and unconfigured disks. PERC H730P, H730, cards also support the Manage Physical Disk Power task with additional powersaving modes, Spin Down Configured Drives, and Automatic Disk Power Saving (Idle C) options.
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. Managing Physical Disk Power Using The Customized Power Savings Mode To manage physical disk power through the Customized Power Savings Mode: 1. Select the Customized Power Save Mode option. 2. Edit the remaining parameters on the Manage Physical Disk Power page.
CAUTION: You may not be able to use Storage Management to manage the preserved cache in some cases. As an example, consider you have a RAID 1 level with two disks — D1 and D2. If you now remove D2, the virtual disk is degraded and the data in the controller cache is written to D1. So, D1 has the latest data. Now, if you re-insert D2 and pull out D1, the virtual disk is still degraded and does not have the latest data.
NOTE: If the system crashes while the file is created, the backup file is saved in the specified location. 5. Select the check-box indicating that you understand the implications of using a passphrase and click Apply Changes. In the controller Information/Configuration page, the Encryption Key Present is set to Yes and the Encryption mode is set to LKM. Changing Or Deleting The Encryption Key You can change an encryption key of a controller if the controller already has a configured encryption key.
3. Click Information/Configuration. 4. Select Manage Encryption Key.... from the Controller Tasks drop-down menu. 5. Click Execute. If the controller is encryption-capable and an encryption key is not present, then the Create Encryption Key page is displayed. Else, the Change or Delete Encryption Key page is displayed. Converting To Non-RAID Disks On supported PERC adapters: Does my controller support this feature? See Supported Features.
1. In the Server Administrator window, under the system tree, expand Storage to display the controller objects. 2. Select the Controller object. 3. Click Information/Configuration on the controller Properties page. 4. In the Controller Tasks drop-down menu, select Change Controller Mode..., and then click Execute. The Change Controller Mode window is displayed. The Current Controller Mode section displays the mode of the controller – RAID or HBA or Enhanced HBA. 5.
NOTE: If there are no physical disks in Ready state, the Auto Configure RAID0 operation fails and displays an error message. For more information about alerts and their corrective actions, see the Server Administrator Messages Reference Guide. at dell.com/openmanagemanuals. Set the Auto Configure Behavior of a RAID controller By using the Auto-Configure Behavior feature in OpenManage 10.0.
Global Tasks Supported When System Configuration Lock Down Mode Is On Table 18.
Table 20.
Table 22.
3. Click Execute. Viewing Slot Occupancy Report Does my controller support this feature? See Supported Features. The View Slot Occupancy Report allows you to view empty and occupied slot details of all enclosures and back planes. It provides a diagram that represents the occupancy of physical drive slots. Move the mouse over each slot to view details, such as physical disk ID, state, and size. Dynamic mapping of empty MX5016s will not be reflected on the drive.
Table 23. Physical Disk Firmware Version Report Properties Property Definition Name Displays the nexus or location of each drive that has to be updated. This nexus is represented as a two or three-digit mapping of the drive location.
8 Support For PERC 9, PERC 10, and PERC 11 Hardware Controllers The PowerEdge RAID Controller (PERC) family of enterprise-class controllers is designed for enhanced performance, increased reliability and fault tolerance, and simplified management — providing a powerful, easy-to-manage way to create a robust infrastructure and help maximize server uptime. The introduction of the PERC 9, PERC 10, and PERC 11 family of hardware controllers also brings about improvements in storage solutions.
RAID Level 10 Virtual Disk Creation With Uneven Span RAID Level 10 virtual disk creation with uneven span feature is available on Storage Management User Interface (UI) and Command Line Interface (CLI). For information on Storage Management CLI, see Server Administrator Command Line Interface Guide. ● Based on the minimum (and even) number of physical disks selection the firmware on the PERC 9 and later of hardware controller recommends the preferred span layout.
○ 4KB ● You cannot use both 4KB sector hard-disk drives and 512B sector hard-disk drives for a virtual disk creation as mixing of hard-disk drive sectors is not allowed in Storage Management. NOTE: If the system contains any 512e sector hard-disk drives, the 512e sector hard-disk drives are identified/reported as 512B sector hard-disk drives and follows the behavior of the 512B sector hard-disk drives.
9 Support for BOSS RAID Controllers All Operating Systems compatible are supported by BOSS RAID Controllers. The BOSS RAID Controllers supports the following enumeration and monitoring operations: ● The physical disks (M.2 devices) are directly connected to the Controller. ● Enumeration of Physical Disks on M.2 devices are supported. ● Enumeration of Virtual Disks on M.2 devices are supported. ● Physical disks operations or tasks for Blink and Unblink are supported only for BOSS-S2 (M.2 devices) controller.
10 Enclosures And Backplanes Physical disks can be contained in an enclosure or attached to the backplane of a system. An enclosure is attached to the system externally while the backplane and its physical disks are internal. Topics: • • • • • Backplanes Enclosures Enclosure Management Identifying An Open Connector On The Enclosure Enclosure Components Backplanes You can view the Backplane object by expanding the controller in the Storage Management tree view.
After you hot plug or hot reconfigure an enclosure, refresh the left tree to display the change in status and configuration; a system reboot is not required. NOTE: Storage Management does not allow hot removal of enclosures. Reboot the system to effect this change in Storage Management. NOTE: Minimum of six seconds gap is required for any hot-plugable device in or out operations . Storage Management notifies you of enclosure status changes through alerts that are displayed in the Alert Log.
Fan Properties Table 25. Fan Properties Property Definition Status These icons represent the severity or health of the storage component. — Normal/OK — Warning/Non-critical — Critical/Failure/Error For more information, see Storage Component Severity. Name Displays the name of the fan. State Displays the status of the fan. Possible values are: ● Ready — The fan is functioning normally. ● Degraded — The fan has encountered a failure and is operating in a degraded state.
Table 26. Power Supply Properties (continued) Property Definition Name Displays the name of the power supply. State Displays the status of the power supply. ● Ready — The power supply is functioning normally. ● Degraded — The power supply has encountered a failure and is operating in a degraded state. ● Failed — The power supply has encountered a failure and is no longer functioning. Storage Management is unable to communicate with the enclosure using SES commands.
Table 27. Temperature Probe Properties (continued) Property Definition — Warning/Non-critical — Critical/Failure/Error For more information, see Storage Component Severity. NOTE: On some enclosures, Storage Management may experience a short delay before displaying the current enclosure temperature and temperature probe status. For more information, see Storage Management May Delay Before Updating Temperature Probe Status. Name Displays the name of the temperature probe.
When the alarm on the enclosure is enabled, the EMM activates the alarm when certain conditions occur. For more information on enabling the alarm and the conditions that activate the alarm, see Enabling The Enclosure Alarm. For more information on EMMs, see the enclosure hardware documentation. All EMM modules in the enclosure should have the same version of firmware. You can view the properties of each individual EMM module to verify the firmware version.
Table 28. EMM Properties (continued) Property Definition and monitoring of all environmental elements, such as temperature sensors, cooling modules, and power supplies. SCSI Terminator — The SCSI terminator card is only used if the 220S or 221S enclosure is not configured with a redundant SCSI SES module type of EMM. In systems equipped with two SCSI SES modules, the SCSI termination is done through the EMMs. Firmware Version Indicates the version of the firmware loaded on the EMM.
Table 29. Enclosure and Backplane Properties (continued) Property Definition — Warning/Non-critical — Critical/Failure/Error NOTE: If the enclosure is connected to the controller in redundant path mode (for more information, see Setting The Redundant Path Configuration), the loss of connection to any one EMM may cause the enclosure status to be displayed as degraded. Name Displays the name of the enclosure or backplane. State Displays the status of the enclosure or backplane.
Table 29. Enclosure and Backplane Properties (continued) Property Definition NOTE: For systems supporting multiple backplanes, the firmware version appears as upstream and downstream versions. Service Tag Displays the enclosure Service Tag. The enclosure is identified by a unique Service Tag number. This information is used to route support calls to the appropriate personnel. Express Service Code The enclosure is identified by a unique Express Service Code number.
Disabling The Enclosure Alarm Does my enclosure support this feature? See Supported Features. Select the Disable Alarm task to disable the enclosure alarm. The alarm is turned off 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 turned on, you can turn it off with this task. Setting Asset Data Does my enclosure support this feature? See Supported Features.
Checking The Temperature Of The Enclosure Does my controller support this feature? See Supported Features. To check the temperature: 1. In the Server Administrator window, under the system tree, click Storage dashboard. 2. Expand the tree view until the Temperatures object is displayed. 3. Select the Temperatures object. The temperature reported by the temperature probe is displayed in celsius in the Reading column in the right pane.
To Locate View Slot Occupancy Report In Storage Management 1. In the Server Administrator window, under the system tree, expand Storage to display the controller objects. 2. Expand a controller object. 3. Select the enclosure object. 4. Click Information/Configuration. 5. Select View Slot Occupancy Report from the Available Tasks drop-down menu. 6. Click Execute. If the backplane supports flexible backplane zoning, then only the slots, empty or occupied, of the controller you are viewing is displayed.
Enclosure Components For information on attached components, see: ● ● ● ● ● Physical Disk Or Physical Device Properties EMM Properties Fan Properties Power Supply Properties Temperature Probe Properties and Tasks Enclosures And Backplanes 99
11 Connectors A controller contains one or more connectors (channels or ports) to which you can attach disks. You can externally access a connector by attaching an enclosure (for external disks) to the system or internally access by attaching to the backplane (for internal disks) of a system. You can view the connectors on the controller by expanding the controller object in the tree view.
Creating A Physical Disk For Channel Redundant Virtual Disks On PERC Controllers The following sections describe creating a channel-redundant virtual disk using RAID 10 or RAID 50 on PERC controllers. Creating A Channel-Redundant Virtual Disk Using RAID 10 To create a channel-redundant virtual disk using RAID 10: 1. Select one physical disk on each of the two channels. 2. Select an additional disk on each of the two channels. You have now selected the minimum number of disks for a RAID 10.
Table 30. Connector Properties (continued) Property Definition 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 Displays the connector number. State Displays the status of the connector.
Table 31. Logical Connector Properties (continued) Property Definition ● Failed — The connector has encountered a failure and is no longer functioning. Connector Type Displays whether the connector is operating in RAID mode. The connector is always a SAS connector. Path Health The path health of the connectors is represented as normal, warning, or critical. The possible values are displayed as Available, Degraded, or Failed.
12 Tape Drive Tape drives contain several tape backup units (TBUs) on which data can be backed up. Storage Management enumerates the TBUs that are used for data back up. You can view the tape drives associated with a particular controller on the Tape Drives on Controller page. Supports LTO-8 tape drives that can be connected to HBA355e. Topics: • Tape Drive Properties Tape Drive Properties Table 32. Tape Drive Properties Property Definition ID Displays the ID of the tape drive.
13 RAID Controller Batteries Some RAID controllers have batteries. If the controller has a battery, Storage Management displays the battery under the controller object in the tree view. If there is 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 backup of 24 hours. When a RAID controller is first installed in a server, the battery may need charging.
Table 33. Battery Properties (continued) Property Definition Next Learn Time Displays the number of days and hours left before the controller firmware initiates the next learn cycle. Maximum Learn Delay Displays the maximum number of days and hours that you can delay the battery learn cycle. The controller firmware automatically initiates the battery learn cycle. You cannot stop or pause the learn cycle, but you can delay it. Battery Tasks To access the battery tasks: 1.
Battery Transparent Learn Cycle The PERC H710 and PERC H810 controllers support Transparent Learn Cycle (TLC), a periodic operation that calculates the charge that is remaining in the battery to ensure that there is sufficient energy. The operation runs automatically, and causes no impact to the system or controller performance. The controller automatically performs TLC on the battery to calibrate and gauge its charge capacity once every 90 days. The operation can be performed manually, if required.
14 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.
NOTE: Clicking the Refresh button in the right pane refreshes only the right pane. To view the new physical disk in the left pane tree view, click the system name displayed at the top of the left pane, or click View > Refresh on the browser. The new physical disk or physical device is displayed in the tree view after refreshing the display. If the new disk is not displayed, restart the computer. Related Information ● If you are replacing a disk that is part of a virtual disk, see Replacing The Disk.
Physical Disk Or Physical Device Properties To view information about physical disks or physical device and perform physical disk or physical device tasks, use the Physical Disk Or Physical Device Properties page. Table 34. Physical Disk Properties Property Definition Status These icons represent the severity or health of the storage component. — Normal/OK — Warning/Non-critical — Critical/Failure/Error For more information, see Storage Component Severity.
Table 34. Physical Disk Properties (continued) Property Definition ● 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 applies only to physical disks that are part of a virtual disk.
Table 34. Physical Disk Properties (continued) Property Definition Failure Predicted Displays whether 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.
Table 34. Physical Disk Properties (continued) Property Definition In certain circumstances, the Used RAID Disk Space displays a value of zero even though a portion of the physical disk or device is being used. This occurs when the used space is 0.005GB or less. The algorithm for calculating the used disk space rounds a figure of 0.005GB or less to 0. Used disk space that is between 0.006GB and 0.009GB is rounded up to 0.01GB. Available RAID Disk Space Displays the amount of available space on the disk.
Physical Disk Or Physical Device Tasks To execute a physical disk or physical device task: 1. Expand the Storage tree object to display the controller objects. 2. In the Server Administrator window, under the system tree, expand Storage to display the controller objects. 3. Expand the enclosure or backplane object. 4. Select Physical Disks or Physical Devices object. 5. Click Information/Configuration on the controller Properties page. 6. Select a task from the drop-down menu. 7. Click Execute.
● The dead segment is included in a virtual disk, but the virtual disk is no longer using this area of the physical disk or physical device. ● The physical disk or physical device contains more than one virtual disk. In this case, disk space that is not included in one of the virtual disks may be unusable. ● The dead segment resides on a physical disk or physical device that has been disconnected and then reconnected to the controller.
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. Global hot spares must be assigned and unassigned manually. They are not assigned to specific virtual disks. If you want to assign a hot spare to a virtual disk (it replaces any physical disk that fails in the virtual disk), then use the Assign and Unassign Dedicated Hot Spare.
1. Review the physical disk to be erased. Ensure that it does not contain necessary data and make a backup if necessary. If you want to blink the physical disk, click Blink button. 2. Click Clear when you are ready to erase all information on the physical disk. To exit without clearing the physical disk, click Return to Previous Page. To Locate Clear In Storage Management To locate this task in storage management: 1.
Select the Cryptographic Erase task to erase an encrypted physical disk. This task is available for: ● ● ● ● ● Instant Secure Erase (ISE) capable drives Unconfigured SED drive Unconfigured NVMe drive Foreign configured encrypted drives Unconfigured and foreign SED drive even when an Encryption Key is not present in the controller NOTE: The cryptographic erase task will not be available after performing the task. Refresh after some time to get the task displayed.
Convert To RAID Capable Disk This task enables a disk for all RAID operations. NOTE: This task is not supported on PERC hardware controllers running in HBA mode. NOTE: This task is not supported on PERC 10 controllers. Convert To Non-RAID Disk This task converts a disk to a Non-RAID disk. After converting a disk to non- RAID, the disk is exposed to the operating system unlike unconfigured good disks and it enables usage of disk in direct pass-through mode.
15 Virtual Disks A virtual disk refers to a 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 viewed by the operating system as a single disk. Depending on the RAID level used, the virtual disk may retain redundant data if there is a disk failure or have particular performance attributes. NOTE: Virtual disks can only be created on a RAID controller.
● Number Of Virtual Disks Per Controller ● Calculation For Maximum Virtual Disk Size 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 ● Time Delay In Displaying Configuration Changes NOTE: In addition to this document, review the hardware documentation that is provided with the controllers.
Storage Management Server implements the disk group concept during virtual disk creation. Functionally, after a group of physical disks is used to create their first virtual disk, unused space in the disk is used only to expand the virtual disk, or create new virtual disks in the unused space. The virtual disks have identical RAID level. Also, existing mixed configuration is not affected. However, you cannot create mixed configurations.
Number Of Virtual Disks Per Controller There are limitations on the number of virtual disks that can be created on the controller. For information about the maximum number of virtual disks supported by a controller, see the virtual disk specifications for the controller in Supported Features. Calculation For Maximum Virtual Disk Size The Create Virtual Disk Express Wizard displays the minimum and maximum values for the virtual disk size.
Reconfiguring Or Migrating Virtual Disks Does my controller support this feature? See Supported Features. Reconfiguring or migrating a virtual disk enables you to increase the capacity or change the RAID level of the virtual disk.
Table 35.
● Virtual disk format ● I/O ● Patrol Read Recovering a physical disk bad block depends on the RAID level and state of the virtual disk. If a virtual disk is redundant, the controller can recover a bad block on a physical disk. If a virtual disk is not redundant, then the physical disk bad block results in a virtual disk bad block. Table 36. Sample Scenarios For Virtual Disk Bad Blocks RAID Level Virtual Disk State Scenario Result RAID 0 Degraded One bad block on a physical disk.
● Backup operation fails on one or more files. In this case, restore the file from a previous backup. After restoring the file, proceed to step 2. ● Backup operation completes without error. This indicates that there are no bad blocks on the written portion of your virtual disk. If you still receive bad block warnings, the bad blocks are in a non-data area. Proceed to step 2. 2. Run Patrol Read and check the system event log to ensure that no new bad blocks are found.
Table 37. Virtual Disk Properties (continued) Property Definition ● Failed Redundancy — This state is displayed when the initial consistency check for the virtual disk is canceled or is not successful. This state may also be displayed when a RAID 1, RAID 10 or RAID 1-concatenated virtual disk suffers a physical disk failure. In addition, there are other conditions related to disk failures and the firmware that can cause a virtual disk to display a Failed Redundancy state.
Table 37. Virtual Disk Properties (continued) Property Definition Write Policy Displays the write policy that the controller is using for the selected virtual disk. See RAID Controller Read, Write, Cache, and Disk Cache Policy. Stripe Size Displays the stripe size of the virtual disk. Disk Cache Policy Displays whether the disk cache policy of the physical disks that is part of the virtual disk is enabled or disabled. See RAID Controller Read, Write, Cache, and Disk Cache Policy.
Format, Initialize, Slow, And Fast Initialize Does my controller support this feature? See Supported Features. The Format, Initialize, Slow Initialize, or Fast Initialize task enables you to erase the files and remove the file systems on a virtual disk. Some controllers require that you initialize a virtual disk before it can be used. Canceling Background Initialization Does my controller support this feature? See Supported Features.
Resuming A Check Consistency Does my controller support this feature? See Supported Features. The Resume Check Consistency task resumes a check consistency after it has been paused. Blinking And Unblinking A Virtual Disk Does my controller support this feature? See Supported Features. The Blink and Unblink tasks blink or unblink the lights on the physical disks included in the virtual disk. NOTE: The blink operation is available only for removable disks.
Encrypting A Virtual Disk Does my controller support this feature? See Supported Features. The Encrypt Virtual Disk task encrypts an unencrypted virtual disk.
● Select RAID 50 to implement striping across more than one span of physical disks. RAID 50 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. ● Select RAID 60 to implement striping across more than one RAID 6 span. RAID 60 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.
Before creating a virtual disk, you should be familiar with the information in Considerations Before Creating Virtual Disks. You may also want to review Choosing RAID Levels And Concatenation. NOTE: This task is not supported on PERC hardware controllers running in HBA mode. To create a virtual disk using the Create Virtual Disk Advanced Wizard: 1. On the left-hand side of the Server Administrator page, expand Storage. 2. Click on the . 3. Click on Virtual Disks.
￭ ￭ Across connectors at the same level of enclosure and of acceptable size difference. 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. The number of spans and disks in the span is recalculated.
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 the number of disks that must be included in each stripe or span. If the controller is a SAS controller with firmware versions 6.1 and later and you selected RAID 10, RAID 50, and RAID 60, the user interface displays the following: ● All Disks — Enables you to select all the physical disks in all the enclosures.
the Size field. In some cases, the virtual disk is slightly larger than the size you specify. The Create Virtual Disk Wizard adjusts the size of the virtual disk to avoid rendering a portion of the physical disk space unusable. 3. Select a stripe size from the Stripe Element Size drop-down list box. The stripe size refers to the amount of space that each stripe consumes on a single disk. 4. Select the required read, write, and disk cache policy from the respective drop-down list box.
Before continuing with the virtual disk reconfiguration, you should be familiar with the information in Starting And Target RAID Levels For Virtual Disk Reconfiguration And Capacity Expansion and Choosing RAID Levels And Concatenation. NOTE: You cannot reconfigure a virtual disk on a controller that is operating in cluster mode. NOTE: You can create no more than 64 virtual disks on a controller. After you have reached this limit, you can no longer reconfigure any of the virtual disks on the controller.
● Select RAID 1 for mirroring disks — This selection groups two disks together as one virtual disk with a capacity of one single disk. The data is replicated on both disks. When a disk fails, the virtual disk continues to function. This feature provides data redundancy and good read performance, but slightly slower write performance. The system must have at least two physical disks to use RAID 1.
2. Click Finish to complete the virtual disk reconfiguration. To exit without changing the original virtual disk, click Exit Wizard. NOTE: After the virtual disk reconfiguration process starts, the read and write policies temporarily revert to the default settings until the process is completed. Slow And Fast Initialize Considerations For Fast Initialize The Fast Initialize task initializes all physical disks included in the virtual disk.
● ● ● ● Format Initialize Slow Initialize Fast Initialize 5. Click Execute. Deleting A Virtual Disk 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.
To Locate Rename In Storage Management To locate this task in storage management: 1. In the Server Administrator window, under the system tree, expand Storage to display the controller objects. 2. Expand a controller object. 3. Select the Virtual Disks object. 4. Select Rename from the Available Tasks drop-down menu. 5. Click Execute. Changing The Policy Of A Virtual Disk Does my controller support this feature? See Supported Features.
4. Select Split Mirror from the Available Tasks drop-down menu. 5. Click Execute. Unmirror Does my controller support this feature? See Supported Features. Use the Unmirror task to separate mirrored data and restore one half of the mirror to free space. Unmirroring a RAID 1 or RAID 1-concatenated virtual disk results in a single, nonredundant concatenated virtual disk. Unmirroring a RAID 10 virtual disk results in a single, nonredundant RAID 0 (striped) virtual disk. Data is not lost during this operation.
1. Select the disk in the Disks currently configured as dedicated hot spare table to unassign it. On some controllers, more than one disk can be selected. Clicking the disk removes the disk from the Disks currently configured as dedicated hot spare table and returns it to the Connector (channel or port) table. 2. Click Apply Changes when ready. To Locate Assign Or Unassign Dedicated Hot Spare In Storage Management 1. Expand the Storage tree object to display the controller objects. 2.
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 page displays the summary of the attributes of the virtual disk in which you replaced the member disk. Use this page to review your changes before completing the virtual disk replace member task. To Replace a Member Disk: Step 2 of 2 1. Review your changes.
16 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. Topics: • • Required Conditions Migrating SAS Virtual Disks To Another System Required Conditions SAS Controllers Virtual disks can only be migrated to a controller that is using the same technology. For example, virtual disks on a SAS controller must be migrated to a SAS controller.
17 Protecting Your Virtual Disk With A Hot Spare When you create a virtual disk using a RAID controller, it enables the system to continue functioning even during a disk failure. This feature can be enabled by assigning a hot spare to the virtual disk. When a disk fails, the redundant data is rebuilt onto the hot spare without interrupting system operations.
Table 38. Hot Spare Properties (continued) Property Definition NOTE: The status of the virtual disk is determined by the severity level you specify for this policy. Resetting The Hot Spare Protection Policy Clear RAID Layout to reset the dedicated hot spare protection policy. Global Hot Spare Protection Policy Table 39. Global Hot Spare Protection Policy Properties Property Definition Enable Global Hot Spare Enables the Global Hot Spare Protection Policy.
NOTE: For PERC H700 and PERC 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, you can assign more than one dedicated hot spare to a virtual disk. Considerations For Hot Spares On PERC S100, PERC S300, PERC S130 and later controllers For the PERC S100, PERC S300, PERC S130 and later controllers, a hot spare is assigned to a virtual disk.
18 Troubleshooting This section contains troubleshooting procedures for common situations as well as for specific problems. Topics: • • • • Common Troubleshooting Procedures Virtual Disk Troubleshooting Specific Problem Situations And Solutions PCIe SSD Troubleshooting Common Troubleshooting Procedures This section describes commands and procedures that can be used in troubleshooting.
Isolate Hardware Problems If you receive a timeout alert related to a hardware device or if you otherwise suspect that a device attached to the system is experiencing a failure, then to confirm the problem: ● Verify that the cables are correctly connected. ● If the cables are correctly connected and you are still experiencing the problem, then disconnect the device cables and reboot the system. If the system reboots successfully, then one of the devices may be defective.
4. Create a new virtual disk. 5. Restore from backup. Using The Physical Disk Online Command On Select Controllers Does my controller support this feature? See Supported Features. If you do not have a suitable backup available, and if the failed disk is part of a virtual disk on a controller that supports the Online physical disk task, then you can attempt to retrieve data by selecting Online from the drop-down task menu of the failed disk.
● The virtual disk is nonredundant — 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: ○ Remove 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.
● Virtual disk or logical drive size is smaller than expected. If you have created a virtual disk that exceeds the 1TB limitation, you must: 1. Back up your data. 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.
● 2148 ● 2149 ● 2150 This damage is discovered when the controller performs an operation that requires scanning the disk. Examples of operations that may result in these alerts are as follows: ● ● ● ● Consistency check Rebuild Virtual disk format I/O If you receive alerts 2146 through 2150 as the result of performing a rebuild or while the virtual disk is in a degraded state, then data cannot be recovered from the damaged disk without restoring from the backup.
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. This problem resolves when the Windows operating system recovers from hibernation.
Physical Disks Are Displayed Under The Connector Object Instead Of The Enclosure Object Storage Management surveys the status of physical disks at frequent intervals. When the physical disk is located in an enclosure, the data reported by the SCSI Enclosure Processor (SEP) is used to determine the status of the physical disk. When the SEP is not functioning, Storage Management can survey the status of the physical disk, but cannot identify the physical disk as being located in the enclosure.
19 Frequently Asked Questions This section provides frequently asked questions that address situations commonly experienced in a storage environment.
How Do I Identify The Firmware Version That Is Installed The properties information of the controller 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. You can also view this information in the Information/Configuration page of the controller. To display the firmware version of all controllers: 1. Select the Storage object in the tree view. 2.
20 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 chapter lists the features supported by the controllers. For more information on Controllers, see your hardware documentation. NOTE: The order of the controllers displayed on Storage Management may differ with the order of the controllers displayed in the Human Interface (HII) and PERC Option ROM.
Table 40.
Table 40.
Table 40. Controller Tasks Supported On PERC Hardware Controllers (continued) Controller Task Name PERC H745 Frnt/ Adapter Physical Disk Firmware Version Report PERC H345 PERC Frnt / H755N Adapter Yes Yes PERC H755 Frnt/Adapter Yes PERC H745P MX Yes PERC H755 PERC H840 MX Adapter Yes Yes Yes Battery Tasks Supported On PERC Hardware Controllers NOTE: The Battery Tasks are not supported on PERC Hardware Controllers Table 41.
Table 42.
Table 43.
Table 44.
Table 44.
Read, Write, Cache And Disk Cache Policy Supported By PERC Hardware Controllers Table 46.
Controller Tasks Supported On H200 Controllers Table 47.
Physical Disk Tasks Supported On H200 Controllers Table 50. Physical Disk Tasks Supported on H200 Controllers Physical Disk Task Name PERC H200 Blink/Unblink Yes Assign and Unassign Global Hot Spare Supports up to two global hot spares Prepare to Remove No Offline No Online No Initialize No Rebuild NA Rebuild automatically initiated by the controller.
Table 51. Virtual Disk Tasks Supported On H200 Controllers (continued) Virtual Disk Task Name PERC H200 Cancel Format Virtual Disk No Restore Dead Disk Segments No Initialize Virtual Disk No Fast Initialize Virtual Disk No Slow Initialize Virtual Disk No Cancel Initialize Virtual Disk No RAID Levels Supported By H200 Controllers Table 52.
Table 53.
Supported Features On The PERC Software RAID Controllers This section identifies the controller-supported features and whether or not an enclosure can be attached to the controller. The Software RAID controller includes PERC S100, PERC S110, PERC S130, PERC S300, PERC S140, and PERC S150 Controller.
Table 58. Virtual Disk Tasks Supported by the PERC S150 Controllers Virtual Disk Task Name PERC S150 Assign and Unassign Dedicated Hot Spare Yes Create Virtual Disk Yes Create Virtual Disk Advanced Wizard Yes Create Virtual Disk Express Wizard Yes Rename Yes Blink/Unblink Yes Reconfigure Yes Change Policy Yes Delete (any) Virtual Disk Yes Check Consistency Yes Check Cancel Consistency Yes Disk Cache Policy Yes Virtual Disk Specifications For PERC Software RAID Controllers Table 59.
information does not cause any functional limitation. If you are creating partial virtual disks, it is recommended that you provide Storage Management adequate time between each partial virtual disk creation process. NOTE: RAID 1 VD on SWRAID controller will enumerate for the attribute Stripe Element Size as NA. RAID Levels Supported By The PERC Software RAID Controllers Table 60.
Table 62. Enclosure Support on the PERC S150 Controller Enclosure Support PERC S150 Can an enclosure be attached to this controller? No Supported Features On The Non-RAID Controllers This section identifies the controller-supported features and whether an enclosure can be attached to the controller. ● Controller Tasks ● Battery Tasks ● Connector Tasks ● Physical Disk Tasks ● Virtual Disk Tasks ● Enclosure Support For enclosure supported tasks, see Enclosure And Backplane Features.
Battery Tasks Supported By Non-RAID Controllers Table 64. Battery Tasks supported by 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 Supported On The Non-RAID Controllers Table 65. Connector Tasks Supported on the Non-RAID Controllers Connector Task Name Non-RAID SCSI Non-RAID SAS Connector Rescan No No Physical Disk Tasks Supported On The Non-RAID Controllers Table 66.
Table 67.
Enclosure And Backplane Tasks Table 69.
21 Determining The Health Status For Storage Components The chapter describes 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 - Physical Disks In A Virtual Disk Are Failed Or Removed Table 72. Health Status Rollup: Physical Disks in a Virtual Disk are Failed or Removed (Enclosures Not Included) Storage Subsystem Controller Battery Connector Physical Disk(s) Firmware/ Driver Virtual Disks Component Status Health Rollup Health Status Rollup - Physical Disks In A Virtual Disk Are Unsupported, Partially, Or Permanently Degraded Table 73.
Health Status Rollup - Some Physical Disks In A Virtual Disk Are In Foreign State Table 75. Health Status Rollup: Some Physical Disks in a Virtual Disk are in Foreign State (Enclosures Not Included) Storage Subsystem Controller Battery Connector Physical Disk(s) Firmware/ Driver Virtual Disk(s) Component Status Health Rollup Health Status Rollup - Virtual Disk Is Degraded, Physical Disks Are Failed Or Rebuilding Table 76.
Health Status Rollup - Enclosure Power Supply Failed Or Power Connection Removed Table 79. Health Status Rollup: Enclosure Power Supply Failed or Power Connection Removed Storage Subsystem Controller Connector Enclosure Enclosure Power Supply Virtual Disks Physical Disks N/A N/A Component Status Health Rollup N/A Health Status Rollup - One Enclosure Fan Is Failed Table 80.
Table 82. Health Status Rollup: One Enclosure Temperature Probe is Failed (continued) Storage Subsystem Controller Connector Enclosure Health Rollup Enclosure Virtual Disks Temperature Probe Physical Disks N/A Health Status Rollup - Lost Both Power Connections To The Enclosure Table 83.
A Identifying the series of your Dell EMC PowerEdge servers The PowerEdge series of servers form Dell EMC are divided into different categories on the basis of their configuration. For easier reference, they are referred to as YX2X, YX3X, YX4X, YX4XX, or YX5XX series of servers. The structure of the naming convention is described below: The letter Y denotes the alphabets in the server model number. The alphabets denote the form factor of the server.
