Type | System Health | ||
Severity | Critical | ||
Detailed Description | The current sensor identified in the message has failed. This condition can cause system performance issues and degradation in the monitoring capability of the system. | ||
Recommended Action | Check the Embedded System Management (ESM) Log for any sensor related faults. If there is a failed sensor, replace the system board. For more information, contact your service provider. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The current sensor identified in the message has failed. This condition can cause system performance issues and degradation in the monitoring capability of the system. | ||
Recommended Action | Check the Embedded System Management (ESM) Log for any sensor related faults. If there is a failed sensor, replace the system board. For more information, contact your service provider. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | The current sensor identified in the message has returned to a normal state. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The current sensor identified in the message is faulty or the current drawn by the system exceeds the warning threshold. This condition can cause system performance issues and degradation in the monitoring capability of the system. | ||
Recommended Action | Verify the Embedded System Management (ESM) Log for any sensor related faults. If there is a failed sensor, replace the system board. For more information, contact your service provider. Otherwise, change the warning threshold for the current sensor such that it corresponds to the hardware configuration. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The current sensor identified in the message is faulty or the current drawn by the system exceed the critical threshold. This condition can cause system performance issues and degradation in the monitoring capability of the system. | ||
Recommended Action | Review system power policy, check system logs for power related failures, and review system configuration changes. For more information, contact your service provider. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The current sensor identified in the message may be faulty. This condition can cause system performance issues and degradation in the monitoring capability of the system. | ||
Recommended Action | Check the Embedded System Management (ESM) Log for any sensor related faults. If there is a faulty sensor, replace the system board. For more information, contact your service provider. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The watchdog timer has expired at the date and time identified in the message, because iDRAC did not receive a response within the specified time. | ||
Recommended Action | To determine the correct cause of the exception, contact your service provider. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The watchdog timer has restarted the system at the date and time identified in the message, because the operating system has crashed or hung. | ||
Recommended Action | To determine the correct cause of the exception, contact your service provider. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The watchdog timer has turned off the system after the specified time at the date and time identified in the message, because the operating system has crashed or hung. | ||
Recommended Action | To determine the correct cause of the exception, contact your service provider. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The watchdog timer has performed an AC power cycle on the system after the specified time at the date and time identified in the message, because the operating system has crashed or hung. | ||
Recommended Action | To determine the correct cause of the exception, contact your service provider. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | System settings may be preserved if input power is not removed from the power supplies. | ||
Recommended Action | Check the system board battery at the next service window. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | System settings may be preserved if input power is not removed from the power supplies. | ||
Recommended Action | Check the system board battery. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | None. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | System settings may be preserved if input power is not removed from the power supplies. | ||
Recommended Action | Check the system board battery to confirm presence. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | System settings may be preserved if input power is not removed from the power supplies. | ||
Recommended Action | Check the battery at the next service window. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | None. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | System settings may be preserved if input power is not removed from the power supplies. | ||
Recommended Action | Check the battery. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | None. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | System settings may be preserved if input power is not removed from the power supplies. | ||
Recommended Action | Check the battery to confirm presence. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The system battery level is low, and if the input power is disconnected, the system settings will not be preserved. | ||
Recommended Action | Replace the battery. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The system battery level is unknown, and if the input power is disconnected, the system settings will not be preserved. | ||
Recommended Action | Replace the battery. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller cannot communicate with the battery. The battery is absent or improperly connected. A battery with a weak or depleted charge may also cause this message. | ||
Recommended Action | Verify that the device is present and then check the cables. See the storage hardware documentation to verify cabling. In addition check the connection to the controller battery and the battery health. A battery with a weak or depleted charge may cause this message. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A controller's battery was replaced. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller battery must be fully charged before the learn cycle can begin. The battery may be unable to maintain a full charge causing the learn cycle to timeout. In addition, the battery must be able to maintain cached data for a specified period of time in the event of a power loss. For example, some batteries maintain cached data for 24 hours. If the battery is unable to maintain cached data for the required period of time, then the Learn cycle will timeout. | ||
Recommended Action | Replace the battery pack. The battery is unable to maintain a full charge. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller battery cannot maintain cached data for the required period of time. For example, if the required period of time is 24 hours, then the battery cannot maintain cached data for 24 hours. | ||
Recommended Action | Verify the battery health is good. See the storage hardware documentation to verify battery health. Contact technical support. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The controller battery health has returned to normal. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | Battery is in warn only mode and requires reconditioning. | ||
Recommended Action | Start a learn cycle on the battery. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The battery cannot be recharged further. | ||
Recommended Action | Replace the battery pack. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Diagnostic event for service to determine if there is an ambient temperature problem. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Diagnostic event for service to determine if there is an ambient temperature problem. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The temperature of the battery is high. This may be due to the battery being charged. | ||
Recommended Action | If the battery is being charged, then charging the battery should be stopped until the battery cools down and charging should be resumed. If this is not case, then some other condition exists and should be investigated. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller battery cannot maintain sufficient charge level to function properly or the battery is discharging. | ||
Recommended Action | Check for other events related to the state of the battery. These may help determine the cause of this event. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The battery health has returned to normal. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The battery or the battery charger is not functioning properly. The battery may have an inadequate charge. | ||
Recommended Action | Contact technical support. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The controller was unable to recover data from the cache. This may indicate data loss has occurred. | ||
Recommended 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. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The controller has retrieved cached data. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The battery successfully completed a charge cycle. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller battery voltage is low. This may indicate that the battery is no longer protecting the controller cache. | ||
Recommended Action | The battery needs to recharged. Wait 24 hours to see if the charge is restored. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed 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 Action | Contact technical support. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The room temperature may be too hot. In addition, the system fan may be degraded or failed. | ||
Recommended Action | Verify that the room temperature is normal and that fans are functioning properly. See the storage hardware documentation for acceptable operating temperatures. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The battery temperature is within the normal operating range. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller cannot communicate with the battery. Either the battery was removed, or the contact point between the controller and the battery is degraded. | ||
Recommended Action | Make sure that the battery is present and properly connected. If the battery is present, wait for a few minutes and re-check if the battery is detected. If the contact point between the battery and the controller is degraded, you must replace the battery, the controller, or both. Refer to the storage hardware documentation for information on how to safely access, or remove. Contact technical support if the issue persists. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The battery temperature is above normal operating temperature. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The battery on the controller identified in the message is being discharged. | ||
Recommended Action | No response action is required. | ||
Type | Configuration | ||
Severity | Critical | ||
Detailed Description | The system configuration data that BIOS exposes to Server Administrator is malformed or not available and Server Administrator is unable to read or change any of the system BIOS configuration settings. | ||
Recommended Action | Power cycle the system and retry the operation. If the problem persists, reinstall the BIOS firmware Update Package. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | A BIOS update job is scheduled through the remote access controller, and the system must be rebooted to apply the update. | ||
Recommended Action | Reboot the system to apply the BIOS update. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | A previously scheduled BIOS update job is cancelled. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | System event log and OS logs may indicate the source of the error. | ||
Recommended Action | Review System Event Log and Operating System Logs. These logs can help the user identify the possible issue that is producing the problem. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The processor temperature increased beyond the operational range. Thermal protection shut down the processor. Factors external to the processor may have induced this exception. | ||
Recommended Action | Review logs for fan failures, replace failed fans. If no fan failures are detected, check inlet temperature (if available) and reinstall processor heatsink. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | System is unable to boot or may run in a degraded state. | ||
Recommended Action | Review product documentation for supported CPU configurations. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | None. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | System is unable to boot or may run in a degraded state. | ||
Recommended Action | If unexpected, check presence, and system setup (BIOS) configuration. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | None. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The CPU is throttled due to thermal or power conditions. | ||
Recommended Action | Review system logs for power or thermal exceptions. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | None. | ||
Recommended Action | Review System Event Log and Operating System Logs. If the issue persists, contact technical support. Refer to the product documentation to choose a convenient contact method. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | None. | ||
Recommended Action | Verify processor installation. If present, reseat the processor. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The controller alarm test has run successfully. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A user operation to reset the controller configuration was performed. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The controller and attached enclosures are not cabled correctly. | ||
Recommended Action | Refer to the storage hardware documentation for information on correct cabling configurations. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller has flushed the cache and all data in the cache has been lost. This may occur when the system has memory or battery problems that cause the controller to distrust the cache. Although user data may have been lost, this alert does not always indicate that relevant or user data has been lost. | ||
Recommended Action | Verify that the battery and memory are functioning properly. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The storage controller memory identified in the message is not operating correctly. | ||
Recommended Action | Contact your service provider. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | Re-issue the command. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | Re-issue the command. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | Re-issue the command. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | You have changed the controller rebuild rate. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | Re-issue the command. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The firmware on the controller identified in the message is not a supported version. | ||
Recommended Action | Download the supported version from the service provider and install it on the controller. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller driver for the identified controller is not a supported version. | ||
Recommended Action | Download the supported version of the driver from the service provider and install it on the operating system. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | Storage Management is unable to determine whether the system has the minimum required versions of the RAID controller firmware and driver due to one of the following: 1) Incorrect installation directory path to the configuration file. 2) Removed or renamed configuration file. | ||
Recommended Action | Reinstall Server Administrator Storage Management software on the operating system. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The status of the changed attribute values are reported for information purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The status of the changed attribute values are reported for information purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The status of the changed attribute values are reported for information purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The status of the changed attribute values are reported for information purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The number of Virtual Disks selected for import has exceeded the supported limit of Virtual Disks on the controller identified in the message. | ||
Recommended Action | Make sure that the number of Virtual Disks selected for import is within the supported limit on the controller, and retry the operation. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | Unable to authenticate the entered passphrase. | ||
Recommended Action | Enter the correct passphrase and retry. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The persistent hot spare feature is enabled on the controller identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | Re-issue the command. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The persistent hot spare feature is disabled on the controller identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The physical disk properties displayed under "Manage Physical Disk Power" option has changed. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is generated when the encryption key in the controller is deleted. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The Local Key Management (LKM) security mode is enabled on the controller identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The Local Key Management (LKM) encryption key in the controller identified in the message has changed. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller identified in the message has two connectors that are connected to the same enclosure. The communication path on one connector has lost connection with the enclosure. The communication path on the other connector is reporting this loss. | ||
Recommended Action | Make sure both the cables are securely attached to the enclosure and controller. For more information about connecting the cables to the enclosure, see the Cables Attached Correctly section in the PERC Users Guide. Also, make sure both Enclosure Management Modules (EMMs) are healthy. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The communication in the redundant path on the connectors of the controller identified in the message is restored. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The redundant path view on the controller identified in the message is cleared. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The Auto Configure operation is successfully completed on the controller identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The disk write cache policy of non-RAID physical disk drives on the controller identified in the message is changed. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | Re-issue the command. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | Re-issue the command. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | Re-issue the command. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | Re-issue the command. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | Re-issue the command. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | You have enabled the controller alarm. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | Re-issue the command. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | Re-issue the command. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This is the result of a user operation. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The operation to import foreign configuration (virtual disks, host spares, and so on) completed successfully. | ||
Recommended Action | Verify the foreign configuration was successfully imported by viewing the virtual disks and hot spares. See the hardware documentation for more information. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A patrol read operation was initiated by the controller or the user. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The patrol read task ended. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | You have disabled the controller alarm. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed 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 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. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | An error involving a single bit has been encountered during a read or write operation. The error correction algorithm has corrected this error. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | An attempt to hot plug an Enclosure Management Module (EMM) has been detected. | ||
Recommended Action | If the new enclosure and its device are not detected by the operating system, try restarting your system to verify the newly attached enclosure and its sub-components are detected. See the hardware documentation for more information. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. The text for this alert is generated by the utility that ran the diagnostics and can vary depending on the situation. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed 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 Action | Refer to the storage hardware documentation for more information on the diagnostic test. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The Dual In-line Memory Module (DIMM) is beginning to malfunction. | ||
Recommended Action | Replace the Dual In-line Memory Module (DIMM) to avoid data loss or data corruption. The DIMM is a part of the controller battery pack. Refer to hardware documentation for information on replacing the DIMM. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The Dual In-line Memory Module (DIMM) is malfunctioning. Data loss or data corruption may occur. | ||
Recommended 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. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The Dual In-line Memory Module (DIMM) is malfunctioning. Data loss or data corruption may occur. The DIMM must be replaced immediately. | ||
Recommended 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. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The controller has physical disks that were moved from another controller or have been removed and replaced on the current configuration. These physical disks contain virtual disks that were created on the current or other controller. See the storage hardware documentation for Import Foreign Configuration and Clear Foreign Configuration for more information. Foreign configuration is seen when a controller is replaced. | ||
Recommended Action | Import or clear the detected foreign configuration using a configuration tool or utility. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The NVRAM has corrupted data. This may occur after a power surge, a battery failure, or for other reasons. The controller is reinitializing the NVRAM. | ||
Recommended Action | No response action is required as the controller is taking the required corrective action. However, If this message is generated often (such as during each reboot), then replace the controller. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | A portion of a physical disk is damaged. See Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error for more information. | ||
Recommended Action | See Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error for more information. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The NVRAM has corrupt data. The controller is unable to correct the situation. | ||
Recommended Action | Replace the controller. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The text for this message is generated by the controller during runtime and can vary depending on the situation. | ||
Recommended Action | Make sure the SAS cables attached to the enclosure/backplane are attached securely. Refer to the storage hardware documentation for more information on checking the cables. Contact technical support if the issue persists. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. The text for this alert is generated by the controller and can vary depending on the situation. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. The text for this alert is generated by the controller and can vary depending on the situation. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The text for this alert is generated by the controller and can vary depending on the situation. This text is from events in the controller event log that were generated while Storage Management was not running. | ||
Recommended Action | If there is a problem, review the controller event log and the Server Administrator alert log for significant events or alerts that may assist in diagnosing the problem. Verify the health of the storage components. See the hardware documentation for more information. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The text for this alert is generated by the controller and can vary depending on the situation. This text is from events in the controller event log that were generated while Storage Management was not running. | ||
Recommended Action | See the hardware documentation for more information. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The controller was reset to factory default configuration settings. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed 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 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. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed 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 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. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | A portion of a physical disk is damaged. See Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error for more information. | ||
Recommended Action | See Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error for more information. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller has detected a change in the storage configuration between since its last shut down. This can generally happen if some configured physical disks are removed from the system when the system was shutdown. | ||
Recommended Action | Shut down the system. Re-insert the removed physical disks and re-start the system. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Physical disk(s) have been removed from a virtual disk. The virtual disk will be in Failed state during the next system reboot. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller is unable to retrieve storage configuration saved during last shut down. This can generally happen if some configured physical disks are removed from the system when the system was shutdown. | ||
Recommended Action | Shut down the system. Re-insert the removed physical disks and re-start the system. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | A portion of a physical disk is damaged. See Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error for more information. | ||
Recommended Action | See Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error for more information. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | There is too much foreign configuration data to be imported in one attempt. | ||
Recommended Action | Import these foreign configurations in multiple attempts. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller has preserved data in the cache from a virtual disk, which it can no longer locate. No data loss has occurred as the controller is saving these operations in its cache. | ||
Recommended Action | Check for the existence of a foreign configuration and import if any. Check that enclosures are cabled correctly. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller cache was discarded by the user. Data may have been lost or corrupted. | ||
Recommended Action | If data was corrupted or lost, restore the data to the disk from a backup copy. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The controller encountered errors while applying the configuration on the physical disks. The configuration command applied has not taken effect. | ||
Recommended Action | Re-issue the failed configuration command or try with a different set of physical disks. Contact technical support if the problem persists. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | A portion of a physical disk is damaged. See Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error for more information. | ||
Recommended Action | See Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error for more information. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | A portion of a physical disk is damaged. See Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error for more information. | ||
Recommended Action | See Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error for more information. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The controller identified in the message has requested a new personality mode (HBA or RAID or Unsupported). | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | An Enclosure Management Module (EMM) has failed is inserted into the enclosure. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | You have changed the enclosure asset name. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed 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 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. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | An enclosure service tag was changed. In most circumstances, this service tag should only be changed by the service provider. | ||
Recommended Action | Make sure that the service tag was changed under authorized circumstances. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Communication with an enclosure has been restored. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | An unsupported configuration was detected. The SCSI rate of the Enclosure Management Modules (EMMs) are not the same. | ||
Recommended Action | Replace one of the EMMs with the matching SCSI rate EMM. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | There are too many enclosures attached to the controller port. When the enclosure limit is exceeded, the controller loses contact with all enclosures attached to the port. This is an unsupported configuration. | ||
Recommended Action | Remove the extra enclosures. Refer to the storage hardware documentation for maximum number of enclosures that can be connected. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The controller has lost communication with an Enclosure Management Module (EMM). The cables may be loose or defective. | ||
Recommended Action | Make sure the cables are attached securely. See the storage hardware documentation for more information on checking the cables. Reboot the system. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed 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 Action | Reset 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. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | An Enclosure Management Module (EMM) was removed. | ||
Recommended Action | Reinsert the Enclosure Management Module (EMM). See the storage hardware documentation for information on replacing the EMM. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A device is inserted in the enclosure. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | A device has been removed and the system is no longer functioning in optimal condition. | ||
Recommended Action | Replace the device. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The enclosure has a bad sensor. The enclosure sensors monitor the fan speeds, temperature probes, and so on. | ||
Recommended Action | Refer to the storage hardware documentation for more information. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | There is a problem with a physical connection or PHY in the enclosure identified in the message. | ||
Recommended Action | Contact your service provider. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed 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 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. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The enclosure or an enclosure component is in a Failed or Degraded state. | ||
Recommended Action | Verify the health of the enclosure and its components. See the storage hardware documentation for more information. Contact technical support. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed 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 Action | Verify the health of the enclosure and its components. See the hardware documentation to for more information. Contact technical support. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The enclosure cannot support both SAS and SATA physical disks. Physical disks may be disabled. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The firmware on the EMM modules is not the same version. Both modules must have the same firmware version. This message is caused when you attempt to insert an EMM module that has a different firmware version than an existing module. | ||
Recommended Action | Upgrade to the same version of the firmware on both EMM modules and then powercycle the system and attached enclosures. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The physical disk enclosure is either hotter or cooler than the maximum or minimum allowable temperature range. | ||
Recommended 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. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The system was unable to download firmware to the enclosure. The controller may have lost communication with the enclosure. There may have been problems with the data transfer or the download media may be corrupt. | ||
Recommended Action | Attempt to download the enclosure firmware again. If problems continue, verify that the controller can communicate with the enclosure. Make sure that the enclosure is powered ON. Refer to the storage hardware documentation for information on checking the cables. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The SEP has been rebooted as part of the firmware download operation and will be unavailable until the operation completes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Data redundancy has been restored to an enclosure that previously suffered a loss of redundancy. | ||
Recommended Action | This alert is provided for informational purposes. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The firmware on the EMM modules is not the same version. It is required that both modules have the same version of the firmware. This alert may be caused when you attempt to insert an EMM module that has a different firmware version than an existing module. | ||
Recommended Action | Download the same version of the firmware to both EMM modules. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The controller detected a new enclosure. This is due either to a hot plug of an enclosure, or a power state change of an enclosure. In addition, this message is generated if the daisy chain order of the enclosures changes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | One or more of the enclosure components has failed. For example, a fan or power supply may have failed. Although the enclosure is currently operational, the failure of additional components could cause the enclosure to fail. | ||
Recommended Action | Identify and replace the failed component. To identify the failed component, select the enclosure in the tree view and click the Health subtab. Any failed component will be identified with a red X on the enclosure's Health subtab. Alternatively, you can select the Storage object and click the Health subtab. The controller status displayed on the Health subtab indicates whether a controller has a failed or degraded component. See the enclosure documentation for information on replacing enclosure components and for other diagnostic information. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed 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 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. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | You have enabled the enclosure alarm. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | You have disabled the enclosure alarm. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | You have changed the enclosure asset tag. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The fan identified in the message has failed or it is not installed correctly. | ||
Recommended Action | Remove and re-install the fan or replace the fan, and open the OMSA Web interface to verify if the fan specified in the message is displayed correctly. If the issue persists, contact your service provider. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | The fan identified in the message is removed. However, the fan may be required for optimal system performance. | ||
Recommended Action | Re-install the fan, and open the OMSA Web interface to verify if the fan identified in the message is displayed correctly. If the issue persists, contact your service provider. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The sensor identified in the message has failed. The sensor may be required for optimal system performance. | ||
Recommended Action | Check the Embedded System Management (ESM) Log for any sensor related faults. If the fan sensor has failed, replace the system board. For more information, contact your service provider. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The fan sensor identified in the message has failed or the fan has failed. | ||
Recommended Action | Do the following: 1) Remove the old fan, install a new fan and power cycle the system to check if the fan is working properly, 2) Replace the system board if the fan sensor has failed. 3) If the issue persists, contact your service provider. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | The sensor identified in the message has returned to a normal state. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The fan identified in the message is not functioning correctly. The fan may be installed incorrectly or may be failing. | ||
Recommended Action | Remove and re-install the fan, or replace the fan. If the issue persists, contact your service provider. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The fan sensor identified in the message indicates that the related fan has exceeded critical RPM thresholds. | ||
Recommended Action | Remove and re-install the fan, or replace the fan with a new fan. If the issue persists, contact your service provider. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The sensor identified in the message has failed. The sensor may be required for optimal system performance. | ||
Recommended Action | Check the Embedded System Management (ESM) Log for any sensor related faults. If the fan sensor has failed, replace the system board. For more information, contact your service provider. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The entry in the journal for the device identified in the message with the WWN (World Wide Name) is available. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The journal mirror at the reported file path is being replaced. This event is a notification that the journal mirror replacement is now complete. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The cache flushing operation has started for the virtual disk identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The cache flushing operation has completed for the virtual disk identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The cache device identified in the message is registered by the Fluid Cache. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The cache device identified in the message is removed from the Fluid Cache configuration. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The cache device identified in the message is being removed from the Fluid Cache configuration. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Caching is being removed for the virtual disk identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Caching is enabled on the virtual disk identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The operation to disable caching is successful. Caching is disabled for the virtual disk identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The cached LUN identified in the message has had a failure to successfully perform a read or write operation. The user application should now be seeing I/O failures when trying to read or write to the Fluid Cache device at the path identified in the message. | ||
Recommended Action | Contact your service provider to diagnose the cause and assist in recovery process. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Replication of the cache device identified in the message is complete. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The recovery of the cache device identified in the message complete. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A valid permanent license is installed for Fluid Cache. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A license has been installed for Fluid Cache. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A license has been removed for Fluid Cache. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | All cache devices have been found and registered for Fluid Cache. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The storage device identified in the message is in unknown state. | ||
Recommended Action | Service is required. Contact your service provider. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The device identified in the message having the journal mirror entry with given WWN (World Wide Name) is not accessible. A portion of an SSD is used for journal content. To assure consistency, the journal content is written into two other SSDs. These copies are journal mirrors. If the journal content cannot be written to any of the journal mirrors, then this event is signaled. It is a warning because the FLDC code will then attempt to choose another SSD to be a journal mirror. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The cache device identified in the message with given WWN does not exist in the Fluid Cache configuration. | ||
Recommended Action | To identify the cause of the configuration inconsistency, contact your service provider. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Fluid Cache is currently running on an evaluation license and the evaluation license expires in the number of days identified in message. | ||
Recommended Action | A permanent license for Fluid Cache should be purchased for continued service. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | Caching was enabled in write-back mode but currently it is operating in write-through mode because the fluid Cache Pool has one PCIe-SSD. | ||
Recommended Action | Add another PCIe SSD device to the Fluid Cache Pool to resolve the issue. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | Caching was enabled in write-back mode or write through mode, but currently it is operating in write-through mode because fluid Cache Pool has no PCIe-SSD device. | ||
Recommended Action | Add another PCIe SSD device to the Fluid Cache Pool to resolve the issue. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The caching mode has been restored back to write-back mode due to the availability of additional PCIeSSD devices in the Fluid Cache configuration. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The caching mode has been restored back to the configured mode due to the availability of additional PCIeSSD devices in the Fluid Cache configuration. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The communications connection between OMSS and the Fluid Cache service is no longer present. | ||
Recommended Action | To reconnect OMSS to the Fluid Cache service: 1) Verify the Fluid Cache service is running. To verify the service run the following command: "fldc --status". 2) Re-establish the connect by running the following command: :"omconfig storage fluidcache action=connect". | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The message indicates that there are not enough journal mirrors available for Fluid Cache to operate. Make sure that there are at least two journal mirrors that are accessible. Activate either one or more failed cache devices or use the fldc_restore utility to rebuild the node. | ||
Recommended Action | Contact your service provider to diagnose the cause and assist in recovery process. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | An Inconsistency was found in Fluid Cache configuration data. | ||
Recommended Action | Service is required. Contact your service provider. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | Unable to access redundant Fluid Cache configuration information. | ||
Recommended Action | Service is required. Contact your service provider. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The PCIeSSD cache device identified in the message is no longer functional. | ||
Recommended Action | Replace the non-functional PCIe SSD. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The message indicates that the storage device is either inaccessible or is no longer functional. | ||
Recommended Action | If the virtual disk is inaccessible, restore accessibility by bringing the virtual disk back online. After the virtual disk is accessible, run the following command to reactivate disk, "omconfig storage vdisk action=reactivate controller=id vdisk=id devicename=<string>". If the device is no longer functional, replace it. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | A valid license is not installed for Fluid Cache. | ||
Recommended Action | Install a valid Fluid Cache license. For more information, contact your service provider. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | Configuration changes are not allowed because Fluid Cache is running on an expired evaluation license. The message also indicates the number of days that Fluid Cache has been running with an expired license (maximum 30 days after expiration are allowed). | ||
Recommended Action | Install a valid Fluid Cache license. For more information, contact your service provider. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | Caching functionality is disabled because Fluid cache is running on an expired evaluation license. The message also indicates the number of days that Fluid Cache has been running with an expired license (maximum 30 days after expiration are allowed). | ||
Recommended Action | Install a permanent Fluid Cache license. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | Configuration changes are disabled, because Fluid cache is running on an expired or invalid license. | ||
Recommended Action | Install a permanent Fluid Cache license. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | There is not enough memory capacity to run necessary services for Fluid Cache. | ||
Recommended Action | The minimum memory required to run Fluid Cache for DAS is 16 GB. For optimum operation, recommendation is to install 32 GB of RAM. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | One or more cache devices are missing and the cache is unresponsive. | ||
Recommended Action | Insert the missing cache device. If the cache device was unplugged, reactivate it. Reactivate a cache device by running the following command: "omconfig storage pciessd action=reactivate subsystem=id pciedevice=<PDISKID>". | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | An unknown device plug event occurred at the identified device location. Along with the device location, additional event details are provided if available. | ||
Recommended Action | No response action is required. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | A device was added to the system at the location identified in the message. Along with the device location, additional event details are provided if available. | ||
Recommended Action | No response action is required. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | A device was removed from the system at the location identified in the message. Along with the device location, additional event details are provided if available. | ||
Recommended Action | No response action is required. | ||
Type | Audit | ||
Severity | Critical | ||
Detailed Description | A configuration error was detected for a pluggable device installed at the location identified in the message. The device may not be installed correctly. | ||
Recommended Action | Reinsert the device or try inserting a different device of the same type and retry the operation. If the issue persists, check the system documentation to make sure the device is supported or contact your service provider. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The SD card device sensor of the type identified in the message has failed. The current status of the SD card is also displayed. | ||
Recommended Action | Reinsert the SD card or try a different SD card and retry the operation. If the issue persists, do one of the following to resolve the error: 1) If the SD card sensor is installed on the internal SD module, replace the module. 2) If the SD card sensor is embedded on the system board, replace the system board. . For more information, contact your service provider. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | The SD card device has returned to a normal state. The SD card type and the current status of the SD card is also displayed. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The SD card device is not functioning correctly, and its state has changed to a warning state. | ||
Recommended Action | Reinsert the SD card or try a different SD card and retry the operation. If the issue persists, do one of the following to resolve the error: 1) If the SD card sensor is installed on the internal SD module, replace the module. 2) If the SD card sensor is embedded on the system board, replace the system board. . For more information, contact your service provider. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The SD card sensor detected an SD card failure. | ||
Recommended Action | Replace the old SD card with a new SD card. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | An SD card device sensor has detected an irrecoverable error in the SD card. | ||
Recommended Action | Replace the old SD card with a new SD card. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | An SD card device sensor in the identified system could not obtain a reading. | ||
Recommended Action | Remove and reinsert the identified SD card. | ||
Type | Audit | ||
Severity | Warning | ||
Detailed Description | The hardware log in the system is disabled. The log type information is provided. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | The hardware log may not be up-to-date. The log type information is provided. | ||
Recommended Action | Make sure that iDRAC is functioning correctly. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | The hardware log in the system is no longer near its maximum capacity. The log type information is provided. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The size of a hardware log in the system is near its maximum capacity. The log type information is provided. | ||
Recommended Action | Clear the log to make sure new entries are recorded. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The size of a hardware log in the system has reached its maximum capacity. The log type information is provided. | ||
Recommended Action | Clear the log to make sure new entries are recorded. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | Unable to receive any log entries, and therefore log status cannot be monitored. The log type information is provided. | ||
Recommended Action | Make sure that iDRAC is functioning correctly. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | The Alert Log was cleared. | ||
Recommended Action | No response action is required. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | An Alert Log backup was created. | ||
Recommended Action | No response action is required. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | The Server Based Management Mode is enabled. Chassis based PSUs, fans, and sensor information can be displayed from server based system management tools. | ||
Recommended Action | No response action is required. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | The Server Based Management Mode is disabled. Chassis based PSUs, fans, and sensor information will not be displayed from server based system management tools. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | The memory module may not be correctly seated, wrongly configured, or has failed. | ||
Recommended Action | Review the Embedded System Management (ESM) Log for memory exceptions. Re-install the memory modules. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The memory module may not be correctly seated, wrongly configured, or has failed. | ||
Recommended Action | Review the Embedded System Management (ESM) Log for memory exceptions. Re-install the memory modules at the identified location . | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | The memory device identified in the message has returned to a normal state. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The memory module may not be correctly seated, wrongly configured, or has failed. | ||
Recommended Action | Review the Embedded System Management (ESM) Log for memory exceptions. Re-install the memory modules at the identified location . | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The memory module may not be correctly seated, wrongly configured, or has failed. | ||
Recommended Action | Review the Embedded System Management (ESM) Log for memory exceptions. Re-install the memory modules at the identified location . | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The memory module failed because of an irrecoverable error. | ||
Recommended Action | Review the Embedded System Management (ESM) Log for memory exceptions. Remove the old memory module and install a new memory module at the identified location . | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The NVDIMM device in the slot, identified in the message, is about to reach the end of supported life duration. | ||
Recommended Action | During the next scheduled maintenance, replace the Non-Volatile Dual In-line Memory Module (NVDIMM) device. For more information about the usage of NVDIMMs, see the system Owner's Manual on the support site. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The NVDIMM in the slot identified in the message is running the backup firmware image because the primary firmware image has issues. | ||
Recommended Action | Update the Non-Volatile Dual In-line Memory Module(NVDIMM) to the latest firmware. If the issue persists, contact your service provider. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The NVDIMM device identified in the message has encountered a correctable memory error. This may be an early indicator of a possible future uncorrectable error. | ||
Recommended Action | Remove and reinstall the Non-Volatile Dual In-line Memory Module (NVDIMM) device. If the issue persists, contact the service provider. For information about removing and reinstalling the NVDIMM, see the system Owner's Manual on the support site. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The NVDIMM device in the slot identified in the message is not responding and is disabled. | ||
Recommended Action | Remove and reinstall the Non-Volatile Dual In-line Memory Module (NVDIMM) device. If the issue persists, contact your service provider. For information about removing and reinstalling the NVDIMM, see the system Owner's Manual on the support site. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The NVDIMM device in the slot identified in the message is unable to save the data during the previous system shutdown operation or power loss. The NVDIMM is placed in write-protect mode. | ||
Recommended Action | Remove and reinstall the Non-Volatile Dual In-line Memory Module (NVDIMM) device. If the issue persists, contact your service provider. For information about removing and reinstalling the NVDIMM, see the system Owner's Manual on the support site. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The NVDIMM device in the slot identified in the message is unable to restore the data that was saved in the previous 'save' operation. The NVDIMM is placed in write-protect mode. | ||
Recommended Action | Remove and reinstall the Non-Volatile Dual In-line Memory Module (NVDIMM) device. If the issue persists, contact your service provider. For information about removing and reinstalling the NVDIMM, see the system Owner's Manual on the support site. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | An NVDIMM device is of unsupported configuration and unable to operate as currently configured. | ||
Recommended Action | Review the memory configuration and make sure the configuration is as per memory rules defined in the system Owner's Manual on the support site. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The NVDIMM device in the slot identified in the message is not responding. | ||
Recommended Action | Remove and reinstall the Non-Volatile Dual In-line Memory Module (NVDIMM) device. If the issue persists, contact your service provider. For information about removing and reinstalling the NVDIMM, see the system Owner's Manual on the support site. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The NVDIMM device in the slot identified in the message cannot be configured to save data during a power loss because of an issue in the NVDIMM. | ||
Recommended Action | Remove and reinstall the Non-Volatile Dual In-line Memory Module (NVDIMM) device. If the issue persists, contact your service provider. For information about removing and reinstalling the NVDIMM, see the system Owner's Manual on the support site. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The NVDIMM devices are placed in write-protect mode because the server may not provide sufficient power or the battery is not sufficiently charged to save data in case of power loss. | ||
Recommended Action | Review any preceding power or battery entries in the log and resolve the issues. Refer to your documentation for details on how to view the log. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The NVDIMM device in the slot identified in the message has reached the end of supported life duration and is placed in write-protect mode. | ||
Recommended Action | Replace the Non-Volatile Dual In-line Memory Module (NVDIMM) device. For information about removing and reinstalling the NVDIMM, see the system Owner's Manual on the support site. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The NVDIMM device in the slot identified in the message has lost persistency and is placed in write-protect mode. | ||
Recommended Action | Remove and reinstall the Non-Volatile Dual In-line Memory Module (NVDIMM) device. If the issue persists, contact the service provider. For information about removing and reinstalling the NVDIMM, see the system Owner's Manual on the support site. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The NVDIMM device in the slot identified in the message was unable to clear its storage media as part of the initialization process and is disabled. | ||
Recommended Action | Remove and reinstall the Non-Volatile Dual In-line Memory Module (NVDIMM) device. If the issue persists, contact the service provider. For information about removing and reinstalling the NVDIMM, see the system Owner's Manual on the support site. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The NVDIMM device in the slot identified in the message has encountered a uncorrectable error. System performance may be degraded. The operating system and/or applications may fail as a result. | ||
Recommended Action | Remove and reinstall the Non-Volatile Dual In-line Memory Module (NVDIMM) device. If the issue persists, contact the service provider. For information about removing and reinstalling the NVDIMM, see the system Owner's Manual on the support site. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | The NVDIMM device in the slot identified in the message has regained persistency and is available for use. | ||
Recommended Action | No response action required. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | The NVDIMM device in the slot identified in the message is functioning normally. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | This message is generated after a copyback stops on a physical disk during a rebuild operation. | ||
Recommended Action | Wait for rebuild to finish, then copyback should resume. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This message is generated after a rebuild starts on a physical disk. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller is not able to communicate with a disk that is assigned as a dedicated hot spare. The disk may have been removed. There may also be a bad or loose cable. | ||
Recommended Action | Verify that the disk is healthy and that it has not been removed. Check the cables. See the Cables Attached Correctly section for more information on checking the cables. If necessary, replace the disk and reassign the dedicated hot spare. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | This alert message occurs if there are arrays not protected with a global hot spare. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The Patrol Read operation was manually stopped before completion. | ||
Recommended Action | If desired, restart the Patrol Read operation at a later time. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Cryptographic Erase operation is successfully completed on the physical disk drive identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The PCIe solid state device identified in the message has turned off because the critical temperature threshold of the device was exceeded. | ||
Recommended Action | Contact your service provider. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A user has cancelled the rebuild operation. | ||
Recommended Action | Restart the rebuild operation. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The reliability of the PCIe solid state device identified in the message degraded. Data loss is possible. | ||
Recommended Action | Back up the data on the device, and contact your service provider for further instructions. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The volatile memory backup device on the PCIe solid state device identified in the message is no longer functional. Data loss is possible. | ||
Recommended Action | Back up the data on the device, and contact your service provider for further instructions. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The PCIe solid state device identified in the message is between 90% and 100% of reaching read-only mode. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The physical disk has failed or is corrupt. | ||
Recommended Action | Replace the failed or corrupt disk. Identify a disk that has failed by locating the disk that has a red "X" for its status. Restart the initialization. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | A physical disk included in the virtual disk has failed or is corrupted. In addition, you may have cancelled the rebuild. | ||
Recommended Action | Replace the failed or corrupt disk, and then start the rebuild operation. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This message is generated after a rebuild completes on a physical disk. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The physical disk is predicted to fail. Many physical disks contain Self Monitoring Analysis and Reporting Technology (SMART). When enabled, SMART monitors the disk health based on indications such as the number of write operations that were performed on the disk. | ||
Recommended Action | Replace the physical disk. Even though the disk may not have failed yet, it is strongly recommended that the disk be replaced. Review other messages for additional information. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A user has have assigned a physical disk as a global hot spare. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A physical disk assigned as a hot spare was unassigned and is no longer functioning as a hot spare. The physical disk was unassigned by a user or automatically unassigned by Storage Management. Storage Management unassigns hot spares were used to rebuild data. Once the data is rebuilt onto the hot spare, the hot spare becomes a member of the virtual disk and is no longer assigned as a hot spare. Assign a new hot spare to maintain data protection in this situation. | ||
Recommended Action | Although this alert is provided for informational purposes, you may need to assign a new hot spare to the virtual disk. See Protecting Your Virtual Disk with a Hot Spare for more information. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | A disk on the specified controller has received a SMART alert (predictive failure) indicating that the disk is likely to fail in the near future. | ||
Recommended Action | Replace the disk that has received the SMART alert. If the physical disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk. Removing a physical disk that is included in a non-redundant virtual disk causes the virtual disk to fail and may cause data loss. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | This message is generated if a physical disk does not have enough space to do a copyback operation. | ||
Recommended Action | Replace the physical disk with a larger physical disk, and then restart the copyback operation. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | A disk has received a SMART alert (predictive failure) after a configuration change. The disk is likely to fail in the near future. | ||
Recommended Action | Replace the disk that has received the SMART alert. If the physical disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk. Removing a physical disk that is included in a non-redundant virtual disk will cause the virtual disk to fail and may cause data loss. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The storage controller does not support the attached SSD devices. | ||
Recommended Action | Remove SSD devices not supported by the controller, and retry the operation. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Unable to assign the physical disk as a dedicated hot spare because the selected disk size does not meet the size requirements of the target Virtual Disk. | ||
Recommended Action | Select a physical disk that matches the size required for the disks used in the target Virtual Disk, and retry the operation. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The Cryptographic Erase operation is successfully completed on the physical disk drive identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The Manage Physical Disk Power feature is enabled for physical drives and the power status of the drives changed. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | A disk has received a SMART alert (predictive failure). The disk is likely to fail in the near future. | ||
Recommended Action | Replace the disk that has received the SMART alert. If the physical disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk. Removing a physical disk that is included in a non-redundant virtual disk will cause the virtual disk to fail and may cause data loss. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This event is generated while initializing the drives during reboot. The controller updated the configuration data on the physical disks identified in the message. The drive configuration was updated because the following conditions were present: 1) The spundown drives were used for configuration. Spundown drives are drives that are temporarily powered off because power saving option is enabled. 2) The storage controller was not able to update the Configuration On Disk (COD) records on the drive while they were spundown. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | Storage medium error was detected on the disk identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The physical disk state has changed from Ready state to Non-RAID state. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The physical disk state has changed from Non-RAID state to Ready state. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The physical disk identified in the message is not compliant with the standards set by the hardware provider and is not supported. | ||
Recommended Action | Replace the physical disk with a supported physical disk that is provided by an authorized hardware provider. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The Replace Member Disk operation did not complete successfully because of internal errors. The error may be due to problems with the source or target physical disks or the controller may be out of resources. | ||
Recommended Action | Retry the Replace Member Disk operation with a different target physical disk. If the problem persists, check the condition of the target physical disk and replace if necessary, then retry the operation. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The disk write cache policy of the physical disk drive identified in the message is changed. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The cryptographic erase operation cannot be completed on the physical disk drive identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The media error on the physical disk drive identified in the message cannot be corrected. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | A disk has reached an unacceptable temperature and received a SMART alert (predictive failure). The disk is likely to fail in the near future. | ||
Recommended Action | Do the following:1) Determine why the physical disk reached an unacceptable temperature. For example, a fan failure, incorrect thermostat settings, or the room temperature may be too hot or cold. 2) Verify that the fans in the server or enclosure are working. 3) If the physical disk is in an enclosure, check the thermostat settings and examine whether the enclosure is located near a heat source. Verify the enclosure has enough ventilation and that the room temperature is not too hot. Refer to the enclosure documentation for more diagnostic information. 4) If you cannot identify why the disk has reached an unacceptable temperature, then replace the disk. If the physical disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk. Removing a physical disk that is included in a non-redundant virtual disk causes the virtual disk to fail and may cause data loss. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The rebuild operation is abruptly stopped because of a media error on the physical disk drive identified in the message. | ||
Recommended Action | Replace the drive with a supported physical disk drive and retry the operation. For more information about supported drives, see the OMSS User's Guide available on the support site. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | A disk is degraded and has received a SMART alert (predictive failure). The disk is likely to fail in the near future. | ||
Recommended Action | Replace the disk that has received the SMART alert. If the physical disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk. Removing a physical disk that is included in a non-redundant virtual disk will cause the virtual disk to fail and may cause data loss. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | A disk has received a SMART alert (predictive failure) due to test conditions. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Portions of the physical disk that were formerly inaccessible have been recovered. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A drive has entered the online state. This may be because the system just started or could be because a problem with the drive has been corrected. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A user assigned a physical disk as a dedicated hot spare to a virtual disk. See Protecting Your Virtual Disk with a Hot Spare for more information. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A physical disk that was assigned as a hot spare has been unassigned and is no longer functioning as a hot spare. The physical disk was unassigned by a user or automatically unassigned by Storage Management. Storage Management unassigns hot spares that have been used to rebuild data. Once data is rebuilt onto the hot spare, the hot spare becomes a member of the virtual disk and is no longer assigned as a hot spare. Assign a new hot spare to maintain data protection in this situation. | ||
Recommended Action | Although this alert is provided for informational purposes, you may need to assign a new hot spare to the virtual disk. Refer to product documentation and see the section Protecting Your Virtual Disk with a Hot Spare for more information. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | See A Rebuild Completes with Errors for more information. | ||
Recommended Action | See A Rebuild Completes with Errors for more information. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller cannot to communicate with a disk that is assigned as a global hot spare. The disk either failed or was removed. There may also be a bad or loose cable. | ||
Recommended Action | Verify that the disk is healthy and installed. Check the cables. Refer to the product documentation and see the Cables Attached Correctly section for more information on checking the cables. If necessary, replace the disk and reassign the global hot spare. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The controller cannot to communicate with a disk that is assigned as a global hot spare. The disk either failed or was removed. There may also be a bad or loose cable. | ||
Recommended Action | Verify that the disk is healthy and installed. Check the cables. Refer to the product documentation and see the Cables Attached Correctly section for more information on checking the cables. If necessary, replace the disk and reassign the global hot spare. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller cannot to communicate with a disk that is assigned as a global hot spare. The disk either failed or was removed. There may also be a bad or loose cable. | ||
Recommended Action | Verify that the disk is healthy and installed. Check the cables. Refer to the product documentation and see the Cables Attached Correctly section for more information on checking the cables. If necessary, replace the disk and reassign the global hot spare. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The controller cannot to communicate with a disk that is assigned as a dedicated hot spare. The disk either failed or was removed. There may also be a bad or loose cable. | ||
Recommended Action | Verify that the disk is healthy and installed. Check the cables. Refer to the product documentation and see the Cables Attached Correctly section for more information on checking the cables. If necessary, replace the disk and reassign the dedicated hot spare. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The hot spare is no longer required because the virtual disk it was assigned to has been deleted. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The only physical disk available to be assigned as a hot spare is using SATA technology. The physical disks in the virtual disk are using SAS technology. Because of this difference in technology, the hot spare cannot rebuild data if one of the physical disks in the virtual disk fails. | ||
Recommended Action | Add a SAS disk that is large enough to be used as the hot spare and assign the new disk as a hot spare. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The only physical disk available to be assigned as a hot spare is using SAS technology. The physical disks in the virtual disk are using SATA technology. Because of this difference in technology, the hot spare cannot rebuild data if one of the physical disks in the virtual disk fails. | ||
Recommended Action | Add a SATA disk that is large enough to be used as the hot spare and assign the new disk as a hot spare. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The physical device may not have a supported version of the firmware or the physical device may not be supported. | ||
Recommended Action | If the physical device is supported, then update the firmware to a supported version. If the physical device is not supported, then replace the physical device with one that is supported. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A user has initiated a clear operation on a physical disk. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The clear command did not complete on the physical disk. This means that some data was not cleared and may be recoverable. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This message is generated after a clear operation completes on a physical disk. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | A Clear task was being performed on a physical disk but the task was interrupted and did not complete successfully. The controller may have lost communication with the disk, the disk was removed, or the cables may be loose or defective. | ||
Recommended Action | Verify that the disk is present and not in a Failed state. Make sure the cables are attached securely. See the storage hardware documentation for more information on checking the cables. Restart the Clear task. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The Patrol Read task has encountered an error that cannot be corrected. There may be a bad disk block that cannot be remapped. | ||
Recommended Action | Backup your data from the disk. Start disk initialization and wait for it to complete, then restore the data from the backup to the disk. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The controller encountered an unrecoverable medium error when attempting to read a block on the physical disk and marked that block as invalid. If the controller encountered the unrecoverable medium error on a source physical disk during a rebuild or reconfigure operation, it punctures the corresponding block on the target physical disk. The invalid block clears on a write operation. | ||
Recommended Action | Back up the data from the disk. Start disk initialization and wait for it to complete, and then restore the data from a backup copy. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This message is generated after rebuild resumes on a physical disk. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The dedicate hot-spare either does not meet bus protocol, media type, or does not have sufficient storage space to cover all the virtual drives that form the disk group. | ||
Recommended Action | Assign a drive with matching bus protocol, media type, and sufficient storage space. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | A physical disk has been removed from the disk group. This alert can also be caused by loose or defective cables or by problems with the enclosure. | ||
Recommended Action | Do one of the following: 1) If a physical disk was removed from the disk group, either replace the disk or restore the original disk. Identify the disk that was removed by locating the disk that has a red "X" for its status. 2) Perform a rescan after replacing or restoring the disk. 3) If a disk was not removed from the disk group, then check for cable problems. Refer to product documentation for more information on checking the cables. 4) Make sure that the enclosure is powered on. 5) If the problem persists, check the enclosure documentation for further diagnostic information. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The global hot-spare identified in the message either does not meet bus protocol, media type, or does not have sufficient storage space to cover all the virtual drives available on the controller. | ||
Recommended Action | Assign a drive with matching bus protocol, media type, and sufficient storage space. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The controller firmware attempted to do SMART polling on the hot spare but could not complete the SMART polling. The controller may have lost communication with the hot spare. | ||
Recommended Action | Verify the health of the disk assigned as a hot spare. Replace the disk and reassign the hot spare. Make sure the cables are attached securely. See the storage hardware documentation for more information on checking the cables. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller has two connectors that are connected to the same enclosure. The communication path on one connector has lost connection with the enclosure. The communication path on the other connector is reporting this loss. | ||
Recommended Action | Make sure the cables are attached securely. See the Cables Attached Correctly section for more information on checking the cables. Make sure both Enclosure Management Modules (EMMs) are healthy. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This message is generated after a disk media error is corrected on a physical disk. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The physical disk inserted is too small for the rebuild to occur. | ||
Recommended Action | Replace the physical disk with one of correct protocol (SAS, SATA) with at least the required size. Force rebuild if it does not start automatically. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The bad block table is the table used for remapping bad disk blocks. This table fills as bad disk blocks are remapped. When the table is full, bad disk blocks are no longer remapped, which means that disk errors are no longer corrected. At this point, data loss can occur. The bad block table is now 80 percent full. | ||
Recommended Action | Replace the disk generating this message. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The bad block table is the table used for remapping bad disk blocks. This table fills as bad disk blocks are remapped. When the table is full, bad disk blocks are no longer remapped, which means that disk errors are no longer corrected. At this point, data loss can occur. | ||
Recommended Action | Replace the disk generating this message and restore from a backup copy. You may have lost data. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | A user attempted to replace a disk with another disk that is using an incompatible technology. For example, replaced one side of a mirror with a SAS disk when the other side of the mirror is using SATA technology. | ||
Recommended Action | Refer to the hardware documentation for information on replacing disks. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The disk has a bad block. Data was remapped to another disk block. No data loss has occurred. | ||
Recommended Action | Monitor the disk for other messages or indications of poor health. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | A physical disk in the virtual disk is offline. This may have been user initiated. | ||
Recommended Action | Force the physical disk online or assign a hot spare to the virtual disk. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The reason for the error can vary depending on the situation. The firmware error code is indicated in the message. | ||
Recommended Action | Verify the health of attached devices. Review the Lifecycle log for significant events. Replace faulty hardware, if required. Make sure the cables are attached securely. Refer to the storage hardware documentation for more information on checking the cable connections. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | It is not possible to rebuild data that resides on a defective disk. | ||
Recommended Action | Replace the source disk and restore data from backup. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | It is not possible to rebuild data that resides on a defective disk. | ||
Recommended Action | Replace the target disk. If a rebuild does not automatically start after replacing the disk, then initiate the Rebuild task. You may need to assign the new disk as a hot spare to initiate the rebuild. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | A write operation cannot complete because the disk contains bad disk blocks that could not be reassigned. Data loss may have occurred. Data redundancy may be lost. | ||
Recommended Action | Replace the disk. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The rebuild or recovery operation encountered an unrecoverable disk media error. | ||
Recommended Action | Replace the disk. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | Physical disk inserted is of the incorrect protocol. SAS or SATA mixing is not supported in the same virtual disk. | ||
Recommended Action | Remove drive, insert correct protocol type, and force a rebuild as imposed for controller and system. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | A physical disk has reported an error condition and may be degraded. The physical disk may have reported the error condition in response to a check consistency or other operation. | ||
Recommended Action | Replace the degraded physical disk. Identify the disk that is degraded by locating the disk that has a red "X" for its status. Perform a rescan after replacing the disk. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A copyback operation began to copy data from one physical disk to another physical disk. This may be due to a user initiated operation or a predictive failure. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The copyback operation completed. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A user cancelled the copyback operation. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | Copyback not possible as SAS or SATA mixing is not supported in the same virtual disk. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | When physical drives in spun down power state are configured, the drives should transition to spun up power state. If the drive is not functioning properly, this transition could fail. | ||
Recommended Action | Replace the physical disk and try again. Contact technical support if the issue persists. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | An error occurred while performing an action on the disk. | ||
Recommended Action | Check the disk is present or replace the disk. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | None. | ||
Recommended Action | Remove and re-install the power supply. If the issue persists, contact technical support. Refer to the product documentation to choose a convenient contact method. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The operating requirements for the power supply may be found in product documentation or on the power supply itself. | ||
Recommended Action | Verify the input power is within the operating requirements for the power supply. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The power supply identified in the message must be supported by the platform. Generally, multiple power supplies in the server should have the same feature set and power rating. | ||
Recommended Action | Review server product documentation for supported power supplies and power supply configurations. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | None. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | Power supplies should be of the same input type and power rating. | ||
Recommended Action | Install matched power supplies and review product documentation for proper configuration. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | This power supply revision is not supported for this system. | ||
Recommended Action | Review product documentation, change power supply with correct revision. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The power supply is installed correctly but an input source is not connected or is not functional. | ||
Recommended Action | Verify the input source is attached to the power supply. Verify the input power is within the operating requirements for the power supply. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | Status from the power supply indicates a power supply exception occurred. The power supply will try to operate in a degraded state. System Performance and power redundancy may be degraded or lost. | ||
Recommended Action | Check input power. Re-install the power supply. If problem persists contact support. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | Status from the power supply indicates a power supply exception occurred. The power supply will try to operate. System Performance and power redundancy may be degraded or lost. | ||
Recommended Action | Remove input power and re-install supply at the next service window. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The power supply unit identified in the message is offline, because of the one of the following reasons: 1) The power supply unit is not correctly seated. 2) The power cable may not be connected properly or disconnected. 3) The power supply unit has failed. 4) There is an input power failure. | ||
Recommended Action | Do one of the following to resolve the issue: 1) reseat the power supply unit. 2) Reconnect the power cable to the power supply unit. 3) Install a new power supply unit 4) Restore the input power supply. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The power supply unit is not receiving input AC power. The power cable may not be connected properly or removed. This can happen if there is an AC failure or problems with the power strip attached to the enclosure power supply. | ||
Recommended Action | Reconnect the power cable to the power supply unit if it was disconnected. Restore the input AC power supply. Make sure the power supply is restored to the enclosure from the mains. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The enclosure detected that a power supply unit was removed and is no longer functioning in optimal condition. | ||
Recommended Action | Re-insert the power supply unit into the enclosure. Re-connect the AC power cable and switch on the power supply unit. Contact technical support if the issue persists. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The enclosure detected that AC power supply was restored to the power supply unit. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The enclosure detected that a power supply unit was switched on. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The power supply unit identified in the message is not present, because of the one of the following reasons: 1) The power supply unit is not correctly seated. 2) The power cable may not be connected properly or disconnected. 3) The power supply unit has failed. 4) There is an input power failure. | ||
Recommended Action | Do one of the following to resolve the issue: 1) reseat the power supply unit. 2) Reconnect the power cable to the power supply unit. 3) Install a new power supply unit 4) Restore the input power supply. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The status of the power supply unit identified in the message is unknown, because of one of the following reasons: 1) The power supply unit is not correctly seated. 2) The power cable may not be connected properly or disconnected. 3) The power supply unit has failed. 4) There is an input power failure. | ||
Recommended Action | Do one of the following to resolve the issue: 1) reseat the power supply unit. 2) Reconnect the power cable to the power supply unit. 3) Install a new power supply unit 4) Restore the input power supply. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The power supply identified in the message is switched ON. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | To avoid system damage because of insufficient cooling, the system is being shut down. | ||
Recommended Action | Review the Embedded System Management Log for thermal or environmental failures and warnings, and replace the faulty components. If the issue persists, contact your service provider. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | The system has detected a new peak power value. | ||
Recommended Action | Make sure that the power usage corresponds to the current hardware configuration and workload. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | None. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | One of more fans have failed or have been removed or a configuration change occurred which requires additional fans. | ||
Recommended Action | Remove and re-install failed fans or install additional fans. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | One of more fans have failed or have been removed or a configuration change occurred which requires additional fans. | ||
Recommended Action | Remove and re-install failed fans or install additional fans. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | None. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The current power operational mode is non-redundant because of a power supply exception, a power supply inventory change, or a system power inventory change. The system was previously operating in a power redundant mode. | ||
Recommended Action | Check the event log for power supply failures. Review system configuration and power consumption. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The current power operational mode is non-redundant because of a power supply exception, a power supply inventory change, or a system power inventory change. The system was previously operating in a power redundant mode. | ||
Recommended Action | Check the event log for power supply failures. Review system configuration and power consumption. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | Redundancy is not currently enabled for the power supplies. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | One of the power supply units have failed. | ||
Recommended Action | Replace the failed power supply with a new power supply. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | Redundancy is not currently enabled for the fans. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | One or more fans are non-functional or may have failed. | ||
Recommended Action | Check that all fans are working properly. Replace any non-functional fan with a new fan. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The SD card module is installed but may be improperly installed or configured incorrectly. | ||
Recommended Action | Reinstall the SD module. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The SD card module is installed but improperly configured or failed to initialize. | ||
Recommended Action | Reinstall the SD module and remove and reinstall SD cards. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | None. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | Either one of the SD card or both the SD cards are not functioning properly. | ||
Recommended Action | Replace the failed SD card. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | Either one of the SD card or both the SD cards are not functioning properly. | ||
Recommended Action | Replace the failed SD card. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | Redundancy is not currently enabled for the Internal SD Module. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | This occurs because of one of the following reasons: 1) Either one of the SD card or both the SD cards have failed. 2) The Internal SD Module has failed. | ||
Recommended Action | Replace the failed SD card with a new SD card, or replace the Internal SD Module. For more information, contact your service provider. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The chassis is open. System performance may be degraded, and security may be compromised. | ||
Recommended Action | Close the chassis. Check system logs. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | None. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The chassis may be open. This condition can lead to degraded system performance because of insufficient cooling and the system security may be compromised. | ||
Recommended Action | Close the chassis. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The chassis intrusion sensor may have failed, because of this it cannot be determined whether the chassis is closed or opened. This condition can lead to degraded system performance because of insufficient cooling. The system security may be compromised. | ||
Recommended Action | Replace the chassis intrusion sensor. For more information, contact your service provider. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | Write-cache is enabled on the PCIe solid state drive (SSD) identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | Write-cache is disabled on the PCIe solid state drive (SSD) identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The PCIe solid state drive (SSD) identified in the message is ready for removal. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The log file of the PCIe solid state drive (SSD) identified in the message is successfully exported. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The initialization of the PCIe solid state drive (SSD) identified in the message is complete. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The PCIe solid state device identified in the message is approaching the warranted wear-out limit. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The solid state device identified in the message has either reached or exceeded the warranted wear-out limit. | ||
Recommended Action | Back up the data on the device, and contact your service provider for further instructions. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The PCIe solid state device identified in the message is between 90% and 100% of reaching read-only mode. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The PCIe solid state device identified in the message is in read-only mode. | ||
Recommended Action | Back up the data on the device, and contact your service provider for further instructions. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The PCIe solid state device identified in the message is in a locked state, because an existing initialization task was interrupted due to a power failure or disk removal. | ||
Recommended Action | Run Full Initialize operation on the device identified in the message. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The Remaining Rated Write Endurance (RRWE) Threshold for PCIe solid state devices has been modified. A warning alert is generated when the RRWE for any PCIeSSD device falls below the user set RRWE Threshold value. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The Remaining Rated Write Endurance (RRWE) Threshold for SAS and SATA solid state devices has been modified. A warning alert when the RRWE for any SAS or SATA SSD falls below the threshold set by the user. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The Available Spare Warning threshold for PCIe solid state drives (SSDs) is set to the value identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The Available Spare value of PCI solid state drive (SSDs) is less than the Warning threshold value. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The available spare critical threshold value of PCIe Solid State Drives (SSDs) is set to the value identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The available spare critical threshold value of PCIe Solid State Drives (SSDs) is less than the critical threshold value. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The available spare critical threshold value of PCIe Solid State Drives (SSDs) has reached zero. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | Installing Storage Services and Array Manager on the same system is not a supported configuration. Storage Services is not installed on a system where Array Manager is installed. | ||
Recommended Action | Uninstall either Storage Services or Array Manager and retry the operation. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Unable to determine whether the system has the minimum required versions of the RAID controller drivers. | ||
Recommended Action | See the Readme file on the installation media for driver and firmware requirements. If Storage Services experiences performance problems, make sure that minimum supported versions of the drivers and firmware are installed. For a list of correct driver and firmware versions, contact the service provider. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | Storage Services is unable to determine whether the system has the minimum required versions of the RAID controller firmware and drivers because a configuration file is not readable, corrupted, or has missing data. | ||
Recommended Action | Reinstall Server Administrator and Storage Services. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The version of the operating system kernel and the driver do not meet the minimum requirements. Storage Services may not be able to display or perform storage management functions until the system meets the minimum requirements. | ||
Recommended Action | See the Readme file on the installation media for operating system kernel and driver version requirements. Update the system to meet the minimum requirements and then reinstall Storage Services. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The driver version does not meet the minimum requirements and Storage Services cannot perform the required operations until the minimum requirements are met. | ||
Recommended Action | See the Readme file for the driver requirements and update the system to meet the minimum requirements and reinstall Storage Services. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A rescan of all storage components in the system is initiated. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The storage shutdown feature based on high ambient temperature (smart thermal shutdown) is enabled. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The storage shutdown feature based on high ambient temperature (smart thermal shutdown) is disabled. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A new protection policy is created or an existing protection policy is modified. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The initialization sequence of SAS components did not complete during system startup. | ||
Recommended Action | Do the following: 1) Make sure that the supported versions of the SAS drivers and firmware are installed. 2) Reboot the system. If problem persists, reinstall Server Administrator and Storage Services on the managed node to make sure all the required components are installed. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A SCSI device may have experienced an error that generated sense data after the device recovery. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The device identified in the message that was previously in an error state has returned to a normal state. For example, if an enclosure became too hot and subsequently cooled down, or if a degraded virtual disk returns to normal state. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The device (physical disk or an enclosure) identified in the message has failed. The device (physical disk or an enclosure) failure was detected while performing a rescan. However, physical disk failures are also detected during a check consistency operation. | ||
Recommended Action | Replace the identified device. A failed device is indicated with a red color "X" status icon. Perform a rescan after replacing the failed device. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller cannot communicate with a device. The state of the device cannot be determined. There may be a bad or loose cable, or a missing device, or a problem with the driver or firmware. | ||
Recommended Action | See the storage hardware documentation for information on checking the cables. Check for problems with any enclosures attached to the system. Verify that the controller has a supported version of the driver and firmware. Rebooting the system may resolve this problem. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | A virtual disk or enclosure has lost data redundancy. In the case of a virtual disk, one or more physical disks included in the virtual disk have failed. Due to the failed physical disk or disks, the virtual disk is no longer maintaining redundant (mirrored or parity) data. The failure of an additional physical disk will result in lost data. In the case of an enclosure, more than one enclosure component has failed. For example, the enclosure may have suffered the loss of all fans or all power supplies. | ||
Recommended Action | Identify and replace the failed components. To identify the failed component, select the Storage object and click the Health subtab. The controller status displayed on the Health subtab indicates whether a controller has a failed or degraded component. Click the controller that displays a Warning or Failed status. This action displays the controller Health subtab which displays the status of the individual controller components. Continue clicking the components with a Warning or Failed status until you identify the failed component. See Storage Health for more information. See the enclosure documentation for information on replacing enclosure components and for other diagnostic information. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | The Server Administrator Data Manager service has started. | ||
Recommended Action | No response action is required. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | The Server Administrator Data manager service has stopped. | ||
Recommended Action | Restart the Server Administrator Data Manager service. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | The Server Administrator has started. | ||
Recommended Action | No response action is required. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | The Server Administrator is starting. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The current software version is unable to process this event because of an internal error. | ||
Recommended Action | Contact your service provider. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | An unknown system control action was initiated by the user. | ||
Recommended Action | No response action is required. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | The user initiated a system reboot. | ||
Recommended Action | No response action is required. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | The user has initiated a system power off action. | ||
Recommended Action | No response action is required. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | The user has initiated a system power cycle action. | ||
Recommended Action | No response action is required. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | The actions will shut down the operating system and then reboot the system. | ||
Recommended Action | No response action is required. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | The actions will shut down the operating system and then the system. | ||
Recommended Action | No response action is required. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | The actions will shut down the operating system and then power cycle the system. | ||
Recommended Action | No response action is required. | ||
Type | Audit | ||
Severity | Informational | ||
Detailed Description | An invalid action was requested by the user. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | IPMI is supported for identified interface, Baseboard Management Controller (BMC), Sensor Data Records (SDR), and System Event Log (SEL). | ||
Recommended Action | If any status is not present, power cycle the system, and apply the latest firmware update packages for Lifecycle Controller and iDRAC. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The power cord sensor becomes non-functional because of one of the following reasons: 1) The power cable may not be connected properly or disconnected. 2) The power cord sensor in the power supply unit has failed. However, the power supply unit may still function. 3) There is an input power failure. | ||
Recommended Action | Do of the following to resolve the issue: 1) Reconnect the power cord to the power supply unit. 2) Replace the power supply unit that has the failed power cord sensor, with a new power supply unit. 3) Make sure that the input power supply is restored. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The status of the power cord cannot be determined because of one of the following reasons: 1) The power cable may not be connected properly or disconnected. 2) The power cord sensor in the power supply unit has failed. However, the power supply unit may still function. 3) There is an input power failure. | ||
Recommended Action | Do of the following to resolve the issue: 1) Reconnect the power cord to the power supply unit. 2) Replace the power supply unit that has the failed power cord sensor, with a new power supply unit. 3) Make sure that the input power supply is restored. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | The input power supply is restored to the system. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The input power supply is not available because of one of the following reasons: 1) The power cable may not be connected properly or disconnected. 2) There is an input power failure. | ||
Recommended Action | Do of the following to resolve the issue: 1) Reconnect the power cord to the power supply unit. 2) Make sure that the input power supply is restored. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | An event is logged in the IPMI System Event Log (SEL) for a sensor not specifically monitored by Open Manage Server Administrator (OMSA). For more information about the error message ID identified in the message, see the Event and Error Message Reference Guide available on the support site. | ||
Recommended Action | For more information about the error message ID identified in the message, see the Event and Error Message Reference Guide for Servers available on the support site. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | An event is logged in the IPMI System Event Log (SEL) for a sensor not specifically monitored by Open Manage Server Administrator (OMSA). For more information about the error message ID identified in the message, see the Event and Error Message Reference Guide available on the support site. | ||
Recommended Action | For more information about the error message ID identified in the message, see the Event and Error Message Reference Guide for Servers available on the support site. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | A critical event is logged in the IPMI System Event Log (SEL) for a sensor not specifically monitored by Open Manage Server Administrator (OMSA). For more information about the error message ID identified in the message, see the Event and Error Message Reference Guide available on the support site. | ||
Recommended Action | For more information about the error message ID identified in the message, see the Event and Error Message Reference Guide for Servers available on the support site. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The enclosure is too hot. A variety of factors can cause the excessive temperature. For example, a fan may have failed, the thermostat may be set too high, or the room temperature may be too hot. | ||
Recommended Action | Check for factors that may cause overheating. For example, verify that the enclosure fan is working. You should 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. Refer to the enclosure documentation for more diagnostic information. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The enclosure is too cold. | ||
Recommended Action | Check whether the thermostat setting is too low and whether the room temperature is too cool. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The enclosure is too hot. A variety of factors can cause the excessive temperature. For example, a fan may have failed, the thermostat may be set too high, or the room temperature may be too hot. | ||
Recommended Action | Check for factors that may cause overheating. 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. Refer to the enclosure documentation for more diagnostic information. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The enclosure is too cold. | ||
Recommended Action | Check whether the thermostat setting is too low and whether the room temperature is too cool. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | You have changed the value for the maximum temperature probe warning threshold. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | A temperature sensor identified in the message has failed. This condition can cause system performance issues and degradation in the monitoring capability of the system. | ||
Recommended Action | Verify the Embedded System Management (ESM) Log for any sensor related faults. If there is a failed sensor, replace the system board. For more information, contact your service provider. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | A temperature sensor identified in the message has failed. This condition can cause system performance issues and degradation in the monitoring capability of the system. | ||
Recommended Action | Verify the Embedded System Management (ESM) Log for any sensor related faults. If there is a failed sensor, replace the system board. For more information, contact your service provider. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | The sensor identified in the message has returned to a normal state. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The temperature sensor identified in the message is faulty, or the temperature exceeds the warning threshold. This condition can cause system performance issues and degradation in the monitoring capability of the system. | ||
Recommended Action | Verify the Embedded System Management (ESM) Log for any sensor related faults. If there is a failed sensor, replace the system board. For more information, contact your service provider. Otherwise, change the warning threshold for the temperature sensor (if applicable) such that it corresponds to the hardware configuration. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The temperature sensor identified in the message is faulty, or the temperature exceeds the critical threshold. This condition can cause system performance issues and degradation in the monitoring capability of the system. | ||
Recommended Action | Review system power policy, check system logs for temperature related failures. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The temperature sensor identified in the message has failed. | ||
Recommended Action | Verify the Embedded System Management (ESM) Log for any sensor related faults. If there is a failed sensor, replace the system board. For more information, contact your service provider. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | You have changed the value for the minimum temperature probe warning threshold. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The virtual disk identified in message cannot be used because of missing features on the current controller. The features may be missing because they are not available in the firmware version on the controller or the necessary licenses are not installed. | ||
Recommended Action | Update the controller firmware and license to match the peer controller. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The number of hot spares available for the virtual disks identified in the message are not compliant with Hot Spare Protection policy, whose severity is set at Warning level. | ||
Recommended Action | Make appropriate assignments of hotspares to meet the policy. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The number of hot spares available for the virtual disks identified in the message are not compliant with Hot Spare Protection policy, whose severity is set at Critical level. | ||
Recommended Action | Make appropriate assignments of hotspares to meet the policy. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The secure virtual disk operation was successful on the security capable virtual disk identified in the message. A security capable virtual disk is created using only Self-Encrypting Drives (SED). | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Virtual Disk creation using power save mode drives successfully completed and the Virtual Disk identified in the message is ready for use. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is generated after successfully configuring a virtual disk on at least one spundown drive. The virtual disk creation is not yet complete on the remaining spundown drives because the drives are still spinning up. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The Controller Enhanced cache identified in the message was successfully resized. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The Controller Enhanced cache identified in the message was successfully created. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The Controller Enhanced cache identified in the message was successfully deleted. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This message is generated after initialization of a virtual disk starts. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | This alert is generated when an unrecoverable storage medium error is detected on the virtual disk. This error can be a prelude to the physical disk becoming non-functional. | ||
Recommended Action | Make sure a hot spare to the Virtual Disk identified in the message is available and back up the data on the virtual disk. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The controller corrected a disk storage medium error on one of the participating physical disks of the virtual disk identified in the message. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller removed a virtual disk because of a delete virtual disk operation or a reset configuration operation. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The number of hot spares available for the virtual disks identified in the message are not compliant with Hot Spare Protection policy, whose severity is set at Informational level. | ||
Recommended Action | Make appropriate assignments of hotspares to meet the policy. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This message is generated after reconfiguration of a virtual disk starts. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The rebuild operation on the virtual drive (VD) identified in the message is abruptly stopped. | ||
Recommended Action | Replace the physical drive associated with the virtual drive and retry the operation. For information about replacing a physical drive, see the server's Installation and Service Manual available on the support site. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The encryption operation on the virtual drive (VD) identified in the message is abruptly stopped. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A user cancelled the consistency check operation for a virtual disk. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The initialization operation could not be completed. This may be due to a user action or a physical disk failure. | ||
Recommended Action | If a physical disk failed, then replace the physical disk. Restart the virtual disk initialization. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | A physical disk included in the virtual disk failed or there is an error in the parity information. A failed physical disk causes errors in parity information. | ||
Recommended Action | Check that all the physical disks of the virtual disk are in a healthy condition. Replace any disks that are not healthy and restart the operation. If this is not the problem, delete the virtual disk and restore the data to the disk from a backup copy. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | A physical disk included in the virtual disk failed. | ||
Recommended Action | Replace the failed physical disk. Identify the failed physical disk by locating the disk that has a red "X" for its status. Rebuild the physical disk. When finished, restart the virtual disk format operation. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | A physical disk included in the virtual disk has failed or was removed. | ||
Recommended Action | If a physical disk has failed, replace the physical disk. Restart the virtual disk initialization. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The reconfiguration operation was not completed. This may be due to a user action or a physical disk failure. | ||
Recommended Action | Recreate the virtual disk and restore data from a backup copy. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | A physical disk included in the virtual disk has failed or is corrupt. You may also have cancelled the rebuild. | ||
Recommended Action | Replace the failed or corrupt disk. You can identify a disk that has failed by locating the disk that has a red "X" for its status. Restart the virtual disk rebuild. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This message is generated after a consistency check completes on a virtual disk. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This message is generated after initialization completes on a virtual disk. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The re-configuration operation on the virtual disk completed. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | You paused the Check Consistency operation on a virtual disk. | ||
Recommended Action | To resume the Check Consistency operation, right-click the virtual disk in the Storage Management tree view and select Resume Check Consistency. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The check consistency on a virtual disk has resumed processing after a pause. | ||
Recommended Action | This alert is provided for informational purposes. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A user has caused a mirrored virtual disk to be split. When a virtual disk is mirrored, its data is copied to another virtual disk to maintain redundancy. After being split, both virtual disks retain a copy of the data. Because the mirror is no longer intact, updates to the data are no longer copied to the mirror. | ||
Recommended Action | This alert is provided for informational purposes. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A mirrored virtual disk is un-mirrored. When a virtual disk is mirrored, its data is copied to another virtual disk to maintain redundancy. After being un-mirrored, the disk formerly used as the mirror returns to being a physical disk and becomes available for inclusion in another virtual disk. | ||
Recommended Action | This alert is provided for informational purposes. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A user changed the write policy for a virtual disk. | ||
Recommended Action | This alert is provided for informational purposes. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The controller is getting disconnected from its virtual disk, while Input Output (IO) is in-progress. | ||
Recommended Action | Try importing foreign disks, if any. Check if the enclosure containing the Virtual Disk is disconnected from the controller. Insert any disks that are reported missing or failed. If the enclosure or disks were removed intentionally, the preserved cache can be discarded. See storage hardware documentation for more information on performing these steps. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Background initialization of a virtual disk has started. This is an automated process that writes the parity or mirror data on newly created virtual disks. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Background initialization of a virtual disk was cancelled. This may be due to user action. This operation may automatically restart. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | Background initialization of a virtual disk failed. | ||
Recommended Action | Run a consistency check on the virtual disk. If that fails, check the health of the member drives of the virtual disk and then recreate. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Background initialization of a virtual disk completed. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | Disk space that was formerly "dead" or inaccessible to a redundant virtual disk has been restored. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A user renamed a virtual disk. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The virtual disk check consistency has identified issues and made corrections. For example, the check consistency may have encountered a bad disk block and remapped the disk block to restore data consistency. This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. As a precaution, monitor the Log for other errors related to this virtual disk. If problems persist, contact technical support. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This message is generated after a virtual disk was created on a controller. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This message is generated after the reconfiguration of a virtual disk resumes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A disk media error was detected while the controller was completing a background task. A bad disk block was identified. The disk block was remapped. | ||
Recommended Action | Check the Lifecycle log for information related to members of this virtual disk. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. The virtual disk has inconsistent data. This may be caused when a power loss or system shutdown occurs while data is being written to the virtual disk. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | A redundant virtual disk has lost redundancy. This may occur when the virtual disk suffers the failure of more than one physical disk. In this case, both the source physical disk and the target disk with redundant data have failed. A rebuild is not possible because there is no longer redundancy. | ||
Recommended Action | Replace the failed disks and restore from backup. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The controller removed a virtual disk. This is due to a delete virtual disk operation, a reset configuration operation, or the removal of every physical disk that was a member of the virtual disk. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The background initialization task encountered errors that cannot be corrected. The virtual disk contains physical disks that have unusable disk space or disk errors that cannot be corrected. | ||
Recommended Action | Review other messages to identify whether the physical disk that has errors. If the virtual disk is redundant, you can replace the physical disk and continue using the virtual disk. If the virtual disk is non-redundant, you need to recreate the virtual disk after replacing the physical disk. After replacing the physical disk, run a consistency check to verify the data. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The consistency check completed on the virtual disk after making corrections. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The data on physical disk members of the virtual disk does not match. Redundancy may be lost. | ||
Recommended Action | Rerun the consistency check task. If you receive this message again, verify the health of the physical disks included in the virtual disk. See the storage hardware documentation for more information. Review messages for significant messages related to the physical disks. If a physical disk has a problem, replace it and restore from a backup copy. Contact technical support if the issue persists. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The consistency check can no longer report errors in the parity data. | ||
Recommended Action | See the storage hardware documentation for more information on consistency check operation. Contact technical support. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | You have cancelled the virtual disk initialization. | ||
Recommended Action | Restart the initialization. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | The controller cannot communicate with attached devices. A disk may be removed or contain errors. Cables may also be loose or defective. | ||
Recommended Action | Verify the health of attached devices. Review the Alert Log for significant events. Make sure the cables are attached securely. See the Cables Attached Correctly section for more information on checking the cables. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | Virtual disk bad blocks are due to presence of unrecoverable bad blocks on one or more member physical disks. | ||
Recommended Action | Recovering a physical disk bad block depends on the RAID level and state of the virtual disk. If a virtual disk is redundant, the controller can recover a bad block on a physical disk. If a virtual disk is not redundant, then the physical disk bad block results in a virtual disk bad block. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This alert is provided for informational purposes. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | One or more physical disks included in the virtual disk have failed. If the virtual disk is non-redundant (does not use mirrored or parity data), then the failure of a single physical disk can cause the virtual disk to fail. If the virtual disk is redundant, then more physical disks have failed than you can rebuild using mirrored or parity information. | ||
Recommended Action | Create a new virtual disk and restore from a backup. | ||
Type | Storage | ||
Severity | Warning | ||
Detailed Description | The virtual drive on the Controller identified in the message is degraded either because the physical disk drive in the drive group is removed or the physical disk drive added in a redundant virtual drive has failed. | ||
Recommended Action | Do the following and retry the operation: 1) Insert a physical disk drive. After the drive is inserted, the previous data is automatically rebuilt by the system. 2) If not already done, configure a hot-spare for the virtual drive. 3) If a physical disk drive is removed from the disk drive group, either replace the disk or restore the original disk drive. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | A consistency check operation on a virtual disk has started. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | This message occurs if there are medium errors in the physical drives. | ||
Recommended Action | Replace the failed drives. | ||
Type | Storage | ||
Severity | Critical | ||
Detailed Description | This message occurs if there are medium errors in the physical drives. | ||
Recommended Action | Replace the failed drives. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The bad block table(s) is cleared because the virtual drive is initialized. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | This message occurs if the controller pinned cache is recovered. | ||
Recommended Action | No response action is required. | ||
Type | Storage | ||
Severity | Informational | ||
Detailed Description | The Patrol Read task has encountered an error such as a bad disk block and remapped data to correct the error. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | A voltage sensor identified in the message may have failed. This condition can cause system performance issues and degradation in the monitoring capability of the system. | ||
Recommended Action | Do one of the following to resolve the issue: 1) Verify the Embedded System Management (ESM) Log for any sensor related faults. If there is a failed sensor, replace the system board. 2) Re-configure the system to a minimum configuration, and verify if the sensor displays a normal value, otherwise replace the system board. 3) If the sensor identified is a processor voltage sensor, remove the processor module and inspect processor socket, and replace if required. If the issue persists, contact your service provider. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | A voltage sensor identified in the message may have failed. This condition can cause system performance issues and degradation in the monitoring capability of the system. | ||
Recommended Action | Do one of the following to resolve the issue: 1) Verify the Embedded System Management (ESM) Log for any sensor related faults. If there is a failed sensor, replace the system board. 2) Re-configure the system to a minimum configuration, and verify if the sensor displays a normal value, otherwise replace the system board. 3) If the sensor identified is a processor voltage sensor, remove the processor module and inspect processor socket, and replace if required. If the issue persists, contact your service provider. | ||
Type | System Health | ||
Severity | Informational | ||
Detailed Description | The voltage sensor identified in the message has returned to a normal state. | ||
Recommended Action | No response action is required. | ||
Type | System Health | ||
Severity | Warning | ||
Detailed Description | The voltage sensor identified in the message is faulty, or the voltage exceeds the preset warning threshold. This condition can cause system performance issues and degradation in the monitoring capability of the system. | ||
Recommended Action | Do one of the following to resolve the issue: 1) Verify the Embedded System Management (ESM) Log for any sensor related faults. If there is a failed sensor, replace the system board. 2) Re-configure the system to a minimum configuration, and verify if the sensor displays a normal value, otherwise replace the system board. 3) If the sensor identified is a processor voltage sensor, remove the processor module and inspect processor socket, and replace if required. If the issue persists, contact your service provider. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | The voltage sensor identified in the message is faulty, or the voltage exceeds the preset critical threshold. This condition can cause system performance issues and degradation in the monitoring capability of the system. | ||
Recommended Action | Do one of the following to resolve the issue: 1) Verify the Embedded System Management (ESM) Log for any sensor related faults. If there is a failed sensor, replace the system board. 2) Re-configure the system to a minimum configuration, and verify if the sensor displays a normal value, otherwise replace the system board. 3) If the sensor identified is a processor voltage sensor, remove the processor module and inspect processor socket, and replace if required. If the issue persists, contact your service provider. | ||
Type | System Health | ||
Severity | Critical | ||
Detailed Description | A voltage sensor identified in the message may have failed. This condition can cause system performance issues and degradation in the monitoring capability of the system. | ||
Recommended Action | Do one of the following to resolve the issue: 1) Verify the Embedded System Management (ESM) Log for any sensor related faults. If there is a failed sensor, replace the system board. 2) Re-configure the system to a minimum configuration, and verify if the sensor displays a normal value, otherwise replace the system board. 3) If the sensor identified is a processor voltage sensor, remove the processor module and inspect processor socket, and replace if required. If the issue persists, contact your service provider. | ||