Symptoms

A message referencing the EventID 52806 may be seen in mccli event show, the Avamar User Interface (AUI) events page, or in /var/log/messages.

Cause

There are several causes that are listed below.

Resolution

Use the table below to locate the MessageID, and the recommended action. STOR006Detailed Description The operation could not be completed because of an issue with the management controller (either the iDRAC or the Chassis Management Controller (CMC)) that is managing the storage. Recommended Response Action Retry the operation. If the issue persists, contact your service provider.STOR007 Detailed Description The operation could not be completed because of insufficient memory space on the management controller (either the iDRAC or the Chassis Management Controller (CMC)) managing the storage. Recommended Response Action Retry the operation. If the issue persists, contact your service provider.STOR009 Detailed Description Physical disk did not identify valid physical disk for the operation. Recommended Response Action Provide compatible physical disk with the operation.STOR0101Detailed Description No RAID controller data to display. The system is powered off, no RAID controller is present in the system, or the RAID controller is not connected to the system. Recommended Response Action Check if the server has power, RAID controller is available, and that a RAID controller is connected to the system.STOR0102Detailed Description No battery data to display. The system is powered off, batteries are not present on the system, batteries are not connected to the RAID controller, or the batteries are depleted. Recommended Response Action Check if the server has power, batteries are available, and batteries are connected to the RAID controller.STOR0103 Detailed Description No physical disk data to display. The system is powered off, physical disks are not present on the system, or physical disks are not connected to the enclosure or backplane Recommended Response Action Check if the server has power, physical disks are available, and physical disks are connected to the enclosure or backplane.STOR0104Detailed Description No virtual disk data to display. The system is powered off, physical disks are not present on the system, or virtual disks are not created. Recommended Response Action Check if the server has power, physical disks are available, and virtual disks are created.STOR0105 Detailed Description No enclosure data to display. The system is powered off, enclosures are not present on the system, or enclosures are not connected to the RAID controllers. Recommended Response Action Check if the server has power, enclosures are available, and enclosures are connected to the RAID controllers.STOR0106Detailed Description No fan data to display. The system is powered off, no fan enclosures are present in the system, or the fans are not connected to the enclosures. Recommended Response Action Check if the server has power, enclosure fan is available, and fan is connected to the enclosure.STOR0109 Detailed Description No power supply unit data to display. The system is powered off, no power supply unit is present in the system, or the power supply unit is not connected to the enclosure. Recommended Response Action Check if the server has power, enclosure power supply unit is available, and power supply unit is connected to the enclosure.BAT0002Detailed Description System settings may be preserved if input power is not removed from the power supplies. Recommended Response Action Check the system board battery.BAT0004Detailed Description System settings may be preserved if input power is not removed from the power supplies. Recommended Response Action Check the system board battery to confirm presence.BAT0007Detailed Description The PERC RAID controller battery may have failed because of thermal exceptions. Recommended Response Action 1) Verify the PERC RAID controller battery installation. 2) Check the system logs for thermal related issues.BAT0009Detailed Description The PERC RAID controller battery may report absent due to disconnect or thermal exceptions. Recommended Response Action 1) Verify the PERC RAID controller battery installation. 2) If installed, reseat or reconnect the battery and cables. 3) Check the system logs for thermal related issues.BAT0012Detailed Description The PERC RAID controller battery may have failed because of thermal exceptions. Recommended Response Action 1) Verify the PERC RAID controller battery installation for the associated bay. 2) Check the system logs for thermal related issues.BAT0014Detailed Description The PERC RAID controller battery may report absent due to disconnect or thermal exceptions. Recommended Response Action 1) Verify the PERC RAID controller battery installation for the associated bay. 2) If installed, reseat or reconnect the battery and cables. 3) Check the system logs for thermal related issues.BAT0017Detailed Description System settings may be preserved if input power is not removed from the power supplies. Recommended Response Action Check the battery.BAT0019Detailed Description System settings may be preserved if input power is not removed from the power supplies. Recommended Response Action Check the battery to confirm presence.BAT1025Detailed Description The controller was unable to recover data from the cache. This may indicate data loss has occurred. Recommended Response Action Verify that the battery is charged and in good health. See the hardware documentation for more information. When the battery charge is unacceptably low, the battery cannot maintain cached data. Data loss may also have occurred, restoring data from backups may be needed. Verify whether the battery has met its recharge limit. The battery may need to be recharged. Contact technical support if the issue persists.BAT1029Detailed Description The controller battery cannot recharge. The battery may have already recharged the maximum number of times or the battery charger may not be working. Recommended Response Action Contact technical support.CTL40Detailed Description An error involving multiple bits has been encountered during a read or write operation. The error correction algorithm recalculates parity data during read and write operations. If an error involves only a single bit, it may be possible for the error correction algorithm to correct the error and maintain parity data. An error involving multiple bits, however, generally indicates data loss. In some cases, if the multi-bit error occurs during a read operation, then the data on the disk may be ok. If the multi-bit error occurs during a write operation, then data loss has occurred. Recommended Response Action Replace the Dual In-line Memory Module (DIMM). The DIMM is a part of the controller battery pack. Refer to the storage hardware documentation for information on replacing the DIMM. You may need to restore data from backup.CTL44Detailed Description A diagnostics test failed. The text for this message is generated by the tool that ran the diagnostics and can vary depending on the situation. Recommended Response Action Refer to the storage hardware documentation for more information on the diagnostic test.CTL46Detailed Description The Dual In-line Memory Module (DIMM) is malfunctioning. Data loss or data corruption may occur.. Recommended Response Action Replace the DIMM immediately to avoid data loss or data corruption. The DIMM is a part of the controller battery pack. Refer to the storage hardware documentation for information on replacing the DIMM.CTL47Detailed Description The Dual In-line Memory Module (DIMM) is malfunctioning. Data loss or data corruption may occur. The DIMM must be replaced immediately. Recommended Response Action Replace the DIMM immediately. The DIMM is a part of the controller battery pack. Refer to your hardware documentation for information on replacing the DIMM.CTL58Detailed Description The text for this alert is generated by the firmware and can vary depending on the situation. The reference to SMP in this text refers to SAS Management Protocol. Recommended Response Action There may be a SAS topology error. See the hardware documentation for information on correct SAS topology configurations. There may be problems with the cables such as a loose connection or an invalid cabling configuration. See the Cables Attached Correctly section for more information on checking the cables. See the hardware documentation for information on correct cabling configurations. Verify that the firmware version is supported.CTL59Detailed Description There may be a problem with the enclosure. Verify the health of the enclosure and its components. To verify the health of the enclosure, select the enclosure object in the tree view. The Health sub-tab displays a red X or yellow exclamation point for enclosure components that are failed or degraded. See the enclosure documentation for more information. Recommended Response Action There may be a problem with the enclosure. Verify the health of the enclosure and its components. To verify the health of the enclosure, select the enclosure object in the tree view. The Health sub-tab displays a red X or yellow exclamation mark for enclosure components that are failed or degraded. See the enclosure documentation for more information.CTL83Detailed Description The management controller is not communicating with the storage controller identified in the message. This may be because of any one of the following: a) PCIe subsystem is has stopped functioning b) An issue in the storage controller c) An issue in the management controller. Recommended Response Action Restart the server. If the issue persists, contact your service provider.CTL85Detailed Description The controller identified in the message experienced a PCIe training error and is operating at less than full bandwith. Until this issue is resolved, a reduction in the storage performace is expected. Recommended Response Action Perform a Powercycle operation on the Chassis. If the issue persists, contact your service provider.ENC100Detailed Description The storage controller is not receiving a consistent response from the enclosure due to a firmware problem or an incorrect cabling configuration. If the cables are longer than the specified maximum length, the signals may be degraded. Recommended Response Action Turn off all the enclosures attached to the system, check if the cable configurations are correct. and reboot the system. If the problem persists, update the enclosure firmware to the latest supported version. Download the latest supported version of the firmware from the service provider. For more information about cable configuration, see storage enclosure documentation.ENC18Detailed Description The controller has lost communication with an Enclosure Management Module (EMM). The cables may be loose or defective. Recommended Response Action Make sure the cables are attached securely. See the storage hardware documentation for more information on checking the cables. Reboot the system.ENC19Detailed Description An Enclosure Management Module (EMM) has failed. The failure may be caused by a loss of power to the EMM. The EMM self-test may also have identified a failure. There may also be a firmware problem or a multi-bit error. Recommended Response Action Reseat the Enclosure Management Module (EMM). See the storage hardware documentation for information on replacing the EMM. Replace the EMM. Contact technical support if the issue persists.ENC2Detailed Description An Enclosure Management Module (EMM) was removed. Recommended Response Action Reinsert the Enclosure Management Module (EMM). See the storage hardware documentation for information on replacing the EMM.ENC21Detailed Description A device has been removed and the system is no longer functioning in optimal condition. Recommended Response Action Replace the device.ENC23Detailed Description There is a problem with a physical connection or PHY in the enclosure identified in the message. Recommended Response Action Contact your service provider.ENC24Detailed Description The controller is not receiving a consistent response from the enclosure. There could be a firmware problem or an invalid cabling configuration. If the cables are too long, they degrade the signal. Recommended Response Action Power down all enclosures attached to the system and reboot . If the problem persists, upgrade the firmware to the latest supported version. Verify the cable configuration is valid. See the storage hardware documentation for valid cabling configurations.ENC25Detailed Description The enclosure or an enclosure component is in a Failed or Degraded state. Recommended Response Action Verify the health of the enclosure and its components. See the storage hardware documentation for more information. Contact technical support.ENC26Detailed Description The enclosure or an enclosure component is in a Failed or Degraded state. It is not responding to storage management commands or there is a connectivity problem between the controller and enclosure. Recommended Response Action Verify the health of the enclosure and its components. See the hardware documentation to for more information. Contact technical support.ENC3Detailed Description The physical disk enclosure is either hotter or cooler than the maximum or minimum allowable temperature range. Recommended Response Action Check for factors that may cause overheating or excessive cooling. For example, verify that the enclosure fan is working. You should also check the thermostat settings and examine whether the enclosure is located near a heat source. Make sure the enclosure has enough ventilation and that the room temperature is not too hot or too cold. Refer to the enclosure documentation for more diagnostic information.ENC6Detailed Description The controller is unable to communicate with an enclosure. There are several reasons for communication loss. For example, there may be a bad or loose cable. An unusual amount of I/O may also interrupt communication with the enclosure. In addition, communication loss may be caused by software, hardware, or firmware problems, bad or failed power supplies, and enclosure shutdown. Recommended Response Action Check for problems with the cables. See the Cables attached correctly section for more information on checking the cables. You should also check to see if the enclosure has degraded or failed components. To do this, select the enclosure object in the tree view and click the Health subtab. The Health subtab displays the status of the enclosure components. Verify that the controller has the supported driver and firmware versions installed and that each Enclosure Management Modules (EMMs) are running the same version of supported firmware.

Support Cases