Users Guide
Table Of Contents
- Dell Technologies PowerEdge RAID Controller 11 User’s Guide PERC H755 adapter, H755 front SAS, H755N front NVMe, and PERC H755 MX adapter
- Contents
- Dell Technologies PowerEdge RAID Controller 11
- Applications and User Interfaces supported by PERC 11
- Features of PowerEdge RAID Controller 11
- Controller features
- Virtual disk features
- Hard drive features
- Fault tolerance
- Install and remove a PERC 11 card
- Safety instructions
- Before working inside your system
- After working inside your system
- Remove the PERC H755 adapter
- Install the PERC H755 adapter
- Remove the PERC H755 front SAS card
- Install the PERC H755 front SAS card
- Remove the PERC H755N front NVMe card
- Install the PERC H755N front NVMe card
- Remove the PERC H755 MX adapter
- Install the PERC H755 MX adapter
- Driver support for PERC 11
- Firmware
- Manage PERC 11 controllers using HII configuration utility
- Enter the PERC 11 HII configuration utility
- Exit the PERC 11 HII configuration utility
- Navigate to Dell PERC 11 configuration utility
- View the HII Configuration utility dashboard
- Configuration management
- Controller management
- Clear controller events
- Save controller events
- Save debug log
- Enable security
- Disable security
- Change security settings
- Restore factory default settings
- Auto configure behavior
- Manage controller profile
- Advanced controller properties
- Virtual disk management
- Physical disk management
- Hardware components
- Security key management in HII configuration utility
- Security key and RAID management
- Security key implementation
- Local Key Management
- Create a security key
- Change Security Settings
- Disable security key
- Create a secured virtual disk
- Secure a non-RAID disk
- Secure a pre-existing virtual disk
- Import a secured non-RAID disk
- Import a secured virtual disk
- Dell Technologies OpenManage Secure Enterprise Key Manager
- Supported controllers for OpenManage Secure Enterprise Key Manager
- Manage enterprise key manager mode
- Disable enterprise key manager mode
- Manage virtual disks in enterprise key manager mode
- Manage non–RAID disks in enterprise key manager mode
- Migration of drives from local key management to enterprise key management
- Troubleshooting
- Single virtual disk performance or latency in hypervisor configurations
- Configured disks removed or not accessible error message
- Dirty cache data error message
- Discovery error message
- Drive Configuration Changes Error Message
- Windows operating system installation errors
- Firmware fault state error message
- Foreign configuration found error message
- Foreign configuration not found in HII error message
- Degraded state of virtual disks
- Memory errors
- Preserved Cache State
- Security key errors
- General issues
- Physical disk issues
- Physical disk in failed state
- Unable to rebuild a fault tolerant virtual disk
- Fatal error or data corruption reported
- Multiple disks are inaccessible
- Rebuilding data for a failed physical disk
- Virtual disk fails during rebuild using a global hot spare
- Dedicated hot spare disk fails during rebuild
- Redundant virtual disk fails during reconstruction
- Virtual disk fails rebuild using a dedicated hot spare
- Physical disk takes a long time to rebuild
- Drive removal and insertion in the same slot generates a foreign configuration event
- SMART errors
- Replace member errors
- Linux operating system errors
- Drive indicator codes
- HII error messages
- Appendix RAID description
- Getting help
- Documentation resources
Multiple disks are inaccessible
Issue: Multiple disks are simultaneously inaccessible.
Probable Cause: Multiple physical disk errors in a single array typically indicate a failure in cabling or connection and could
involve the loss of data.
Corrective
Action:
You can recover the virtual disk after multiple physical disks become simultaneously inaccessible. Perform
the following steps to recover the virtual disk:
CAUTION: Follow the safety precautions to prevent electrostatic discharge.
1. Turn off the system, check cable connections, and reseat physical disks.
2. Ensure that all the disks are present in the enclosure.
3. Turn on the system and enter the HII Configuration Utility.
4. Import the foreign configuration.
5. Press <F> at the prompt to import the configuration, or press <C> to enter the HII Configuration Utility and either import
or clear the foreign configuration.
If the virtual disk is redundant and transitioned to Degraded state before going Offline, a rebuild operation starts automatically
after the configuration is imported. If the virtual disk has gone directly to the Offline state due to a cable pull or power loss
situation, the virtual disk is imported in its Optimal state without a rebuild occurring.
NOTE: You can use the HII Configuration Utility or Dell OpenManage storage management application to perform a
manual rebuild of multiple physical disks.
Rebuilding data for a failed physical disk
Issue:
Rebuilding data for a physical disk that is in a failed state.
Probable Cause: Physical disk is failed or removed.
Corrective
Action:
If you have configured hot-spares, the PERC card automatically tries to use one of the hot-spares to
rebuild a physical disk that is in a failed state. Manual rebuild is necessary if no hot-spares with enough
capacity to rebuild the failed physical disks are available. You must insert a physical disk with enough
storage in the subsystem before rebuilding the physical disk.
NOTE: You can use the HII Configuration Utility or Dell OpenManage storage management application to perform a
manual rebuild of an individual physical disk.
Virtual disk fails during rebuild using a global hot spare
Issue:
A virtual disk fails during rebuild while using a global hot spare.
Probable Cause: One or more disks in the virtual disks fails or is disconnected while the rebuild is in progress.
Corrective
Action:
No action is required. The global hot spare reverts to Hot spare state and the virtual disk is in Failed
state.
Dedicated hot spare disk fails during rebuild
Issue:
A hot spare disk fails during rebuild while using a dedicated hot spare.
Probable Cause: The dedicated hot spare assigned to the virtual disk fails or is disconnected while the rebuild is in
progress.
Corrective
Action:
If there is a global hot spare available with enough capacity, rebuild will automatically start on the global
hot spare. Where there is no hot spare present, you must insert a physical disk with enough capacity into
the system before performing a rebuild.
74 Troubleshooting