Dell EMC Server Administrator Storage Management 10.1.0.0 June 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 Component Severity.........................................................................................................................................29 Storage Properties And Current Activity.................................................................................................................... 30 Alerts Or Events................................................................................................................................................................
Read Policy................................................................................................................................................................... 50 Write Policy...................................................................................................................................................................50 Disk Cache Policy...........................................................................................................................................
Viewing Slot Occupancy Report..............................................................................................................................85 Viewing Physical Disk Firmware Version Report................................................................................................. 85 Physical Disk Firmware Version Report Properties.............................................................................................
Battery Properties And Tasks....................................................................................................................................... 110 Battery Tasks..................................................................................................................................................................... 111 Battery — Available Tasks........................................................................................................................................
Recommendations For Clearing Bad Blocks..............................................................................................................132 Virtual Disk Properties And Tasks................................................................................................................................132 Virtual Disk Properties.............................................................................................................................................. 132 Virtual Disk Tasks......
To Locate Unmirror In Storage Management..................................................................................................... 149 Assigning And Unassigning Dedicated Hot Spare....................................................................................................149 Assigning A Dedicated Hot Spare.......................................................................................................................... 150 Unassigning A Dedicated Hot Spare..........................
Alerts 2146 Through 2150 Received While Performing IO, Consistency Check, Format, Or Other Operation..................................................................................................................................................................161 Read And Write Operations Experience Problems............................................................................................. 161 A Task Menu Option Is Not Displayed....................................................................
Virtual Disk Specifications For PERC Software RAID Controllers.................................................................. 191 RAID Levels Supported By The PERC Software RAID Controllers................................................................192 Read Write Cache And Disk Cache Policy Supported By The PERC Software RAID Controllers......... 193 Enclosure Support On The PERC Software 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.
If you install Storage Management without the minimum required firmware and drivers, Storage Management may not be able to display the controllers or perform other functions. Storage Management generates alerts 2131 and 2132 when it detects unsupported firmware or drivers on a controller. For information on alert messages, see the Server Administrator Messages Reference Guide.
NOTE: A logical connector is displayed for all PERC 10 and later family of hardware controllers, HBA controllers, and MX series controllers all the physical disks will be detected under this logical connector. However, the logical connector will not be displayed under PERC 9 and prior family of hardware controllers,12 Gbps HBA and PERC H840. NOTE: At times, the connector ID for SAS 12 Gbps HBA may not be displayed correctly on Storage Management.
2 Getting Started Server Administrator Storage Management is designed for system administrators who implement hardware RAID solutions and understand corporate and small business storage environments. Storage Management enables you to configure the storage components attached to your system. These components include RAID and non-RAID controllers and the channels, ports, enclosures, and disks attached to them.
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 2.
Table 2. 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 3. 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 4. 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 5. 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 6. 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 6. 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.
6. In the Export Telemetry Log page, the following attributes are displayed: ● Host Name ● Path ● File Name — In this text box, you can provide a custom file name for the log file. The export telemetry log file is saved with a .bin file extension and the file extension cannot be overwritten by any other file extension entered by the user. The default file name is NVME_TELEMETRY__.bin.
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. Select a task from the Available Tasks drop-down menu. 5. Click Execute. To Locate Cryptographic Erase In Storage Management For A PCIe SSD In Slot Card 1.
Table 7. PCIe SSD in Slot Card Properties (continued) Properties Description Device Name Displays the name of the PCIe SSD in slot card. The name comprises the bay ID and the slot in which the PCIe SSD in slot card is installed. Bus Protocol Displays the technology that the PCIe SSD is using. Device Protocol Displays the device protocol of the PCIe SSD in slot card, such as Non-Volatile Memory Express (NVMe).
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. You can export the reliability log for the PCIe SSD in Slot Card from the Available Tasks drop-down list. Related information To Locate Export Log In Storage Management For NVMe PCIe SSDs To Locate Export Log In Storage Management For NVMe PCIe SSDs To locate this task in storage management: NOTE: This operation is supported only on NVMe PCIe SSDs. 1.
● If any Raw IO in progressWhen you perform the 'Cryptographic Erase' operation, any data on the disk will be lost permanently.This device may still be in use. We recommend that you stop all applications accessing the device before continuing. Areyou sure you want to continue? NOTE: If the system reboots or experiences a power loss during a Cryptographic Erase, the operation is canceled. You must reboot the system and restart the operation.
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 8.
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 10. 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.
Table 11.
Controller — Supported Stripe Sizes When creating a virtual disk, you must specify the stripe size for the virtual disk. Different controllers have different limitations on the stripe sizes they can support. For information on the supported stripe sizes for a controller, see the virtual disk specifications section for the controller in Supported Features.
The following are the disk cache policy options for Non-RAID disks connected to a PERC hardware controller: ● Enabled — Disk Cache Policy is enabled. ● Disabled — Disk Cache Policy is disabled. ● Unchanged — The disk uses the default write cache mode. NOTE: The Unchanged option is applicable only for PERC 9 and later of hardware controllers with the latest firmware version.
● ● ● ● ● ● HBA 330 Mini HBA 330 Adpt HBA 345 Frnt/Adpt HBA 355i Frnt/Adpt HBA 355e HBA 350iMX NOTE: Storage Management only enumerates and provides the PCI slot information for Broadcom SAS 9207-8e and SAS 9300-8e controllers. As Storage Management does not monitor these non-RAID controllers, devices connected to these controllers are not enumerated, alerts are not logged, and SNMP traps are not sent for these controllers.
Table 12. Firmware/Driver Properties (continued) Property Definition Minimum Required Driver Version Displays the minimum driver version that is required by Storage Management. This property is displayed only if the controller driver does not meet the minimum requirement. Storport Driver Version Displays the version of the storport driver that is installed on the system. Minimum Required Storport Driver Version Displays the minimum storport driver version required by Storage Management.
Table 13. Controller Properties (continued) Property Definition ● Name — Critical/Failure/Error Displays the name of the controller. NOTE: For PowerEdge FD332 storage sled, the name is displayed as: ● Single controller — PERC FD33xS (Integrated RAID Controller in Front Chassis Slot , where X displays the controller number and Y displays the front chassis slot number.
Table 13. Controller Properties (continued) Property Definition Rebuild Rate Rebuild rate is the percentage of resources available on a system dedicated to rebuild a failed disk when necessary. For more information on rebuild rate, see Setting The Rebuild Rate. NOTE: The value for the Revertible Hot Spare operation is the same as the value set for the Rebuild Rate property.
Table 13. Controller Properties (continued) Property Definition Patrol Read Mode Displays the Patrol Read Mode setting for the controller. Possible values are: ● Auto — 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 an interval specified by the controller. You do not have the option of manually starting or stopping the Patrol Read in this mode.
Table 13. Controller Properties (continued) Property Definition Auto Configure Behavior Displays the nonconfigured hot inserted Non-RAID physical disks which are in ready state. The possible attributes are Off and Non-RAID Disk. However, these attributes depend on the storage support available on the system. Front Chassis Slot Displays the front chassis slot number. This property is applicable only for PowerEdge FD332 storage sled.
Creating A Virtual Disk Does my controller support this feature? See Supported Features. To launch the Create Virtual Disk Express Wizard, select the Create Virtual Disk task. Enabling The Controller Alarm Does my controller support this feature? See Supported Features. To enable the alarm on the controller, select the Enable Alarm task. When enabled, the alarm sounds in the event of a device failure. Disabling The Controller Alarm Does my controller support this feature? Supported Features.
2. Click Apply Changes. To exit and cancel your changes, click Return to Previous Page. To locate Set Rebuild Rate In Storage Management 1. Expand the Storage tree object to display the controller objects. 2. Select a controller object. 3. Click Information/Configuration. 4. Select Set Rebuild 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.
Depending on the controller, the log file name is afa_.log or lsi_.log, where is the month and date. NOTE: In the VMware ESXi environment, only one log file is created (lsiexport.log). If the file exists, exporting the log file overwrites the existing log file. NOTE: Controllers without cache cannot store logs and export log files. Export The Controller Log File 1. Click Export Log File when ready. 2. To exit without exporting the controller log file, click Return to Previous Page.
Foreign Configuration Properties The following table describes the properties that are displayed for the Foreign Disks and Global Hot Spares. Table 14. Foreign Configuration 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 foreign configuration and is available as a link.
Based on the properties information, you can decide whether you want to import, recover, or clear the foreign configuration. To Locate Foreign Configuration Operations Task In Storage Management For SAS controllers with firmware version 6.1: 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.
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 Import/Recover. For SAS controllers with firmware version 6.0 and earlier, select Import/Recover Foreign Configuration from the Controller tasks. Clearing Foreign Configuration Does my controller support this feature? See Supported Features.
Table 15. Physical Disk Properties (continued) Property Definition Name Displays the name of the physical disk. The name is comprised of the connector number followed by the disk number. State Displays the current state of the physical disk. After Import State 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.
Table 15. Physical Disk Properties (continued) Property Definition ● Unknown — Storage Management is unable to determine the media type of the physical disk. Used RAID Disk Space Displays the amount of the physical disk space that is used by the virtual disks on the controller. This property is not applicable for physical disks attached to non-RAID controllers.
The background initialization rate, configurable between 0% and 100%, represents the percentage of the system resources dedicated for running the background initialization task. At 0%, the background initialization has the lowest priority for the controller, takes maximum time to complete, and has the least impact to system performance. A background initialization rate of 0% does not mean that the background initialization is stopped or paused.
The Set Reconstruct Rate task changes the amount of system resources dedicated for the reconstruct task. The reconstruct task recreates the virtual disk after you have changed the RAID level or reconfigured the virtual disk. The reconstruct rate, configurable between 0% and 100%, represents the percentage of the system resources dedicated for running the reconstruct task.
If the communication channel between the connector and the first enclosure is lost, the redundant path configuration is lost. In this case, the health of the logical connector is displayed as critical. Navigate to the Information/Configuration page of the logical connector to view details of the Path Health. For a brief outline of this scenario, see the following table: Table 16.
Set up single and multiple multipath connections On OpenManage 10.0.1 and later versions, controllers that have four ports enable you to connect enclosures in single multipath and multiple multipath connections. At a time, you can connect a maximum of four enclosures in multiple multipath connection. However, you can connect a maximum of eight enclosures in singlepath.
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 18.
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.
To start or stop the Patrol Read Task: 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 20.
Global Tasks Name PERC S150 HBA 345 HBA 355i PERC 755 Front / Adapter PERC H755N Front PERC HBA355e H745 Front / Adapte r HBA 350i MX PERC H755 MX PERC H755 Front/ Adapter No No No No No No No No Thresh old Settin No g Availab le Spare Thresh old No Controller Tasks Supported When System Configuration Lock Down Mode is On Table 21.
Controller Reports Supported When System Configuration Lock Down Mode is On Table 22.
Controlle r Reports Name PERC H745P Front and Adapter PERC H345 Front and Adapter HBA 355i PERC 755 Front / Adapter PERC H755N Front PERC 745 Front/ Adapter HBA355 e HBA 350i MX PERC H755 MX PERC H755 Frnt / Adapt er Version Report Physical Disk Tasks Supported When System Configuration Lock Down Mode Is On Table 23.
Virtual Disk Tasks Supported When System Configuration Lock Down Mode Is On Table 24.
1. In the Server Administrator window, under the system tree, click Storage. 2. Select View Patrol Read Report from the Select Report drop-down menu. 3. Click Execute. Viewing Check Consistency Report Does my controller support this feature? See Supported Features. The check consistency report provides information on all the consistency checks performed on the controller in a chronological order. It provides information such as last run time and result.
On systems running Linux: /opt/dell/srvadmin/etc/srvadmin-storage/hddfwver.csv On systems running ESXi: /etc/cim/dell/srvadmin/srvadmin-storage/hddfwver.csv If the existing firmware(s) for all physical disks is the latest, the following message is displayed: There are no physical disks available that require firmware update. Physical Disk Firmware Version Report Properties The report displays information for the drives that require a firmware upgrade as listed in the table below: Table 25.
Table 25. Physical Disk Firmware Version Report Properties (continued) Property Definition Part Number In the event of a drive failure, you can run the View Physical Disk Firmware Version Report to find out the part number of the failed drive and to check if any of the drives require an update.
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.
Related Tasks ● Create Virtual Disk Express Wizard ● Create Virtual Disk Advanced Wizard 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.
● When you create a virtual disk using the Advanced Wizard, you can select the physical disk sector from the Sector Size drop-down list. The options available are: ○ 512B ○ 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.
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 27. 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 28. 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 29. 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 30. 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 31. 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 31. 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 104 Enclosures And Backplanes
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 32. 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 33. 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 34. 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 35. 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 36. 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 36. 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 36. 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 36. 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.
● Reconfiguring virtual disks — The Reconfigure task is not available when you have more than one virtual disk using the same set of physical disks. You can, however, reconfigure a virtual disk that is the only virtual disk residing on a set of physical disks. ● Virtual disk names not stored on controller — The names of the virtual disks that you create are not stored on the controller.
Number Of Physical Disks Per Virtual Disk There are limitations on the number of physical disks that can be included in the virtual disk. These limitations depend on the controller. When creating a virtual disk, the controllers support some stripes and spans (methods for combining the storage on physical disks). Since, the number of total stripes and spans is limited, the number of physical disks that can be used is also limited.
Creating Virtual Disks Does my controller support this feature? See Supported Features. WARNING: There is an automatic initialization in the background which starts and if there are some user data it will be erased. In order to implement RAID functions, you 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.
Table 38.
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. A global hot spare drive can be part of different RAID level Virtual drives rebuilding operation on SWRAID controllers.
Table 39. Sample Scenarios For Virtual Disk Bad Blocks (continued) RAID Level Virtual Disk State Scenario Result RAID 6 Degraded (two failed/missing physical disks) One bad block on a physical disk. The controller cannot regenerate data from the peer disks. This results in a virtual disk bad block. RAID 6 Ready One bad block on a physical disk. The controller regenerates data from peer disks and sends a Write to the bad block.
Table 40. Virtual Disk Properties (continued) Property Definition For more information, see Storage Component Severity. Name Displays the virtual disk name. For all the disk which are not part of the virtual disk will display as NON-Raid Disks for systems running on Enhanced HBA mode. Hot-plugged in disks will also come up as NON-RAID disks. State Displays the status of the virtual disk. Possible values are: ● Ready — The virtual disk is functioning normally.
Table 40. Virtual Disk Properties (continued) Property Definition virtual disk size of 819.725 is rounded down to 819.72. A virtual disk size of 819.726 is rounded up to 819.73. Device Name Displays the operating system device name for this object. NOTE: Device name is not displayed for a virtual drive on BOSS. Bus Protocol Displays the technology that the physical disks included in the virtual disk are using.
● ● ● ● ● ● ● ● ● ● ● ● ● ● Assigning And Unassigning Dedicated Hot Spare Performing A Check Consistency Canceling A Check Consistency Pausing A Check Consistency Resuming A Check Consistency Blinking And Unblinking A Virtual Disk Renaming A Virtual Disk Split Mirror Unmirror Canceling A Rebuild Changing The Virtual Disk Policy Replacing A Member Disk Clearing Virtual Disk Bad Blocks Encrypting A Virtual Disk Reconfiguring A Virtual Disk Does my controller support this feature? See Supported Features.
Performing A Check Consistency Does my controller support this feature? See Supported Features. The Check Consistency task verifies the accuracy of the redundant (parity) information. This task only applies to redundant virtual disks. When necessary, the Check Consistency task rebuilds the redundant data. If the virtual disk is in a Failed Redundancy state, running a check consistency may be able to return the virtual disk to a Ready state.
Changing The Virtual Disk Policy Does my controller support this feature? See Supported Features. The Change Policy task enables you to change the read, write, or cache policy of a virtual disk. Changes to the read, write, and cache policy only apply to the virtual disk that you have selected. This task does not change the policy for all virtual disks on the controller. Replacing A Member Disk Does my controller support this feature? See Supported Features.
Table 42.
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. The system must have at least four physical disks to use RAID 10. ● 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.
controller connector. You must have a good knowledge of RAID levels and hardware, to use the Advanced Wizard. If you want the wizard to choose a recommended virtual disk configuration for you, select the Express Wizard option. 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.
￭ ￭ ￭ ￭ Across enclosures connected to the same connector and to a disk of the same size. Within the enclosure with a physical disk of acceptable size difference. 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.
● Physical disk 0:0:0 ● Physical disk 0:1:0 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.
NOTE: The Size field displays the default size of the virtual disk depending upon the RAID configuration you selected. You can specify a different size. The virtual disk size must be within the minimum and maximum values displayed near 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.
The Reconfigure task enables you to change the virtual disk configuration. Using this task, you can change the RAID level and increase the virtual disk size by adding physical disks. On some controllers, you can also remove physical disks. Before continuing with the virtual disk reconfiguration, you should be familiar with the information in Starting And Target RAID Levels For Virtual Disk Reconfiguration And Capacity Expansion and Choosing RAID Levels And Concatenation.
Virtual Disk Task - Reconfigure Step 2 of 3 Does my controller support this feature? See Supported Features. The virtual disk reconfigure Step 2 page enables you to select the RAID level and size for the reconfigured virtual disk. If you selected Expand Capacity in Step 1, this page allows you to expand the capacity of the virtual disk. To Reconfigure a Virtual Disk (Changing the RAID Level and Size): Step 2 of 3 1.
To Reconfigure A Virtual Disk Expand Virtual Disk Capacity - Step 2 of 3 NOTE: For RAID 10 partial virtual disks, there are only two methods to increase the disk size or capacity: ● Expanding the capacity by increasing the percentage value. ● Adding disks into the original RAID 10 virtual disk. 1. Enter the percentage of the free disk size available by which you want to expand the virtual disk capacity. The page displays the maximum free size available and the description of the selected RAID level. 2.
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 page to blink the physical disks included in the virtual disk. 2.
5. Click Execute. Renaming A Virtual Disk Does my controller support this feature? See Supported Features. Renaming a virtual disk enables you to change the name of the virtual disk. The numbering format for the virtual disk remains unchanged. Depending on the controller you have, there are different considerations regarding the controller BIOS: The virtual disk name can contain only alphanumeric characters as well as spaces, dashes and underscores. The maximum length of the name depends on the controller.
Split Mirror Does my controller support this feature? See Supported Features. Use the Split Mirror task to separate mirrored data originally configured as a RAID 1, RAID 1-concatenated, or RAID 10 virtual disk. Splitting a RAID 1 or RAID 1-concatenated mirror creates two concatenated non-redundant virtual disks. Splitting a RAID 10 mirror creates two RAID 0 (striped) non-redundant virtual disks. Data is not lost during this operation.
A dedicated hot spare is an unused backup disk that is assigned to a single virtual disk. When a physical disk in the virtual disk fails, the hot spare is activated to replace the failed physical disk without interrupting the system or requiring your intervention. 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.
Replacing A Member Disk Step 1 of 2 1. Select the physical disk in the Connector table that you want to replace. 2. Select the destination disk in the Disks available for replace member operation table. CAUTION: If you choose a hot spare as the destination physical disk, your virtual disk does not have a hot spare, unless you assign one. NOTE: You can select only one source or destination physical disk at a time. 3. Click Apply 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 44. 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 45. 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.
● Read, Write, Cache And Disk Cache Policy Controller Tasks Supported On PERC Hardware Controllers Table 47.
Table 47.
Table 48.
Table 48.
Table 48.
Table 50.
Table 51.
Table 52.
Table 53.
Table 53.
Table 54.
Table 55.
Table 55.
Table 56.
Table 56.
RAID Levels Supported By PERC Hardware Controllers Table 57.
Table 59.
Table 60.
Table 61. Controller Tasks Supported on H200 Controllers (continued) Controller Task Name PERC H200 Set Patrol Read Mode No Start Patrol Read No Stop Patrol Read No Controller Reports Patrol Read Report No Check Consistency Report No Slot Occupancy Report Yes Physical Disk Firmware Version Report Yes Battery Tasks Supported On H200 Controllers Table 62.
Table 64. Physical Disk Tasks Supported on H200 Controllers (continued) Physical Disk Task Name PERC H200 Cancel Clear No Virtual Disk Tasks Supported On H200 Controllers Table 65.
Virtual Disk Specifications For PERC H200 Controllers Table 67.
Read, Write, And Cache Policy Supported By H200 Controllers Table 68. Read, Write, and Cache Policy Supported by H200 Controllers Read, Write, and Cache Policy PERC H200 Cache settings No Read Policy No Read Ahead (Enabled) No No Read Ahead (Disabled) No Write Policy No Write Back No Write Through No Force Write Back (Enabled Always) No Write Cache Enabled Protected No Cache Policy No Disk Cache Policy Yes Cache I/O No Direct I/O No Enclosure Support On H200 Controllers Table 69.
Controller Tasks Supported On The PERC Software RAID Controllers Table 70. Controller Tasks Supported On The PERC S100, PERC S110, PERC S130, PERC S300, PERC S140 and PERC S150 Controllers Controller Task Name PERC S100 PERC S110 PERC S130 PERC S300 PERC S140 PERC S150 Create Virtual Disk Yes Yes Yes Yes Yes Yes NOTE: For physical disks connected to Software RAID S130 controller, 512 MB of disk space is by default used by the controller for metadata. Table 71.
NOTE: For physical disks connected to Software RAID S130 controller, 512 MB of disk space is by default used by the controller for metadata. NOTE: When you perform the Prepare to Remove operation on the physical disk, the associated virtual disk will be in failed state. NOTE: The operation failed to complete message is displayed, if you perform the Prepare to Remove operation on the physical disk of Boot virtual disk/mounted virtual disk.
Virtual Disk Specifications For PERC Software RAID Controllers Table 75.
Table 75. Virtual Disk Specifications for PERC S100, PERC S110, PERC S130, PERC S300 , PERC S140 and PERC S150 Controllers (continued) Virtual Disk Specification PERC S100 PERC S110 PERC S130 PERC S300 PERC S140 PERC S150 Minimum Number of Physical Disks in a RAID 5 3 3 3 3 3 3 Minimum Number of Physical Disks in a RAID 10 4 4 4 4 4 4 Table 76.
Table 77. RAID Levels Supported by the PERC S100, PERC S110, PERC S130, PERC S300, PERC S140 and PERC S150 Controllers (continued) RAID Level PERC S100 PERC S110 PERC S130 PERC S300 PERC S140 PERC S150 RAID 1 Yes Yes Yes Yes Yes Yes RAID 5 Yes No Yes Yes Yes Yes RAID 10 Yes No Yes Yes Yes Yes RAID 50 No No No No No No RAID 6 No No No No No No RAID 60 No No No No No No Table 78.
Table 79.
Table 82.
Table 85. Physical Disk Tasks Supported on the Non-RAID Controllers (continued) Physical Disk Task Name Non-RAID SCSI Non-RAID SAS Offline No No Online No No Initialize No No Rebuild No No Cancel Rebuild No No Remove Dead Disk Segments No No Format Disk No No Clear No No Cancel Clear No No Virtual Disk Tasks Supported By The Non-RAID Controllers Table 86.
Table 86. Virtual Disk Tasks supported by the Non-RAID Controllers (continued) Virtual Disk Task Name Non-RAID SCSI Non-RAID SAS Fast Initialize Virtual Disk No No Slow Initialize Virtual Disk No No Cancel Initialize Virtual Disk No No Enclosure Support On The Non-RAID Controllers Table 87.
Maximum Supported Configuration For SAS Controllers Table 89.
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 91. 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 92.
Health Status Rollup - Some Physical Disks In A Virtual Disk Are In Foreign State Table 94. 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 95.
Health Status Rollup - Enclosure Power Supply Failed Or Power Connection Removed Table 98. 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 99.
Table 101. 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 102.
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.
