Storage Management's alert or event management features let you monitor the health of storage resources such as controllers, channels, array disks, and virtual disks.
The Storage Management Service performs alert monitoring and logging. By default, the Storage Management Service starts when the managed system starts up. If you stop the Disk Management Service, then alert monitoring and logging stops. Alert monitoring does the following:
Storage Management generates alerts that are added to the Windows application alert log and to the Server Administrator Alert log. To view these alerts in Server Administrator:
Each alert message in the Storage Management alert log has a severity level. The severity level is displayed in the Severity field of the alert message. The severity level indicates the nature of the alert.
By default, Storage Management installs SNMP trap forwarding support. For this support to function, you should have SNMP installed on the managed system prior to installing Storage Management.
The Storage Management alerts are displayed in the Server Administrator alert log and are forwarded to the Windows application alert log. If you have SNMP installed on the managed system (and the SNMP service is running), the Storage Management alerts in the Windows application alert log will be forwarded as SNMP traps. In order for these traps to be viewable, however, a target system or application must be configured to receive these traps. SNMP traps that are generated by Storage Management can be viewed in any standard SNMP-compatible enterprise management console.
The Windows SNMP service must be configured to forward the SNMP traps to the target system or application. When forwarding to an application, the application should also be configured to receive the SNMP traps. The IT Assistant application is already configured to receive the SNMP traps generated by Storage Management.
See your Windows operating system documentation for information on configuring the operating system to forward SNMP traps. This information may be located under such topics as "setting up SNMP" or "SNMP traps." When configuring SNMP for Windows, be sure that the SNMP traps are forwarded to the correct server. For information on configuring an application to receive SNMP traps, see the documentation for that application.
The Storage Management management information base (MIB) defines the SNMP traps that Storage Management generates. These traps correspond to the alerts documented in the "Alert Descriptions and Corrective Actions" section. The MIB is located in ..\sm\mibs\dcstorag.mib, a subdirectory of the Storage Management installation directory.
The Storage Management SNMP traps use a set of variables that are included with every trap. These variables are the following:
SNMP traps that are generated by Storage Management can be viewed in any standard SNMP-compatible enterprise management console. These traps are defined in the Storage Management MIB. These traps correspond to the alerts documented in the "Alert Descriptions and Corrective Actions" section. For more information on the MIB and its structure, as well as a change history of the SNMP traps, see the "Introduction" section. For more information on configuring SNMP, see "SNMP Support for Storage Management Alerts."
The following sections describe alerts generated by the Redundant Array of Independent disks (RAID) or Small Computer System Interface (SCSI) controllers supported by Storage Management. The alerts are displayed in the Server Administrator Alert subtab or through Windows Event Viewer. These alerts can also be forwarded as SNMP traps to other applications.
SNMP traps are generated for the alerts listed in the following sections. These traps are included in the Storage Management MIB. The SNMP traps for these alerts use all of the SNMP trap variables. For more information on SNMP support and the MIB, see "SNMP Support for Storage Management Alerts."
To locate an alert, scroll through the following table to find the alert number displayed on the Server Administrator Alert tab or search this HTML file for the alert message text or number. See "Alert Severity Levels" for more information on severity levels.
For more information regarding alert descriptions and the appropriate corrective actions, see the online help.
|
Event
ID
|
Description
|
Severity
|
Cause and Action
|
SNMP Trap Numbers
|
Array Manager Event Number
|
|---|
2048
| Device failed
| Critical / Failure / Error
| Cause: A storage component such as an array disk or an enclosure has failed. The failed component may have been identified by the controller while performing a task such as a rescan or a check consistency.
Action: Replace the failed component. You can identify which component has failed by locating the component that has a red "X" for its status. Perform a rescan after replacing the failed component.
| 754, 804, 854, 904, 954, 1004, 1054, 1104, 1154, 1204
| 500
|
2049
| Array disk removed
| Warning / Non-critical
| Cause: A physical disk has been removed from the array. A user may have also executed the "Prepare to Remove" task. This alert can also be caused by loose or defective cables or by problems with the enclosure.
Action: If a physical disk was removed from the array, either replace the disk or restore the original disk. You can identify which disk has been removed by locating the disk that has a red "X" for its status. Perform a rescan after replacing or restoring the disk. If a disk has not been removed from the array, then check for problems with the cables. See the online help for more information on checking the cables. Make sure that the enclosure is powered on. If the problem persists, check the enclosure documentation for further diagnostic information.
| 903
| 501
|
2050
| Array disk offline
| Warning / Non-critical
| Cause: A physical disk in the array is offline. A disk can be made offline during a Prepare to Remove operation or because a user manually put the disk offline.
Action: Perform a rescan. You can also select the offline disk and perform a Make Online operation.
| 903
| 502
|
2051
| Array disk is degraded
| Warning / Non-critical
| Cause: An array disk has reported an error condition and may be degraded. The array disk may have reported the error condition in response to a consistency check or other operation.
Action: Replace the degraded array disk. You can identify which disk is degraded by locating the disk that has a red "X" for its status. Perform a rescan after replacing the disk.
| 903
| 503
|
2052
| Array disk inserted
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| 504
|
2053
| Virtual disk created
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| 505
|
2054
| Virtual disk deleted
| Warning / Non-critical
| Cause: A virtual disk has been deleted. "Performing a Reset Configuration" may detect that a virtual disk has been deleted and generate this alert.
Action: None.
| 1203
| 506
|
2055
| Virtual disk configuration changed
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| 507
|
2056
| Virtual disk failed
| Critical / Failure / Error
| Cause: 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 can be rebuilt using mirrored or parity information.
Action: Create a new virtual disk and restore from a backup.
| 1204
| 508
|
2057
| Virtual disk degraded
| Warning / Non-critical
| Cause 1: This alert message occurs when a physical disk included in a redundant virtual disk fails. Because the virtual disk is redundant (uses mirrored or parity information) and only one physical disk has failed, the virtual disk can be rebuilt.
Action 1: Configure a hot spare for the virtual disk if one is not already configured. Rebuild the virtual disk. When using a PowerEdge RAID Controller (PERC) 2/SC, 3/SC, 2/DC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 5/E or CERC ATA100/4ch controller, rebuild the virtual disk by first configuring a hot spare for the disk, and then initiating a write operation to the disk. The write operation will initiate a rebuild of the disk.
Cause 2: A physical disk in the array has been removed.
Action 2: If a physical disk was removed from the array, either replace the disk or restore the original disk. You can identify which disk has been removed by locating the disk that has a red "X" for its status. Perform a rescan after replacing the disk.
| 1203
| 509
|
2058
| Virtual disk check consistency started
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| 520
|
2059
| Virtual disk format started
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| 521
|
2061
| Virtual disk initialization started
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| 523
|
2063
| Virtual disk reconfiguration started
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| 525
|
2064
| Virtual disk rebuild started
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| 526
|
2065
| Array disk rebuild started
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| 527
|
2067
| Virtual disk check consistency cancelled
| OK/Normal/ Informational
| Cause: The check consistency operation cancelled because a physical disk in the array has failed or because a user cancelled the check consistency operation.
Action: If the physical disk failed, then replace the physical disk. You can identify which disk failed by locating the disk that has a red "X" for its status. Perform a rescan after replacing the disk. When performing a consistency check, be aware that the consistency check can take a long time. The time it takes depends on the size of the physical disk or the virtual disk.
| 1201
| 529
|
2070
| Virtual disk initialization cancelled
| OK/Normal/ Informational
| Cause: The virtual disk initialization cancelled because a physical disk included in the virtual disk has failed or because a user cancelled the virtual disk initialization.
Action: If a physical disk failed, then replace the physical disk. You can identify which disk has failed by locating the disk that has a red "X" for its status. Perform a rescan after replacing the disk. Restart the format array disk operation. Restart the virtual disk initialization.
| 1201
| 532
|
2074
| Array Disk rebuild cancelled
| OK/Normal/ Informational
| Cause: A user has cancelled the rebuild operation.
Action: Restart the rebuild operation.
| 901
| 536
|
2076
| Virtual disk check consistency failed
| Critical / Failure / Error
| Cause: An array disk included in the virtual disk failed or there is an error in the parity information. A failed array disk can cause errors in parity information.
Action: Replace the failed array disk. You can identify which disk has failed by locating the disk that has a red "X" for its status. Rebuild the array disk. When finished, restart the check consistency operation.
| 1204
| 538
|
2077
| Virtual disk format failed
| Critical / Failure / Error
| Cause: An array disk included in the virtual disk failed.
Action: Replace the array disk. You can identify which array disk has failed by locating the disk that has a red "X" for its status. Rebuild the array disk. When finished, restart the virtual disk format operation.
| 1204
| 539
|
2079
| Virtual disk initialization failed
| Critical / Failure / Error
| Cause: An array disk included in the virtual disk has failed or a user has cancelled the initialization.
Action: If an array disk has failed, then replace the array disk.
| 1204
| 541
|
2080
| Array disk initialize failed
| Critical / Failure / Error
| Cause: The array disk has failed or is corrupt.
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 initialization.
| 904
| 542
|
2081
| Virtual disk reconfiguration failed
| Critical / Failure / Error
| Cause: An array disk included in the virtual disk has failed or is corrupt. A user may also have cancelled the reconfiguration.
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. If the array disk is part of a redundant array, then rebuild the array disk. When finished, restart the reconfiguration.
| 1204
| 543
|
2082
| Virtual disk rebuild failed
| Critical / Failure / Error
| Cause: An array disk included in the virtual disk has failed or is corrupt. A user may also have cancelled the rebuild.
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.
| 1204
| 544
|
2083
| Array disk rebuild failed
| Critical / Failure / Error
| Cause: An array disk included in the virtual disk has failed or is corrupt. A user may also have cancelled the rebuild.
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. Rebuild the virtual disk rebuild.
| 904
| 545
|
2085
| Virtual disk check consistency completed
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| 547
|
2086
| Virtual disk format completed
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| 548
|
2088
| Virtual disk initialization completed
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| 550
|
2089
| Array disk initialize completed
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| 551
|
2090
| Virtual disk reconfiguration completed
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| 552
|
2091
| Virtual disk rebuild completed
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| 553
|
2092
| Array disk rebuild completed
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| 554
|
2094
| Predictive Failure reported. If this disk is part of a redundant virtual disk, select the `Offline' option and then replace the disk. Then configure a hot spare and it will start the rebuild automatically. If this disk is a hot spare, select the `Prepare to Remove' option and then replace the disk. If this disk is part of a non-redundant disk, you should back up your data immediately. If the disk fails, you will not be able to recover the data.
| Warning / Non-critical
| Cause: The array disk is predicted to fail. Many array disks contain Self Monitoring Analysis and Reporting Technology (S.M.A.R.T.). When enabled, SMART monitors the health of the disk based on indications such as the number of write operations that have been performed on the disk.
Action: Replace the array disk. Even though the disk may not have failed yet, it is strongly recommended that you replace the disk. Review the message text for additional information.
| 903
| 570
|
2095
| SCSI sense data. If this disk is part of a redundant virtual disk, select the `Offline' option and then replace the disk. Then configure a hot spare and it will start the rebuild automatically. If this disk is a hot spare, select the `Prepare to Remove' option and then replace the disk. If this disk is part of a non-redundant disk, you should back up your data immediately. If the disk fails, you will not be able to recover the data.
| Warning / Non-critical
| Cause: An array disk has failed, is corrupt, or is otherwise experiencing a problem.
Action: Replace the array disk. Even though the disk may not have failed yet, it is strongly recommended that you replace the disk. Review the message text for additional information.
| 903
| 571
|
2098
| Global hot spare assigned
| OK/Normal/ Informational
| Cause: A user has assigned an array disk as a global hot spare. This alert is provided for informational purposes.
Action: None.
| 901
| 574
|
2099
| Global hot spare unassigned
| OK/Normal/ Informational
| Cause: An array disk that was assigned as a hot spare has been unassigned and is no longer functioning as a hot spare. The array disk may have been 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. You need to assign a new hot spare to maintain data protection in this situation.
On the PERC 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and Cost Effective Raid Controller (CERC) Serial Advanced Technology Attachment (SATA)1.5/2s controllers, if you use another application such as the Basic Input/Output System (BIOS) to include a hot spare in a virtual disk, then Storage Management unassigns the array disk as a hot spare.
Action: Although this alert is provided for informational purposes, you may need to assign a new hot spare to the virtual disk.
| 901
| 575
|
2100
| Temperature exceeded the maximum warning threshold
| Warning / Non-critical
| Cause: The array disk 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.
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. See the enclosure documentation for more diagnostic information.
| 1053
| 591
|
2101
| Temperature dropped below the minimum warning threshold
| Warning / Non-critical
| Cause: The array disk enclosure is too cool.
Action: Check whether the thermostat setting is too low and whether the room temperature is too cool.
| 1053
| 592
|
2102
| Temperature exceeded the maximum failure threshold
| Critical / Failure / Error
| Cause: The array disk 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.
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. See the enclosure documentation for more diagnostic information.
| 1054
| 593
|
2103
| Temperature dropped below the minimum failure threshold
| Critical / Failure / Error
| Cause: The array disk enclosure is too cool.
Action: Check whether the thermostat setting is too low and whether the room temperature is too cool.
| 1054
| 594
|
2104
| Controller battery is reconditioning
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1151
| 581
|
2105
| Controller battery recondition is completed
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1151
| 582
|
2106
| Smart FPT exceeded
| Warning / Non-critical
| Cause: 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.
Action: Replace the disk that has received the SMART alert. If the array disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk. Removing an array disk that is included in a non-redundant virtual disk will cause the virtual disk to fail and may cause data loss.
| 903
| 585
|
2107
| Smart configuration change
| Critical / Failure / Error
| Cause: A disk has received a SMART alert (predictive failure) after a configuration change. The disk is likely to fail in the near future.
Action: Replace the disk that has received the SMART alert. If the array disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk. Removing an array disk that is included in a non-redundant virtual disk will cause the virtual disk to fail and may cause data loss
| 904
| 586
|
2108
| Smart warning
| Warning / Non-critical
| Cause: A disk has received a SMART alert (predictive failure). The disk is likely to fail in the near future.
Action: Replace the disk that has received the SMART alert. If the array disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk. Removing an array disk that is included in a non-redundant virtual disk will cause the virtual disk to fail and may cause data loss.
| 903
| 587
|
2109
| Smart warning temperature
| Warning / Non-critical
| Cause: A disk has reached an unacceptable temperature and received a SMART alert (predictive failure). The disk is likely to fail in the near future.
First Action: Determine why the array disk has reached an unacceptable temperature. 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 or cold. Verify that the fans in the server or enclosure are working. If the array disk is in an enclosure, 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. See the enclosure documentation for more diagnostic information.
| 903
| 588
|
|
|
| Second Action: If you cannot identify why the disk has reached an unacceptable temperature, then replace the disk. If the array disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk. Removing an array disk that is included in a non-redundant virtual disk will cause the virtual disk to fail and may cause data loss.
|
|
|
2110
| Smart warning degraded
| Warning / Non-critical
| Cause: A disk is degraded and has received a SMART alert (predictive failure). The disk is likely to fail in the near future.
Action: Replace the disk that has received the SMART alert. If the array disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk. Removing an array disk that is included in a non-redundant virtual disk will cause the virtual disk to fail and may cause data loss.
| 903
| 589
|
2111
| Failure prediction threshold exceeded due to test - No action needed
| Warning / Non-critical
| Cause: A disk has received a SMART alert (predictive failure) due to test conditions.
Action: None.
| 903
| 590
|
2112
| Enclosure was shut down
| Critical / Failure / Error
| Cause: The array disk enclosure is either hotter or cooler than the maximum or minimum allowable temperature range.
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. See the enclosure documentation for more diagnostic information.
| 854
| 602
|
2114
| A consistency check on a virtual disk has been paused (suspended)
| OK/Normal/ Informational
| Cause: The check consistency operation on a virtual disk was paused by a user.
Action: To resume the check consistency operation, right-click the virtual disk in the Storage Management tree view and select Resume Check Consistency.
| 1201
| 604
|
2115
| A consistency check on a virtual disk has been resumed
| OK/Normal/ Informational
| Cause: The check consistency operation on a virtual disk has resumed processing after being paused by a user.
Action: This alert is provided for informational purposes.
| 1201
| 605
|
2116
| A virtual disk and its mirror have been split
| OK/Normal/ Informational
| Cause: 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 in order to maintain redundancy. After being split, both virtual disks retain a copy of the data, although because the mirror is no longer intact, updates to the data are no longer copied to the mirror.
Action: This alert is provided for informational purposes.
| 1201
| 606
|
2117
| A mirrored virtual disk has been unmirrored
| OK/Normal/ Informational
| Cause: A user has caused a mirrored virtual disk to be unmirrored. When a virtual disk is mirrored, its data is copied to another virtual disk in order to maintain redundancy. After being unmirrored, the disk formerly used as the mirror returns to being an array disk and becomes available for inclusion in another virtual disk.
Action: This alert is provided for informational purposes.
| 1201
| 607
|
2118
| Change write policy
| OK/Normal/ Informational
| Cause: A user has changed the write policy for a virtual disk.
Action: This alert is provided for informational purposes.
| 1201
| 601
|
2120
| Enclosure firmware mismatch
| Warning / Non-critical
| Cause: The firmware on the Expanded Memory Manager (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 a user attempts to insert an EMM module that has a different firmware version than an existing module.
Action: Download the same version of the firmware to both EMM modules.
| 853
| 672
|
2121
| Device returned to normal
| OK/Normal/ Informational
| Cause: A device 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, then you may receive this alert.
Action: This alert is provided for informational purposes.
| 752, 802, 852, 902, 952, 1002, 1052, 1102, 1152, 1202
| None
|
2122
| Redundancy degraded
| Warning / Non-critical
| Cause: 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.
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.
| 1305
| None
|
2123
| Redundancy lost
| Warning / Non-critical
| Cause: A virtual disk or an enclosure has lost data redundancy. In the case of a virtual disk, one or more array disks included in the virtual disk have failed. Due to the failed array disk or disks, the virtual disk is no longer maintaining redundant (mirrored or parity) data. The failure of an additional array 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.
| 1306
| None
|
|
|
| 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 Health status until you identify the failed component. See the online help for more information. See the enclosure documentation for information on replacing enclosure components and for other diagnostic information.
|
|
|
2124
| Redundancy normal
| OK/Normal/ Informational
| Cause: Data redundancy has been restored to a virtual disk or an enclosure that previously suffered a loss of redundancy.
Action: This alert is provided for informational purposes.
| 1304
| None
|
2126
| SCSI sense sector reassign
| Warning / Non-critical
| Cause: A sector of the disk is corrupted and data cannot be maintained on this portion of the disk.
Action: If the disk is part of a non-redundant virtual disk, then replace the disk. Any data residing on the corrupt portion of the disk may be lost and you may need to restore from backup. If the disk is part of a redundant virtual disk, then any data residing on the corrupt portion of the disk will be reallocated elsewhere in the virtual disk.
| 903
| None
|
2127
| Background initialization started
| OK/Normal/ Informational
| Cause: Background initialization of a virtual disk has started. This alert is provided for informational purposes.
Action: None.
| 1201
| 683
|
2128
| Background initialization cancelled
| OK/Normal/ Informational
| Cause: Background initialization of a virtual disk has been cancelled. A user or the firmware may have stopped background initialization.
Action: None.
| 1201
| 684
|
2129
| Background initialization failed
| Critical / Failure / Error
| Cause: Background initialization of a virtual disk has failed.
Action: None.
| 1204
| 685
|
2130
| Background initialization completed
| OK/Normal/ Informational
| Cause: Background initialization of a virtual disk has completed. This alert is provided for informational purposes.
Action: None.
| 1201
| 686
|
2131
| Firmware version mismatch
| Warning / Non-critical
| Cause: The firmware on the controller is not a supported version.
Action: Install a supported version of the firmware. If you do not have a supported version of the firmware available, it can be downloaded from the Dell support site at support.dell.com. If you do not have a supported version of the firmware available, check with your support provider for information on how to obtain the most current firmware.
| 753
| None
|
2132
| Driver version mismatch
| Warning / Non-critical
| Cause: The controller driver is not a supported version.
Action: Install a supported version of the driver. If you do not have a supported driver version available, it can be downloaded from the Dell support site at support.dell.com. If you do not have a supported version of the driver available, check with your support provider for information on how to obtain the most current driver.
| 753
| None
|
2135
| Array Manager is installed on the system
| Warning / Non-critical
| Cause: Storage Management has been installed on a system that has an Array Manager installation.
Action: Installing Storage Management and Array Manager on the same system is not a supported configuration. Uninstall either Storage Management or Array Manager.
| 103
| None
|
2136
| Virtual disk initialization
| OK/Normal/ Informational
| Cause: Virtual disk initialization is in progress. This alert is provided for informational purposes.
Action: None.
| 1201
| None
|
2137
| Communication timeout
| Warning / Non-critical
| Cause: The controller is unable to communicate with an enclosure. There are several reasons why communication may be lost. 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.
When viewed in the Alert Log, the description for this event displays several variables: controller name, enclosure name, type of communication problem, return code, and SCSI status.
Action: Check for problems with the cables. See the online help for more information on checking the cables. You should also check to see if the enclosure has degraded or failed components. To do so, 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 supported driver and firmware versions installed and that the enclosure management modules (EMMs) are each running the same version of supported firmware.
| 853
| 688, 610, 611
|
2138
| Enclosure alarm enabled
| OK/Normal/ Informational
| Cause: A user has enabled the enclosure alarm. This alert is provided for informational purposes.
Action: None.
| 851
| 676
|
2139
| Enclosure alarm disabled
| OK/Normal/ Informational
| Cause: A user has disabled the enclosure alarm.
Action: None.
| 851
| 677
|
2140
| Dead disk segments restored
| OK/Normal/ Informational
| Cause: Disk space that was formerly "dead" or inaccessible to a redundant virtual disk has been restored. This alert is provided for informational purposes.
Action: None.
| 1201
| None
|
2141
| Array disk dead segments recovered
| OK/Normal/ Informational
| Cause: Portions of the array disk that were formerly inaccessible have been recovered. Any data residing on these dead segments has been lost.This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2142
| Controller rebuild rate has changed
| OK/Normal/ Informational
| Cause: A user has changed the controller rebuild rate. This alert is provided for informational purposes.
Action: None.
| 751
| 680
|
2143
| Controller alarm enabled
| OK/Normal/ Informational
| Cause: A user has enabled the controller alarm. This alert is provided for informational purposes.
Action: None.
| 751
| 678
|
2144
| Controller alarm disabled
| OK/Normal/ Informational
| Cause: A user has disabled the controller alarm. This alert is provided for informational purposes.
Action: None.
| 751
| 679
|
2145
| Controller battery low
| Critical / Failure / Error
| Cause: The controller battery charge is low. On batteries that automatically recharge or recondition, this alert may indicate that the recharge limit has been reached.
Action: Recondition the battery. See the online help for more information
| 1154
| 580
|
2146
| Bad block replacement error
| Warning / Non-critical
| Cause: A portion of an array disk is damaged.
Action: See the Storage Management online help or the Dell OpenManage™ Server Administrator Storage Management User's Guide for more information.
| 753
| 691
|
2147
| Bad block sense error
| Warning / Non-critical
| Cause: A portion of an array disk is damaged. See the online help for more information.
Action: See the online help for more information.
| 753
| 691
|
2148
| Bad block medium error
| Warning / Non-critical
| Cause: A portion of an array disk is damaged. See the online help for more information.
Action: See the online help for more information.
| 753
| 691
|
2149
| Bad block extended sense error
| Warning / Non-critical
| Cause: A portion of an array disk is damaged. See the online help for more information.
Action: See the online help for more information.
| 753
| 691
|
2150
| Bad block extended medium error
| Warning / Non-critical
| Cause: A portion of an array disk is damaged. See the online help for more information.
Action: See the online help for more information.
| 753
| 691
|
2151
| Asset tag changed
| OK/Normal/ Informational
| Cause: A user has changed the enclosure asset tag. This alert is provided for informational purposes.
Action: None.
| 851
| None
|
2152
| Asset name changed
| OK/Normal/ Informational
| Cause: A user has changed the enclosure asset name. This alert is provided for informational purposes.
Action: None.
| 851
| None
|
2153
| Service tag changed
| Warning / Non-critical
| Cause: An enclosure service tag was changed. In most circumstances, this service tag should only be changed by Dell™ support or your service provider.
Action: Ensure that the tag was changed under authorized circumstances.
| 853
| None
|
2154
| Maximum temperature probe warning threshold value changed
| OK/Normal/ Informational
| Cause: A user has changed the value for the maximum temperature probe warning threshold. This alert is provided for informational purposes.
Action: None
| 1051
| None
|
2155
| Minimum temperature probe warning threshold value changed
| OK/Normal/ Informational
| Cause: A user has changed the value for the minimum temperature probe warning threshold. This alert is provided for informational purposes.
Action: None.
| 1051
| None
|
2156
| Controller alarm has been tested
| OK/Normal/ Informational
| Cause: The controller alarm test has run successfully. This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2157
| Controller configuration has been reset
| OK/Normal/ Informational
| Cause: A user has reset the controller configuration. See the online help for more information. This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2158
| Array disk online
| OK/Normal/ Informational
| Cause: An offline array disk has been made online. This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2159
| Virtual disk renamed
| OK/Normal/ Informational
| Cause: A user has renamed a virtual disk. This alert is provided for informational purposes.
When renaming a virtual disk on a PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controller, this alert displays the new virtual disk name. On the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM,4e/Si, 4e/Di, 5/E, and CERC SATA100/4ch controllers, this alert displays the original virtual disk name.
Action: None.
| 1201
| 608
|
2160
| Dedicated hotspare assigned
| OK/Normal/ Informational
| Cause: A user has assigned an array disk as a dedicated hot spare to a virtual disk. See the online help for more information. This alert is provided for informational purposes.
Action: None.
| 901
| 574
|
2161
| Dedicated hotspare unassigned
| OK/Normal/ Informational
| Cause: An array disk that was assigned as a hot spare has been unassigned and is no longer functioning as a hot spare. The array disk may have been 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. You need to assign a new hot spare to maintain data protection in this situation.
On the PERC 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers, if you use another application such as the BIOS to include a hot spare in a virtual disk, then Storage Management unassigns the array disk as a hot spare.
Action: Although this alert is provided for informational purposes, you may need to assign a new hot spare to the virtual disk.
| 901
| 575
|
2162
| Communication regained
| OK/Normal/ Informational
| Cause: Communication with an enclosure has been restored. This alert is provided for informational purposes.
Action: None.
| 851
| None
|
2163
| Rebuild completed with errors
| Critical / Failure / Error
| Cause: See the online help for more information.
Action: See the online help for more information.
| 904
| 690
|
2164
| See readme.txt for a list of validated controller driver versions
| OK/Normal/ Informational
| Cause: Storage Management is unable to determine whether the system has the minimum required versions of the RAID controller drivers.
Action: This alert is generated for informational purposes. See the Readme file for driver and firmware requirements. In particular, if Storage Management experiences performance problems, you should verify that you have the minimum supported versions of the drivers and firmware installed.
| 101
| None
|
2165
| The RAID controller firmware and driver validation was not performed. The configuration file cannot be opened.
| Warning / Non-critical
| Cause: Storage Management is unable to determine whether the system has the minimum required versions of the RAID controller firmware and drivers. This situation may occur for a variety of reasons. For example, the installation directory path to the configuration file may not be correct. The configuration file may also have been removed or renamed.
Action: Reinstall Storage Management
| 753
| None
|
2166
| The RAID controller firmware and driver validation was not performed. The configuration file is out of date or corrupted.
| Warning / Non-critical
| Cause: Storage Management is unable to determine whether the system has the minimum required versions of the RAID controller firmware and drivers. This situation has occurred because a configuration file is unreadable or missing data. The configuration file may be corrupted.
Action: Reinstall Storage Management
| 753
| None
|
2167
| The current kernel version and the non-RAID SCSI driver version are older than the minimum required levels. See readme.txt for a list of validated kernel and driver versions.
| Warning / Non-critical
| Cause: The version of the kernel and the driver do not meet the minimum requirements. Storage Management may not be able to display the storage or perform storage management functions until you have updated the system to meet the minimum requirements.
Action: See the Readme file for kernel and driver requirements. Update the system to meet the minimum requirements and then reinstall Storage Management.
| 103
| None
|
2168
| The non-RAID SCSI driver version is older than the minimum required level. See readme.txt for the validated driver version.
| Warning / Non-critical
| Cause: The version of the driver does not meet the minimum requirements. Storage Management may not be able to display the storage or perform storage management functions until you have updated the system to meet the minimum requirements.
Action: See the Readme file for the driver requirements. Update the system to meet the minimum requirements and then reinstall Storage Management.
| 103
| None
|
2169
| The controller battery needs to be replaced.
| Critical/Failure/Error
| Cause: The controller battery cannot recharge. The battery may be old or it may have been already recharged the maximum number of times. In addition, the battery charger may not be working.
Action: Replace the battery pack.
| 1154
| None
|
2170
| The controller battery charge level is normal.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1151
| None
|
2171
| The controller battery temperature is above normal.
| Warning/
Non-critical
| Cause: The battery may be in the process of recharging. The room temperature may also be too hot. The fan in the system may also be degraded or failed.
Action: If this alert was generated due to a battery recharge, then the situation will correct itself when the recharge is complete. You should also verify that the room temperature is normal and that system components such as the fan are functioning properly.
| 1153
| None
|
2172
| The controller battery temperature is normal.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1151
| None
|
2174
| The controller batty has been removed.
| Warning/
Non-critical.
| Cause: The controller cannot communicate with the battery. The battery may be removed. The contact point between the controller and the battery may also be burned or corroded.
Action: Verify whether the battery is present. Replace the battery if it is not present. If the contact point between the battery and the controller is burned or corroded, you will need to replace either the battery or the controller or both. Refer to the hardware documentation for information on how to safely access, remove, and replace the battery.
| 1153
| None
|
2175
| The controller battery has been replaced.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1151
| None
|
2176
| The controller battery Learn cycle has started.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1151
| None
|
2177
| The controller battery Learn cycle has completed.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1151
| None
|
2178
| The controller battery Learn cycle has timed out.
| Warning/ Non-critical
| Cause: 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.
Action: Replace the battery pack. The battery is unable to maintain a full charge.
| 1153
| None
|
2179
| The controller battery Learn cycle has been postponed.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1151
| None
|
2180
| The controller battery Learn cycle will start in % days.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1151
| None
|
2181
| The controller battery Learn cycle will start in % hours.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1151
| None
|
2182
| An invalid SAS configuration has been detected.
| Critical/
Failure/
Error
| Cause: The controller and attached enclosures are not cabled correctly.
Action: See the hardware documentation for information on correct cabling configurations.
| 754
| None
|
2186
| The controller cache has been discarded.
| Warning/
Non-critical
| Cause: The controller has flushed the cache and any 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.
Action: Verify that the battery and memory are functioning properly.
| 753
| None
|
2187
| Single-bit ECC error limit exceeded.
| Warning/
Non-critical
| Cause: The system memory is malfunctioning.
Action: Replace the battery pack.
| 753
| None
|
2188
| The controller write policy has been changed to Write Through.
| Warning/
Non-critical
| Cause: The controller battery is unable to maintain cached data for the required period of time. For example, if the required period of time is 24 hours, then the battery is unable to maintain cached data for 24 hours. It is normal to receive this alert during the battery Learn cycle. This is because the Learn cycle discharges the battery before recharging it. When discharged, the battery cannot maintain cached data.
Action: Verify the health of the battery. If the battery is not healthy, then replace the battery pack.
| 1153
| None
|
2189
| The controller write policy has been changed to Write Back.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1151
| None
|
2191
| There are too many enclosures attached to the controller. This is an unsupported configuration.
| Critical/
Failure/
Error
| Cause: 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.
Action: Remove the last enclosure. You must remove the enclosure that has been added last and is causing the enclosure limit to be exceeded.
| 854
| None
|
2192
| The virtual disk Check Consistency has made corrections and completed.
| OK/Normal/ Informational
| Cause: The virtual disk Check Consistency has identified errors 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.
Action: Monitor the battery health and the cache health to make sure the battery and cache are functioning properly. Monitor the Alert Log for events related to the battery and to write policy changes. You should also monitor the Alert Log for events related to disk errors. If you suspect that the battery or a disk have problems, then replace the battery pack or the disk.
| 1203
| None
|
2193
| The virtual disk reconfigure has resumed.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| None
|
2194
| The virtual disk read policy has changed.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| None
|
2199
| The virtual disk cache policy has changed.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| None
|
2201
| A global hot spare failed.
| Warning/
Non-critical
| Cause: The controller is not able to communicate with a disk that is assigned as a global hot spare. The disk may have failed or been removed. There may also be a bad or loose cable.
Action: Verify that the disk is healthy and that it has not been removed. Check the cables. If necessary, replace the disk and reassign the hot spare.
| 903
| None
|
2202
| A global hot spare has been removed.
| Warning/
Non-critical
| Cause: The controller is not able to communicate with a disk that is assigned as a global hot spare. The disk may have been removed. There may also be a bad or loose cable.
Action: Verify that the disk is healthy and that it has not been removed. Check the cables. If necessary, replace the disk and reassign the hot spare.
| 903
| None
|
2203
| A dedicated hot spare failed.
| Warning/
Non-critical
| Cause: The controller is not able to communicate with a disk that is assigned as a dedicated hot spare. The disk may have failed or been removed. There may also be a bad or loose cable.
Action: Verify that the disk is healthy and that it has not been removed. Check the cables. If necessary, replace the disk and reassign the hot spare.
| 903
| None
|
2204
| A dedicated hot spare has been removed.
| Warning/
Non-critical
| Cause: 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.
Action: Verify that the disk is healthy and that it has not been removed. Check the cables. If necessary, replace the disk and reassign the hot spare.
| 903
| None
|
2205
| A dedicated hot spare has been automatically unassigned.
| Warning/
Non-critical
| Cause: The hot spare is no longer required because the virtual disk it was assigned to has been deleted.
Action: None.
| 903
| None
|
2206
| The only hot spare available is a SATA disk. SATA disks cannot replace SAS disks.
| Warning/
Non-critical
| Cause: The only array disk available to be assigned as a hot spare is using SATA technology. The array disks in the virtual disk are using Serial Attached SCSI (SAS) technology. Because of this difference in technology, the hot spare cannot rebuild data if one of the array disks in the virtual disk fails.
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.
| 903
| None
|
2207
| The only hot spare available is a SAS disk. SAS disks cannot replace SATA disks.
| Warning/
Non-critical
| Cause: The only array disk available to be assigned as a hot spare is using SAS technology. The array 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 array disks in the virtual disk fails.
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.
| 903
| None
|
2211
| The physical disk is not supported.
| Warning/
Non-critical
| Cause: The physical disk may not have a supported version of the firmware or the disk may not be supported by Dell.
Action: If the disk is supported by Dell, then update the firmware to a supported version. If the disk is not supported by Dell, then replace the disk with one that is supported.
| 903
| None
|
2232
| The controller alarm is silenced.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2233
| The background initialization (BGI) rate has changed.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2234
| The Patrol Read rate has changed.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2235
| The Check Consistency rate has changed.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2237
| A controller rescan has been initiated.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2238
| The controller debug log file has been exported.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2239
| A foreign configuration has been cleared.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2240
| A foreign configuration has been imported.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2241
| The Patrol Read mode has changed.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2242
| The Patrol Read has started.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2243
| The Patrol Read has stopped.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2244
| A virtual disk blink has been initiated.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| None
|
2245
| A virtual disk blink has ceased.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| None
|
2246
| The controller battery is degraded.
| Warning/
Non-critical
| Cause: The controller battery charge is weak. As the battery charge weakens, the battery charger should automatically recharge the battery. If the battery has already met its recharge limit, then the battery pack needs to be replaced.
Action: Monitor the battery to make sure that it recharges successfully. If the battery does not recharge, then replace the battery pack.
| 1153
| None
|
2247
| The controller battery is charging.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 245
| None
|
2248
| The controller battery is executing a Learn cycle.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1151
| None
|
2249
| The array disk Clear operation has started.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2251
| The array disk blink has initiated.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2252
| The array disk blink has ceased.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2254
| The Clear operation has cancelled.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2255
| The array disk has started.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2259
| An enclosure blink operation has initiated.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 851
| None
|
2260
| An enclosure blink has ceased.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 851
| None
|
2261
| A global rescan has initiated.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 101
| None
|
2262
| Smart thermal shutdown is enabled.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 101
| None
|
2263
| Smart thermal shutdown is disabled.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 101
| None
|
2264
| A device is missing.
| Warning/
Non-critical
| Cause: The controller cannot communicate with a device. The device may be removed. There may also be a bad or loose cable.
Action: Verify that the device is present and not removed. If it is present, then check the cables. You should also check the connection to the controller battery and the battery health. A battery with a weak or depleted charge may cause this alert.
| 753, 803, 853, 903, 953, 1003, 1053, 1103, 1153, 1203
| None
|
2265
| A device is in an unknown state.
| Warning/
Non-critical
| Cause: The controller cannot communicate with a device. The state of the device cannot be determined. There may be a bad or loose cable. The system may also be experiencing problems with the application programming interface (API). There could also be a problem with the driver or firmware.
Action: Check the cables. Verify that the controller has a supported version of the driver and firmware. You can download the most current version of the driver and firmware from support.dell.com. Rebooting the system may also resolve this problem.
| 753, 803, 853, 903, 953, 1003, 1053, 1103, 1153, 1203
| None
|
2266
| Controller log file entry:%1
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2267
| The controller reconstruct rate has changed.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2268
| %1, Storage Management has lost communication with this RAID controller and attached storage. An immediate reboot is strongly recommended to avoid further problems. If the reboot does not restore communication, then there may be a hardware failure.
| Critical/
Failure/
Error
| Cause: Storage Management has lost communication with a device. There may be faulty hardware or loose or defective cables.
Action: Reboot the system. If the problem is not resolved, check for hardware failures. Any failed component must be replaced. Make sure the cables are attached securely. Refer to the hardware documentation for more diagnostics information.
| 104
| None
|
2269
| The array disk Clear operation has completed.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2270
| The array disk Clear operation failed.
| Critical/
Failure/
Error
| Cause: A Clear task was being performed on an array disk but the task was interrupted and did not complete successfully. The controller may have lost communication with the disk. They disk may have been removed or the cables may be loose or defective.
Action: Verify that the disk is present and not in a Failed state. Make sure the cables are attached securely. Restart the Clear task.
| 904
| None
|
2271
| The Patrol Read corrected a media error.
| OK/Normal/ Informational
| Cause: The Patrol Read task has encountered an error such as a bad disk block and remapped data to correct the error.
Action: None.
| 901
| None
|
2272
| Patrol Read found an uncorrectable media error.
| Critical/
Failure/
Error
| Cause: The Patrol Read task has encountered an error that cannot be corrected. There may be a bad disk block that cannot be remapped.
Action: Replace the array disk to avoid future data loss.
| 903
| None
|
2273
| Bad media.
| Critical/
Failure/
Error
| Cause: A source (array) disk in a redundant virtual disk has a bad disk block. The algorithm that maintains redundant data has created a similar bad block on the target redundant disk in order to maintain consistency in disk block addressing. Data has been lost.
Action: Restore from backup.
| 904
| None
|
2274
| The array disk rebuild has resumed.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2276
| The dedicated hot spare is too small.
| Warning/
Non-critical
| Cause: The dedicated hot spare is not large enough to protect all virtual disks that reside on the disk group.
Action: Assign a larger disk as the dedicated hot spare.
| 903
| None
|
2277
| The global hot spare is too small.
| Warning/
Non-critical
| Cause: The global hot spare is not large enough to protect all virtual disks that reside on the controller.
Action: Assign a larger disk as the global hot spare.
| 903
| None
|
2278
| The controller battery charge level is below a normal threshold.
| Critical/
Failure/
Error
| Cause: The battery is discharging. A battery discharge is a normal activity during the battery Learn cycle. Before completing, the battery Learn cycle recharges the battery. You should receive alert 2179 when the recharge occurs.
Action: Verify whether the battery Learn cycle is in progress. Alert 2176 indicates that the battery Learn cycle has initiated. The battery also displays the Learn state while the Learn cycle is in progress. If a Learn cycle is not in progress, then replace the battery pack.
| 1154
| None
|
2279
| The controller battery charge level is above a normal threshold.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes. This alert indicates that the battery is recharging during the battery Learn cycle.
Action: None.
| 1151
| None
|
2280
| A disk media error has been corrected.
| OK/Normal/ Informational
| Cause: A disk media error was detected while the controller was completing a background task. A bad disk block was identified. The disk block has been remapped.
Action: Consider replacing the disk. If you receive this alert frequently, be sure to replace the disk. You should also routinely back up your data.
| 1201
| None
|
2281
| Virtual disk has inconsistent data.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| None
|
2282
| Hot spare SMART polling failed.
| Critical/
Failure/
Error
| Cause: The controller firmware attempted to do SMART polling on the hot spare but was not able to complete the SMART polling. The controller has lost communication with the hot spare.
Action: Verify the health of the disk assigned as a hot spare. You may need to replace the disk and reassign the hot spare. Make sure the cables are attached securely.
| 904
| None
|
2283
| A redundant path is broken.
| Warning/
Non-critical
| Cause: 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.
Action: Make sure the cables are attached securely, and that both enclosure management modules (EMMs) are healthy.
| 903
| None
|
2284
| A redundant path has been restored.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2285
| A disk media error was corrected during recovery.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2286
| A Learn cycle start is pending while the battery charges.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1151
| None
|
2287
| The Patrol Read is paused.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2288
| The patrol read has resumed.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2289
| Multi-bit ECC error.
| Critical/
Failure/
Error
| Cause: 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.
Action: Replace the dual in-line memory module (DIMM). The DIMM is a part of the controller battery pack. Refer to your hardware documentation for information on replacing the DIMM. You may need to restore data from backup.
| 754
| None
|
2290
| Single-bit ECC error.
| Warning/
Non-critical
| Cause: An error involving a single bit has been encountered during a read or write operation. The error correction algorithm has corrected this error.
Action: None.
| 753
| None
|
2291
| An enclosure management module (EMM) has been discovered.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 851
| None
|
2292
| Communication with the enclosure has been lost.
| Critical/
Failure/
Error
| Cause: The controller has lost communication with an EMM. The cables may be loose or defective.
Action: Make sure the cables are attached securely. Reboot the system.
| 854
| None
|
2293
| The enclosure management module (EMM) has failed.
| Critical/
Failure/
Error
| Cause: An 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 could also be a firmware problem or a multi-bit error.
Action: Replace the EMM. See the hardware documentation for information on replacing the EMM.
| 854
| None
|
2294
| A device has been inserted.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 752, 802, 852, 902, 952, 1002, 1052, 1102, 1152, 1202
| None
|
2295
| A device has been removed.
| Critical/
Failure/
Error
| Cause: A device has been removed and the system is no longer functioning in optimal condition.
Action: Replace the device.
| 754, 804, 854, 904, 954, 1004, 1054, 1104, 1154, 1204
| None
|
2296
| An enclosure management module (EMM) has been inserted.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 851
| None
|
2297
| An enclosure management module (EMM) has been removed.
| Critical/
Failure/
Error
| Cause: An EMM has been removed.
Action: Replace the EMM. See the hardware documentation for information on replacing the EMM.
| 854
| None
|
2298
| There is a bad sensor on an enclosure.
| Warning/
Non-critical
| Cause: The enclosure has a bad sensor. The enclosure sensors monitor the fan speeds, temperature probes, and so on.
Action: Refer to the hardware documentation for more information.
| 853
| None
|
2299
| Bad PHY %1
| Critical/
Failure/
Error
| Cause: There is a problem with a physical connection or PHY.
Action: Replace the EMM that contains the bad PHY. See the hardware documentation for information on replacing the EMM. Attach the storage to a different connector if one is available. Make sure the cables are attached securely.
| 854
| None
|
2300
| The enclosure is unstable.
| Critical/
Failure/
Error
| Cause: 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 will degrade the signal.
Action: Completely power down all enclosures attached to the system and reboot the system. If the problem persists, upgrade the firmware to the latest supported version. You can download the most current version of the driver and firmware from support.dell.com. Make sure the cable configuration is valid. See the hardware documentation for valid cabling configurations.
| 854
| None
|
2301
| The enclosure has a hardware error.
| Critical/
Failure/
Error
| Cause: The enclosure or an enclosure component is in a Failed or Degraded state.
Action: Verify the health of the enclosure and its components. Replace any hardware that is in a Failed state. See the hardware documentation for more information.
| 854
| None
|
2302
| The enclosure is not responding.
| Critical/
Failure/
Error
| Cause: The enclosure or an enclosure component is in a Failed or Degraded state.
Action: Verify the health of the enclosure and its components. Replace any hardware that is in a Failed state. See the hardware documentation for more information.
| 854
| None
|
2303
| The enclosure cannot support both SAS and SATA array disks. Array disks may be disabled.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 851
| None
|
2304
| An attempt to hot plug an enclosure management module (EMM) has been detected. This type of hot plug is not supported.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 851
| None
|
2305
| The array disk is too small to be used for a rebuild.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2306
| Bad block table is 80% full.
| Warning/
Non-critical
| Cause: 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 can no longer be remapped which means that disk errors can no longer be corrected. At this point, data loss can occur. The bad block table is now 80% full.
Action: Back up your data. Replace the disk generating this alert and restore from back up.
| 903
| None
|
2307
| Bad block table is full. Unable to log block %1
| Critical/
Failure/
Error
| Cause: 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 can no longer be remapped which means that disk errors can no longer be corrected. At this point, data loss can occur.
Action: Replace the disk generating this alert and restore from backup. You may have lost data.
| 904
| None
|
2309
| An array disk is incompatible.
| Warning/
Non-critical
| Cause: You have attempted to replace a disk with another disk that is using an incompatible technology. For example, you may have replaced one side of a mirror with a SAS disk when the other side of the mirror is using SATA technology.
Action: Refer to the hardware documentation for information on replacing disks
| 903
| None
|
2310
| A virtual disk is permanently degraded.
| Critical/
Failure/
Error
| Cause: A redundant virtual disk has lost redundancy. This may occur when the virtual disk suffers the failure of more than one array disk. In this case, both the source array disk and the target disk with redundant data have failed. A rebuild is not possible because there is no longer redundancy.
Action: Replace the failed disks and restore from backup.
| 1204
| None
|
2311
| The firmware on the enclosure management modules (EMMs) is not the same version. EMM0 %1 EMM1 %2
| Warning/
Non-critical
| Cause: 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 a user attempts to insert an EMM module that has a different firmware version than an existing module.
Action: Upgrade to the same version of the firmware on both EMM modules.
| 853
| None
|
2312
| A power supply in the enclosure has an AC failure.
| Warning/
Non-critical
| Cause: The power supply has an AC failure.
Action: Replace the power supply.
| 1003
| None
|
2313
| A power supply in the enclosure has a DC failure.
| Warning/
Non-critical
| Cause: The power supply has a DC failure.
Action: Replace the power supply.
| 1003
| None
|
2314
| The initialization sequence of SAS components failed during system startup. SAS management and monitoring is not possible.
| Critical/
Failure/
Error
| Cause: Storage Management is unable to monitor or manage SAS devices.
Action: Reboot the system. If problem persists, make sure you have supported versions of the drivers and firmware. You may need to reinstall Storage Management or Server Administrator. You may be missing some of the installation components.
| 104
| None
|
2315
| Diagnostic message %1
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2316
| Diagnostic message %1
| Critical/ Failure/Error
| Cause: A diagnostics test failed. The text for this alert is generated by the utility that ran the diagnostics.
Action: See the documentation for the utility that ran the diagnostics for more information.
| 754
| None
|
2317
| Background initialization (BGI) terminated due to loss of ownership in a cluster configuration.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| None
|
2318
| Problems with the battery or the battery charger have been detected. The battery health is poor.
| Critical/
Failure/
Error
| Cause: The battery or the battery charger is not functioning properly.
Action: Replace the battery pack.
| 1154
| None
|
2319
| Single-bit ECC error. The dual in-line memory module (DIMM) is degrading.
| Warning/
Non-critical
| Cause: The DIMM is beginning to malfunction.
Action: Replace the DIMM to avoid data loss or data corruption. The DIMM is a part of the controller battery pack. Refer to your hardware documentation for information on replacing the DIMM.
| 753
| None
|
2320
| Single-bit ECC error. The dual in-line memory module (DIMM) is critically degraded.
| Critical/
Failure/
Error
| Cause: The DIMM is malfunctioning. Data loss or data corruption may be imminent.
Action: Replace the DIMM immediately to avoid data loss or data corruption. The DIMM is a part of the controller battery pack. Refer to your hardware documentation for information on replacing the DIMM.
| 754
| None
|
2321
| Single-bit ECC error. The dual in-line memory module (DIMM) is critically degraded. There will be no further reporting.
| Critical/
Failure/
Error
| Cause: The dual in-line memory module DIMM is malfunctioning. Data loss or data corruption is imminent. The DIMM must be replaced immediately. No further alerts will be generated.
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.
| 754
| None
|
2322
| The DC power supply is switched off.
| Critical/
Failure/
Error
| Cause: The power supply unit is switched off. Either a user switched off the power supply unit or it is defective.
Action: Check to see whether the power switch is turned off or on. If it is turned off, turn it on. If the problem is not corrected, verify that the power cord is attached and functional. If the problem is still not corrected or if the power switch is already turned on, then replace the power supply unit.
| 1004
| None
|
2323
| The power supply is switched on.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1001
| None
|
2324
| The AC power supply cable has been removed.
| Critical/
Failure/
Error
| Cause: The power cable may be pulled out or removed. The power cable may also have overheated and become warped and nonfunctional.
Action: Replace the power cable.
| 1004
| None
|
2325
| The power supply cable has been inserted.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1001
| None
|
2326
| A foreign configuration has been detected.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes. The controller has array disks that were moved from another controller. These array disks contain virtual disks that were created on the other controller.
Action: None.
| 751
| None
|
2327
| The NVRAM has corrupted data. The controller is reinitializing the NVRAM.
| Warning/
Non-critical
| Cause: The Non-Volatile Random-Access Memory (NVRAM) has corrupted data. This may occur after a power surge, a battery failure, or for other reasons. The controller is reinitializing the NVRAM.
Action: None. The controller is taking the required corrective action. If this alert is generated often (such as during each reboot), then replace the controller.
| 753
| None
|
2328
| The NVRAM has corrupt data.
| Warning/
Non-critical
| Cause: The NVRAM has corrupt data. The controller is unable to correct the situation.
Action: Replace the controller.
| 753
| None
|
2329
| SAS port report: %1
| Warning/
Non-critical
| Cause: The text for this alert is generated by the controller and can vary depending on the situation.
Action: Make sure the cables are attached securely. If the problem is not resolved, replace the cable with a valid cable according to SAS specifications. If the problem persists, you may need to replace devices such as the controller or EMM. Refer to the hardware documentation for more information.
| 753
| None
|
2330
| SAS port report: %1
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2331
| A bad disk block has been reassigned.
| Warning/
Non-critical
| Cause: The disk has a bad block. Data has been readdressed to another disk block. No data loss has occurred.
Action: Monitor the disk for other alerts or indications of poor health. For example, you may receive alert 2306. Replace the disk if you suspect there is a problem.
| 903
| None
|
2332
| A controller hot plug has been detected.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2333
| An enclosure temperature sensor differential has been detected.
| Warning/
Non-critical
| Cause: The firmware has detected a temperature sensor differential in the enclosure.
Action: Monitor the enclosure for other alerts related to the temperature. For example, you may receive alerts related to the fan or temperature probes. Verify the health of the enclosure and its components. Replace any component that is failed.
| 853
| None
|
2334
| Controller event log: %1
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2335
| Controller event log: %1
| Warning/
Non-critical
| Cause: 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.
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.
| 753
| None
|
2336
| Controller event log: %1
| Critical/
Failure/
Error
| Cause: 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.
Action: See the hardware documentation for more information.
| 754
| None
|
2337
| The controller is unable to recover cached data from the battery backup unit (BBU).
| Critical/
Failure/
Error
| Cause: The controller was unable to recover data from the cache.
Action: Verify that the battery is charged and in good health. When the battery charge is unacceptably low, the battery cannot maintain cached data. Verify whether the battery has met its recharge limit. The battery may need to be recharged or replaced.
| 1154
| None
|
2338
| The controller has recovered cached data from the battery backup unit (BBU).
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1151
| None
|
2339
| The factory default settings have been restored.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2340
| The background initialization (BGI) completed with uncorrectable errors.
| Critical/
Failure/
Error
| Cause: The BGI task encountered errors that cannot be corrected. The virtual disk contains array disks that have unusable disk space or disk errors that cannot be corrected.
Action: Replace the array disk that contains the disk errors. Review other alert messages to identify the array disk that has errors. If the virtual disk is redundant, you can replace the array disk and continue using the virtual disk. If the virtual disk is non-redundant, you may need to recreate the virtual disk after replacing the array disk. After replacing the array disk, run a Check Consistency to verify the data.
| 1204
| None
|
2341
| The Check Consistency made corrections and completed.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1201
| None
|
2342
| The Check Consistency found inconsistent parity data. Data redundancy may be lost.
| Warning/
Non-critical
| Cause: The data on a source disk and the redundant data on a target disk is inconsistent.
Action: Restart the Check Consistency task. If you receive this alert again, verify the health of the array disks included in the virtual disk. Review the alert messages for significant alerts related to the array disks. If you suspect that an array disk has a problem, replace it and restore from backup.
| 1203
| None
|
2343
| The Check Consistency logging of inconsistent parity data is disabled.
| Warning/
Non-critical
| Cause: The Check Consistency can no longer report errors in the parity data.
Action: See the hardware documentation for more information.
| 1203
| None
|
2344
| The virtual disk initialization terminated.
| Warning/
Non-critical
| Cause: A user has cancelled the virtual disk initialization.
Action: Restart the initialization.
| 1203
| None
|
2345
| The virtual disk initialization failed.
| Critical/
Failure/
Error
| Cause: The controller cannot communicate with attached devices. A disk may be removed or contain errors. Cables may also be loose or defective.
Action: Verify the health of attached devices. Review the Alert Log for significant events. Make sure the cables are attached securely.
| 1204
| None
|
2346
| Error occurred: %1
| Warning/
Non-critical
| Cause: The text for this alert is generated by the firmware and can vary depending on the situation.
Action: Verify the health of attached devices. Review the Alert Log for significant events. You may need to replace faulty hardware. Make sure the cables are attached securely. See the hardware documentation for more information.
| 903
| None
|
2347
| The rebuild failed due to errors on the source physical disk.
| Critical/
Failure/
Error
| Cause: You are attempting to rebuild data that resides on a defective disk.
Action: Replace the source disk and restore from backup.
| 904
| None
|
2348
| The rebuild failed due to errors on the target physical disk.
| Critical/
Failure/
Error
| Cause: You are attempting to rebuild data onto a disk that is defective.
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 in order to initiate the rebuild.
| 904
| None
|
2349
| A bad disk block could not be reassigned during a write operation.
| Critical/
Failure/
Error
| Cause: A write operation could not complete because the disk contains bad disk blocks that could not be reassigned. Data loss may have occurred. Data redundancy may also be lost.
Action: Replace the disk.
| 904
| None
|
2350
| There was an unrecoverable disk media error during the rebuild.
| Critical/
Failure/
Error
| Cause: The rebuild encountered an unrecoverable disk media error.
Action: Replace the disk.
| 904
| None
|
2351
| A physical disk is marked as missing.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2352
| A physical disk that was marked as missing has been replaced.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2353
| The enclosure temperature has returned to normal.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 851
| None
|
2354
| Enclosure firmware download in progress.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 851
| None
|
2355
| Enclosure firmware download failed.
| Warning/
Non-critical
| Cause: 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.
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. Check the cables. 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 subtab displays a red "X" or yellow exclamation point for enclosure components that are failed or degraded.
| 853
| None
|
2356
| SAS Management Protocol (SMP) communications error %1.
| Critical/
Failure/
Error
| Cause: 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.
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 hardware documentation for information on correct cabling configurations. Verify that the firmware is a supported version.
| 754
| None
|
2357
| SAS expander error: %1
| Critical/
Failure/
Error
| Cause: The text for this alert is generated by the firmware and can vary depending on the situation.
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 subtab displays a red "X" or yellow exclamation point for enclosure components that are failed or degraded. See the enclosure documentation for more information.
| 754
| None
|
2358
| The battery charge cycle is complete.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 1151
| None
|
2359
| The physical disk is not certified.
| Warning/
Non-critical
| Cause: The physical disk does not comply with the standards set by Dell and is not supported.
Action: Replace the physical disk with a physical disk that is supported.
| 903
| None
|
2360
| A user has discarded data from the controller cache.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2361
| Array disk(s) that are part of a virtual disk have been removed while the system was shut down. This removal was discovered during system start-up.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2362
| Array disk(s) have been removed from a virtual disk. The virtual disk will be in Failed state during the next system reboot.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2363
| A virtual disk and all of its member array disks have been removed while the system was shut down. This removal was discovered during system start-up.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2364
| All virtual disks are missing from the controller. This situation was discovered during system start-up.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 751
| None
|
2365
| The speed of the enclosure fan has changed.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 851
| None
|
2366
| Dedicated spare imported as global due to missing arrays.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2367
| Rebuild not possible as SAS/SATA is not supported in the same virtual disk.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 901
| None
|
2368
| The Scalable Encryption Processor (SEP) has been rebooted as part of the firmware download operation and will be unavailable until the operation completes.
| OK/Normal/ Informational
| Cause: This alert is provided for informational purposes.
Action: None.
| 851
| None
|
