- Notes, cautions, and warnings
- Overview
- Getting started with your PERC card
- Installing the operating system and the PERC card on a base system
- Installing the PERC card on a system with the operating system pre-installed
- Installing the operating system on a system with the PERC card pre-installed
- Setting up the system with the PERC card and the operating system pre-installed
- Configuring settings of a replaced PERC card on a system with operating system pre-installed
- Features
- Enhanced rebuild prioritization
- Redundant path support for PERC H830
- 240 virtual disk support for H830
- PERC 9 personality management
- Secure firmware update
- Improved RAID 10 configuration
- 4 KB sector disk drives
- Physical disk power management
- Types of virtual disk initialization
- Background initialization
- Consistency checks
- Disk roaming
- FastPath
- Virtual disk migration
- Virtual disk write cache policies
- Virtual disk read cache policies
- Reconfigure virtual disks
- Fault tolerance
- Deploying the PERC card
- Removing the PERC H730P MX adapter card
- Installing the PERC H730P MX adapter card
- Removing the PERC 9 adapter
- Installing the PERC 9 adapter
- Removing the HBA330 mini monolithic controller
- Installing the HBA330 mini monolithic controller
- Installing a H730P slim card
- Removing the PERC 9 mini blade controller
- Installing the PERC 9 mini blade controller
- Removing the PERC FD33xD Card
- Installing the PERC FD33xD card
- Driver installation
- BIOS Configuration Utility
- Entering the BIOS Configuration Utility
- Exiting the Configuration Utility
- Menu navigation controls
- Setting up virtual disks
- BIOS Configuration Utility menu options
- Virtual Disk Management
- Creating virtual disks
- Selecting virtual disk parameters
- Initializing virtual disks
- Checking data consistency
- Running a data consistency check
- Importing or clearing foreign configurations using the VD mgmt menu
- Importing or clearing foreign configurations using the foreign configuration view screen
- Break mirror
- Managing preserved cache
- Managing dedicated hot spares
- Deleting virtual disks
- Deleting disk groups
- Clearing the configuration
- Physical Disk Management
- Physical disk erase
- Converting physical disk to Non-RAID or RAID capable
- Setting LED blinking
- Creating global hot spares
- Removing global or dedicated hot spares
- Replacing an online physical disk
- Restrictions and limitations
- Stopping background initialization
- Performing a manual rebuild of an individual physical disk
- Controller Management
- UEFI/HII RAID configuration utility
- Entering the UEFI configuration utility
- Exiting the UEFI configuration utility
- Navigating to Dell PERC 9 configuration utility
- Configuration management
- Creating virtual disks
- Creating profile based virtual disks
- Converting physical disks to RAID capable disk
- Converting physical disks to non-RAID disk
- Viewing disk group properties
- Viewing disk group properties
- Managing foreign configurations on a RAID controller
- Deleting existing configurations on a RAID controller
- Controller management
- Virtual disk management
- Physical disk management
- Hardware components management
- Controller management (Ctrl Mgmt)
- Controller management actions
- Dirty cache data error message
- Discovery error message
- Drive Configuration Changes Error Message
- Security key and RAID management
- Troubleshooting
- Adapter at baseport not responding error message
- BIOS disabled error message
- BIOS configuration utility error messages
- Discovery error message
- Extra enclosure error message
- Missing disks in virtual disk error message
- Previous configuration of disks removed error message
- Missing virtual disks error message
- Dirty cache data error message
- BIOS disabled error message
- Drive Configuration Changes Error Message
- Adapter at baseport not responding error message
- Offline or missing virtual drives with preserved cache error message
- Virtual disks offline error message
- Virtual disks degraded error message
- Virtual disks partially degraded error message
- Memory or battery problem error message
- Firmware fault state error message
- Foreign configuration found error message
- Foreign configuration not found in <ctrl> <R> error message
- Previous configuration cleared or missing error message
- Invalid SAS topology detected error message
- Configured disks removed or not accessible error message
- Discovery error message
- Windows operating system installation errors
- Extra enclosure 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
- Physical disk displayed as blocked
- Multiple disks become inaccessible
- Rebuilding a failed physical disk
- Virtual disk fails during rebuild using a global hot spare
- Virtual disk fails during rebuild using a dedicated hot spare
- Physical disk fails during reconstruction on redundant virtual disk
- Virtual disk fails rebuild using a dedicated hot spare
- Physical disk takes a long time to rebuild
- SMART errors
- Replace member errors
- Linux operating system errors
- Disk Carrier LED Indicators
- HII error messages
- Appendix RAID description
- Getting help
Dell PowerEdge RAID Controller 9 User’s Guide H330, H730, and H830
Background initialization
Background Initialization (BGI) is an automated process
that writes the parity or mirror data on newly created virtual disks.
BGI does not run on RAID 0 virtual disks. You can control the BGI
rate in the Dell OpenManage storage management application. Any change
in the BGI rate does not take effect until the next BGI run.
NOTE:You cannot disable
BGI permanently. If you cancel BGI, it automatically restarts within
five minutes. For information on stopping BGI, see Stopping Background
Initialization.
NOTE:Unlike full or
fast initialization of virtual disks, background initialization does
not clear data from the physical disks.
NOTE:Consistency Check
(CC)/BGI typically causes some loss in performance until the operation
completes.
Consistency Check (CC) and BGI perform similar functions in that they both correct parity errors. However, CC reports data inconsistencies through an event notification, but BGI does not. You can start CC manually, but not BGI.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\