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
Spanned RAID levels
Spanning is a term used to describe the way in which RAID levels 10, 50, and 60 are constructed from multiple sets of basic, or
simple RAID levels. For example, a RAID 10 has multiple sets of RAID 1 arrays where each RAID 1 set is considered a span. Data is
then striped (RAID 0) across the RAID 1 spans to create a RAID 10 virtual disk. Similarly, RAID 50 and RAID 60 combine multiple
sets of RAID 5 or RAID 6 respectively with striping.
Parity data
Parity data is redundant data that is generated to provide fault tolerance within certain RAID levels. In the event of a disk failure,
the parity data can be used by the controller to regenerate user data. Parity data is present for RAID 5, 6, 50, and 60.
The parity data is distributed across all the physical disks in the system. If a single physical disk fails, it can be rebuilt from the
parity and the data on the remaining physical disks. RAID level 5 combines distributed parity with disk striping. Parity provides
redundancy for one physical disk failure without duplicating the contents of the entire physical disks.
RAID 6 combines dual distributed parity with disk striping. This level of parity allows for two disk failures without duplicating the
contents of entire physical disks.
Figure 16. Example of Distributed Parity (RAID 5)
NOTE: Parity is distributed across multiple physical disks in the disk group.
Figure 17. Example of Dual Distributed Parity (RAID 6)
NOTE: Parity is distributed across all disks in the array.
Appendix RAID description 83