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
Windows operating system installation errors
Ensure that you perform the following step before installing Windows on 4 KB sector drives:
1. Read and understand the updates to the version of Windows that you have installed. You can find this information in the
Microsoft help. For more information, see Microsoft support policy for 4 K sector hard drives in Windows.
Firmware fault state error message
Error Message:
Firmware is in Fault State.
Corrective
Action:
Contact Global Technical Support.
Foreign configuration found error message
Error Message:
Foreign configuration(s) found on adapter. Press any key to continue,
or ’C’ to load the configuration utility or ’F’ to import foreign
configuration(s) and continue.
Probable Cause: When a controller firmware detects a physical disk with existing foreign metadata, it flags the physical
disk as foreign and generates an alert indicating that a foreign disk was detected.
Corrective
Action:
Press <F> at this prompt to import the configuration (if all member disks of the virtual disk are present)
without loading the HII Configuration Utility. Or press <C> to enter the HII Configuration Utility and
either import or clear the foreign configuration.
Foreign configuration not found in HII error message
Error Message:
The foreign configuration message is present during POST but no foreign
configurations are present in the foreign view page in HII configuration
utility. All virtual disks are in an optimal state.
Corrective
Action:
Ensure all your PDs are present and all VDs are in optimal state. Clear the foreign configuration using HII
configuration utility or Dell OpenManage Server Administrator Storage Management.
CAUTION: The physical disk goes to Ready state when you clear the foreign configuration.
If you insert a physical disk that was previously a member of a virtual disk in the system, and that disk’s
previous location has been taken by a replacement disk through a rebuild, you must manually remove the
foreign configuration flag of the newly inserted disk.
Degraded state of virtual disks
A redundant virtual disk is in a degraded state when one or more physical disks have failed or are inaccessible. For example, if a
RAID 1 virtual disk consists of two physical disks and one of them fails or become inaccessible, the virtual disk become degraded.
To recover a virtual disk from a degraded state, you must replace the failed physical disk and rebuild it. Once the rebuilding
process is complete, the virtual disk state changes from degraded to optimal.
Memory errors
Memory errors can corrupt cached data, so the controllers are designed to detect and attempt to recover from the memory
errors. Single-bit memory errors can be handled by the controller and do not disrupt normal operation. A notification is sent if
the number of single-bit errors exceeds a threshold value.
Troubleshooting
71