Storage Management Message Reference

The Dell OpenManage Server Administrator Storage Management’s alert or event management features let you monitor the health of storage resources such as controllers, enclosures, physical disks, and virtual disks.

Alert Monitoring and Logging

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 Storage Management Service, the alert monitoring and logging stops. Alert monitoring does the following:

Updates the status of the storage object that generated the alert.
Propagates the storage object’s status to all the related higher objects in the storage hierarchy. For example, the status of a lower-level object will be propagated up to the status displayed on the Health tab for the top-level storage object.
Logs an alert in the Alert log and the operating system (OS) application log.
Sends an SNMP trap if the operating system’s SNMP service is installed and enabled.
NOTE: Dell OpenManage Server Administrator Storage Management does not log alerts regarding the data I/O path. These alerts are logged by the respective RAID drivers in the system alert log.

See the Storage Management Online Help and the Dell OpenManage Server Administrator Storage Management User’s Guide for updated information.

Alert Message Format with Substitution Variables

When you view an alert in the Server Administrator alert log, the alert identifies the specific components such as the controller name or the virtual disk name to which the alert applies. In an actual operating environment, a storage system can have many combinations of controllers and disks as well as user-defined names for virtual disks and other components. Because each environment is unique in its storage configuration and user-defined names, an accurate alert message requires that the Storage Management Service be able to insert the environment-specific names of storage components into an alert message.

This environment-specific information is inserted after the alert message text as shown for alert 2127 in Table 4-1.

For other alerts, the alert message text is constructed from information passed directly from the controller (or another storage component) to the Alert Log. In these cases, the variable information is represented with a % (percent sign) in the Storage Management documentation. An example of such an alert is shown for alert 2334 in Table 4-1.

Table 4-1. Alert Message Format

Alert ID

Message Text Displayed in the Storage Management Service Documentation

Message Text Displayed in the Alert Log with Variable Information Supplied

2127

Background Initialization started

Background Initialization started: Virtual Disk 3 (Virtual Disk 3) Controller 1 (PERC 5/E Adapter)

2334

Controller event log %

Controller event log: Current capacity of the battery is above threshold.: Controller 1 (PERC 5/E Adapter)

The variables required to complete the message vary depending on the type of storage object and whether the storage object is in a SCSI or SAS configuration. The following table identifies the possible variables used to identify each storage object.

NOTE: Some alert messages relating to an enclosure or an enclosure component, such as a fan or EMM, are generated by the controller when the enclosure or enclosure component ID cannot be determined.

Table 4-2. Message Format with Variables for Each Storage Object  

Storage Object

Message Variables

A, B, C and X, Y, Z in the following examples are variables representing the storage object name or number.

Controller

Message Format: Controller A (Name)

Message Format: Controller A

Example: 2326 A foreign configuration has been detected.: Controller 1 (PERC 5/E Adapter)

NOTE: The controller name is not always displayed.

Battery

Message Format: Battery X Controller A

Example: 2174 The controller battery has been removed: Battery 0 Controller 1

SCSI Physical Disk

Message Format: Physical Disk X:Y Controller A, Connector B

Example: 2049 Physical disk removed: Physical Disk 0:14 Controller 1, Connector 0

SAS Physical Disk

Message Format: Physical Disk X:Y:Z Controller A, Connector B

Example: 2049 Physical disk removed: Physical Disk 0:0:14 Controller 1, Connector 0

Virtual Disk

Message Format: Virtual Disk X (Name) Controller A (Name)

Message Format: Virtual Disk X Controller A

Example: 2057 Virtual disk degraded: Virtual Disk 11 (Virtual Disk 11) Controller 1 (PERC 5/E Adapter)

NOTE: The virtual disk and controller names are not always displayed.

Enclosure:

Message Format: Enclosure X:Y Controller A, Connector B

Example: 2112 Enclosure shutdown: Enclosure 0:2 Controller 1, Connector 0

SCSI Power Supply

Message Format: Power Supply X Controller A, Connector B, Target ID C

where "C" is the SCSI ID number of the enclosure management module (EMM) managing the power supply.

Example: 2122 Redundancy degraded: Power Supply 1, Controller 1, Connector 0, Target ID 6

SAS Power Supply

Message Format: Power Supply X Controller A, Connector B, Enclosure C

Example: 2312 A power supply in the enclosure has an AC failure.: Power Supply 1, Controller 1, Connector 0, Enclosure 2

SCSI Temperature Probe

Message Format: Temperature Probe X Controller A, Connector B, Target ID C

where "C" is the SCSI ID number of the EMM managing the temperature probe.

Example: 2101 Temperature dropped below the minimum warning threshold: Temperature Probe 1, Controller 1, Connector 0, Target ID 6

SAS Temperature Probe

Message Format: Temperature Probe X Controller A, Connector B, Enclosure C

Example: 2101 Temperature dropped below the minimum warning threshold: Temperature Probe 1, Controller 1, Connector 0, Enclosure 2

SCSI Fan

Message Format: Fan X Controller A, Connector B, Target ID C

where "C" is the SCSI ID number of the EMM managing the fan.

Example: 2121 Device returned to normal: Fan 1, Controller 1, Connector 0, Target ID 6

SAS Fan

Message Format: Fan X Controller A, Connector B, Enclosure C

Example: 2121 Device returned to normal: Fan 1, Controller 1, Connector 0, Enclosure 2

SCSI EMM

Message Format: EMM X Controller A, Connector B, Target ID C

where "C" is the SCSI ID number of the EMM.

Example: 2121 Device returned to normal: EMM 1, Controller 1, Connector 0, Target ID 6

SAS EMM

Message Format: EMM X Controller A, Connector B, Enclosure C

Example: 2121 Device returned to normal: EMM 1, Controller 1, Connector 0, Enclosure 2

Alert Message Change History

The following table describes changes made to the Storage Management alerts from the previous release of Storage Management to the current release.

Table 4-3. Alert Message Change History 

Storage Management 2.1

Comments

Product Versions to which Changes Apply

Storage Management 2.1

Server Administrator 2.4

Dell OpenManage™ 5.1

 

New Alerts

2062 (see Note)

2173

2195

2196

2212

2213

2214

2215

2260 (see Note)

The alert numbers for the new alerts were previously unassigned.

NOTE: Alerts 2062 and 2260 were previously undocumented in the Storage Management online help, Dell OpenManage Server Administrator Storage Management User’s Guide, and the Dell OpenManage Server Administrator Messages Reference Guide.

Modified Alerts

2049, 2050, 2051, 2052, 2065, 2074, 2080, 2083, 2089, 2092, 2141, 2158, 2249, 2251, 2252, 2255, 2269, 2270, 2274, 2303, 2305, 2309, 2361, 2362, 2363

The term “array disk” has been changed to “physical disk” throughout Storage Management. This change affects the message text of the modified alerts.

Obsolete Alerts

2160

2161

2160 replaced by 2195.

2161 replaced by 2196.

Documentation Changes

Documentation updated to indicate clear alert status.

Reference to SNMP trap variables removed.

Corresponding Array Manager event numbers removed (see comments).

Starting with Dell OpenManage 5.0, Array Manager is no longer an installable option. If you have an Array Manager installation and wish to see how the Array Manager events correspond to the Storage Management alerts, refer to the product documentation prior to Storage Management 2.1 or Dell OpenManage 5.1.

Alert Descriptions and Corrective Actions

The following sections describe alerts generated by the RAID or 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 Dell OpenManage Server Administrator Storage Management management information base (MIB). The SNMP traps for these alerts use all of the SNMP trap variables. For more information on SNMP support and the MIB, see the SNMP Reference Guide.

To locate an alert, scroll through the following table to find the alert number displayed on the Server Administrator Alert tab or search this file for the alert message text or number. See "Understanding Event Messages" for more information on severity levels.

For more information regarding alert descriptions and the appropriate corrective actions, see the online help.

Table 4-4. Storage Management Messages 

Event ID

Description

Severity

Cause and Action

Clear Event Number

SNMP Trap Numbers

2048

Device failed

Critical / Failure / Error

Cause: A storage component such as a physical 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 disk has failed by locating the disk that has a red “X” for its status. Perform a rescan after replacing the disk.

2121

754
804
854
904
954
1004
1054
1104
1154
1204

2049

Physical disk removed

Warning / Non-critical

Cause: 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.

Action: If a physical disk was removed from the disk group, either replace the disk or restore the original disk. On some controllers, a removed disk has a red "X" for its status. On other controllers, a removed disk may have an Offline status or is not displayed on the user interface. Perform a rescan after replacing or restoring the disk. If a disk has not been removed from the disk group, 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.

2052

903

2050

Physical disk offline

Warning / Non-critical

Cause: A physical disk in the disk group is offline. A user may have manually put the physical disk offline.

Action: Perform a rescan. You can also select the offline disk and perform a Make Online operation.

2158

903

2051

Physical disk degraded

Warning / Non-critical

Cause: 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 consistency check or other operation.

Action: Replace the degraded physical 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.

None

903

2052

Physical disk inserted

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

901

2053

Virtual disk created

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1201

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

None

1203

2055

Virtual disk configuration changed

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1201

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.

None

1204

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 an Expandable RAID Controller (PERC) 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 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.

None

1203

2058

Virtual disk check consistency started

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

2085

1201

2059

Virtual disk format started

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

2086

1201

2061

Virtual disk initialization started

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

2088

1201

2062

Physical disk initialization started

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

2089

901

2063

Virtual disk reconfiguration started

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

2090

1201

2064

Virtual disk rebuild started

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

2091

1201

2065

Physical disk rebuild started

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

2092

901

2067

Virtual disk check consistency cancelled

Ok / Normal

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.

None

1201

2070

Virtual disk initialization cancelled

Ok / Normal

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 physical disk operation. Restart the virtual disk initialization.

None

1201

2074

Physical disk rebuild cancelled

Ok / Normal

Cause: A user has cancelled the rebuild operation.

Action: Restart the rebuild operation.

None

901

2076

Virtual disk check consistency failed

Critical / Failure / Error

Cause: A physical disk included in the virtual disk failed or there is an error in the parity information. A failed physical disk can cause errors in parity information.

Action: Replace the failed physical disk. You can identify which disk has failed by locating the disk that has a red “X” for its status. Rebuild the physical disk. When finished, restart the check consistency operation.

None

1204

2077

Virtual disk format failed.

Critical / Failure / Error

Cause: A physical disk included in the virtual disk failed.

Action: Replace the failed physical disk. You can identify which physical disk has failed by locating the disk that has a red "X" for its status. Rebuild the physical disk. When finished, restart the virtual disk format operation.

None

1204

2079

Virtual disk initialization failed

Critical / Failure / Error

Cause: A physical disk included in the virtual disk has failed or a user has cancelled the initialization.

Action: If a physical disk has failed, then replace the physical disk.

None

1204

2080

Physical disk initialize failed

Critical / Failure / Error

Cause: The physical 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.

None

904

2081

Virtual disk reconfiguration failed

Critical / Failure / Error

Cause: A physical 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 physical disk is part of a redundant array, then rebuild the physical disk. When finished, restart the reconfiguration.

None

1204

2082

Virtual disk rebuild failed

Critical / Failure / Error

Cause: A physical 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.

None

1204

2083

Physical disk rebuild failed

Critical / Failure / Error

Cause: A physical 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.

None

904

2085

Virtual disk check consistency completed

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

Clear event

1201

2086

Virtual disk format completed

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

Clear event

1201

2088

Virtual disk initialization completed

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

Clear event

1201

2089

Physical disk initialize completed

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

Clear event

901

2090

Virtual disk reconfiguration completed

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

Clear event

1201

2091

Virtual disk rebuild completed

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

Clear event

1201

2092

Physical disk rebuild completed

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

Clear event

901

2094

Predictive Failure reported.

Warning / Non-critical

Cause: The physical disk is predicted to fail. Many physical disks contain Self Monitoring Analysis and Reporting Technology (SMART). 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 physical disk. Even though the disk may not have failed yet, it is strongly recommended that you replace the disk.

If this disk is part of a redundant virtual disk, perform the Offline task on the disk; replace the disk; and then assign a hot spare and the rebuild will start automatically.

If this disk is a hot spare, then unassign the hot spare; perform the Prepare to Remove task on the disk; replace the disk; and assign the new disk as a hot spare.

NOTICE: If this disk is part of a nonredundant disk, back up your data immediately. If the disk fails, you will not be able to recover the data.

None

903

2095

SCSI sense data.

Warning / Non-critical

Cause: A physical disk has failed, is corrupt, or is otherwise experiencing a problem.

Action: Replace the physical 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.

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.

NOTICE: If the disk fails, you will not be able to recover the data.

None

903

2098

Global hot spare assigned

Ok / Normal

Cause: A user has assigned a physical disk as a global hot spare. This alert is for informational purposes.

Action: None

None

901

2099

Global hot spare unassigned

Ok / Normal

Cause: A user has unassigned a physical disk as a global hot spare. This alert is for informational purposes.

Action: None

None

901

2100

Temperature exceeded the maximum warning threshold

Warning / Non-critical

Cause: The physical 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 physical disk enclosure documentation for more diagnostic  information.

2353

1053

2101

Temperature dropped below the minimum warning threshold

Warning / Non-critical

Cause: The physical disk enclosure is too cool.

Action: Check if the thermostat setting is too low and if the room temperature is too cool.

2353

1053

2102

Temperature exceeded the maximum failure threshold

Critical / Failure / Error

Cause: The physical 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 physical disk enclosure documentation for more diagnostic information.

None

1054

2103

Temperature dropped below the minimum failure threshold

Critical / Failure / Error

Cause: The physical disk enclosure is too cool.

Action: Check if the thermostat setting is too low and if the room temperature is too cool.

None

1054

2104

Controller battery is reconditioning

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

2105

1151

2105

Controller battery recondition is completed

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

Clear event

1151

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 physical disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk.

NOTICE: 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.

None

903

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 physical disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk.

NOTICE: 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.

None

904

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 physical disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk.

NOTICE: 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.

None

903

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.

Action 1: Determine why the physical 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 physical 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 physical disk enclosure documentation for more diagnostic information.

Action 2: 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.

NOTICE: 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.

None

903

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 physical disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk.

NOTICE: 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.

None

903

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

None

903

2112

Enclosure was shut down

Critical / Failure / Error

Cause: The physical 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.

None

854

2114

A consistency check on a virtual disk has been paused (suspended)

Ok / Normal

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 tree view and select Resume Check Consistency.

2115

1201

2115

A consistency check on a virtual disk has been resumed

Ok / Normal

Cause: This alert is for informational purposes. The check consistency operation on a virtual disk has resumed processing after being paused by a user.

Action: None

Clear event

1201

2116

A virtual disk and its mirror have been split

Ok / Normal

Cause: This alert is for informational purposes. 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: None

None

1201

2117

A mirrored virtual disk has been unmirrored

Ok / Normal

Cause: This alert is for informational purposes. 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 a physical disk and becomes available for inclusion in another virtual disk.

Action: None

None

1201

2118

Change write policy

Ok / Normal

Cause: This alert is for informational purposes. A user has changed the write policy for a virtual disk.

Action: None

None

1201

2120

Enclosure firmware mismatch

Warning / Non-critical

Cause: The firmware on the EMM 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.

None

853

2121

Device returned to normal

Ok / Normal

Cause: This alert is for informational purposes. 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: None

Clear event

752
802
852
902
952
1002
1052
1102
1152
1202

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.

2124

1305

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 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.

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

1306

2124

Redundancy normal

Ok / Normal

Cause: This alert is for informational purposes. Data redundancy has been restored to a virtual disk or an enclosure that previously suffered a loss of redundancy.

Action: None

Clear event

1304

2126

SCSI sense sector reassign

Warning / Non-critical

Cause: A sector of the physical disk is corrupted and data cannot be maintained on this portion of the disk. This alert is for informational purposes.

NOTICE: Any data residing on the corrupt portion of the disk may be lost and you may need to restore your data from backup.

Action: If the physical disk is part of a nonredundant virtual disk, then back up the data and replace the physical disk.

NOTICE: Removing a physical disk that is included in a nonredundant virtual disk will cause the virtual disk to fail and may cause data loss.

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.

None

903

2127

Background initialization (BGI) started

Ok / Normal

Cause: BGI of a virtual disk has started. This alert is for informational purposes.

Action: None

2130

1201

2128

BGI cancelled

Ok / Normal

Cause: BGI of a virtual disk has been cancelled. A user or the firmware may have stopped BGI.

Action: None

None

1201

2129

BGI failed

Critical / Failure / Error

Cause: BGI of a virtual disk has failed.

Action: None

None

1204

2130

BGI completed

Ok / Normal

Cause: BGI of a virtual disk has completed. This alert is for informational purposes.

Action: None

Clear event

1201

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.

None

753

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.

None

753

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.

None

103

2136

Virtual disk initialization

Ok / Normal

Cause: This alert is for informational purposes. Virtual disk initialization is in progress.

Action: None

2088

1201

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. These variables are: Controller and enclosure names, 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 EMMs are each running the same version of supported firmware.

2162

853

2138

Enclosure alarm enabled

Ok / Normal

Cause: This alert is for informational purposes. A user has enabled the enclosure alarm.

Action: None

None

851

2139

Enclosure alarm disabled

Ok / Normal

Cause: A user has disabled the enclosure alarm.

Action: None

None

851

2140

Dead disk segments restored

Ok / Normal

Cause: This alert is for informational purposes. Disk space that was formerly “dead” or inaccessible to a redundant virtual disk has been restored.

Action: None

None

1201

2141

Physical disk dead segments recovered

Ok / Normal

Cause: This alert is for informational purposes. Portions of the physical disk were formerly inaccessible. The disk space from these dead segments has been recovered and is now usable. Any data residing on these dead segments has been lost.

Action: None

None

901

2142

Controller rebuild rate has changed

Ok / Normal

Cause: This alert is for informational purposes. A user has changed the controller rebuild rate.

Action: None

None

751

2143

Controller alarm enabled

Ok / Normal

Cause: This alert is for informational purposes. A user has enabled the controller alarm.

Action: None

None

751

2144

Controller alarm disabled

Ok / Normal

Cause: This alert is for informational purposes. A user has disabled the controller alarm.

Action: None

None

751

2145

Controller battery low

Warning / Non-critical

Cause: The controller battery charge is low.

Action: Recondition the battery. See the online help for more information

None

1153

2146

Bad block replacement error

Warning / Non-critical

Cause: A portion of a physical disk is damaged.

Action: See the Dell OpenManage Server Administrator Storage Management online help or the Dell OpenManage Server Administrator Storage Management User's Guide for more information.

None

753

2147

Bad block sense
error

Warning / Non-critical

Cause: A portion of a physical disk is damaged.

Action: See the Dell OpenManage Server Administrator Storage Management online help for more information.

None

753

2148

Bad block medium error

Warning / Non-critical

Cause: A portion of a physical disk is damaged.

Action: See the Dell OpenManage Server Administrator Storage Management online help for more information.

None

753

2149

Bad block extended sense error

Warning / Non-critical

Cause: A portion of a physical disk is damaged.

Action: See the Dell OpenManage Server Administrator Storage Management online help for more information.

None

753

2150

Bad block extended medium error

Warning / Non-critical

Cause: A portion of a physical disk is damaged.

Action: See the Dell OpenManage Server Administrator Storage Management online help for more information.

None

753

2151

Asset tag changed

Ok / Normal

Cause: This alert is for informational purposes. A user has changed the enclosure asset tag.

Action: None

None

851

2152

Asset name changed

Ok / Normal

Cause: This alert is for informational purposes. A user has changed the enclosure asset name.

Action: None

None

851

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.

None

753

2154

Maximum temperature probe warning threshold value changed

Ok / Normal

Cause: This alert is for informational purposes. A user has changed the value for the maximum temperature probe warning threshold.

Action: None

None

1051

2155

Minimum temperature probe warning threshold value changed

Ok / Normal

Cause: This alert is for informational purposes. A user has changed the value for the minimum temperature probe warning threshold.

Action: None

None

1051

2156

Controller alarm has been tested

Ok / Normal

Cause: This alert is for informational purposes. The controller alarm test has run successfully.

Action: None

None

751

2157

Controller configuration has been reset

Ok / Normal

Cause: This alert is for informational purposes. A user has reset the controller configuration. See the online help for more information.

Action: None

None

751

2158

Physical disk online

Ok / Normal

Cause: This alert is for informational purposes. An offline physical disk has been made online.

Action: None

Clear event

901

2159

Virtual disk renamed

Ok / Normal

Cause: This alert is for informational purposes. A user has renamed a virtual disk.

When renaming a virtual disk on a PERC  3/Si, 3/Di, CERC SATA 1.5/6ch, or CERC SATA 1.5/2s controller, this alert displays the new virtual disk name.

On the PERC 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di, and CERC ATA 100/4ch controllers, this alert displays the original virtual disk name.

Action: None

None

1201

2162

Communication regained

Ok / Normal

Cause: This alert is for informational purposes. Communication with an enclosure has been restored.

Action: None

Clear event

851

2163

Rebuild completed with errors

Ok / Normal

Cause: This alert is for informational purposes.

Action: See the online help for more information.

None

904

2164

See the Readme file for a list of validated controller driver versions

Ok / Normal

Cause: This alert is for informational purposes. Storage Management is unable to determine whether the system has the minimum required versions of the RAID controller drivers.

Action: 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.

None

101

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

None

753

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.

None

753

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 a list of validated kernel and driver versions. Update the system to meet the minimum requirements and then reinstall Storage Management.

None

103

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 validated driver version. Update the system to meet the minimum requirements and then reinstall Storage Management.

None

103

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.

None

1154

2170

The controller battery charge level is normal.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1151

2171

The controller battery temperature is above normal.

Warning / Non-critical

Cause: The battery may be recharging, the room temperature may be too hot, or the fan in the system may be degraded or failed.

Action: If this alert was generated due to a battery recharge, the situation will correct when the recharge is complete. You should also check if the room temperature is normal and that the system components are functioning properly.

2172

1153

2172

The controller battery temperature is normal.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

Clear event

1151

2173

Unsupported configuration detected. The SCSI rate of the enclosure management modules (EMMs) is not the same. EMM0 %1 EMM1 %2

Warning / Non-critical

Cause: The EMMs in the enclosure have a different SCSI rate. This is an unsupported configuration. All EMMs in the enclosure should have the same SCSI rate. The % (percent sign) indicates a substitution variable. The text for this substitution variable is displayed with the alert in the Alert Log and can vary depending on the situation.

Action: The EMMs in the enclosure have a different SCSI rate. This is an unsupported configuration. All EMMs in the enclosure should have the same SCSI rate.

None

853

2174

The controller battery has been removed.

Warning / Non-critical

Cause: The controller cannot communicate with the battery, the battery may be removed, or the contact point between the controller and the battery may be burnt or corroded.

Action: Replace the battery if it has been removed. If the contact point between the battery and the controller is burnt or corroded, you will need to replace either the battery or the controller, or both. See the hardware documentation for information on how to safely access, remove, and replace the battery.

None

1153

2175

The controller battery has been replaced.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1151

2176

The controller battery Learn cycle has started.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

2177

1151

2177

The controller battery Learn cycle has completed.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

Clear event

1151

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. Additionally, 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 as the battery is unable to maintain a full charge.

None

1153

2179

The controller battery Learn cycle has been postponed.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1151

2180

The controller battery Learn cycle will start in %1 days.

Ok / Normal

Cause: This alert is for informational purposes. The %1 indicates a substitution variable. The text for this substitution variable is displayed with the alert in the Alert Log and can vary depending on the situation.

Action: None

None

1151

2181

The controller battery Learn cycle will start in %1 hours.

Ok / Normal

Cause: This alert is for informational purposes. The %1 indicates a substitution variable. The text for this substitution variable is displayed with the alert in the Alert Log and can vary depending on the situation.

Action: None

None

1151

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.

None

754

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 happen if 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.

None

753

2187

Single-bit ECC error limit exceeded.

Warning / Non-critical

Cause: The system memory is malfunctioning.

Action: Replace the battery pack.

None

753

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, the battery is unable to maintain cached data for 24 hours. It is normal to receive this alert during the battery Learn cycle as the Learn cycle discharges the battery before recharging it. When discharged, the battery cannot maintain cached data.

Action: Check the health of the battery. If the battery is weak, replace the battery pack.

None

1153

2189

The controller write policy has been changed to Write Back.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1151

2191

Multiple enclosures are attached to the controller. This is an unsupported configuration.

Critical / Failure / Error

Cause: Many enclosures are 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 exceed.

None

854

2192

The virtual disk Check Consistency has made corrections and completed.

Ok / Normal

Cause: This alert is for informational purposes. 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.

Action: Monitor the battery and cache health to make sure they 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 has problems, replace the battery pack or the disk.

None

1203

2193

The virtual disk reconfiguration has resumed.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1201

2194

The virtual disk Read policy has changed.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1201

2195

Dedicated hot spare assigned. Physical disk %1

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

2196

1201

2196

Dedicated hot spare unassigned. Physical disk %1

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

Clear event

1201

2199

The virtual disk cache policy has changed.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1201

2201

A global hot spare failed.

Warning / Non-critical

Cause: The controller is unable to communicate with a disk that is assigned as a global hot spare. The disk may have failed or has been removed. There may also be a bad or loose cable.

Action: Check if the disk is healthy and that it has not been removed. Check the cables. If necessary, replace the disk and reassign the hot spare.

None

903

2202

A global hot spare has been removed.

Warning / Non-critical

Cause: The controller is unable 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: Check if the disk is healthy and that it has not been removed. Check the cables. If necessary, replace the disk and reassign the hot spare.

None

903

2203

A dedicated hot spare failed.

Warning / Non-critical

Cause: The controller is unable 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: Check if the disk is healthy and that it has not been removed. Check the cables. If necessary, replace the disk and reassign the hot spare.

None

903

2204

A dedicated hot spare has been removed.

Warning / Non-critical

Cause: The controller is unable 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: Check if the disk is healthy and that it has not been removed. Check the cables. If necessary, replace the disk and reassign the hot spare.

None

903

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.

None

903

2206

The only hot spare available is a SATA disk. SATA disks cannot replace SAS disks.

Warning / Non-critical

Cause: 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.

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.

None

903

2207

The only hot spare available is a SAS disk. SAS disks cannot replace SATA disks.

Warning / Non-critical

Cause: 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.

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.

None

903

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, update the firmware to a supported version. If the disk is not supported by Dell, replace the disk with one that is supported.

None

903

2212

The controller battery temperature is above normal.

OK/Normal

Cause: This alert is for informational purposes.

Action: None

None

1151

2213

Recharge count maximum exceeded

Warning / Non-critical

Cause: The battery has been recharged more times than the battery recharge limit allows.

Action: Replace the battery pack.

None

1153

2214

Battery charge in progress

OK/Normal

Cause: This alert is for informational purposes.

Action: None.

None

1151

2215

Battery charge process interrupted

OK/Normal

Cause: This alert is for informational purposes.

Action: None.

None

1151

2232

The controller alarm is silenced.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

751

2233

The background initialization (BGI) rate has changed.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

751

2234

The Patrol Read rate has changed.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

751

2235

The Check Consistency rate has changed.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

751

2237

A controller rescan has been initiated.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

751

2238

The controller debug log file has been exported.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

751

2239

A foreign configuration has been cleared.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

751

2240

A foreign configuration has been imported.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

751

2241

The Patrol Read mode has changed.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

751

2242

The Patrol Read has started.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

2243

751

2243

The Patrol Read has stopped.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

Clear event

751

2244

A virtual disk blink has been initiated.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1201

2245

A virtual disk blink has ceased.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1201

2246

The controller battery is degraded.

Warning / Non-critical

Cause: The controller battery charge is weak.

Action: As the charge weakens, the charger should automatically recharge the battery. If the battery has reached its recharge limit, replace the battery pack. Monitor the battery to make sure that it recharges successfully. If the battery does not recharge, replace the battery pack.

None

1153

2247

The controller battery is charging.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

2358

1151

2248

The controller battery is executing a Learn cycle.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1151

2249

The physical disk Clear operation has started.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

901

2251

The physical disk blink has initiated.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

901

2252

The physical disk blink has ceased.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

901

2254

The Clear operation has cancelled.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

901

2255

The physical disk has been started.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

901

2259

An enclosure blink operation has initiated.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

2260

851

2260

An enclosure blink has ceased

OK/Normal

Cause: This alert is for informational purposes.

Action: None.

None

851

2261

A global rescan has initiated.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

101

2262

SMART thermal shutdown is enabled.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

101

2263

SMART thermal shutdown is disabled.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

101

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: Check if the device is in and not removed. If it is in, 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.

None

753
803
853
903
953
1003
1053
1103
1153
1203

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. Check if 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.

None

753
803
853
903
953
1003
1053
1103
1153
1203

2266

Controller log file entry: %1

Ok / Normal

Cause: This alert is for informational purposes. The %1 indicates a substitution variable. The text for this substitution variable is generated by the controller and is displayed with the alert in the Alert Log. This text can vary depending on the situation.

Action: None

None

751

2267

The controller reconstruct rate has changed.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

751

2268

%1, Storage Management has lost communication with the controller. An immediate reboot is strongly recommended to avoid further problems. If the reboot does not restore communication, then contact technical support for more information.

Critical / Failure / Error

Cause: Storage Management has lost communication with a controller. This may occur if the controller driver or firmware is experiencing a problem. The %1 indicates a substitution variable. The text for this substitution variable is displayed with the alert in the Alert Log and can vary depending on the situation.

Action: Reboot the system. If the problem is not resolved, contact technical support. See your system documentation for information about contacting technical support by using telephone, fax, and Internet services.

None

104

2269

The physical disk Clear operation has completed.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

901

2270

The physical disk Clear operation failed.

Critical / Failure / Error

Cause: 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 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. See the online help for more information on checking the cables. Restart the Clear task.

None

904

2271

The Patrol Read corrected a media error.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

901

2272

Patrol Read found an uncorrectable media error.

Critical / Failure / Error

Cause: The Patrol Read task has faced an error that cannot be corrected. There may be a bad disk block that cannot be remapped.

Action: Replace the physical disk to avoid future data loss.

None

903

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 to maintain consistency in disk block addressing. Data has been lost.

Action: Restore from backup.

None

904

2274

The physical disk rebuild has resumed.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

901

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.

None

903

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.

None

903

2278

The controller battery charge level is below a normal threshold.

Ok / Normal

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: Check if 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, replace the battery pack.

None

1154

2279

The controller battery charge level is above a normal threshold.

Ok / Normal

Cause: This alert is for informational purposes. This alert indicates that the battery is recharging during the battery Learn cycle.

Action: None

None

1151

2280

A disk media error has been corrected.

Ok / Normal

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.

None

1201

2281

Virtual disk has inconsistent data.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1201

2282

Hot spare SMART polling failed.

Critical / Failure / Error

Cause: The controller firmware attempted a SMART polling on the hot spare but was unable to complete it. The controller has lost communication with the hot spare.

Action: Check 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. See the Cables Attached Correctly section in the Dell OpenManage Server Administrator Storage Management User’s Guide for more information on checking the cables.

None

904

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. Make sure both EMMs are healthy.

2284

903

2284

A redundant path has been restored.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

Clear event

901

2285

A disk media error was corrected during recovery.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

901

2286

A Learn cycle start is pending while the battery charges.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1151

2287

The Patrol Read is paused.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

2288

751

2288

The patrol read has resumed.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

Clear event

751

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, usually indicates data loss. In some cases, if the multi-bit error occurs during a read operation, the data on the disk may be correct/valid. If the multi-bit error occurs during a write operation, data loss has occurred.

Action: Replace the dual in-line memory module (DIMM). The DIMM is a part of the controller battery pack. See your hardware documentation for information on replacing the DIMM. You may need to restore data from backup.

None

754

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

None

753

2291

An EMM has been discovered.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

851

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.

2162

854

2293

The EMM has failed.

Critical / Failure / Error

Cause: 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.

None

854

2294

A device has been inserted.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

752
802
852
902
952
1002
1052
1102
1152
1202

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.

None

754
804
854
904
954
1004
1054
1104
1154
1204

2296

An EMM has been inserted.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

851

2297

An 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.

None

854

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, etc.

Action: See the hardware documentation for more information.

None

853

2299

Bad PHY %1

Critical / Failure / Error

Cause: There is a problem with a physical connection or PHY. The %1 indicates a substitution variable. The text for this substitution variable is displayed with the alert in the Alert Log and can vary depending on the situation.

Action: Run the PHY integrity test diagnostics. Replace the EMM that contains the bad PHY if necessary. See the hardware documentation for information on replacing the EMM. Make sure the cables are attached securely. See the "Cables Attached Correctly" section in the Dell OpenManage Server Administrator Storage Management User’s Guide for more information on checking the cables. If necessary, attach the storage to a different connector if one is available.

None

854

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: 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.

None

854

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: Check the health of the enclosure and its components. Replace any hardware that is in a Failed state. See the hardware documentation for more information.

None

854

2302

The enclosure is not responding.

Critical / Failure / Error

Cause: The enclosure or an enclosure component is in a Failed or Degraded state.

Action: Check the health of the enclosure and its components. Replace any hardware that is in a Failed state. See the hardware documentation for more information.

None

854

2303

The enclosure cannot support both SAS and SATA physical disks. Physical disks may be disabled.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

851

2304

An attempt to hot plug an EMM has been detected. This type of hot plug is not supported.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

751

2305

The physical disk is too small to be used for a rebuild.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

901

2306

Bad block table is 80% full.

Warning / Non-critical

Cause: The bad block table is 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, and 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.

None

903

2307

Bad block table is full. Unable to log block %1

Critical / Failure / Error

Cause: The bad block table is 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 and disk errors can no longer be corrected. At this point, data loss can occur. The %1 indicates a substitution variable. The text for this substitution variable is displayed with the alert in the Alert Log and can vary depending on the situation.

Action: Replace the disk generating this alert. If necessary, restore your data from backup.

None

904

2309

A physical 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: See the hardware documentation for information on replacing disks.

None

903

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 multiple physical disks. 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 redundancy.

Action: Replace the failed disks and restore from backup.

None

1204

2311

The firmware on the 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 if you attempt to insert an EMM module that has a different firmware version than an existing module. The %1 and %2 indicate a substitution variable. The text for these substitution variables is displayed with the alert in the Alert Log and can vary depending on the situation.

Action: Upgrade to the same version of the firmware on both EMM modules.

None

853

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.

2325

1003

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.

2323

1003

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. Also, you may need to reinstall Storage Management or Server Administrator because of some missing installation components.

None

104

2315

Diagnostic message %1

Ok / Normal

Cause: This alert is for informational purposes. The %1 indicates a substitution variable. The text for this substitution variable is generated by the utility that ran the diagnostics and is displayed with the alert in the Alert Log. This text can vary depending on the situation.

Action: None

None

751

2316

Diagnostic message %1

Critical / Failure / Error

Cause: A diagnostics test failed. The %1 indicates a substitution variable. The text for this substitution variable is generated by the utility that ran the diagnostics and is displayed with the alert in the Alert Log. This text can vary depending on the situation.

Action: See the documentation for the utility that ran the diagnostics for more information.

None

754

2317

BGI terminated due to loss of ownership in a cluster configuration.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1201

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.

None

1154

2319

Single-bit ECC error. The 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. See your hardware documentation for information on replacing the DIMM.

None

753

2320

Single-bit ECC error. The 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. See your hardware documentation for information on replacing the DIMM.

None

754

2321

Single-bit ECC error. The DIMM is critically degraded. There will be no further reporting.

Critical / Failure / Error

Cause: The 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. See your hardware documentation for information on replacing the DIMM.

None

754

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 if the power switch is turned off. If it is turned off, turn it on. If the problem persists, check if the power cord is attached and functional. If the problem is still not corrected or if the power switch is already turned on, replace the power supply unit.

2323

1004

2323

The power supply is switched on.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

Clear event

1001

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.

2325

1004

2325

The power supply cable has been inserted.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

Clear event

1001

2326

A foreign configuration has been detected.

Ok / Normal

Cause: This alert is for informational purposes. The controller has physical disks that were moved from another controller. These physical disks contain virtual disks that were created on the other controller. See the Import Foreign Configuration and Clear Foreign Configuration section in the Dell OpenManage Server Administrator Storage Management User’s Guide for more information.

Action: None

None

751

2327

The NVRAM has corrupted data. The controller is reinitializing the NVRAM.

Warning / Non-critical

Cause: 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.

Action: None. The controller is taking the required corrective action. If this alert is generated often (such as during each reboot), replace the controller.

None

753

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.

None

753

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. The %1 indicates a substitution variable. The text for this substitution variable is generated by the controller and is displayed with the alert in the Alert Log. This text can vary depending on the situation.

Action: Make sure the cables are attached securely. If the problem persists, replace the cable with a valid cable according to SAS specifications. If the problem still persists, you may need to replace some devices such as the controller or EMM. See the hardware documentation for more information.

None

753

2330

SAS port report: %1

Ok / Normal

Cause: This alert is for informational purposes. The %1 indicates a substitution variable. The text for this substitution variable is generated by the controller and is displayed with the alert in the Alert Log. This text can vary depending on the situation.

Action: None

None

751

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 and 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.

None

903

2332

A controller hot plug has been detected.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

751

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. Check the health of the enclosure and its components. Replace any component that is failed.

None

853

2334

Controller event log: %1

Ok / Normal

Cause: This alert is for informational purposes. The %1 indicates a substitution variable. The text for this substitution variable is generated by the controller and is displayed with the alert in the Alert Log. This text is from events in the controller event log that were generated while Storage Management was not running. This text can vary depending on the situation.

Action: None

None

751

2335

Controller event log: %1

Warning / Non-critical

Cause: The %1 indicates a substitution variable. The text for this substitution variable is generated by the controller and is displayed with the alert in the Alert Log. This text is from events in the controller event log that were generated while Storage Management was not running. This text can vary depending on the situation.

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. Check the health of the storage components. See the hardware documentation for more information.

None

753

2336

Controller event log: %1

Critical / Failure / Error

Cause: The %1 indicates a substitution variable. The text for this substitution variable is generated by the controller and is displayed with the alert in the Alert Log. This text is from events in the controller event log that were generated while Storage Management was not running. This text can vary depending on the situation.

Action: See the hardware documentation for more information.

None

754

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: Check if the battery is charged and in good health. When the battery charge is unacceptably low, it cannot maintain cached data. Check if the battery has reached its recharge limit. The battery may need to be recharged or replaced.

None

1154

2338

The controller has recovered cached data from the BBU.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1151

2339

The factory default settings have been restored.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

751

2340

The BGI completed with uncorrectable errors.

Critical / Failure / Error

Cause: The BGI 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.

Action: Replace the physical disk that contains the disk errors. Review other alert messages to identify 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 may need to recreate the virtual disk after replacing the physical disk. After replacing the physical disk, run Check Consistency to check the data.

None

1204

2341

The Check Consistency made corrections and completed.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None

None

1201

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, check the health of the physical disks included in the virtual disk. Review the alert messages for significant alerts related to the physical disks. If you suspect that a physical disk has a problem, replace it and restore from backup.

None

1203

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.

None

1203

2344

The virtual disk initialization terminated.

Warning / Non-critical

Cause: A user has cancelled the virtual disk initialization.

Action: Restart the initialization.

None

1203

2345

The virtual disk initialization failed.

Critical / Failure / Error

Cause: The controller cannot communicate with the attached devices. A disk may be removed or contain errors. The cables may also be loose or defective.

Action: Check the health of attached devices. Review the Alert Log for significant events and make sure the cables are attached securely. See the Cables Attached Correctly section in the Dell OpenManage Server Administrator Storage Management User’s Guide for more information on checking the cables.

None

1204

2346

Error occurred: %1

Warning / Non-critical

Cause: A physical device may have an error. The %1 indicates a substitution variable. The text for this substitution variable is generated by the firmware and is displayed with the alert in the Alert Log. This text can vary depending on the situation.

Action: Verify the health of attached devices. Review the Alert Log for significant events. Run the PHY integrity diagnostic tests. You may need to replace faulty hardware. Make sure the cables are attached securely. See the hardware documentation for more information.

None

903

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.

None

904

2348

The rebuild failed due to errors on the target physical disk.

Critical / Failure / Error

Cause: You are attempting to rebuild data on a disk that is defective.

Action: Replace the target disk. If a rebuild does not automatically start after replacing the disk, initiate the Rebuild task. You may need to assign the new disk as a hot spare to initiate the rebuild.

None

904

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 and data redundancy may also be lost.

Action: Replace the disk.

None

904

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.

None

904

2351

A physical disk is marked as missing.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

2352

901

2352

A physical disk that was marked as missing has been replaced.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

Clear event

901

2353

The enclosure temperature has returned to normal.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

Clear event

851

2354

Enclosure firmware download in progress.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

None

851

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, check if the controller can communicate with the enclosure. Make sure that the enclosure is powered on. Check the cables. Check the health of the enclosure and its components.

To check 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.

None

853

2356

SAS SMP communications error %1.

Critical / Failure / Error

Cause: The %1 indicates a substitution variable. The text for this substitution variable is generated by the firmware and is displayed with the alert in the Alert Log. This text 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. Check if the firmware is a supported version.

None

754

2357

SAS expander error: %1

Critical / Failure / Error

Cause: The %1 indicates a substitution variable. The text for this substitution variable is generated by the firmware and is displayed with the alert in the Alert Log. This text can vary depending on the situation.

Action: There may be a problem with the enclosure. Check the health of the enclosure and its components. by selecting 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.

None

754

2358

The battery charge cycle is complete.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

None

1151

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.

None

903

2360

A user has discarded data from the controller cache.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

None

751

2361

Physical 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

Cause: This alert is for informational purposes.

Action: None.

None

751

2362

Physical disk(s) have been removed from a virtual disk. The virtual disk will be in Failed state during the next system reboot.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

None

751

2363

A virtual disk and all of its member physical disks have been removed while the system was shut down. This removal was discovered during system start-up.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

None

751

2364

All virtual disks are missing from the controller. This situation was discovered during system start-up.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

None

751

2365

The speed of the enclosure fan has changed.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

None

851

2366

Dedicated spare imported as global due to missing arrays

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

None

901

2367

Rebuild not possible as SAS/SATA is not supported in the same virtual disk.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

None

901

2368

The SCSI Enclosure Processor (SEP) has been rebooted as part of the firmware download operation and will be unavailable until the operation completes.

Ok / Normal

Cause: This alert is for informational purposes.

Action: None.

None

851