Dell PowerEdge RAID Controller 12 User’s Guide PERC H965i Adapter, PERC H965i Front, PERC H965i MX, and PERC H965e Adapter

PDF

Event log errors

The following table lists error messages, probable causes, and recommended response action to resolve the Event Log errors.

NOTE:Text used in the following messages may vary based on the type of management application.

Table 1. Run-time issues and corrective actionsRun-time issues and corrective actions when using PERC 12
Description	Error Message	Probable Cause	Recommended Corrective Action
Correctable Error During BGI	A medium error was corrected on the following virtual drive during background initialization: <VD_Name> at <variable Name>, <PD_Name>, LUN <Name>, Count <Number>.	The drive had a correctable medium error and the data is recovered. The drive may be getting corrupted or facing a data-rot.	Verify the SMART status of the drive, and if necessary, replace the drive.
Uncorrectable Error During BGI	The Background Initialization operation is completed in the virtual drive <VD_Name> with uncorrectable errors.	One or more uncorrectable errors are detected during the BGI operation. Data may be lost.	Verify the SMART status of the drive and ensure that the data is backed up.
Uncorrectable Error During BGI	The Background Initialization operation is completed in the virtual drive <VD_Name> with uncorrectable errors.	An uncorrectable error was detected during the BGI operation. Data may be lost.	Verify the SMART status of the drive and ensure that the data is backed up.
BGI Failed	Unable to complete the Background Initialization operation on the virtual drive <VD_Name>.	A physical drive may have failed during the BGI operation which made the virtual drive appear as offline.	Check the health status of virtual drives and physical drives, and then replace corrupted drives if necessary.
Error Corrected during consistency check	The Consistency Check operation corrected error on the drive: <VD_Name> at <variable Name>, <PD_Name>, LUN <Name>, Count <Number>.	The drive had a medium error and corrected during Consistency Check. Data may be lost.	Verify the SMART status of the drive and ensure that the data is backed up.
Consistency check completed with corrected errors	The Consistency Check operation was completed on the drive: <VD_Name> Corrections <correctionData>.	The drive had a correctable medium error and the data is recovered. The drive may be getting corrupted or facing a data-rot.	Verify the SMART status of the drive, and if necessary, replace the drive.
Uncorrectable media errors detected during consistency check	The Consistency Check operation detected uncorrectable multiple medium errors on the drive: <VD_Name> at <variable Name>, <PD_Name>, LUN <Name>, Count <Number>.	The drive had a medium error and corrected during Consistency Check. Data may be lost.	Check the health status of virtual drives and PDs, and then replace corrupted drives if necessary.
Unable to complete consistency check	Unable to complete the Consistency Check operation on the virtual drive <VD_Name>.	Consistency Check has failed on virtual drive which could be because of media errors.	Check the health status of the virtual drives and PDs. Replace any non-functional drives.
Consistency check completed with uncorrectable errors	The Consistency Check (CC) operation is completed with uncorrectable errors on the virtual drive <VD_Name>.	Medium Errors were not corrected after CC. If virtual drive is not redundant (or is degraded), then data cannot be regenerated and the medium error cannot be resolved. Data may be lost.	Check the health status of virtual drives and physical drives, and then replace corrupted drives if necessary.
Inconsistent parity data detected during consistency check	The Consistency Check operation detected inconsistency parity on the virtual drive <VD_Name>, at strip <stripName>.	The Consistency Check operation detected an on the virtual drive. The inconsistency is corrected.	No response action is required.
Consistency check logging disabled due to too many inconsistencies	Inconsistency data on the virtual drive <VD_Name> cannot be logged in because too many inconsistencies are detected on the virtual drive, and the feature is disabled during the Consistency Check operation.	The Consistency Check operation detected multiple inconsistencies and disabled data logging.	Check the health status of virtual drives and physical drives, and then replace corrupted drives if necessary.
Virtual drive Initialization failed	Unable to initialize the virtual drive <VD_Name>.	A disk could have failed during initialization causing the virtual drive to go offline.	Check the health status of virtual drives and physical drives, and then replace corrupted drives if necessary.
Physical drive erase errors	Data on the following physical drive cannot be cleared: <PD Name>, <Path Name>, <ErrorDescription>.	The drive could have either failed or returned an error during the Clear operation.	Check the health and SMART status of physical drives, and then replace corrupted drives if necessary.
Physical drive error	An error is detected on the following physical drive: <PD Name>, <Path Name>, <ErrorDescription>.	An error is detected on the physical drive.	Check the health and SMART status of physical drives, and then replace corrupted drives if necessary.
Physical drive not supported	The physical drive <PD Name> is either not supported by the controller or is in an unsupported format.	The physical drive is either not supported by the controller or is in an unsupported format.	Replace the drive or reformat by using a supported file format.
Physical drive not certified warning	The physical drive <PD Name> is not certified.	The physical drive is not manufactured as per Dell technical specifications and cannot guarantee that the physical drive will be fully compliant with Dell standards and functionalities.	Use a physical drive that complies to Dell standards and retry the operation.
Media error corrected during patrol-read	The patrol-read operation corrected a medium error on the physical drive <PD Name>, LUN <LUN Name>.	The drive had a medium error and corrected during Consistency Check. Data may be lost.	Verify the SMART status of the drive and ensure that the data is backed up.
Uncorrectable media error detected during patrol-read	The patrol-read operation detected an uncorrectable medium error on the physical drive <PD Name>, LUN <LUN Name>.	An uncorrectable error was detected during the patrol-read operation. Data may be lost.	Check the health status of virtual drives and physical drives, and then replace corrupted drives if necessary.
Physical drive Predictive Failure	A predictive failure is detected in the physical drive: <PD Name>.	The SMART data is indicating that the drive may fail soon.	Replace the drive and ensure the rebuild or copy-back operation is successful.
Bad block punctured on the physical disk	A bad block is being punctured on the physical drive: <PD Name>, LUN <LUN Name>.	LBA on physical drive was punctured. Data may be lost.	Check the health status of virtual drives and physical drives, and then replace corrupted drives if necessary.
Unable to rebuild array because of an error on the source disk	Unable to rebuild the physical drive <PD Name> because of an error in the source drive.	Source drive failed because of which the Rebuild operation cannot proceed. Data may be lost	Replace any bad drives and recreate virtual drive from backup.
Unable to rebuild array because of an error on the target disk	Unable to rebuild the physical drive <PD Name> because of an error in the target drive.	Target drive failed due to which the Rebuild operation cannot be continued.	Replace any bad drives and restart the Rebuild operation.
Unrecoverable error detected during rebuild	An unrecoverable medium error is detected during the Rebuild operation on the physical drive: <PD Name>, LUN <LUN Name>.	An uncorrectable error was detected during the rebuild. Data may be lost.	Check the health status of virtual drives and PDs, and then replace corrupted drives if necessary.
Media error corrected during operation	A medium error is corrected during the recovery operation on the physical drive: <PD Name>, LUN <LUN Name>.	An medium error was detected during the BGI operation. Data may be lost.	Verify the SMART status of the drive and ensure that the data is backed up.
Unrecoverable error detected during operation	An unrecoverable medium error is detected during the recovery operation on the physical drive: <PD Name>, LUN <LUN Name>.	Medium Errors were not corrected after recovery. If a virtual drive is not redundant (or is degraded), data cannot be regenerated and medium error cannot be resolved. Data may be lost.	Check the health status of virtual drives and physical drives, and then replace corrupted drives if necessary.
SCSI Sense Data	An unexpected Sense error is on the physical drive: <PD Name>, Patj <Path Name>, CDB <CDB Name>, Sense <Sense Name>.	Drive returned sense data for the SCSI CDB. This can include info during drive power-on, firmware update, or errors.	If the event is seen consistently in logs, contact the Technical Support team.
Physical drive is not accessible	Unable to access the PD: <PD Name>.	An error occurred during the discovery or initialization of the drive. The drive may be corrupted.	Remove or reinstall the drive. Check the health or SMART status of the physical drive. For NVMe drives, run the Recovery operation of the supported format.
The hot-spare is no longer useful	The dedicated hot-spare <PD Name> is no longer useful for all the arrays.	The dedicated hot-spare cannot cover all the arrays and this could be because of a change in the virtual drive size or other parameters.	Check if the assigned dedicated hot-spare physical drive is compatible with the virtual drive it covers. If not, assign a hot-spare physical drive which is compatible.
Hot-Spare no longer covers all arrays	The global hot-spare <PD Name> no longer covers all the arrays.	The assigned global hot-spare physical drive is not of the same type to cover all the virtual drives in the system.	Ensure to assign a global hot-spare physical drive which is of the same type of the other VD. Else, use dedicated hot-spare for virtual drives that are not covered.
Energy Pack is not installed	The Energy Pack is not installed.	Energy pack may be either missing, or have a disconnected or damaged cable.	Ensure that the Energy Pack is installed, connected through a cable. Else, replace the Energy Pack.
Energy Pack temperature is high	The Energy Pack temperature is high.	Energy pack temperature exceeded the operational limit.	Verify system environment is within operational limits. Check for fan failure, or air flow blockage. In the absence of any other temperature condition, replace energy pack.
Energy Pack temperature is low	The Energy Pack temperature is low.	Energy pack may self-discharge in storage, which should self-correct in operation within a few minutes. Virtual drives may transition from write-back to write-thru until condition is resolved.	Persistent condition may require energy pack or controller replacement. Contact support.
Energy Pack temperature is not functional	The Energy Pack is not functioning and cannot support data retention.	Energy pack has failed. Virtual drives will transition to the write-through mode until corrected.	Replace the Energy Pack.
Energy pack below charge threshold	The current capacity of the Energy Pack is less than the threshold value.	May result from energy pack learning cycle indicating it is approaching end of life. Virtual drives will transition to the write-through mode until corrected.	Replace the Energy Pack.
Energy pack above charge threshold	The current capacity of the Energy Pack is more than the threshold value.	May result from energy pack learning cycle.	No response action is required.
Unable to communicate with backplane or enclosure	The controller is unable to communicate with the enclosure <enclosure Name>.	The cable may be loose or damaged.	Ensure that the cables are connected and not damaged. Restart the server if necessary.
Backplane or enclosure discovery error	Discovery error detected for enclosure <enclosure name> (receptacle <receptacle #>) - < error code>.	Error is probably caused by cables, backplane firmware, or slot connections.	Check all cables and drives and ensure they are properly seated. AC power-cycle the system. If the issue persists, contact your Technical Support team.
PHY/Slot bad	The enclosure with physical drive <PD Name> is not detected by controller in the slot <slotName>.	The physical drive is inserted in the slot but not detected by the controller. The physical drive may be corrupted.	Ensure that the cables are connected and not damaged. Restart the server if necessary.
The backplane or enclosure is unstable.	The enclosure <enclosure Name> is unstable.	The backplane or enclosure has detected an error.	Ensure that the cables are connected and not damaged. Upgrade the enclosure firmware and restart the server.
Hardware issues detected on backplane or enclosure	The enclosure <enclosure Name> is has hardware issue.	The backplane or enclosure has indicated that there is a hardware failure or issue.	Ensure that the cables are connected and not damaged. Upgrade the enclosure or backplane firmware and restart the server. If the issue persists, contact your Technical Support team.
Enclosure is not responding	The enclosure with physical drive <enclosure Name> is not responding.	The backplane is not responding to the controller.	Ensure that the cables are connected and not damaged. Upgrade the enclosure or backplane firmware and restart the server. If the issue persists, contact your Technical Support team.
Virtual drives transitioned to write-through because of issues in the energy pack hardware	The Energy pack charger has been disabled because of hardware issues. Currently changing the write-back virtual drives to write-through. However, the forced write-back virtual drives are not affected.	The energy pack is not functional or defective. Therefore, the virtual drive cache policy is configured for forced write-back.	Verify the energy pack connection, check for cable damage, replace the energy pack. If the issue persists, contact the Technical Support team.
Issues detected with energy pack or charger	Issues are detected in either the Energy Pack or Energy Pack Charger.	The State of Health (SoH) of the Energy Pack is not good. Energy pack is bad, defective, missing, or there is a fault in the energy pack charging system. Virtual drives in the write-back mode will transition to write-through.	Verify the energy pack connection, check for cable damage, replace the energy pack. If the issue persists, contact the Technical Support team.
Disk missing	The following physical drive is missing: <PD Name>.	A configured physical drive is not detected after resetting or restarting the controller.	If this issue is unexpected, ensure that the cables are properly connected and physical drives are seated, and then restart the server.
Virtual disk offline because of missing disks	The following virtual drives are not detected, and therefore, the physical drives will go offline: <VD Names>.	One or more of the physical drives is bad and has gone offline.	Check the health status of the physical disks and replace any bad drives.
Virtual drive is partially degraded	The virtual drive <VD Name> is partially degraded.	One or more of the physical drives is bad and has gone offline.	Check the health status of the physical disks and replace any bad drives.
Virtual drive is degraded	The VD <VD Name> is now fully degraded.	One or more of the physical drives is bad and has gone offline.	Check the health status of the physical disks and replace any bad drives.
Virtual drive is offline.	The virtual drive <VD Name> is now offline.	One or more of the physical drives is bad and has gone offline.	Check the health status of the physical disks and replace any bad drives.
Physical drive command timeout	The command timed out waiting for response: <PD Name>, Patj <Path Name>, CDB <CDB Name>, Sense <Sense Name>.	The drive Command timed out waiting for response. This may occur due to an error or in cases where the device is reset such as a firmware update. Command may have been retried.	Check the health or SMART status of the drive and replace any failing drives. Try restarting the server or controller. If the issue persists, contact the Technical Support team.
Disk Reset	The physical drive <PD Name>, Path <pathname> is reset.	Drive was reset. This can happen in an attempt to recover from an error during device discovery.	If the issue is persistently seen in logs, contact the Technical Support team.
Bad Block table for virtual drive 80% full	The bad block table on the virtual drive <VD Name> is 80% full.	Multiple uncorrectable medium errors were found on the drive and added to LDBBM table.	Check the health status of the physical disks and replace any bad drives.
Bad block logging for virtual drive disabled because of too many bad blocks	Unable to log the block <blockName> on the physical drive <PD Name>, LUN <LUN Name> at <Count> because of a block table on the virtual drive <VD Name>l.	Multiple uncorrectable medium errors were found on the drive and added to LDBBM table.	Check the health status of the physical disks and replace any bad drives.
Uncorrectable media error is detected on virtual drive	An uncorrectable medium error was logged for virtual drive <VD Name>: physical drive <PD Name>, LUN <LUN Name> at <Count> because of a block table on the virtual drive <VD Name>.	Uncorrectable multiple medium errors were found on the disk. Data may be lost.	Check the health status of the physical disks and replace any bad drives.
Media error corrected on virtual drive	A medium error was corrected on the virtual drive <VD Name> at <name>.	Medium Error was found on the disk and corrected. Data may be lost.	Verify the SMART status of the drive and ensure that the data is backed up.
Bad block table for virtual disk is 100% full	The bad block table on the virtual drive <VD Name> is 100% full.	Multiple uncorrectable medium errors were found on the drive and added to LDBBM table.	Check the health status of the physical disks and replace any bad drives.
Preserved Cache Discarded	The controller cache is discarded for either the deleted, missing, or offline virtual drive <VD Name>.	A state of a virtual drive has changed because drives are missing, failed, or deleted. Either the user has discarded the controller cache or the virtual drive was deleted.	Check the state of the virtual drive and all associated physical drives. Replace any non-functional drives.
Physical drives update timeout	The Microcode Update operation timed out on the physical drives <PD Name>.	The drive firmware update operation did not complete within the specified time limit. The firmware may still have updated successfully.	Verify if the drive firmware is fully updated. Else, retry the operation. If the firmware cannot be upgraded, then contact your Technical Support team.
Security key entered is invalid	Unable to unlock the drive because an invalid security key is entered.	An incorrect security key ID is used to unlock the drive or controller.	Enter a valid security key ID and retry the operation. If multiple drives use the same key ID and different security keys then remove the extra drives and separately import the drives.
Unable to unlock drives because of invalid security key	Unable to unlock the drive because the security key provided by Escrow is invalid.	The security key ID provided by Escrow is invalid.	If multiple drives use the same key ID and different security keys then remove the extra drives and import the disks separately.
A Drive Security Error is detected	Security subsystem issues are detected on the physical drive <PD Name>.	There is an issue when managing the security of the drive.	Remove, reinstall the drive, and then retry the operation. If the issue persist, contact your Technical Support team.
Controller cache preserved for VD	The controller cache data was preserved for the missing of offline virtual drive: <VD Name>.	The state of a virtual drive has changed because either drives are missing or failed.	Check the state of the virtual drive and all associated physical drives. Replace any non-functional drives.
Locked drives are not accessible because of a key exchange error	Unable to access the secured configuration because an incorrect security key is entered.	Either an incorrect security key is entered or a key is not entered at all. Locked drives will remain locked and cannot be accessed.	Using iDRAC, verify the SEKM status of the server. Resolve any network communication issues with the KMS server. To retry exchanging the security key, restart the server.
Invalid security key or key id entered	An invalid security key of the drive is entered.	The security key or key ID of the drive does not match the drive information.	Ensure that correct security key and key ID are entered to unlock the drive.
Unable to communicate with the external key manager	Unable to communicate with the external key manager.	Either an incorrect security key is entered or a key is not entered at all. Locked drives will remain locked and cannot be accessed.	Using iDRAC, verify the SEKM status of the server. Resolve any network communication issues with the KMS server. To retry exchanging the security key, restart the server.
Physical drive Erase Error	Unable to erase data on the physical drive: <PD Name>, Path <pathname>, Error Data <error Info>.	The drive may have an internal error or failed during the Erase operation.	Retry the operation. If the issue persist, contact your Technical Support team. If the data must be erased, then follow the DoD 5220.22-M Standard for Drive Erasure to physically destroy the storage device.
Energy pack charging disabled due to high temperature	The Energy Pack charging operation is abruptly stopped because the Energy Pack temperature is too high.	System environment is not within operational specifications, or energy pack is damaged.	Ensure that system environment is within operational limits. Check for fan failure, or air flow blockage around controller. In the absence of an environmental cause, disconnect energy pack and contact support.
Too many bad blocks to support cache backup	The non-volatile cache capacity is too less to support data backup. The write-back virtual drives will be converted to write-through.	Controller has run out of enough good cache buffer space to currently support caching.	Check the state of all virtual drives and all associated physical drives. Discard any preserved cache if necessary.
Non-Volatile cache has failed and backup cannot be supported	The non-volatile cache device failed and cannot support the data retention feature.	Controller cache support may not be functioning properly.	Contact your Technical Support team.
Controller temperature exceeded warning threshold	The controller temperature exceeded the threshold value. This may indicate inadequate server cooling. Currently switching to a low-performance mode.	The server fans may not functioning properly.	Check the health of server fans and replace if necessary. To improve cooling, increase or offset the fan speed.
Controller temperature exceeded critical threshold	The controller has been shut down because the server temperature reached the threshold value. This indicates that the server cooling is inadequate.	The server cooling fans may not be functioning properly.	Increase or offset the fan speed to improve cooling.
Unable to secure virtual drive in future	Unable to secure the virtual drive <VD Name> in future because it is a non-SED.	One of the physical drives hosting the virtual drive is not SED-capable.	Replace the non-SED with an SED-capable one.
Discovery error	The drive cannot be discovered because of an SAS topology error: <Error Description>.	An error occurred during device discovery.	Remove all the newly added or non-functioning hardware. If the issue persists, contact your Technical Support team.
Energy pack unavailable or not functioning	The Energy Pack is either unavailable or not functioning. Incomplete write operations because of power loss may cause data integrity issues on the parity virtual drive: <VD Name>.	Energy pack is bad or defective, and the virtual drive cache policy is configured for forced write back.	Verify energy pack connection, check for cable damage, replace energy pack. Disable forced write back until resolved.
Safe Mode Error	The controller booted to the Safe mode because of critical issues.	Controller has an error during boot that requires user attention.	Correct the errors reported by the controller.
Firmware Update Failure	A validation issue occurred during the firmware update operation: <Issue Description>.	Failed to validate the incoming firmware image file.	Ensure that the firmware image used is correct and retry the operation. If the issue persists, contact your Technical Support team.
Firmware Update Failure	A programming issue occurred during the firmware update operation: <Issue Description>.	Programming of incoming firmware image to the flash failed.	Ensure that the firmware image used is correct and retry the operation. If the issue persists, contact your Technical Support team.
Firmware Update Failure	Unable to complete the Online activate operation while preparing the controller.	The new firmware may require offline activation.	Perform system reset to activate the firmware offline.
Security Key cleaned up	The Escrow key ID <key ID> is cleaned up.	The security key that was saved in the memory for unlocking and importing the drive is erased. Any drive that uses this key which is not imported or rekeyed will be locked.	No action is required. If disks need to be imported then remove the disks, wait 10 seconds, and reinsert the disks. If using LKM then provide the key to unlock the disks. If using SEKM then wait for the key exchange to occur. Import the configuration after the disks are unlocked.
Error detected in the controller Level 2 cache	An error is detected in the Level-2 (L2) cache.	The controller hardware is not functioning or is going to stop functioning.	Contact your Technical Support team.
Controller flash access error	A transient error has occurred while accessing the flash device.	The controller flash device is not functioning or is going to stop functioning.	Contact your Technical Support team.
Controller flash stopped functioning	The flash device has stopped functioning.	The controller flash device is not functioning and must be replaced.	Contact your Technical Support team.
Multi-bit ECC error detected on the onboard controller memory	A multi-bit ECC error is detected in the OCM. This is a high-severity issue.	A Multi-bit ECC error is detected on the controller. Controller must be replaced.	Contact your Tech Support team to replace the controller.
Single-bit ECC error detected on the onboard controller memory	A single-bit ECC error is detected in the OCM. This is not a high-severity issue.	A Single-bit ECC error is detected.	No response action is required.
Multi-bit ECC error detection crossed warning threshold	A number of single-bit ECC errors in the OCM has crossed the Warning threshold.	A Single-bit ECC error is detected multiple times.	Continue to monitor the ECC errors. If ECC errors persists, contact your Tech Support team to replace the controller.
ECC error logging stopped	The detection of single-bit ECC errors in the OCM has been disabled.	Additional ECC errors will not be logged because too many errors are occurring and the controller does not have room to record anymore.	Contact your Technical Support team to get the controller replaced.
Controller fan stopped functioning	The fan stopped functioning because <reason>.	The fan on the adapter controller may not be functioning properly.	Check the controller and system health and replace the controller, if necessary.
Drive Initialization Error	An initialization issue is detected in the physical drive <PD Name>.	An initialization issue is detected in the physical drive during the initialization or discovery of the drive. The drive may not be in good state.	Remove or reinstall the drive. Check the health or SMART status of the physical drive. For NVMe drives, run the Recovery operation of the supported format.
Command timed out on physical drive	During backplane firmware update operation, the Command Timeout event is displayed in PERC.	The backplane may have been reset after updating the firmware, and therefore the commands sent by PERC to backplane could be timed out.	No response action is required.
An I/O delay is observed when a virtual drive state changes	An I/O delay is observed when a virtual drive state changes.	The controller has a delay time of 4 seconds for SAS/SATA and 8 seconds for NVMe drive removal processing to prevent unnecessary rebuild operations. This delay can introduce short pause in IO when the virtual drive state changes.	No response action is required.
Unable to complete the Drive MAKERS Authority disable operation during the securing operation	Failed to disable the MAKERS authority on the drive.	An error occurred while securing the drive or the drive may not support MAKERS authority.	Retry the operation. If the issue persists contact support. f the issue persists, contact your Technical Support team.
Unable to complete the Drive MAKERS Authority enable operation during the erase operation	Failed to enable the MAKERS authority on the drive.	An error occurred while erasing the drive or the drive may not support MAKERS authority.	Retry the operation. If the issue persists contact support. f the issue persists, contact your Technical Support team.
Drive firmware download port lock on reset operation failed during securing operation	Failed to disable the firmware download port on the drive.	An error occurring during securing or drive may not support firmware download port control setting.	Retry the operation. If the issue persists contact support. f the issue persists, contact your Technical Support team.
Drive firmware download port unlock operation failed during erase operation	Failed to enable the firmware download port on the drive.	An error occurring during erase or Drive may not support the firmware download port control setting	Retry the operation. If the issue persists contact support. f the issue persists, contact your Technical Support team.