Critical events indicate a problem with the storage subsystem. If you resolve the critical event immediately, you might prevent loss of data access.
When a critical event occurs, it is logged in the . All critical events are sent to the SNMP management console or to the email recipient that you have configured to receive alert notifications by selecting Edit >> Configure Alerts in the Enterprise Management Window.
When you receive a critical event, refer to the Recovery Guru procedure for a detailed description of the critical event. Complete the Recovery Guru procedure to correct the critical event.
This table provides full descriptions and corrective actions for all critical events. If you need to contact a representative, the representative might need information from this table. The storage management software that you are using might not support all of the critical events in this list.
Critical Event Type and Short Description | Full Description | Corrective Action |
---|---|---|
Event 1001 – Channel failed | The controller failed a channel and no longer accesses disk drives on this channel. This condition is typically caused by a disk drive ignoring SCSI protocol on one of the controller disk drive channels. The controller typically fails a channel if the controller issued a reset on a channel. | Select Support >> Recover from Failure to obtain the recovery procedure. Contact a representative to complete this procedure. |
Event 1010 – Impending disk drive failure (PFA) detected | A disk drive has reported that a failure prediction threshold has been exceeded. This event indicates that the disk drive might fail within 24 hours. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 101E – Impending disk drive failure (PFA) detected by controller | A controller has reported that a disk drive failure prediction threshold has been exceeded. This event indicates that the disk drive might fail within 24 hours. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 1207 – Fibre Channel link errors – threshold exceeded | Invalid characters have been detected in the Fibre Channel signal. Possible causes for the error are a degraded laser in a Gigabit Interface Converter (GBIC), a Small Form-factor Pluggable (SFP) transceiver, or a Media Interface Adapter (MIA); damaged or faulty Fibre Channel cables; or poor cable connections between components on the loop. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 1208 – Data rate negotiation failed | The controller cannot auto-negotiate the transfer link rates. The controller considers the link to be down until negotiation is attempted at controller start-of-day or when a signal is detected after a loss of signal. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 1209 – Disk drive channel set to degraded | A disk drive channel status was set to Degraded because of excessive I/O errors or because a representative advised the storage subsystem’s administrator to manually set the disk drive channel status for diagnostic or other support reasons. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 120A – SFP failed | The SFP transceiver on a DS4800 (Models 82, 84, 88)-class controller failed. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 150E – Controller loopback diagnostics failed | The controller cannot initialize the disk drive Fibre Channel loops. Diagnostics have been run identifying a controller problem, and the controller has been placed offline. This event occurs only on certain controller models. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 150F – Channel cabling error | Two or more disk drive channels are connected to the same Fibre Channel loop, which can cause the storage subsystem to behave unpredictably. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 1510 – ESM CRU cabling error | Two ESM CRUs in the same expansion drawer are connected to the same Fibre Channel loop. A level of redundancy has been lost, and the I/O performance for this expansion drawer is reduced. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 1513 – Individual disk drive – degraded path | The specified disk drive channel is experiencing intermittent errors along the path to a single disk drive or to several disk drives. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 1515 – Disk drive channel hardware failed | A disk drive channel has failed on a controller. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 151A – Optical link speed detection failure | The automatic negotiation for the data rate on the specified port has failed. The port is not operational and does not transfer any data. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 151E – Controller cabling error for disk drive channel occurred | Both ESM CRUs in the expansion drawer are connected to the same controller. The alternate controller is not able to access the data on the expansion drawer if the connected controller fails. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 1521 – Controller loop-back diagnostic failed | The loop or minihub diagnostics detected that the controller is the bad device on the loop. | |
Event 1522 – Drive expansion enclosure type miswire | An unsupported mix of expansion drawer types is attached to the same disk drive channel. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 1600 – Uncertified disk drive detected | An uncertified disk drive has been inserted into the storage subsystem, which is indicated by the word “uncertified” next to the disk drive status. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 1601 – Reserved blocks on ATA disk drives cannot be discovered | Reserved blocks on the ATA disk drives are not recognized. | Contact a representative to complete this procedure. |
Event 1650 – SAS cabling error, controller host port to expansion drawer | The SAS controller host connector has been cabled to the expansion drawer. The Event Log includes this information for correcting
the cabling error:
|
Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 1652 – SAS source driver partner initiator overflow | The SAS source driver detects an initiator overflow condition. As a result of the condition, the partner controller is unable to communicate with the SAS back-end elements. | |
Event 1654 – Host wide port is degraded | One of the host port physical devices is not in Optimal status. | |
Event 1700 – SAS cabling error, invalid topology | The controller detected a cabling error. The Event Log includes this information for correcting the cabling error:
|
Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 1702 – SAS cabling error, HBA connected to controller expansion connector | The HBA has been cabled to the controller expansion connector. The Event Log includes this information for correcting the
cabling error:
|
Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 1704 – SAS cabling error, ESM cabling error | Two environmental services monitor (ESM) CRUs in the same expansion drawer have been cabled together. The Event Log includes
this information for correcting the cabling error:
|
Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 1706 – Optimal wide port becomes degraded | A SAS port has been marked as degraded. | A degraded port is usually caused by a faulty cable, environmental services monitor (ESM), controller, disk drive, or enclosure connector. Analysis of the PHY error logs might help to isolate the problem and to indicate which component must be replaced. |
Event 1707 – Degraded wide port becomes Failed | A SAS port has been marked as failed. | A degraded port is usually caused by a faulty cable, environmental services monitor (ESM), controller, disk drive, or enclosure connector. Analysis of the PHY error logs might help to isolate the problem and to indicate which component must be replaced. |
Event 170A – SAS cabling error, expansion drawer cabling error | The expansion drawer detected a cabling error. The Event Log includes this information for correcting the cabling error:
|
Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 170D – SAS device address limit exceeded | More SAS devices have been discovered than can be successfully addressed by the SAS chip. The hardware device index table size has been exceeded. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 170E – SAS device limit exceeded includes partner | More SAS devices have been discovered than can be successfully addressed by the SAS chip. The hardware device index table size has been exceeded. The missing device is the partner controller. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 180A – Failed I/O host card | The firmware detected an iSCSI interface error. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 1904 – Failed host interface card | The host interface card failed a loopback diagnostic test. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 200A – Data/parity mismatch on logical drive | A data/parity mismatch was detected during data scrubbing. | |
Event 202E – Read disk drive error during interrupted write | A unrecoverable read error was detected. | Any lost data can be recovered only from backups. |
Event 2035 – Redundancy not consistent | ||
Event 203B – Disk drive failed due to unrecoverable read error during scan | A disk drive failed due to an unrecoverable read error that was detected during the scan cycle. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 203C – RAID level not supported | Within the adopted configuration database, disk drives are present from one or several arrays that have a RAID level that the combination of the controller model and the controller firmware cannot support. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2042 – Unsuccessful isolation of redundancy mismatch | A redundancy mismatch was not isolated. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2043 – Threshold exceeded during successful mismatch correction | A redundancy mismatch was corrected, but it required more attempts than the set threshold. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2109 – Controller cache not enabled - cache sizes do not match | The controller does not allow mirroring to be enabled if the alternate controller’s cache size is different. | Make sure that both controllers have the same cache size. Contact a representative to complete this procedure. |
Event 210C – Controller cache battery failed | The controller has detected that the battery is not physically present, is fully discharged, or has reached the expiration date. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 210E – Controller cache memory recovery failed after power cycle or reset | Correcting a data cache error was not successful. User data might have been lost. | Contact a representative to complete this procedure. |
Event 2110 – Controller cache memory initialization failed | The controller has detected the failure of an internal controller component (RAID buffer). This failure might have been detected during operation as well as during an on-board diagnostic routine. | Contact a representative to complete this procedure. |
Event 2113 – Controller cache battery nearing expiration | The cache battery is within the specified number of weeks before failing. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 211B – Batteries present but NVSRAM configured for no batteries | A battery is present in the storage subsystem, but the NVSRAM is set not to include batteries. | Contact a representative to complete this procedure. |
Event 211E – Current cache size is unsupported | A controller is configured with an unsupported cache memory size. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 211F – Insufficient cache backup device capacity | The cache backup device is missing, leaving insufficient capacity to perform a full cache backup. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2120 – Insufficient processor memory for cache | The controller has insufficient processor memory to support the configured cache. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2124 – Dedicated mirror channel failed | The dedicated mirror channel failed. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2125 – Integrity check failed during cache restore | A data integrity check failed when the cache data was being restored from the backup device. | None. |
Event 2126 – Backup of cache to persistent device did not complete | The backup of the cache did not complete before the controller lost both input power and battery backup power. | None. |
Event 2128 – Cache backup data set loss | No cache data (battery-backed or persistently backed) can be recovered from either controller. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 222D – Disk drive manually failed | A user manually failed the disk drive. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2248 – Disk drive failed – write failure | The disk drive failed a write command that was written to it. The disk drive is marked as failed. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2249 – Disk drive capacity less than minimum | During disk drive replacement, the capacity of the disk drive is not large enough to support all the logical drives that must be reconstructed on it. | Replace the disk drive with a larger capacity disk drive. |
Event 224A – Disk drive has wrong block size | The block size of the disk drive does not match that of the other disk drives in the logical drive. The disk drive is marked as failed. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 224B – Disk drive failed – initialization failure | The disk drive failed either a Format Unit command or a Write operation (issued when a logical drive was initialized). The disk drive is marked as failed. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 224D – Disk drive failed – no response at start of day | The disk drive failed a Read Capacity command or a Read command during the start-of-day routine. The controller was unable to read the configuration information stored on it. The disk drive is marked as failed. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 224E – Disk drive failed – initialization/reconstruction failure | The previously failed disk drive was marked as failed. This event occurs during initialization when the disk drive fails a Format Unit. This event occurs during reconstruction when the controller was not able to restore the disk drive. An example of the reconstruction event is that an error occurred on another disk drive required for reconstruction. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2250 – Logical drive failure | The controller has marked the logical drive as failed. User data, redundancy (parity), or both can no longer be maintained to make sure availability. The most likely cause is the failure of a single disk drive in nonredundant configurations or a second disk drive in a configuration protected by one disk drive. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2251 – Disk drive failed – reconstruction failure | A disk drive failed due to a reconstruction failure during the start-of-day routine. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2252 – Disk drive marked offline during interrupted write | An error has occurred during interrupted write processing, which caused the logical drive to be marked as failed. Disk drives in the array that did not experience the read error transition to the Offline state and log this error. | Select Support >> Recover from Failure to obtain the recovery procedure. Contact a representative to complete this procedure. |
Event 2260 – Uncertified disk drive | A disk drive in the storage subsystem is uncertified. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2262 – Configuration wrong disk drive type | A disk drive assigned to an array has failed. The failed disk drive was removed and replaced with a disk drive that is not the same disk drive type as the failed disk drive. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2266 – Logical drive modification operation failed | A disk drive failed during a reconfiguration operation, which caused the failure of all of the logical drives in the array. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2267 – Incompatible disk drive due to invalid configuration on disk drive | A disk drive transitioned to the incompatible state due to an invalid array configuration. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 226B – FDE lock key needed | A Full Disk Encryption (FDE) security key is needed for the controllers to communicate with the security-enabled disk drives. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 226C – Disk drive failure | A disk drive failure has been detected. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 226D – Disk drive in array or hot spare in use removed | A disk drive that was assigned to an array or a hot spare disk drive that was in use has been removed. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2500 – Controller removed | A controller was removed from a storage subsystem that is configured to use dual controllers. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2602 – Automatic controller firmware synchronization failed | The versions of firmware on the redundant controllers are not the same because the automatic controller firmware synchronization failed. Controllers with an incompatible version of firmware might cause unexpected results. | Contact a representative to complete this procedure. |
Event 2607 – FDE inconsistent storage subsystem lock key | An inconsistent storage subsystem security key situation has been detected. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2704 – RPA corruption detected | RAID Parity Assist (RPA) corruption has been detected. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2801 – Storage subsystem running on UPS battery | The uninterruptible power supply (UPS) has indicated that the AC power is no longer present and that the UPS has switched to the standby power. While there is no immediate cause for concern, you should save your data frequently, in case the battery is suddenly depleted. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2803 – UPS battery – two minutes to failure | The uninterruptible power supply (UPS) has indicated that the standby power source is nearing depletion. | Stop I/O activity to the controller. Usually, the controller changes from a write-back caching mode to a write-through mode. |
Event 2807 – ESM CRU failed | An environmental services monitor (ESM) CRU has failed. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2808 – Enclosure ID not unique | The controller has determined that there are multiple expansion drawers with the same ID selected. Make sure that each expansion drawer has a unique ID setting. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 280A – Controller module component missing | A component other than a controller is missing in the controller module. The missing component type and component location are shown in the Event Log. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 280B – Controller module component failed | A component other than a controller has failed in the controller module. The failed component type and component location are shown in the Event Log. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 280D – Expansion drawer component failed | A component other than a disk drive has failed in the expansion drawer. The failed component type and component location are shown in the Event Log. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 280E – Standby power source not fully charged | The uninterruptible power supply (UPS) has indicated that the standby power source is not at full capacity. | Fully charge the UPS. |
Event 280F – ESM CRU – loss of communication | Communication has been lost to one of the dual environmental services monitor (ESM) CRUs in a expansion drawer. The expansion drawer has only one I/O path available. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2813 – Minihub CRU failed | Communication with the minihub CRU has been lost. This situation might be the result of a minihub CRU failure, a controller failure, or a failure in an internal backplane communications board. If there is only one minihub failure, the storage subsystem is still operational, but a second minihub failure could result in the failure of the affected enclosures. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2815 – GBIC/SFP failed | A Gigabit Interface Converter (GBIC) or a Small Form-factor Pluggable (SFP) transceiver on either the controller module or the expansion drawer has failed. If there is only one GBIC or SFP transceiver failure, the storage subsystem is still operational, but a second GBIC or SFP transceiver failure could result in the failure of the affected enclosures. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2816 – Enclosure ID conflict – duplicate ID across expansion drawers | Two or more expansion drawers are using the same enclosure identification number. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2818 – Enclosure ID mismatch – duplicate ID in the same expansion drawer | A expansion drawer in the storage subsystem contains environmental services monitor (ESM) CRUs with different enclosure identification numbers. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 281B – Nominal temperature exceeded | The nominal temperature of the enclosure has been exceeded. Either a fan has failed or the temperature of the room is too high. If the temperature of the enclosure continues to rise, the affected enclosure might automatically shut down. Fix the problem immediately before it becomes more serious. The automatic shutdown conditions depend on the model of the enclosure. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 281C – Maximum temperature exceeded | The maximum temperature of the enclosure has been exceeded. Either a fan has failed or the temperature of the room is too high. This condition is critical and might cause the enclosure to shut down if you do not correct the problem immediately. The automatic shutdown conditions depend on the model of the enclosure. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 281D – Temperature sensor removed | A fan CRU that contains a temperature sensor has been removed from the storage subsystem. | Replace the CRU as soon as possible. Select Support >> Recover from Failure to obtain the recovery procedure. Use this procedure to correct the failure. |
Event 281E – ESM CRU firmware mismatch | A expansion drawer in the storage subsystem contains environmental services monitor (ESM) CRUs with different versions of firmware. ESM CRUs in the same expansion drawer must have the same version of firmware. | Select Support >> Recover from Failure to obtain the recovery procedure. If you do not have a replacement ESM CRU, contact a representative to complete this procedure. |
Event 2821 – Incompatible minihub | An incompatible minihub CRU has been detected in the controller module. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2823 – Disk drive bypassed | The environmental services monitor (ESM) has reported that the disk drive has been bypassed to maintain the integrity of the Fibre Channel loop. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2827 – Controller inadvertently replaced with an ESM | A controller CRU was inadvertently replaced with an environmental services monitor (ESM) CRU. | Replace the ESM CRU with the controller CRU as soon as possible. |
Event 2828 – Unsupported expansion drawer selected | Your storage subsystem contains one or more unsupported expansion drawers. If all of your expansion drawers are detected as unsupported, you might have a problem with an NVSRAM configuration file, or you might have the wrong version of firmware. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2829 – Controller redundancy lost | Communication has been lost between the two controllers through one of the disk drive loops (channels). | Select Support >> Recover from Failure , and determine if there are other loss-of-redundancy problems being reported. If there are other problems being reported, fix those first. If redundancy problems are still being reported, contact a representative to complete this procedure. |
Event 282B – Expansion drawer path redundancy lost | A expansion drawer with redundant disk drive loops (channels) has lost communication through one of the loops. The enclosure has only one loop available for I/O. Correct this failure as soon as possible. Although the storage subsystem is still operational, a level of path redundancy has been lost. If the remaining disk drive loop fails, all I/O to that enclosure fails. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 282D – Disk drive path redundancy lost | A communication path with a disk drive has been lost. Correct this failure as soon as possible. The disk drive is still operational, but a level of path redundancy has been lost. If the disk drive’s other port or any other component fails on the working channel, the disk drive is marked as failed. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 282F – Incompatible version of ESM firmware detected | A expansion drawer in the storage subsystem contains environmental services monitor (ESM) CRUs with different firmware versions. This error might also be reported if a expansion drawer in the storage subsystem contains ESM CRUs with different hardware. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2830 – Mixed disk drive types not supported | The storage subsystem currently contains disk drives of different disk drive technologies, such as Fibre Channel (FC) and Serial ATA (SATA). Mixing different disk drive technologies is not supported on this storage subsystem. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2831 – Uncertified ESM | The storage subsystem currently contains a expansion drawer in which one or both of the environmental services monitor (ESM) CRUs are uncertified. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2832 – Uncertified expansion drawer detected | The storage subsystem contains one or more unsupported expansion drawers. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2833 – Controller host card ID mismatch | One of the controllers in this storage subsystem is incompatible with the other controller. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2835 – Expansion drawers not cabled together | Some expansion drawers in the storage subsystem are not cabled correctly because they have environmental services monitor (ESM) CRUs that must be cabled sequentially together. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2836 – Discrete lines diagnostic failure | A problem occurred during the discrete lines diagnostics. The discrete lines are dedicated control and status connections between the controllers that reside in the interconnect-battery CRU. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2838 – Interconnect-battery CRU removed | The interconnect-battery CRU has been removed from the controller module. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 283A – Power supply missing or removed | At least one power supply CRU in the storage subsystem has failed or been removed. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 283B – Power supply failed | At least one power supply CRU in the storage subsystem has failed. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 283C – Power supply needs attention | The power supply is degraded. | |
Event 283D – Fan missing or removed | At least one fan CRU in the storage subsystem has failed or been removed. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 283E – Fan failed | At least one fan CRU in the storage subsystem has failed. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 283F – Fan needs attention | The fan is degraded. | |
Event 2841 – Controller submodel mismatch | One of the controllers in this storage subsystem is incompatible with the other controller. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2843 – Switch card diagnostic failure. Controller's host channels are down. | The host switch card in one of the controllers is not functioning correctly. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2844 – Switch card runtime failure. Controller's host channels are down. | The host switch card in one of the controllers is not functioning correctly. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2845 – Switch card warning. Controller's host channels may be degraded. | The host switch card in one of the controllers is not functioning correctly. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2849 – ESM hardware mismatch | A expansion drawer in the storage subsystem contains environmental services monitor (ESM) CRUs with different hardware, such as a mixture of switched and non-switched ESMs or a SATA ESM and a Fibre Channel ESM. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 284B – Link speed (data rate) switch position has changed | A switch on the controller module has been changed while the controller module is powered on. | Restore the link speed switch to the previous setting unless a disk drive channel link speed change is desired. In this case, you must turn off the power to the controller module, and then turn the power back on for the rate change to take effect. A recovery procedure does not exist for this event. |
Event 284C – Enclosure limit exceeded | More enclosures were discovered than can be addressed by the controller. The controller cannot communicate with the additional enclosures or the disk drives. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 284E – Redundant power supply CRUs required | The controller discovered a fan-only CRU when the enclosure requires a fan-power supply CRU. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 284F – Invalid enclosure setting | A expansion drawer attached to the storage subsystem is in split mode. When this setting is detected, the controller cannot communicate with the expansion drawer. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2852 – Factory def mismatch | A expansion drawer in the storage subsystem contains environmental services monitor (ESM) CRUs with different configuration settings. ESM CRUs in the same expansion drawer must have the same configuration settings. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2854 – ESM disk drive bypass | A disk drive has exceeded the error threshold and has been bypassed. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 2855 – Alternate board controller ID cannot be read | The controller cannot read the ID for the alternate controller. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 3019 – Logical drive ownership changed due to failover | The multi-path driver software has changed ownership of the logical drives to the other controller because the multi-path driver could not access the logical drives on the particular path. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 4011 – Logical drive not on preferred path | The controller listed in the Recovery Guru area cannot be accessed. Any logical drives that have this controller assigned as their preferred path are moved to the non-preferred path (alternate controller). | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 5005 – Place controller offline | The controller was placed offline. This event could be caused by the controller failing a diagnostic test. Another cause could be that the controller was manually placed offline. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 5038 – Controller in lockout mode. | Both controllers have been placed in Lockout mode for 10 minutes because password authentication failures have exceeded 10 attempts within a 10-minute period. During the lockout period, both controllers deny all authentication requests. When the 10-minute lockout expires, the controller resets the total authentication failure counter and clears the lockout mode. | Wait 10 minutes for the controller to unlock. |
Event 5040 – Place controller in Service mode | The controller was manually placed in Service mode for diagnostic or recovery reasons. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 5222 – Invalid host OS index detected | A host index has been detected that is considered to be invalid due to an NVSRAM setting. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 5223 – Invalid default OS index detected | The default operating system (OS) index is invalid. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 5402 – Premium feature out of compliance | Premium features have been enabled that have not been purchased. | Contact a representative to purchase additional premium features. |
Event 5403 – Premium feature exceeds limit | The limits of a premium feature have been exceeded. For example, six storage partitions are mapped when only four have been purchased. | Contact a representative to purchase additional premium features. |
Event 5405 – Gold Key – mismatched settings | Each controller in the controller pair has a different NVSRAM bit setting that determines if the controller is subject to Gold Key restrictions. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 5406 – Mixed disk drive types – mismatched settings | Each controller in the controller pair has a different setting for the NVSRAM bit that permits mixed disk drive types as a premium feature. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 5602 – This controller’s alternate failed – time-out waiting for results | This controller initiated diagnostics on the alternate controller but did not receive a reply, which indicates that the diagnostics completed. The alternate controller in this pair has been placed offline. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 560B – ctlrDiag task cannot obtain Mode Select lock | The controller was attempting to run diagnostics and could not secure the test area from other storage subsystem operations. The diagnostics were canceled. | Contact a representative to complete this procedure. |
Event 560C – ctlrDiag task on controller’s alternate cannot obtain Mode Select lock | The alternate controller in this pair attempted to run diagnostics and could not secure the test area from other storage subsystem operations. The diagnostics are canceled. | Contact a representative to complete this procedure. |
Event 560D – Diagnostics read test failed on controller | While running diagnostics, the controller has detected that the information received does not match the expected return for the test. This event could indicate that I/O is not operating correctly or that a mismatch exists in the data being read. The controller was placed offline as result of this failure. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 560E – This controller’s alternate failed diagnostics read test | While running diagnostics on this controller, the alternate controller detected that the information received does not match the expected return for the test. This event could indicate that I/O is not completing or that a mismatch exists in the data being read. The alternate controller in this pair was placed offline as result of this failure. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 560F – Diagnostics write test failed on controller | While running diagnostics, the controller was unable to write data to the test area. This event could indicate that I/O is not operating correctly or that a mismatch exists in the data being written. The controller was placed offline as result of this failure. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 5610 – This controller’s alternate failed diagnostics write test | While running diagnostics on this controller, the alternate controller was unable to write data to the test area. This event could indicate that I/O is not operating correctly or that a mismatch exists in the data being written. The alternate controller in this pair was placed offline as result of this failure. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 5616 – Diagnostics rejected - configuration error on controller | This controller attempted to run diagnostics and could not create the test area necessary for the completion of the tests. The diagnostics were canceled. | Contact a representative to complete this procedure. |
Event 5617 – Diagnostics rejected – configuration error on controller’s alternate | The alternate controller for this controller attempted to run diagnostics and could not create the test area necessary for the completion of the tests. The diagnostics were canceled. | Contact a representative to complete this procedure. |
Event 6101 – Internal configuration database full | Because the amount of data required to store certain configuration data for the maximum number of logical drives has been
underestimated, two types of data might have caused the internal configuration database to become full:
|
Delete one or more flashcopy logical drives from your storage subsystem, remove one or more mirror relationships, or both. |
Event 6107 – This controller’s alternate is non-functional and is being held in reset. | A controller in the storage subsystem has detected that the alternate controller is not functional due to hardware problems. The alternate controller needs to be replaced. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 6200 – FlashCopy repository logical drive threshold exceeded | The flashcopy repository logical drive capacity has exceeded a warning threshold level. If the capacity of the flashcopy repository logical drive becomes full, the associated flashcopy logical drive can fail. If you do not correct this problem, this warning is the last one that you receive before the flashcopy repository logical drive becomes full. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 6201 – FlashCopy repository logical drive full | All of the available capacity of the flashcopy repository logical drive has been used. The failure policy of the flashcopy repository logical drive determines what happens when the flashcopy repository logical drive becomes full. The failure policy can be set to either fail the flashcopy logical drive (default setting) or fail incoming I/O to the base logical drive of the flashcopy logical drive. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 6202 – Failed flashcopy logical drive | Either the associated flashcopy repository logical drive of the flashcopy logical drive is full or the associated base logical drive or flashcopy repository logical drives failed due to one or more disk drive failures on the respective arrays. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 6400 – Dual primary logical drive | Both logical drives have been promoted to primary after a forced role reversal. This event could be reported at controller reset or when a cable from a storage subsystem to a Fibre Channel switch is reinserted after having been removed and the other logical drive has been promoted to primary. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 6401 – Dual secondary logical drive | Both logical drives in the Enhanced Remote Mirroring have been demoted to secondary after a forced role reversal. This event could be reported at controller reset or when a cable from an storage subsystem to a Fibre Channel switch is reinserted after having been removed and the other logical drive has been demoted to secondary. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 6402 – Mirror data unsynchronized | This event might occur because of I/O errors, but other events would be associated with it. One of these other events would be the root cause, which would contain the sense data. A Needs Attention icon appears on both the primary storage subsystem and the secondary storage subsystem of the Enhanced Remote Mirroring pair. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 6503 – Remote logical drive link down | This event is triggered when a cable between one storage subsystem and the remote peer has been disconnected, the Fibre Channel switch has been disconnected, or the peer storage subsystem has reset. This event could result in the Mirror Data Unsynchronized event. The affected remote logical drive shows an Unresponsive icon, and this state is selected in the tool tip of the logical drive. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 6505 – WWID change failed | Mirroring causes a World Wide Identifier (WWID) change to be communicated between storage subsystems. Failure of a WWID change is caused by non-I/O communication errors between one storage subsystem, on which the WWID has changed, and a peer storage subsystem. The affected remote logical drive shows an Unresponsive icon, and this state is selected in the tool tip of the logical drive. | Select Support >> Recover from Failure to obtain the recovery procedure. Use this procedure to correct the failure. The only solution to this failure is to delete the remote logical drive and then to establish another one. |
Event 6600 – VolumeCopy operation failed | A VolumeCopy operation with a status of In Progress has failed. This failure can be caused by a read error on the source logical drive, a write error on the target logical drive, or because of a failure that occurred on the storage subsystem that affects the source logical drive or target logical drive. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 6700 – Unreadable sectors detected - data loss occurred | Unreadable sectors have been detected on one or more logical drives, and data loss has occurred. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 6703 – Overflow in unreadable sector database | The Unreadable Sectors Log has filled to the maximum capacity. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 6800 – Support Recovery Interface activated | This informational notice tells you that the Support Recovery Interface (SPRI) has been activated. | None, but this event could be an indication of a security risk if no one is currently using the SPRI for maintenance. |
Event 6801 – Support Recovery Interface wrong password | This informational notice tells you that an incorrect password has been entered for access to the Support Recovery Interface (SPRI). | None, but this event could be an indication of a security risk if no one is currently using the SPRI for maintenance. |
Event 6900 – Diagnostic data capture available | An unusual event occurred on the controller. This event caused the diagnostic data capture feature to store diagnostic data. | Select Support >> Recover from Failure to obtain the recovery procedure to retrieve the diagnostics data. Contact a representative to complete this procedure. |
Event 7001 – Feature pack key file required | The controller detected that one or more features are enabled that do not meet the current submodel definition. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 7300 – Battery backup unit overheated | The battery backup unit is overheated. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 7301 – Insufficient learned battery capacity | The measured capacity of the battery backup unit is not sufficient to hold cache data for at least 72 hours. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 7305 – Battery has failed | A controller has detected that the cache battery has failed or expired. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 7306 – Battery missing | The cache battery is missing. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 7307 – Battery is near expiration | A controller has detected that a cache battery is near expiration. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 7308 – Battery expired | The cache battery has expired. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 7309 – Battery configuration is mismatched | A controller has detected that a cache battery is present when the storage subsystem is configured to operate without cache batteries. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 730F – Incomplete battery learn cycle | The battery learn cycle was incomplete. | Wait for the battery learn cycle to complete, and repeat the action that produced the error. |
Event 7500 – Persistent cache backup device has failed | The persistent cache backup device has failed. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Solid State Disk - Nearing end of life | A Solid State Disk (SSD) disk drive reports that it is nearing the end of its life. If the disk drive fails, any associated logical drives and arrays will become degraded and might lose data. | Plan to replace the disk drive at your earliest convenience. Select Support >> Recover from Failure to obtain the recovery procedure. |
Solid State Disk - End of life | A Solid State Disk (SSD) disk drive reports that it is at the end of its life. The disk drive could fail at any time. If the disk drive fails, any associated logical drives and arrays will become degraded and might lose data. | Replace the disk drive immediately. Select Support >> Recover from Failure to obtain the recovery procedure. |
Solid State Disk - Out of Compliance | The storage subsystem contains SSD disk drives, but the SSD premium feature is not enabled. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 7501 – Cache backup device is write-protected | Write protection is enabled on the cache backup device. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 7502 – Cache backup device has insufficient capacity | The cache backup device has insufficient capacity for the memory cache. | Select Support >> Recover from Failure to obtain the recovery procedure. |
Event 7503 – Alternate controller is running on backup power | The alternate controller has indicated that it is running on uninterruptible power supply (UPS) power. |