Lenovo Storage events organized by severity
The following table lists all Lenovo Storage events, organized by severity (Information, Warning, and Critical).
| Event Code | Message String | Severity |
|---|---|---|
| FQXDE0100I | Event log cleared | Informational |
| FQXDE0101I | Start of delayed events | Informational |
| FQXDE0102I | End of delayed events | Informational |
| FQXDE0103I | A needs-attention condition was raised by the controller firmware | Informational |
| FQXDE0104I | A needs-attention condition was cleared by the controller firmware | Informational |
| FQXDE0105I | Unknown event occurred that is not found in event configuration table. | Informational |
| FQXDE0106I | A needs-attention condition was suppressed due to event configuration table settings. | Informational |
| FQXDE0107I | An event that would have caused a needs-attention condition was suppressed and now is cleared | Informational |
| FQXDE0108I | All non-alertable events are temporarily being discarded | Informational |
| FQXDE0109I | All events are now being saved and persisted | Informational |
| FQXDE1004I | Error on drive open. | Informational |
| FQXDE100AI | Drive returned CHECK CONDITION | Informational |
| FQXDE100DI | Timeout on drive side of controller | Informational |
| FQXDE1012I | Destination driver error | Informational |
| FQXDE1015I | Incorrect mode parameters modified and saved on drive | Informational |
| FQXDE1016I | Drive returned unrecoverable media error | Informational |
| FQXDE1017I | Fibre channel link down | Informational |
| FQXDE1018I | Fibre channel link up | Informational |
| FQXDE1019I | Extended Fibre Channel link down (more than one minute) | Informational |
| FQXDE101FI | Summary of impending drive failure detected by controller | Informational |
| FQXDE1021I | Slow drive detected by drive performance analyzer. Info for Analysis Purposes | Informational |
| FQXDE1022I | Drive not compared by drive performance analyzer | Informational |
| FQXDE1023I | Drive copy triggered by a controller detected impending drive failure | Informational |
| FQXDE1024I | Start or restart of issuing unmaps to a drive | Informational |
| FQXDE1025I | Completion of all unmap requests to a drive | Informational |
| FQXDE1026I | Abnormal decisions were made for drives undergoing provisioning unmaps, not limited to errors | Informational |
| FQXDE1201I | Fibre channel - LIP reset received | Informational |
| FQXDE1202I | Fibre channel - TGT reset received | Informational |
| FQXDE1203I | Fibre channel - TPRLO reset received | Informational |
| FQXDE1205I | Fibre channel - driver detected error during initialization | Informational |
| FQXDE1206I | Fibre channel link errors continue | Informational |
| FQXDE120BI | SFP changed to Optimal | Informational |
| FQXDE120CI | Fibre channel loopback diagnostic failed | Informational |
| FQXDE120EI | Host-side SFP optimal | Informational |
| FQXDE1300I | InfiniBand channel loopback diagnostic failed | Informational |
| FQXDE1301I | InfiniBand port up | Informational |
| FQXDE1302I | InfiniBand port down | Informational |
| FQXDE1303I | InfiniBand - TGT reset received | Informational |
| FQXDE1400I | Password reset to default | Informational |
| FQXDE1401I | XCopy Lite was disabled | Informational |
| FQXDE1402I | XCopy Lite was enabled | Informational |
| FQXDE1404I | This event indicates that the controller is no longer experiencing excessive reboots | Informational |
| FQXDE1500I | Channel initialization error | Informational |
| FQXDE1501I | Selective LIP reset issued to drive | Informational |
| FQXDE1502I | Selective LIP reset issued to alternate controller | Informational |
| FQXDE1503I | Selective LIP reset issued to IOM (ESM) | Informational |
| FQXDE1507I | Loop port bypass (LPB) issued to drive | Informational |
| FQXDE1511I | Channel miswire resolved | Informational |
| FQXDE1512I | IOM (ESM) miswire resolved | Informational |
| FQXDE1514I | Drive channel changed to optimal | Informational |
| FQXDE1516I | Switch on chip (SOC) EEPROM failed | Informational |
| FQXDE1517I | Switch on chip (SOC) EEPROM cannot be initialized | Informational |
| FQXDE1518I | SFP link speed mismatch detected | Informational |
| FQXDE1519I | SFP link speed mismatch resolved | Informational |
| FQXDE151BI | Optical link speed detection failure resolved | Informational |
| FQXDE151CI | Copper link speed detection failure | Informational |
| FQXDE151DI | Copper link speed detection failure resolved | Informational |
| FQXDE151FI | Controller miswire for drive channel cleared | Informational |
| FQXDE1520I | Internal Drive Port PTBI Failure | Informational |
| FQXDE1523I | Drive enclosure type miswire clear | Informational |
| FQXDE1526I | Trunk state enabled | Informational |
| FQXDE1527I | Trunk state disabled | Informational |
| FQXDE1528I | Corrected trunk incompatible IOM (ESM) | Informational |
| FQXDE1529I | Trunk miswire corrected | Informational |
| FQXDE1651I | SAS host channel miswire resolved | Informational |
| FQXDE1653I | SAS source driver detected regular initiator overflow | Informational |
| FQXDE1655I | Host wide port link is up | Informational |
| FQXDE1656I | Host wide port link is down | Informational |
| FQXDE1657I | Host wide port link is optimal | Informational |
| FQXDE1658I | A host card SAS port connection speed is below the maximum | Informational |
| FQXDE1659I | An SMP Timeout event has occurred to a switch connected on a host channel. Check host channel switches for possible issues. | Informational |
| FQXDE165BI | The controller detected that a SAS IOC has faulted | Informational |
| FQXDE165CI | The controller detected that a SAS IOC has faulted and started a recovery procedure in an attempt to bring it back to an operational state | Informational |
| FQXDE165DI | The controller detected that a SAS IOC has faulted and completed a recovery procedure. The SAS IOC was recovered and is now in an operational state | Informational |
| FQXDE1701I | Invalid SAS topology resolved | Informational |
| FQXDE1703I | SAS host adapter miswire resolved | Informational |
| FQXDE1705I | SAS IOM (ESM) miswire resolved | Informational |
| FQXDE1708I | Single connection established through previously failed wide port | Informational |
| FQXDE1709I | All connections established through wide port | Informational |
| FQXDE170BI | Drive expansion port miswire resolved | Informational |
| FQXDE170CI | SAS host port configuration error | Informational |
| FQXDE1711I | Controller wide port has gone to degraded state | Informational |
| FQXDE1712I | Controller wide port has gone to optimal state | Informational |
| FQXDE1717I | Link in the controller tray is slow | Informational |
| FQXDE1718I | Expansion tray link is slow | Informational |
| FQXDE1719I | SAS drive link is slow | Informational |
| FQXDE171BI | Access to expansion trays restored | Informational |
| FQXDE1801I | Authentication failure | Informational |
| FQXDE1802I | Unsupported authentication type | Informational |
| FQXDE1804I | iSNS server failure | Informational |
| FQXDE1805I | iSNS server contacted | Informational |
| FQXDE1806I | Forced session end | Informational |
| FQXDE1807I | IP address failure | Informational |
| FQXDE1808I | Login failure | Informational |
| FQXDE180CI | Connection terminated unexpectedly | Informational |
| FQXDE180DI | Session terminated unexpectedly | Informational |
| FQXDE180EI | iSCSI interface correctable ECC error occurred | Informational |
| FQXDE180FI | iSCSI interface restarted | Informational |
| FQXDE1810I | DHCP failure in iSCSI interface | Informational |
| FQXDE1811I | DHCP success | Informational |
| FQXDE1812I | iSCSI IPV6 error, configuration change, or duplicate IP address detected | Informational |
| FQXDE1813I | iSCSI data overrun | Informational |
| FQXDE1814I | ISCSI carrier was detected | Informational |
| FQXDE1815I | ISCSI carrier was lost | Informational |
| FQXDE1816I | iSCSI connection speed warning | Informational |
| FQXDE1817I | iSCSI communication was established | Informational |
| FQXDE1818I | iSCSI communication lost to remote target | Informational |
| FQXDE1819I | iSCSI duplicate IPv4 address | Informational |
| FQXDE1900I | Cache memory DIMM detected | Informational |
| FQXDE1901I | Cache memory DIMM is missing | Informational |
| FQXDE1902I | Host interface card added | Informational |
| FQXDE1903I | Host interface card removed | Informational |
| FQXDE1905I | Host interface card replaced with same board type | Informational |
| FQXDE1906I | Host interface card replaced with different board type | Informational |
| FQXDE200FI | Cache synchronization started | Informational |
| FQXDE2010I | Cache synchronization completed | Informational |
| FQXDE2011I | Cache flush started | Informational |
| FQXDE2012I | Cache flush completed | Informational |
| FQXDE2013I | Unwritten data/parity recovered from cache | Informational |
| FQXDE2014I | VDD logged an error | Informational |
| FQXDE2015I | Uncompleted writes detected in NVSRAM at start-of-day | Informational |
| FQXDE2016I | Interrupted writes processed | Informational |
| FQXDE2017I | Interrupted writes detected from checkpoint logs | Informational |
| FQXDE201CI | VDD recover started | Informational |
| FQXDE201DI | VDD recover completed | Informational |
| FQXDE201EI | VDD repair started | Informational |
| FQXDE201FI | VDD repair completed | Informational |
| FQXDE2020I | Piece failed during interrupted write | Informational |
| FQXDE2021I | Virtual disk failed during interrupted write | Informational |
| FQXDE2022I | Media scan (scrub) started | Informational |
| FQXDE2023I | Media scan (scrub) completed | Informational |
| FQXDE2024I | Media scan (scrub) resumed | Informational |
| FQXDE2025I | Reconstruction started | Informational |
| FQXDE2026I | Reconstruction completed | Informational |
| FQXDE2027I | Reconstruction resumed | Informational |
| FQXDE2028I | Modification (reconfigure) started | Informational |
| FQXDE2029I | Modification (reconfigure) completed | Informational |
| FQXDE202AI | Modification (reconfigure) resumed | Informational |
| FQXDE202BI | Redundancy check started | Informational |
| FQXDE202CI | Redundancy check completed | Informational |
| FQXDE202FI | Automatic volume transfer completed | Informational |
| FQXDE2030I | Initialization completed on volume | Informational |
| FQXDE2031I | Initialization started on volume | Informational |
| FQXDE2032I | Initialization resumed on volume | Informational |
| FQXDE2033I | Parity reconstructed on volume | Informational |
| FQXDE2035I | Redundancy not consistent | Informational |
| FQXDE2036I | Redundancy consistent after retry | Informational |
| FQXDE2037I | Redundancy not verified | Informational |
| FQXDE2038I | Media scan cycle started on unused drives | Informational |
| FQXDE2039I | Media scan cycle on unassigned drives completed | Informational |
| FQXDE203DI | Drive adopted | Informational |
| FQXDE203EI | FDE drive re-provisioned | Informational |
| FQXDE203FI | FDE drive re-provision failed | Informational |
| FQXDE2040I | FDE secure component conversion | Informational |
| FQXDE2043I | Threshold exceeded during successful mismatch correction | Informational |
| FQXDE2044I | IO shipping implicit volume transfer | Informational |
| FQXDE2049I | Fail-back implicit volume transfer | Informational |
| FQXDE204AI | Auto Load Balancing implicit volume transfer | Informational |
| FQXDE204BI | The reconstruction agent failed to enable drive write caching as part of rebuild | Informational |
| FQXDE204CI | The reconstruction agent failed to sync drive write caching as part of rebuild | Informational |
| FQXDE204DI | The reconstruction agent failed to disable drive write caching as part of rebuild | Informational |
| FQXDE2060I | Data assurance mismatch detected - probable cause is channel interface | Informational |
| FQXDE2061I | Data assurance mismatch detected - probable cause is cached data | Informational |
| FQXDE2062I | Data assurance mismatch detected - probable cause is data on drive | Informational |
| FQXDE2064I | Data assurance error detected during cache backup | Informational |
| FQXDE2066I | A protected volume to LUN mapping was automatically deleted | Informational |
| FQXDE2067I | Host data assurance change | Informational |
| FQXDE2068I | Cluster data assurance change | Informational |
| FQXDE206BI | Controller has exited Analysis Lockdown Mode | Informational |
| FQXDE206CI | Controller has exited Data Assurance Service Mode | Informational |
| FQXDE206DI | Data assurance mismatch detected -- cached data recovered from alternate | Informational |
| FQXDE206EI | PI errors on cache data blocks were repaired | Informational |
| FQXDE206FI | Data assurance mismatch detected -- data recovered, but volume degraded | Informational |
| FQXDE2070I | Data assurance mismatch detected -- cached data error on both controllers | Informational |
| FQXDE2101I | Alternate controller checked in late | Informational |
| FQXDE2102I | Cache mirroring on controllers not synchronized | Informational |
| FQXDE2105I | Controller cache reconfigure event | Informational |
| FQXDE210AI | Controller cache not enabled or was internally disabled | Informational |
| FQXDE210BI | Cache between controllers not synchronized | Informational |
| FQXDE210FI | Controller cache memory parity error detected | Informational |
| FQXDE2112I | Controller cache battery is fully charged | Informational |
| FQXDE2117I | Controller cache manager error cleared | Informational |
| FQXDE211AI | Cache corrected by using alternate controller's cache | Informational |
| FQXDE211CI | Battery pack is charging | Informational |
| FQXDE211DI | Persistent single-bit memory ECC event - recovered | Informational |
| FQXDE2127I | Insufficient cache backup device capacity for non-critical data | Informational |
| FQXDE2129I | Cache backup device error | Informational |
| FQXDE212AI | Cache database mismatch was detected | Informational |
| FQXDE212CI | Write-back caching fully restored | Informational |
| FQXDE212DI | A cache data loss occurred but no action is required from the user | Informational |
| FQXDE212FI | Cache manager enabled secondary cache | Informational |
| FQXDE2130I | Secondary cache not enabled because of initialization timeout | Informational |
| FQXDE2202I | Volume added | Informational |
| FQXDE2203I | Volume group or volume deleted | Informational |
| FQXDE2204I | I/O is resumed | Informational |
| FQXDE2206I | Reconstruction completed | Informational |
| FQXDE2207I | Device copy completed | Informational |
| FQXDE2208I | Modification (reconfigure) setup | Informational |
| FQXDE220AI | Copyback started | Informational |
| FQXDE2213I | Volume initialized with zeros | Informational |
| FQXDE2215I | Drive marked failed | Informational |
| FQXDE2216I | Piece taken out of service | Informational |
| FQXDE2217I | Piece failed | Informational |
| FQXDE221AI | Piece replaced | Informational |
| FQXDE221BI | Piece placed in service | Informational |
| FQXDE221CI | Component placed offline | Informational |
| FQXDE221FI | Immediate availability initialization (IAF) completed on volume | Informational |
| FQXDE2220I | Hot spare drive added to hot spare list | Informational |
| FQXDE2221I | Hot spare drive removed from hot spare list | Informational |
| FQXDE2222I | Logical unit number for volume reassigned | Informational |
| FQXDE2224I | Reconstruction started | Informational |
| FQXDE2226I | Drive spun down | Informational |
| FQXDE2227I | Drive marked optimal | Informational |
| FQXDE2228I | Drive deleted | Informational |
| FQXDE222EI | Mark drive removed | Informational |
| FQXDE2231I | Drive marked removed | Informational |
| FQXDE2233I | Unassigned drive marked removed | Informational |
| FQXDE2234I | Reconstructing drive marked removed | Informational |
| FQXDE2235I | Optimal/Replaced drive marked removed | Informational |
| FQXDE2236I | Hot spare drive copy completed | Informational |
| FQXDE2247I | Data lost on volume during unrecovered interrupted write | Informational |
| FQXDE224CI | Wrong drive removed/replaced | Informational |
| FQXDE224FI | Hot spare capacity not sufficient for all drives | Informational |
| FQXDE2256I | Copyback completed on volume | Informational |
| FQXDE225AI | Immediate availability initialization (IAF) started on volume | Informational |
| FQXDE225CI | Controller in stopped state | Informational |
| FQXDE225DI | Automatic configuration started | Informational |
| FQXDE225EI | Automatic configuration completed successfully | Informational |
| FQXDE225FI | Automatic configuration failed | Informational |
| FQXDE2261I | Controller clocks set by NTP or SNTP Server | Informational |
| FQXDE2263I | The drive replacement succeeded | Informational |
| FQXDE2264I | The drive replacement failed | Informational |
| FQXDE2268I | Component's capacity was reduced | Informational |
| FQXDE2269I | Export volume group drive unusable | Informational |
| FQXDE226AI | Dacstore region has moved | Informational |
| FQXDE226FI | Solid state drive nearing end of life | Informational |
| FQXDE2279I | IAF suspended for reconstruction | Informational |
| FQXDE227AI | IAF resumed | Informational |
| FQXDE227BI | Reconfiguration suspended | Informational |
| FQXDE227DI | Drive copy triggered by solid state drive at end of life | Informational |
| FQXDE227EI | Drive copy started | Informational |
| FQXDE227FI | Drive copy started | Informational |
| FQXDE2280I | Drive copy completed and drive failed | Informational |
| FQXDE2281I | Drive copy completed and drive replaced | Informational |
| FQXDE2282I | Drive copy canceled | Informational |
| FQXDE2283I | Drive copy suspended | Informational |
| FQXDE2284I | Drive copy resumed | Informational |
| FQXDE2286I | Drive copy triggered by a drive detected impending failure | Informational |
| FQXDE228AI | . After controllers are rebooted, the NTP state is compared on the two controllers. In this case, they were found to be different, for example, one controller has NTP enabled and the other has NTP disabled. Although this is unconventional, it might be intentional | Informational |
| FQXDE2306I | Mismatched midplane EEPROM contents one controller | Informational |
| FQXDE2307I | Chassis serial number was corrected | Informational |
| FQXDE2400I | Hot swap monitor detected drive removal | Informational |
| FQXDE2401I | Hot swap monitor detected drive insertion | Informational |
| FQXDE2506I | A missing controller was reinserted | Informational |
| FQXDE2600I | Automatic controller firmware synchronization started | Informational |
| FQXDE2601I | Automatic controller firmware synchronization completed | Informational |
| FQXDE2603I | Default volume created | Informational |
| FQXDE2605I | Start-of-day routine completed | Informational |
| FQXDE2606I | Start-of-day routine begun | Informational |
| FQXDE2700I | Controller RPA memory parity error detected | Informational |
| FQXDE2702I | Controller unexpected RPA interrupt detected | Informational |
| FQXDE2703I | Recoverable error in processor memory detected/corrected | Informational |
| FQXDE2802I | UPS battery is fully charged | Informational |
| FQXDE2809I | Controller tray component changed to optimal | Informational |
| FQXDE280CI | Drive tray component changed to optimal | Informational |
| FQXDE2817I | Tray ID conflict resolved | Informational |
| FQXDE281AI | Temperature changed to optimal | Informational |
| FQXDE281FI | IOM (ESM) firmware mismatch resolved | Informational |
| FQXDE2824I | Drive by-passed condition resolved | Informational |
| FQXDE282AI | Controller redundancy restored | Informational |
| FQXDE282CI | Drive tray path redundancy restored | Informational |
| FQXDE282EI | Drive path redundancy restored | Informational |
| FQXDE2834I | Controller host interface card ID mismatch resolved | Informational |
| FQXDE2837I | Discrete lines diagnostic failure resolved | Informational |
| FQXDE2839I | Interconnect/battery canister reinserted | Informational |
| FQXDE2840I | Controller submodel not set or not supported | Informational |
| FQXDE2842I | Controller submodel mismatch resolved | Informational |
| FQXDE2847I | GBIC/SFP Installed | Informational |
| FQXDE2848I | GBIC/SFP removed | Informational |
| FQXDE284AI | IOM (ESM) Hardware mismatch resolved | Informational |
| FQXDE284DI | Drive tray expansion limit out of range | Informational |
| FQXDE2850I | Drive trays cabled correctly | Informational |
| FQXDE2851I | Enclosure EEPROM read failure | Informational |
| FQXDE2853I | IOM (ESM) configuration settings version mismatch cleared | Informational |
| FQXDE2858I | Drawer closed | Informational |
| FQXDE2859I | Host-side SFP installed | Informational |
| FQXDE285AI | Host-side SFP removed | Informational |
| FQXDE285BI | Drive-side SFP installed | Informational |
| FQXDE285CI | Drive-side SFP removed | Informational |
| FQXDE2860I | The drawer's status is optimal | Informational |
| FQXDE2865I | Host-side SFP optimal | Informational |
| FQXDE2901I | Leaving invalid system configuration | Informational |
| FQXDE3000I | Format unit issued | Informational |
| FQXDE3002I | Reassign blocks issued from host | Informational |
| FQXDE3006I | Safe pass-through issued | Informational |
| FQXDE3007I | Mode select for page 1 received | Informational |
| FQXDE3009I | Mode for caching page 8 received | Informational |
| FQXDE300AI | Mode select for control mode page A received | Informational |
| FQXDE300DI | Mode select for redundant controller page 2C received | Informational |
| FQXDE3012I | Write buffer received | Informational |
| FQXDE3014I | Drive firmware download started | Informational |
| FQXDE301AI | Drive firmware download failed | Informational |
| FQXDE301BI | Drive firmware and/or interposer firmware download is completed | Informational |
| FQXDE301CI | IOM (ESM) firmware download started | Informational |
| FQXDE301DI | IOM (ESM) firmware download failed | Informational |
| FQXDE301EI | IOM (ESM) firmware download completed | Informational |
| FQXDE301FI | Unable to register a volume due to insufficient resources | Informational |
| FQXDE3020I | Update of power supply firmware was blocked | Informational |
| FQXDE3021I | Update of power supply firmware failed | Informational |
| FQXDE3022I | Update of power supply firmware started | Informational |
| FQXDE3023I | Update of power supply firmware completed | Informational |
| FQXDE3024I | All drive downloads complete | Informational |
| FQXDE3025I | A Set Target Port Groups (STPG) command was received for this volume and caused the volume to be transferred | Informational |
| FQXDE3101I | Asynchronous event notification (AEN) was posted for recently logged event | Informational |
| FQXDE3300I | Autocode synchronization drive image write started | Informational |
| FQXDE3301I | Autocode synchronization drive image write completed | Informational |
| FQXDE3302I | Autocode synchronization drive image invalidated | Informational |
| FQXDE3303I | Autocode synchronization drive image write failure | Informational |
| FQXDE3304I | Autocode synchronization drive image invalidate failure | Informational |
| FQXDE3305I | Drive image write retry exhausted | Informational |
| FQXDE3306I | Insufficient storage for autocode synchronization image | Informational |
| FQXDE3402I | Raw data retrieve canceled by user | Informational |
| FQXDE3403I | Raw data retrieve canceled by controller | Informational |
| FQXDE3404I | Raw data restore start | Informational |
| FQXDE3405I | Raw data restore completed | Informational |
| FQXDE3406I | Raw data restore canceled by user | Informational |
| FQXDE3407I | Raw data restore canceled by controller | Informational |
| FQXDE3408I | Raw data retrieve structure inconsistency detected | Informational |
| FQXDE3500I | A schedule was created | Informational |
| FQXDE3501I | A previously defined schedule was modified | Informational |
| FQXDE3502I | A previously defined schedule was deleted | Informational |
| FQXDE3503I | A previously defined schedule was enabled | Informational |
| FQXDE3504I | A previously defined schedule was disabled | Informational |
| FQXDE3505I | The start of a scheduled operation was missed | Informational |
| FQXDE3506I | An operation associated with a schedule completed | Informational |
| FQXDE3508I | The scheduled time for an operation was reached and the associated action initiated | Informational |
| FQXDE3600I | SSD cache created on the storage array | Informational |
| FQXDE3601I | SSD cache deleted on the storage array | Informational |
| FQXDE3602I | SSD cache suspended | Informational |
| FQXDE3603I | SSD cache resumed | Informational |
| FQXDE3607I | SSD cache enabled on a volume | Informational |
| FQXDE3608I | SSD cache disabled on a volume | Informational |
| FQXDE3609I | Drives added to an SSD cache | Informational |
| FQXDE360AI | Drives removed from an SSD cache | Informational |
| FQXDE360BI | SSD cache performance modeling started | Informational |
| FQXDE360CI | SSD cache performance modeling stopped | Informational |
| FQXDE360DI | SSD cache performance modeling results reset | Informational |
| FQXDE360EI | SSD cache transitioned to optimal | Informational |
| FQXDE360FI | SSD cache performance modeling internal structures created on the storage array | Informational |
| FQXDE3610I | SSD cache performance modeling internal structures deleted on the storage array | Informational |
| FQXDE3611I | SSD cache performed modeling enabled on a volume | Informational |
| FQXDE3612I | SSD cache performed modeling disabled on a volume | Informational |
| FQXDE3613I | SSD cache renamed | Informational |
| FQXDE3700I | Core dump was captured | Informational |
| FQXDE3701I | Core dump was not captured | Informational |
| FQXDE3702I | Core dump capture failed | Informational |
| FQXDE3703I | Core dump retrieval started | Informational |
| FQXDE3704I | Core dump retrieval completed | Informational |
| FQXDE3705I | Core dump retrieval was cancelled | Informational |
| FQXDE3706I | Core dump retrieval has timed out | Informational |
| FQXDE3707I | Core dump has not been retrieved and overwritten | Informational |
| FQXDE3708I | Core dump restore completed | Informational |
| FQXDE3807I | Disk pool drive reconstruction started | Informational |
| FQXDE3808I | Disk pool drive reconstruction completed | Informational |
| FQXDE380AI | Disk pool reconfiguration started | Informational |
| FQXDE380BI | Disk pool reconfiguration completed | Informational |
| FQXDE380EI | A disk pool capacity reduction operation started | Informational |
| FQXDE380FI | A reconstruction of a critically degraded disk pool volume started | Informational |
| FQXDE3810I | A reconstruction of a critically degraded disk pool volume completed | Informational |
| FQXDE4004I | Alternate controller quiescence message received | Informational |
| FQXDE4005I | Controller quiescence started | Informational |
| FQXDE4006I | Alternate controller quiescence started | Informational |
| FQXDE4007I | Subsystem quiescence started | Informational |
| FQXDE4008I | Controller quiescence halted | Informational |
| FQXDE4009I | Controller quiescence released | Informational |
| FQXDE400AI | Alternate controller quiescence released | Informational |
| FQXDE400BI | All channel reset detected | Informational |
| FQXDE400CI | Controller placed offline | Informational |
| FQXDE400DI | Controller placed online | Informational |
| FQXDE400EI | Automatic volume transfer started | Informational |
| FQXDE400FI | Controller reset by its alternate | Informational |
| FQXDE4010I | Controller reset | Informational |
| FQXDE4012I | Volume not on preferred path due to AVT/RDAC failover | Informational |
| FQXDE5000I | Assign component ownership | Informational |
| FQXDE5001I | Assign hot spare drive | Informational |
| FQXDE5002I | Create volume | Informational |
| FQXDE5003I | De-assign hot spare drive | Informational |
| FQXDE5004I | Delete volume | Informational |
| FQXDE5006I | Fail drive | Informational |
| FQXDE5007I | Initialize volume group, disk pool, or volume | Informational |
| FQXDE5008I | Initialize drive | Informational |
| FQXDE5009I | Controller firmware download started | Informational |
| FQXDE500BI | Controller NVSRAM download started | Informational |
| FQXDE500EI | Reconstruct drive/volume | Informational |
| FQXDE500FI | Start component defragment | Informational |
| FQXDE5010I | Add free capacity to component | Informational |
| FQXDE5011I | Change RAID level of component | Informational |
| FQXDE5012I | Change segment size of volume | Informational |
| FQXDE5014I | Change controller to active mode | Informational |
| FQXDE5015I | Update cache parameters of storage array | Informational |
| FQXDE5016I | Change name of storage array | Informational |
| FQXDE5017I | Synchronize controller clock | Informational |
| FQXDE5018I | Change cache parameters of volume | Informational |
| FQXDE501AI | Change name of volume | Informational |
| FQXDE501BI | Place controller online | Informational |
| FQXDE501CI | Revive drive | Informational |
| FQXDE501DI | Revive volume | Informational |
| FQXDE501EI | Change positions of trays in PHYsical view | Informational |
| FQXDE501FI | Change media scan (scrub) settings of volume | Informational |
| FQXDE5020I | Change media scan (scrub) settings of storage array | Informational |
| FQXDE5021I | Reset configuration of storage array | Informational |
| FQXDE5023I | Controller return status/function call for requested operation | Informational |
| FQXDE5024I | Internal download checkpoint | Informational |
| FQXDE5025I | Controller firmware download failed | Informational |
| FQXDE5026I | Controller firmware download completed | Informational |
| FQXDE5027I | Controller NVSRAM download failed | Informational |
| FQXDE5028I | Controller NVSRAM download completed | Informational |
| FQXDE5029I | Reset controller battery parameters | Informational |
| FQXDE502AI | Assign volume ownership | Informational |
| FQXDE502BI | Increase volume capacity | Informational |
| FQXDE5030I | Activate mirroring | Informational |
| FQXDE5031I | Deactivate mirroring | Informational |
| FQXDE5032I | Change synchronization priority | Informational |
| FQXDE5033I | Start mirror synchronization | Informational |
| FQXDE5037I | Incorrect password attempted | Informational |
| FQXDE5039I | Change parameters of volume copy pair | Informational |
| FQXDE503AI | Start volume copy operation | Informational |
| FQXDE503BI | Stop volume copy operation | Informational |
| FQXDE503CI | Change mirrored pair write mode | Informational |
| FQXDE503DI | Suspend mirror relationship | Informational |
| FQXDE503EI | Resume mirror relationship | Informational |
| FQXDE503FI | Resynchronization set for automatic | Informational |
| FQXDE5041I | Recover volume | Informational |
| FQXDE5042I | Mirror relationships for write consistency group suspended | Informational |
| FQXDE5043I | Mirror relationships for write consistency group resumed | Informational |
| FQXDE5044I | Configuration change from single to dual or dual to single controller mode | Informational |
| FQXDE5045I | Activate controller firmware started | Informational |
| FQXDE5046I | Activate controller firmware completed | Informational |
| FQXDE5047I | Activate controller firmware failed | Informational |
| FQXDE5048I | Clear controller firmware started | Informational |
| FQXDE5049I | Clear controller firmware complete | Informational |
| FQXDE504AI | Suspend mirror list completed | Informational |
| FQXDE504BI | Resume mirror list completed | Informational |
| FQXDE504CI | Enable alarm | Informational |
| FQXDE504DI | Disable alarm | Informational |
| FQXDE504EI | Power down storage array | Informational |
| FQXDE504FI | This command is no longer valid | Informational |
| FQXDE5050I | Clear controller firmware failed | Informational |
| FQXDE5051I | Feature pack key file successfully applied | Informational |
| FQXDE5052I | Feature pack key file successfully removed | Informational |
| FQXDE5053I | Drive was replaced | Informational |
| FQXDE5054I | Create volumes with free capacity (extents) | Informational |
| FQXDE5055I | Get volume free capacities (extents) | Informational |
| FQXDE5056I | Create component | Informational |
| FQXDE5057I | Delete component | Informational |
| FQXDE5058I | Set component user label | Informational |
| FQXDE5059I | Force component | Informational |
| FQXDE505AI | Export component | Informational |
| FQXDE505BI | Import component | Informational |
| FQXDE505CI | Tray ID changed | Informational |
| FQXDE505DI | Importing the component was canceled | Informational |
| FQXDE505EI | Importing the component failed | Informational |
| FQXDE505FI | Exporting the component failed | Informational |
| FQXDE5060I | Volume properties set | Informational |
| FQXDE5061I | Drive has become native to this array | Informational |
| FQXDE5062I | Drives have become native to this array | Informational |
| FQXDE5063I | Reset storage array configuration | Informational |
| FQXDE5064I | Volume configuration was reset | Informational |
| FQXDE5065I | Security (FDE) storage array key created | Informational |
| FQXDE5066I | Security (FDE) storage array key updated | Informational |
| FQXDE5067I | Security (FDE) storage array key exported | Informational |
| FQXDE5068I | Security (FDE) storage array key set | Informational |
| FQXDE5069I | Security (FDE) storage array key set complete | Informational |
| FQXDE506AI | External key management enabled | Informational |
| FQXDE506BI | External key management disabled | Informational |
| FQXDE506CI | New external key installed | Informational |
| FQXDE506EI | Created security (FDE) storage array key cleared | Informational |
| FQXDE506FI | The installed security (FDE) key is not valid | Informational |
| FQXDE5070I | Autosupport enabled | Informational |
| FQXDE5071I | Autosupport disabled | Informational |
| FQXDE5072I | Enable OnDemand | Informational |
| FQXDE5073I | Disable OnDemand | Informational |
| FQXDE5074I | OnDemand Remote Diagnostics Enabled | Informational |
| FQXDE5075I | OnDemand Remote Diagnostics Disabled | Informational |
| FQXDE5076I | External SYMbolAPI access was disabled | Informational |
| FQXDE5077I | External SYMbolAPI access was enabled | Informational |
| FQXDE507AI | AutoSupport maintenance mode enabled | Informational |
| FQXDE507BI | AutoSupport maintenance mode disabled | Informational |
| FQXDE507CI | One of the images contained in the controller firmware package failed to authenticate using the provided public key and signature | Informational |
| FQXDE507DI | The Controller NVSRAM package failed to authenticate using the provided public key and signature | Informational |
| FQXDE5107I | A SAS PHY was enabled | Informational |
| FQXDE5200I | Create host group | Informational |
| FQXDE5201I | Delete host group | Informational |
| FQXDE5202I | Rename host group | Informational |
| FQXDE5203I | Create host | Informational |
| FQXDE5204I | Delete host | Informational |
| FQXDE5205I | Rename host | Informational |
| FQXDE5206I | Move host | Informational |
| FQXDE5207I | Create host port | Informational |
| FQXDE5208I | Delete host port | Informational |
| FQXDE5209I | Rename host port | Informational |
| FQXDE520AI | Move host port | Informational |
| FQXDE520BI | Set host port type | Informational |
| FQXDE520FI | Create volume-to-LUN mapping | Informational |
| FQXDE5210I | Delete volume-to-LUN mapping | Informational |
| FQXDE5211I | Change volume-to-LUN mapping | Informational |
| FQXDE5214I | Topology and mappings deleted | Informational |
| FQXDE5216I | iSCSI initiator was created | Informational |
| FQXDE5217I | iSCSI initiator was deleted | Informational |
| FQXDE5218I | Host properties have been set | Informational |
| FQXDE5219I | Initiator properties have been set | Informational |
| FQXDE521AI | The initiator authentication type was changed | Informational |
| FQXDE521BI | The initiator's CHAP secret was changed | Informational |
| FQXDE521CI | The target authentication type was changed | Informational |
| FQXDE521DI | The target's CHAP secret was changed | Informational |
| FQXDE521EI | The target's iSCSI properties were set | Informational |
| FQXDE521FI | The target's iSCSI alias was set | Informational |
| FQXDE5220I | Create new host port | Informational |
| FQXDE5221I | Set host port properties | Informational |
| FQXDE5226I | Failed host port registration | Informational |
| FQXDE5227I | Inactive host port activated | Informational |
| FQXDE5228I | Failed initiator registration | Informational |
| FQXDE5229I | Inactive initiator activated | Informational |
| FQXDE522AI | Host port records deleted | Informational |
| FQXDE522BI | A remote target was created | Informational |
| FQXDE522CI | A remote target was deleted | Informational |
| FQXDE522DI | The properties for a remote target were set | Informational |
| FQXDE522EI | The authentication for a remote target was changed | Informational |
| FQXDE522FI | The secret for a remote target was changed | Informational |
| FQXDE5230I | The alias for the local initiator was set | Informational |
| FQXDE5231I | The properties for the local initiator were set | Informational |
| FQXDE5232I | The authentication was set for the local initiator | Informational |
| FQXDE5233I | The change secret for the local initiator was set | Informational |
| FQXDE5400I | Premium feature enabled | Informational |
| FQXDE5401I | Premium feature disabled | Informational |
| FQXDE5404I | Feature Enable Identifier changed | Informational |
| FQXDE5407I | Evaluation license is about to expire | Informational |
| FQXDE5408I | Feature evaluation period was enabled | Informational |
| FQXDE5600I | Controller passed diagnostics | Informational |
| FQXDE5601I | This controller's alternate passed diagnostics | Informational |
| FQXDE5603I | Diagnostics rejected - already in progress | Informational |
| FQXDE5604I | Diagnostics rejected this controller's alternate is absent or failed | Informational |
| FQXDE5605I | Diagnostics rejected error occurred when sending the Icon message | Informational |
| FQXDE5607I | Diagnostics returned unknown ReturnCode | Informational |
| FQXDE5608I | Diagnostics rejected - test ID is incorrect | Informational |
| FQXDE560AI | Diagnostics rejected access volume (UTM) is not enabled | Informational |
| FQXDE5611I | Controller passed diagnostics, but loopback test identified an error on loops | Informational |
| FQXDE5612I | This controller's alternate passed diagnostics, put loopback test identified an error on loops | Informational |
| FQXDE5613I | Diagnostics loopback test identified bad destination channels | Informational |
| FQXDE561AI | Diagnostics rejected - data transfer on controller is not disabled (quiesced) | Informational |
| FQXDE561BI | Diagnostics rejected data transfer on this controllers alternate is not disabled (quiesced) | Informational |
| FQXDE561CI | Diagnostics rejected both controllers must be in active mode | Informational |
| FQXDE561DI | Diagnostics initiated from this controller | Informational |
| FQXDE561EI | Running diagnostics on this controller | Informational |
| FQXDE561FI | Diagnostics rejected download is in progress | Informational |
| FQXDE5620I | Cable diagnostic started | Informational |
| FQXDE5621I | Cable diagnostic completed | Informational |
| FQXDE5622I | An exception condition was detected on the controller | Informational |
| FQXDE5801I | Management port link down | Informational |
| FQXDE5802I | Management port link up | Informational |
| FQXDE5900I | WWN migrated from database is invalid | Informational |
| FQXDE6000I | Internal configuration database created | Informational |
| FQXDE6003I | Internal configuration database not enough optimal drives available | Informational |
| FQXDE6004I | Internal configuration database is being resynchronized | Informational |
| FQXDE6005I | Internal configuration database read or write operation failed | Informational |
| FQXDE6006I | Internal configuration database merge failed | Informational |
| FQXDE6007I | Configuration database successfully adopted | Informational |
| FQXDE6008I | Stable storage drive unusable | Informational |
| FQXDE6009I | Stable storage drive usable | Informational |
| FQXDE600AI | A SSTOR miscompare was detected | Informational |
| FQXDE6100I | Internal configuration database cleared | Informational |
| FQXDE6102I | Internal configuration database size increased | Informational |
| FQXDE6103I | This controller's alternate was reset | Informational |
| FQXDE6104I | This controller's alternate failed | Informational |
| FQXDE6105I | Internal configuration database file system corrupted | Informational |
| FQXDE6106I | Internal configuration database incorrect file system version | Informational |
| FQXDE6108I | Configuration information stored in the array's database may have been lost | Informational |
| FQXDE610AI | The storage array is no longer in database recovery mode | Informational |
| FQXDE610CI | A subrecord validation has taken place, and been fixed | Informational |
| FQXDE610DI | Internal configuration database subrecord CRC mismatch | Informational |
| FQXDE6300I | Mirror repository volume created | Informational |
| FQXDE6301I | Mirror repository volume deleted | Informational |
| FQXDE6403I | Data on mirrored pair synchronizing | Informational |
| FQXDE6404I | Data on mirrored pair synchronized | Informational |
| FQXDE6405I | Associated volume in mirrored pair not present | Informational |
| FQXDE6406I | Mirrored pair created | Informational |
| FQXDE6407I | Mirrored pair deleted | Informational |
| FQXDE6408I | Mirrored pair role changed | Informational |
| FQXDE6409I | Mirror relationship suspended | Informational |
| FQXDE640AI | Data on mirrored pair unsynchronized | Informational |
| FQXDE640BI | Attempt to suspend mirrored pair failed | Informational |
| FQXDE640CI | Mirror write mode set to synchronous | Informational |
| FQXDE640DI | Mirror write mode set to asynchronous | Informational |
| FQXDE640EI | Mirror write mode set to asynchronous, write-consistent | Informational |
| FQXDE640FI | Mirror relationship degraded | Informational |
| FQXDE6410I | An asynchronous mode for legacy RVM Mirrors is not supported; therefore all legacy RVM mirrors have been deleted | Informational |
| FQXDE6500I | Remote volume created | Informational |
| FQXDE6501I | Remote volume deleted | Informational |
| FQXDE6502I | Communication to remote volume up | Informational |
| FQXDE6504I | Remote storage array's world-wide name changed | Informational |
| FQXDE6601I | Volume copy pair established | Informational |
| FQXDE6602I | Volume copy pair removed | Informational |
| FQXDE6603I | Volume copy operation in progress | Informational |
| FQXDE6604I | Volume copy operation pending | Informational |
| FQXDE6605I | Volume copy operation stopped | Informational |
| FQXDE6606I | Volume copy operation completed | Informational |
| FQXDE6701I | Unreadable sector repaired | Informational |
| FQXDE6702I | All unreadable sectors on the volume repaired data unrecovered | Informational |
| FQXDE6704I | Unreadable sectors found on volume | Informational |
| FQXDE6705I | Volume import failed - too many unreadable sectors | Informational |
| FQXDE6706I | Unreadable sectors prevented data from being reconstructed to a replaced drive. An unreadable sector record was created on the replaced drive to track the fact that the data cannot be read | Informational |
| FQXDE6802I | Serial port recovery exited | Informational |
| FQXDE6901I | Diagnostic data retrieval operation started | Informational |
| FQXDE6902I | Diagnostic data retrieval operation completed | Informational |
| FQXDE6903I | Diagnostic data Needs Attention status was cleared | Informational |
| FQXDE6904I | Diagnostic data capture information was lost | Informational |
| FQXDE6905I | Non-critical data restore failed | Informational |
| FQXDE6906I | Diagnostic data capture information available | Informational |
| FQXDE7000I | Incorrect feature pack key file | Informational |
| FQXDE7002I | Feature bundle key was deleted | Informational |
| FQXDE7003I | Invalid feature bundle key was applied | Informational |
| FQXDE7100I | Discrete time series activated | Informational |
| FQXDE7101I | Discrete time series deactivated | Informational |
| FQXDE7102I | Discrete time series expired | Informational |
| FQXDE7103I | Histogram activated | Informational |
| FQXDE7104I | Histogram deactivated | Informational |
| FQXDE7105I | Histogram expired | Informational |
| FQXDE7302I | Low battery capacity | Informational |
| FQXDE7303I | Battery temperature nominal | Informational |
| FQXDE7304I | Battery learn cycle will occur in one hour | Informational |
| FQXDE730BI | Battery fully charged | Informational |
| FQXDE730DI | Battery replaced | Informational |
| FQXDE730EI | Battery capacity is sufficient | Informational |
| FQXDE730FI | Incomplete battery learn cycle | Informational |
| FQXDE7310I | Learn cycle for battery started | Informational |
| FQXDE7311I | Learn cycle for battery completed | Informational |
| FQXDE7504I | Cache backup device was replaced | Informational |
| FQXDE7505I | Backup metadata database corrupted | Informational |
| FQXDE7600I | Cache backup operation started | Informational |
| FQXDE7601I | Cache backup operation completed | Informational |
| FQXDE7602I | Cache restore from persistent device was started | Informational |
| FQXDE7603I | Cache restore operation from persistent device completed | Informational |
| FQXDE7700I | Repository volume is created | Informational |
| FQXDE7701I | The capacity of a repository was increased | Informational |
| FQXDE7702I | The capacity of a repository was decreased | Informational |
| FQXDE7808I | Snapshot group was created | Informational |
| FQXDE7809I | Snapshot group was deleted | Informational |
| FQXDE780AI | The parameters for a snapshot group were set (changed) | Informational |
| FQXDE780BI | A snapshot image was created for a volume | Informational |
| FQXDE780CI | A snapshot image was deleted | Informational |
| FQXDE780DI | A consistency group snapshot image was created | Informational |
| FQXDE780EI | A consistency group snapshot image was deleted | Informational |
| FQXDE780FI | A snapshot volume was created | Informational |
| FQXDE7810I | A snapshot volume was deleted | Informational |
| FQXDE7811I | A snapshot volume was disabled (stopped) | Informational |
| FQXDE7812I | The parameters for a snapshot volume have been changed | Informational |
| FQXDE7813I | Create consistency group | Informational |
| FQXDE7814I | Delete consistency group | Informational |
| FQXDE7815I | Add member to consistency group | Informational |
| FQXDE7816I | Remove member from consistency group | Informational |
| FQXDE7817I | The parameters of a consistency group were changed | Informational |
| FQXDE7818I | Snapshot image rollback started | Informational |
| FQXDE7819I | Consistency group snapshot image rollback started | Informational |
| FQXDE781AI | Snapshot image rollback resumed | Informational |
| FQXDE781BI | Snapshot image rollback canceled | Informational |
| FQXDE781CI | Convert snapshot volume to read-write | Informational |
| FQXDE781DI | Consistency group snapshot volume created | Informational |
| FQXDE781EI | Consistency group snapshot volume deleted | Informational |
| FQXDE781FI | Consistency group snapshot volume disabled (stopped) | Informational |
| FQXDE7820I | Parameters on consistency group snapshot volume changed | Informational |
| FQXDE7821I | Snapshot volume recreated (re-started) | Informational |
| FQXDE7822I | Consistency group snapshot volume recreated (re-started) | Informational |
| FQXDE7823I | A scheduled creation of a snapshot image occurred | Informational |
| FQXDE7824I | A scheduled creation of a consistency group snapshot image occurred | Informational |
| FQXDE7829I | The creation of a consistency group snapshot image is pending | Informational |
| FQXDE782AI | A creation of a snapshot image is pending | Informational |
| FQXDE782BI | The pending creation of a snapshot image was canceled | Informational |
| FQXDE782CI | The pending creation of a consistency group snapshot image was canceled | Informational |
| FQXDE782DI | A snapshot group was revived from the failed state | Informational |
| FQXDE782EI | A snapshot volume was revived from the failed state | Informational |
| FQXDE782FI | A snapshot image rollback was completed | Informational |
| FQXDE7830I | Snapshot image rollback activated | Informational |
| FQXDE7B03I | A thin volume was created | Informational |
| FQXDE7B04I | The virtual capacity of a thin volume was increased | Informational |
| FQXDE7B05I | A thin volume was initialized | Informational |
| FQXDE7B06I | The capacity threshold of a thin volume repository was changed | Informational |
| FQXDE7B07I | The expansion policy of a thin volume was changed | Informational |
| FQXDE7B08I | The maximum expansion capacity of a thin volume repository was changed | Informational |
| FQXDE7B09I | A Defrag operation started on a Thin Provisioned Repository Volume | Informational |
| FQXDE7B0AI | A Defrag operation on a Thin Provisioned Repository Volume completed | Informational |
| FQXDE7B0BI | Thin Provisioned Repository Volume capacity was reduced. The freed capacity was returned to the disk pool | Informational |
| FQXDE7B0CI | Thin Volume reporting policy changed to report as thin volume | Informational |
| FQXDE7B0DI | Thin Volume reporting policy changed to report as thick (fully provisioned) volume | Informational |
| FQXDE7C0CI | Asynchronous mirror group was created | Informational |
| FQXDE7C0DI | Asynchronous mirror group creation failed | Informational |
| FQXDE7C0EI | An asynchronous mirror group was deleted | Informational |
| FQXDE7C0FI | The deletion of an asynchronous mirror group failed | Informational |
| FQXDE7C10I | The parameters of an asynchronous mirror group was changed | Informational |
| FQXDE7C11I | The degraded status of an asynchronous mirror group was cleared | Informational |
| FQXDE7C12I | The synchronization interval threshold exceeded condition of an asynchronous mirror group was cleared | Informational |
| FQXDE7C13I | Asynchronous mirror group role changed to primary | Informational |
| FQXDE7C14I | Asynchronous mirror group role changed to secondary | Informational |
| FQXDE7C15I | Asynchronous mirror group role conflict resolved | Informational |
| FQXDE7C16I | The manual synchronization of an asynchronous mirror group was initiated | Informational |
| FQXDE7C1BI | An asynchronous mirror group was suspended by the user | Informational |
| FQXDE7C1CI | An asynchronous mirror group was resumed | Informational |
| FQXDE7C1DI | An orphaned asynchronous mirror group was resolved | Informational |
| FQXDE7C1EI | A primary member was added to an asynchronous mirror group | Informational |
| FQXDE7C1FI | A secondary member placeholder was added to an asynchronous mirror group | Informational |
| FQXDE7C20I | A secondary member was added to an asynchronous mirror group | Informational |
| FQXDE7C21I | A member of an asynchronous mirror group was removed | Informational |
| FQXDE7C22I | A member of an asynchronous mirror group was recovered | Informational |
| FQXDE7C23I | Security on an asynchronous mirror group member was enabled | Informational |
| FQXDE7C24I | The member repository threshold exceeded condition of an asynchronous mirror group was cleared | Informational |
| FQXDE7C25I | The primary member repository full condition of an asynchronous mirror group was cleared | Informational |
| FQXDE7C26I | The secondary member repository full condition of an asynchronous mirror group was resolved | Informational |
| FQXDE7C27I | Ownership change occurred on member repository of asynchronous mirror group | Informational |
| FQXDE7C28I | An orphaned asynchronous mirror group member was resolved | Informational |
| FQXDE7C29I | Read error occurred on primary asynchronous group member | Informational |
| FQXDE7C2AI | Establishing the synchronization data on all primary members of an asynchronous mirror group failed | Informational |
| FQXDE7C2BI | Read error occurred on secondary asynchronous group member | Informational |
| FQXDE7C2CI | Read error occurred on mirror delta log | Informational |
| FQXDE7C2DI | Fibre channel port activated for asynchronous mirroring | Informational |
| FQXDE7C2EI | Fibre channel port deactivated for asynchronous mirroring | Informational |
| FQXDE7C31I | A controlled asynchronous mirror group role change request was canceled | Informational |
| FQXDE7C33I | An orphaned asynchronous mirror group incomplete member condition was resolved | Informational |
| FQXDE7C35I | A mirror has stopped | Informational |
| FQXDE7C36I | A role changed member was requested for an asynchronous mirror group | Informational |
| FQXDE7E00I | Drive power toggled off | Informational |
| FQXDE7E01I | Drive power toggled on | Informational |
| FQXDE7E02I | Drive power cycle sequence started | Informational |
| FQXDE7E03I | Drive power cycle sequence successfully completed | Informational |
| FQXDE7E04I | Drive power cycle sequence aborted | Informational |
| FQXDE7E05I | Drive recovery criteria not met | Informational |
| FQXDE7E06I | Received a request to power cycle a drive | Informational |
| FQXDE7F00I | SNMP Community was added | Informational |
| FQXDE7F01I | SNMP Community was removed | Informational |
| FQXDE7F02I | SNMP Community parameters was changed | Informational |
| FQXDE7F03I | SNMP trap destination was added | Informational |
| FQXDE7F04I | SNMP trap destination was removed | Informational |
| FQXDE7F05I | SNMP trap destination parameters were changed | Informational |
| FQXDE7F06I | SNMP system variable was changed | Informational |
| FQXDE7F07I | SNMP test alert | Informational |
| FQXDE9000I | The active trace buffer size exceeds the defined threshold | Informational |
| FQXDE9001I | IOC Data Captured | Informational |
| FQXDE9100I | Auto Load Balancing enabled | Informational |
| FQXDE9101I | Auto Load Balancing disabled | Informational |
| FQXDE9104I | Analysis of workload balance was performed | Informational |
| FQXDE9105I | Workload was automatically balanced by transferring volumes | Informational |
| FQXDE9106I | The workload balance was evaluated following load optimization | Informational |
| FQXDE9107I | Host Connectivity Reporting disabled | Informational |
| FQXDE9108I | Host Connectivity Reporting enabled | Informational |
| FQXDE9202I | Security Audit Log Full Policy was changed | Informational |
| FQXDE9203I | Security Audit Log entries were manually cleared | Informational |
| FQXDE9205I | Directory Services Server configuration was changed | Informational |
| FQXDE9206I | The given IP address has attempted too many invalid logins and was locked out for a period of time | Informational |
| FQXDE9209I | SAML Server configuration was changed | Informational |
| FQXDE920AI | SAML Server is enabled | Informational |
| FQXDE920BI | SAML Server is disabled | Informational |
| FQXDE920CI | SAML Server authentication was rejected | Informational |
| FQXDE9400I | NVMe controller destroyed due to keep alive timeout | Informational |
| FQXDE9401I | NVM Connection failed due to lack of available resources | Informational |
| FQXDE9645I | Unrecoverable Interrupted Write | Informational |
| FQXDE9715I | Storage Array Component - Loss of Communication | Informational |
| FQXDE9740I | Degraded Volume | Informational |
| FQXHMDE0001I | User {0} started management of storage {1}. | Informational |
| FQXHMST0001I | User {0} started management of storage {1}. | Informational |
| FQXST0004I | The specified disk had a bad block, which was corrected. | Informational |
| FQXST0006I | Disk group creation failed immediately. | Informational |
| FQXST0009I | The specified spare disk has been used in the specified disk group to bring it back to a fault-tolerant status. | Informational |
| FQXST0016I | The specified disk has been designated as a global spare. | Informational |
| FQXST0018I | Disk group reconstruction completed. | Informational |
| FQXST0019I | A rescan has completed. | Informational |
| FQXST0020I | Storage Controller firmware has been updated. | Informational |
| FQXST0021I | Disk group verification succeeded, failed immediately, or was halted by a user. | Informational |
| FQXST0023I | Disk group creation started. | Informational |
| FQXST0025I | Disk group statistics were reset. | Informational |
| FQXST0028I | Controller parameters were changed. | Informational |
| FQXST0031I | The specified disk is no longer a global or dedicated spare. | Informational |
| FQXST0032I | Disk group verification started. | Informational |
| FQXST0033I | Controller time and date were changed. | Informational |
| FQXST0034I | The controller configuration has been restored to factory defaults. | Informational |
| FQXST0037I | Disk group reconstruction started. When complete, event 18 is logged. | Informational |
| FQXST0041I | The specified disk was designated a spare for the specified disk group. | Informational |
| FQXST0043I | The specified disk group was deleted. | Informational |
| FQXST0047I | An error detected by the sensors has been cleared. This event indicates that a problem reported by event 39 or 40 is resolved. | Informational |
| FQXST0048I | The specified disk group was renamed. | Informational |
| FQXST0049I | A lengthy SCSI maintenance command has completed. (This typically occurs during a disk firmware update.) | Informational |
| FQXST0052I | Disk group expansion started. | Informational |
| FQXST0053I | Disk group expansion completed, failed immediately, or was halted by a user. | Informational |
| FQXST0056I | A controller powered up or restarted. | Informational |
| FQXST0058I | A disk drive reported an event. | Informational |
| FQXST0059I | The controller detected a non-parity error while communicating with the specified SCSI device. The error was detected by the controller, not the disk. | Informational |
| FQXST0068I | The controller that logged this event is shut down, or both controllers are shut down. | Informational |
| FQXST0071I | The controller started or completed failing over. | Informational |
| FQXST0072I | After failover, recovery has started or completed. | Informational |
| FQXST0073I | The two controllers are communicating with each other and cache redundancy is enabled. | Informational |
| FQXST0074I | The FC loop ID for the specified disk group was changed to be consistent with the IDs of other disk groups. | Informational |
| FQXST0075I | The specified volume's LUN (logical unit number) has been unassigned because it conflicts with LUNs assigned to other volumes. This can happen when disks containing data for a mapped volume are moved from one storage system to another. | Informational |
| FQXST0076I | The controller is using default configuration settings. This event occurs on the first power up, and might occur after a firmware update. | Informational |
| FQXST0077I | The cache was initialized as a result of power up or failover. | Informational |
| FQXST0079I | A trust operation completed for the specified disk group. | Informational |
| FQXST0080I | The controller enabled or disabled the specified parameters for one or more disks. | Informational |
| FQXST0081I | The current controller has restarted the partner controller. The other controller will restart. | Informational |
| FQXST0083I | The partner controller is shutting down or restarting. | Informational |
| FQXST0086I | Host-port or disk-channel parameters were changed. | Informational |
| FQXST0090I | The partner controller does not have a mirrored configuration image for the current controller, so the current controller's local flash configuration is being used. | Informational |
| FQXST0096I | Pending configuration changes that take effect at startup were ignored because customer data might be present in cache. | Informational |
| FQXST0103I | The name was changed for the specified volume. | Informational |
| FQXST0104I | The size was changed for the specified volume. | Informational |
| FQXST0105I | The default LUN (logical unit number) was changed for the specified volume. | Informational |
| FQXST0106I | The specified volume was added to the specified pool. | Informational |
| FQXST0108I | The specified volume was deleted from the specified pool. | Informational |
| FQXST0109I | The statistics for the specified volume were reset. | Informational |
| FQXST0110I | Ownership of the specified disk group was transferred to the other controller. | Informational |
| FQXST0111I | The link for the specified host port is up. | Informational |
| FQXST0112I | The link for the specified host port went down because the controller is starting up. | Informational |
| FQXST0114I | The link for the specified disk-channel port is down. Note that events 114 and 211 are logged whenever a user-requested rescan occurs and do not indicate an error. | Informational |
| FQXST0118I | Cache parameters have been changed for the specified volume. | Informational |
| FQXST0139I | The Management Controller (MC) powered up or restarted. | Informational |
| FQXST0140I | The Management Controller is about to restart. | Informational |
| FQXST0141I | This event is logged when the IP address used for management of the system has been changed by a user or by a DHCP server (if DHCP is enabled). This event is also logged during power up or failover recovery, even when the address has not changed. | Informational |
| FQXST0152I | The Management Controller (MC) has not communicated with the Storage Controller (SC) for 160 seconds. | Informational |
| FQXST0153I | The Management Controller (MC) re-established communication with the Storage Controller (SC). | Informational |
| FQXST0154I | New firmware was loaded in the Management Controller (MC). | Informational |
| FQXST0155I | New loader firmware was loaded in the Management Controller (MC). | Informational |
| FQXST0156I | The Management Controller (MC) was restarted from the Storage Controller (SC) in a normal case, such as when initiated by a user. | Informational |
| FQXST0170I | The last rescan detected that the specified enclosure was added to the system. | Informational |
| FQXST0171I | The last rescan detected that the specified enclosure was removed from the system. | Informational |
| FQXST0173I | The specified disk group was removed from quarantine. | Informational |
| FQXST0174I | An enclosure or disk firmware update has succeeded, been aborted by a user, or failed. If the firmware update fails, the user will be notified about the problem immediately and should take care of the problem at that time, so even when there is a failure, this event is logged as with a severity of Informational. | Informational |
| FQXST0175I | The network-port Ethernet link for the specified controller is up or down. | Informational |
| FQXST0176I | The error statistics for the specified disk have been reset. | Informational |
| FQXST0177I | Cache data was purged for the specified missing volume. | Informational |
| FQXST0181I | One or more configuration parameters associated with the Management Controller (MC) were changed, such as the configuration for SNMP, SMI-S, email notification, and system strings (system name, system location, etc.). | Informational |
| FQXST0182I | All disk channels have been paused. I/O will not be performed on the disks until all channels are unpaused. | Informational |
| FQXST0183I | All disk channels have been unpaused, meaning that I/O can resume. An unpause initiates a rescan, which when complete is logged as event 19. This event indicates that the pause reported by event 182 has ended. | Informational |
| FQXST0185I | An enclosure management processor (EMP) write command completed. | Informational |
| FQXST0186I | Enclosure parameters were changed by a user. | Informational |
| FQXST0187I | The write-back cache is enabled. Event 188 is the corresponding event that is logged when write-back cash is disabled. | Informational |
| FQXST0188I | Write-back cache is disabled. Event 187 is the corresponding even that is logged when write-back cache is disabled. | Informational |
| FQXST0189I | A disk channel that was previously degraded or failed is now healthy. | Informational |
| FQXST0190I | The controller module's supercapacitor pack has started charging. | Informational |
| FQXST0191I | The auto-write-through trigger event that caused event 190 to be logged has been resolved. | Informational |
| FQXST0192I | The controller module's temperature has exceeded the normal operating range. | Informational |
| FQXST0193I | The auto-write-through trigger event that caused event 192 to be logged has been resolved. | Informational |
| FQXST0194I | The Storage Controller in the partner controller module is not up. | Informational |
| FQXST0195I | The auto-write-through trigger event that caused event 194 to be logged has been resolved. | Informational |
| FQXST0198I | A power supply failed. | Informational |
| FQXST0199I | The auto-write-through trigger event that caused event 198 to be logged has been resolved. | Informational |
| FQXST0200I | A fan failed. | Informational |
| FQXST0201I | The auto-write-through trigger event that caused event 200 to be logged has been resolved. | Informational |
| FQXST0202I | An auto-write-through trigger condition has been cleared, causing write-back cache to be re-enabled. The environmental change is also logged at approximately the same time as this event (event 191, 193, 195, 199, 201, and 241.) | Informational |
| FQXST0204I | The system came up normally, and the NV device is in a normal expected state. | Informational |
| FQXST0205I | The specified volume has been mapped or unmapped. | Informational |
| FQXST0206I | Disk group scrub started. | Informational |
| FQXST0207I | Disk group scrub completed or was stopped by a user. | Informational |
| FQXST0208I | A scrub-disk job started for the specified disk. The result will be logged with event 209. | Informational |
| FQXST0209I | A scrub-disk job logged with event 208 has completed and found no errors, a disk being scrubbed (with no errors found) has been added to a disk group, or a user has stopped the job. | Informational |
| FQXST0211I | SAS topology has changed. The number of SAS expanders has increased or decreased. | Informational |
| FQXST0216I | An uncommitted snapshot has been deleted. Removal of the specified snapshot completed successfully. | Informational |
| FQXST0219I | Utility priority was changed by a user. | Informational |
| FQXST0235I | An enclosure management processor (EMP) reported an event. | Informational |
| FQXST0236I | A special shutdown operation started. These special shutdown operations are used as part of the firmware-update process. | Informational |
| FQXST0237I | A firmware update started and is in progress. This event provides details of the steps in a firmware-update operation. | Informational |
| FQXST0241I | The auto-write-through trigger event that caused event 242 to be logged has been resolved. | Informational |
| FQXST0243I | A new controller enclosure has been detected. This happens when a controller module is moved from one enclosure to another and the controller detects that the midplane WWN is different from the WWN it has in its local flash. | Informational |
| FQXST0245I | An existing disk channel target device is not responding to SCSI discovery commands. | Informational |
| FQXST0248I | A valid feature license was successfully installed. See event 249 for details about each licensed feature. | Informational |
| FQXST0249I | After a valid license is installed, this event is logged for each licensed feature to show the new license value for that feature. The event specifies whether the feature is licensed, whether the license is temporary, and whether the temporary license is expired. | Informational |
| FQXST0251I | A volume-copy operation started for the specified source volume. | Informational |
| FQXST0253I | A license was uninstalled. | Informational |
| FQXST0255I | The PBCs across controllers do not match because the PBC from controller A and the PBC from controller B are from different vendors. This might limit the available configurations. | Informational |
| FQXST0259I | In-band CAPI commands were disabled. | Informational |
| FQXST0260I | In-band CAPI commands were enabled. | Informational |
| FQXST0261I | In-band SES commands were disabled. | Informational |
| FQXST0262I | In-band SES commands were enabled. | Informational |
| FQXST0266I | A volume-copy operation for the specified master volume was stopped by a user. | Informational |
| FQXST0268I | A volume-copy operation for the specified volume completed. | Informational |
| FQXST0269I | A partner firmware update operation started. This operation is used to copy firmware from one controller to the other to bring both controllers up to the same version of firmware. | Informational |
| FQXST0271I | The storage system could not get a valid serial number from the controller's FRU ID SEEPROM, either because it could not read the FRU ID data, because the data in it are not valid or because the data have not been programmed. | Informational |
| FQXST0273I | PHY fault isolation was enabled or disabled by a user for the specified enclosure and controller module. | Informational |
| FQXST0275I | The specified PHY was enabled. | Informational |
| FQXST0299I | The controller's RTC setting was recovered successfully. | Informational |
| FQXST0300I | CPU frequency was changed to high. | Informational |
| FQXST0301I | CPU frequency was changed to low. | Informational |
| FQXST0302I | DDR memory clock frequency was changed to high. | Informational |
| FQXST0303I | DDR memory clock frequency was changed to low. | Informational |
| FQXST0304I | The controller has detected I2C errors that might have been recovered. | Informational |
| FQXST0305I | A serial number in Storage Controller (SC) flash memory was not valid when compared to the serial number in the controller-module or midplane FRU ID SEEPROM. The valid serial number was recovered automatically. | Informational |
| FQXST0306I | The controller-module serial number in Storage Controller (SC) flash memory was not valid when compared to the serial number in the controller-module FRU ID SEEPROM. The valid serial number was recovered automatically. | Informational |
| FQXST0309I | When the Management Controller (MC) is started, the IP data is obtained from the midplane FRU ID SEEPROM where it is persisted. If the system is unable to write it to the SEEPROM the last time it changed, a flag is set in flash memory. This flag is checked during startup, and if set, this event is logged and the IP data that is in flash memory is used. The IP data might not be correct if the controller module was swapped because the data in the controller's flash memory are used. | Informational |
| FQXST0310I | After a rescan, back-end discovery and initialization of data for at least one EMP (Enclosure Management Processor) completed. This event is not logged again when processing completes for other EMPs in the system. | Informational |
| FQXST0311I | A user initiated a ping of a host through the iSCSI interface. | Informational |
| FQXST0312I | This event is used by email messages and SNMP traps when testing notification settings. This event is not recorded in the event log. | Informational |
| FQXST0316I | The temporary license for a feature will expire in 10 days. Any components created with the feature will remain accessible but new components cannot be created after the license expires. | Informational |
| FQXST0352I | Expander Controller (EC) assert data or stack-dump data are available. | Informational |
| FQXST0353I | Expander Controller (EC) assert data and stack-dump data were cleared. | Informational |
| FQXST0354I | The SAS topology has changed on a host port. At least one PHY is active. For example, the SAS cable connecting a controller host port to a host was connected. | Informational |
| FQXST0359I | All PHYs that were down for the specified disk channel have recovered and are now up. | Informational |
| FQXST0360I | The speed of the specified disk PHY was renegotiated. | Informational |
| FQXST0361I | A scheduled task was initiated. | Informational |
| FQXST0362I | The scheduler experienced a problem with the specified task. | Informational |
| FQXST0363I | When the Management Controller (MC) is restarted, firmware versions that are currently installed are compared against those in the bundle that was most recently installed. If the versions match, this event is logged as Infomational severity. Components checked include the CPLD, Expander Controller (EC), Storage Controller (SC), and MC. | Informational |
| FQXST0364I | The broadcast bus is running as generation 1. | Informational |
| FQXST0400I | The specified log has filled to a level at which it needs to be transferred to a log-collection system. | Informational |
| FQXST0454I | A user changed the drive-spin-down delay for the specified disk group to the specified value. | Informational |
| FQXST0457I | The specified virtual pool was created. | Informational |
| FQXST0458I | Disk groups were added to the specified virtual pool. | Informational |
| FQXST0459I | Removal of the specified disk group(s) was started. When this operation is complete, event 470 is logged. | Informational |
| FQXST0461I | The specified disk group that was missing from the specified virtual pool was recovered. This event indicates that a problem reported by event 460 is resolved. | Informational |
| FQXST0462I | The specified virtual pool exceeded one of its thresholds for allocated pages. | Informational |
| FQXST0463I | The specified virtual pool has dropped below one of its thresholds for allocated pages. This event indicates that a condition reported by event 462 is no longer applicable. | Informational |
| FQXST0465I | A user removed an unsupported cable or SFP from the specified controller host port. | Informational |
| FQXST0466I | The specified virtual pool was deleted. | Informational |
| FQXST0467I | The specified disk group was added successfully. | Informational |
| FQXST0468I | The FPGA temperature returned to the normal operating range and the speed of buses connecting the FPGA to downstream adapters was restored. The speed was reduced to compensate for an FPGA over-temperature condition. This event indicates that a problem reported by event 469 is resolved. | Informational |
| FQXST0470I | The removal of the specified disk group(s) completed successfully. | Informational |
| FQXST0473I | The specified volume is using more than its threshold percentage of its virtual pool. | Informational |
| FQXST0474I | The specified volume is no longer using more than its threshold percentage of its virtual pool. This event indicates that the condition reported by event 473 is no longer applicable. | Informational |
| FQXST0477I | The CPU temperature exceeded the normal range so the CPU speed was reduced. IOPS were reduced. The storage system is operational, but I/O performance is reduced. | Informational |
| FQXST0478I | A problem reported by event 476 or 477 is resolved. | Informational |
| FQXST0487I | Historical performance statistics were reset. | Informational |
| FQXST0488I | The creation of a volume group started. | Informational |
| FQXST0489I | The creation of a volume group completed. | Informational |
| FQXST0490I | The creation of a volume group failed. | Informational |
| FQXST0491I | The creation of a volume group started. | Informational |
| FQXST0492I | The volumes in a volume group were ungrouped. | Informational |
| FQXST0493I | A group of volumes was modified. | Informational |
| FQXST0502I | The specified SSD has 20% or less of its life remaining. | Informational |
| FQXST0503I | The Intelligent BackEnd Error Monitor (IBEEM) has discovered that continuous errors are being reported for the specified PHY. IBEEM logged this event after monitoring the PHY for 30 minutes. | Informational |
| FQXST0504I | Service debug access to the system was enabled or disabled by a user. Allowing service debug access might have security implications. After the diagnosis is complete you should disallow such access. | Informational |
| FQXST0506I | The addition of the specified disk group started. When this operation is complete, event 467 is logged. | Informational |
| FQXST0507I | The link speed of the specified disk does not match the link speed capacity of the enclosure. | Informational |
| FQXST0510I | The FDE lock key has been set or changed by a user. | Informational |
| FQXST0511I | The FDE import lock key has been set by a user. | Informational |
| FQXST0512I | The system was set to the FDE secured state by a user. | Informational |
| FQXST0513I | The system was set to the FDE repurposed state by a user. | Informational |
| FQXST0514I | The FDE lock key and import key were cleared by a user. | Informational |
| FQXST0515I | An FDE disk was repurposed by a user. | Informational |
| FQXST0517I | A disk that was formerly in the FDE unavailable state is no longer unavailable. The disk was returned to normal operations. | Informational |
| FQXST0523I | This event provides additional details associated with a scrub-disk-group job, expanding on the information in event 206, 207, or 522. | Informational |
| FQXST0533I | This event provides details about the result of the MC test of the specified component. | Informational |
| FQXST0551I | A SES alert for a power supply in the specified enclosure has been resolved. | Informational |
| FQXST0552I | A SES alert for a fan in the specified enclosure has been resolved. | Informational |
| FQXST0553I | A SES alert for a temperature sensor in the specified enclosure has been resolved. | Informational |
| FQXST0554I | A SES alert for a voltage sensor in the specified enclosure was resolved. | Informational |
| FQXST0555I | A SES alert for an expander in the specified enclosure has been resolved. | Informational |
| FQXST0556I | A SES alert for an expander in the specified enclosure has been resolved. | Informational |
| FQXST0557I | A SES alert for a current sensor in the specified enclosure was resolved. | Informational |
| FQXST0562I | Virtual pool statistics were reset. | Informational |
| FQXST0563I | A disk was restarted. | Informational |
| FQXST0566I | One of the DDR ports has been busy for at least 5 minutes. | Informational |
| FQXST0568I | A disk group has mixed physical sector size disks (for example 512n and 512e disks in the same disk group). | Informational |
| FQXST0569I | A previously detected SAS host port cable mismatch has been resolved for the specified port number. The proper cable type has been connected. | Informational |
| FQXST0571I | Snapshot space exceeded either the low or medium snapshot space threshold. | Informational |
| FQXST0572I | The specified virtual pool dropped below one of its snapshot space thresholds. | Informational |
| FQXST0574I | A peer connection was created. | Informational |
| FQXST0575I | A peer connection was deleted. | Informational |
| FQXST0576I | A replication set was created. | Informational |
| FQXST0577I | A replication set was deleted. | Informational |
| FQXST0578I | A replication started. | Informational |
| FQXST0579I | A replication completed. | Informational |
| FQXST0580I | A replication was stopped. | Informational |
| FQXST0581I | A replication was suspended. | Informational |
| FQXST0584I | A peer connection was modified. | Informational |
| FQXST0585I | A replication set was modified. | Informational |
| FQXST0586I | A replication resumed. | Informational |
| FQXST0594I | The specified disk in the specified disk group is missing and the disk group is quarantined. | Informational |
| FQXST0595I | The specified disk in the specified disk group is missing and the disk group is quarantined. | Informational |
| FQXDE204EF | Recoverable drive hardware failure detected by drive | Warning |
| FQXDE204FF | Recoverable drive hardware failure detected by drive | Warning |
| FQXDE2277G | Repository volume security incompatibility detected | Warning |
| FQXDE2308F | Chassis serial number might be incorrect | Warning |
| FQXDE2866F | An IOM (ESM) has reported an exception event | Warning |
| FQXDE3307F | Insufficient storage or drive count for autocode synchronization image | Warning |
| FQXDE507EF | AutoSupport maintenance mode configuration request failed | Warning |
| FQXDE5108F | Controller failover due to lost expansion tray access | Warning |
| FQXDE7801G | Snapshot group repository over threshold | Warning |
| FQXDE7804G | Snapshot volume repository over threshold | Warning |
| FQXDE7825F | A scheduled creation of a snapshot image failed | Warning |
| FQXDE7826F | A scheduled creation of a consistency group snapshot image failed | Warning |
| FQXDE7827G | A pending creation of a consistency group snapshot image failed | Warning |
| FQXDE7828G | A pending creation of a snapshot image failed | Warning |
| FQXDE7900F | Copy on write integrity fault | Warning |
| FQXDE7A00F | A high level volume utility write ahead log integrity fault | Warning |
| FQXDE7B00G | A thin volume repository capacity threshold was exceeded | Warning |
| FQXDE7C00G | An asynchronous mirror group was marked degraded | Warning |
| FQXDE7C01G | An asynchronous mirror group synchronization interval threshold was exceeded | Warning |
| FQXDE7C05G | An asynchronous mirror group is orphaned (no corresponding mirror group on the other storage array) | Warning |
| FQXDE7C07G | Asynchronous mirror group member repository threshold was exceeded | Warning |
| FQXDE7C08G | An asynchronous mirror group primary member repository is full | Warning |
| FQXDE7C0BG | An asynchronous mirror group member is orphaned | Warning |
| FQXDE7C32G | The controller firmware detected that only a placeholder volume of an asynchronous mirror group member exists | Warning |
| FQXDE9201G | Security Audit Log is nearing maximum capacity and should be cleared now to avoid losing events | Warning |
| FQXDE9300G | An installed certificate used for KMIP server authentication is nearing expiration | Warning |
| FQXDE9306G | An attempt to create a security key failed as the storage array's client certificate does not match any of the existing owners on the KMIP server | Warning |
| FQXDE9631F | Volumes Degraded in Volume Group or Pool - Noncritical Drive Error | Warning |
| FQXDE9777G | Repository - Threshold Exceeded | Warning |
| FQXDE9780G | Snapshot Volume Repository - Threshold Exceeded | Warning |
| FQXDE9784G | Consistency Group Snapshot Image Creation Failed | Warning |
| FQXDE9785G | Snapshot Image Creation Failed | Warning |
| FQXDE9786G | Thin Volume Repository - Threshold Exceeded | Warning |
| FQXDE9789G | Degraded Mirror Group | Warning |
| FQXDE9790G | Mirror Group Synchronization - Threshold Exceeded | Warning |
| FQXDE9794G | Orphaned Mirror Group | Warning |
| FQXDE9796G | Mirrored Volume Repository - Threshold Exceeded | Warning |
| FQXDE9797G | Mirrored Primary Volume Repository - Full | Warning |
| FQXDE9799G | Orphaned Mirrored Volume | Warning |
| FQXDE9800G | Orphaned Mirrored Volume | Warning |
| FQXDE9807G | Audit Log - Early Threshold Exceeded | Warning |
| FQXDE9809G | Key Management Certificate Nearing Expiration | Warning |
| FQXDE9815G | Drive Security Key Creation Failed | Warning |
| FQXDE9816G | A controller was placed in Service mode | Warning |
| FQXHMDE0001G | A trap alert destination subscription failure occurred when user {0} managed server {1}. | Warning |
| FQXHMDE0002G | A trap alert destination unsubscription failure occurred when user {0} unmanaged server {1}. | Warning |
| FQXHMDE0003G | Inventory data could not be retrieved from the endpoint {0}. | Warning |
| FQXHMDE0010G | The SSL/TLS certificate provided by the {0} endpoint is not valid. | Warning |
| FQXHMST0001G | A trap alert destination subscription failure occurred when user {0} managed server {1}. | Warning |
| FQXHMST0002G | A trap alert destination unsubscription failure occurred when user {0} unmanaged server {1}. | Warning |
| FQXHMST0003G | Inventory data could not be retrieved from the endpoint {0}. | Warning |
| FQXHMST0004G | Credentials could not be updated from endpoint {0}. | Warning |
| FQXHMST0005G | User {0} cannot removed the credentials from endpoint {1}. | Warning |
| FQXHMST0006G | User {0} cannot remove endpoint {1}. | Warning |
| FQXHMST0007G | Endpoint {0} could not be accessed because credentials were refused. | Warning |
| FQXHMST0008G | Endpoint {0} could not be accessed. | Warning |
| FQXHMST0009G | User {0} cannot access the endpoint {1}. | Warning |
| FQXHMST0010G | The SSL/TLS certificate provided by the {0} endpoint is not valid. | Warning |
| FQXHMST0015G | The controller {0} is not operational. | Warning |
| FQXDE1010M | Impending drive failure detected by drive | Critical |
| FQXDE101EM | Impending drive failure detected by controller | Critical |
| FQXDE1020M | Data assurance drive was locked out | Critical |
| FQXDE1207M | Fibre channel link errors - threshold exceeded | Critical |
| FQXDE1208M | Data rate negotiation failed | Critical |
| FQXDE1209M | Drive channel set to Degraded | Critical |
| FQXDE120AM | SFP failed | Critical |
| FQXDE120DM | Host-side SFP failed | Critical |
| FQXDE1403M | Excessive reboots (exceptions) have occurred on the controller | Critical |
| FQXDE150EM | Controller loop-back diagnostics failed | Critical |
| FQXDE150FM | Channel miswire | Critical |
| FQXDE1510M | IOM (ESM) miswire | Critical |
| FQXDE1513M | Individual drive - Degraded path | Critical |
| FQXDE1515M | Drive Channel hardware failed | Critical |
| FQXDE151AM | Optical link speed detection failure | Critical |
| FQXDE151EM | Controller miswire for drive channel occurred | Critical |
| FQXDE1522M | Drive enclosure type miswire | Critical |
| FQXDE1524M | Trunk incompatible IOM (ESM) | Critical |
| FQXDE1525M | Fibre trunk miswire | Critical |
| FQXDE1650M | SAS host channel miswire detected | Critical |
| FQXDE1652L | SAS source driver partner initiator overflow | Critical |
| FQXDE1654L | Host wide port is degraded | Critical |
| FQXDE165AM | An error was detected during SAS backend discovery processing | Critical |
| FQXDE1700M | Invalid SAS topology detected | Critical |
| FQXDE1702M | SAS host adapter miswire detected | Critical |
| FQXDE1704M | SAS IOM (ESM) miswire detected | Critical |
| FQXDE1706M | Optimal wide port becomes degraded | Critical |
| FQXDE1707M | Degraded wide port becomes failed | Critical |
| FQXDE170AM | Drive expansion port miswire | Critical |
| FQXDE170FM | Controller wide port has gone to degraded state | Critical |
| FQXDE1710M | Controller wide port has gone to failed state | Critical |
| FQXDE171AM | A controller may have lost access to expansion trays | Critical |
| FQXDE180AM | Failed I/O host card; iSCSI interface error detected | Critical |
| FQXDE1904M | Failed host interface card | Critical |
| FQXDE1907M | Controller was locked down due to too many missing drives | Critical |
| FQXDE1908M | A controller detected that the combination of host interface cards are out of compliance with limitations of the controller or the firmware. | Critical |
| FQXDE200AM | Data/parity mismatch on volume | Critical |
| FQXDE202EM | Read drive error during interrupted write | Critical |
| FQXDE203BM | Drive failed due to un-recoverable read error during scan | Critical |
| FQXDE2045M | Redundancy group not consistent during reconfiguration | Critical |
| FQXDE2046L | Isolation of drive causing redundancy mismatch | Critical |
| FQXDE2047L | Different Data Returned On Read Retry | Critical |
| FQXDE2048L | Data altered to correct redundancy mismatch | Critical |
| FQXDE2069M | Controller is in Service Mode due to excessive Data Assurance errors | Critical |
| FQXDE206AM | Controller is in Analysis Lockdown Mode due to excessive Data Assurance errors | Critical |
| FQXDE2109M | Controller cache not enabled - cache sizes do not match | Critical |
| FQXDE210CM | Controller cache battery failed | Critical |
| FQXDE210EM | Controller cache memory recovery failed after power cycle or reset | Critical |
| FQXDE2110L | Controller cache memory initialization failed | Critical |
| FQXDE2113M | Controller cache battery nearing expiration | Critical |
| FQXDE211BM | Batteries present but NVSRAM file configured for no batteries | Critical |
| FQXDE211EM | Current cache size is unsupported | Critical |
| FQXDE211FM | Insufficient cache backup device capacity | Critical |
| FQXDE2120M | Insufficient processor memory for cache | Critical |
| FQXDE2124M | Dedicated mirror channel failed | Critical |
| FQXDE2125L | Integrity check failed during cache restore | Critical |
| FQXDE2126L | Backup of cache to persistent device did not complete | Critical |
| FQXDE212BM | Write-back caching forcibly disabled | Critical |
| FQXDE212EM | Cached data may have been lost | Critical |
| FQXDE2131M | Dirty cache not flushed on the only active controller | Critical |
| FQXDE222DM | Drive manually failed | Critical |
| FQXDE2249M | Physical drive replacement is too small | Critical |
| FQXDE224AM | Drive has wrong block size | Critical |
| FQXDE224BM | Drive failed - initialization failure | Critical |
| FQXDE224DM | Drive failed - no response at start of day | Critical |
| FQXDE224EM | Drive failed - initialization/reconstruction failure | Critical |
| FQXDE2250M | Volume failure | Critical |
| FQXDE2251M | Drive failed - reconstruction failure | Critical |
| FQXDE2252M | Drive marked offline during interrupted write | Critical |
| FQXDE2260M | Uncertified Drive Detected | Critical |
| FQXDE2262M | Failed drive replaced with wrong drive type | Critical |
| FQXDE2266M | Volume modification operation failed | Critical |
| FQXDE2267M | Incompatible drive due to invalid configuration on drive | Critical |
| FQXDE226BM | Security (FDE) key needed | Critical |
| FQXDE226CM | Drive failure | Critical |
| FQXDE226DM | Assigned drive or hot spare-in use drive removed | Critical |
| FQXDE226EM | Solid state drive at end of life | Critical |
| FQXDE2271M | Physical drive has unsupported capacity | Critical |
| FQXDE2273M | Hot spare in use | Critical |
| FQXDE2274M | Component is missing | Critical |
| FQXDE2275M | Component incomplete | Critical |
| FQXDE2276M | Interposer FW version unsupported | Critical |
| FQXDE2278M | Incompatible alignment for emulation drive | Critical |
| FQXDE227CM | Waiting for eligible copy destination to start drive copy | Critical |
| FQXDE2285M | Impending drive failure detected by drive | Critical |
| FQXDE2287M | A NTP domain server name is either invalid or the configured primary or secondary DNS servers are unreachable | Critical |
| FQXDE2288M | Either the NTP server's resolved or configured IP address is wrong or the IP address is unavailable via the attached network | Critical |
| FQXDE2289M | The DNS/NTP configuration on this controller is either incorrect or all the NTP servers are unreachable over the network | Critical |
| FQXDE2302M | SBB validation failure for power supply | Critical |
| FQXDE2303M | Mismatched midplane EEPROM contents | Critical |
| FQXDE2304M | Two wire interface bus failure | Critical |
| FQXDE2305M | VPD EEPROM corruption | Critical |
| FQXDE2500M | Controller removed | Critical |
| FQXDE2602L | Automatic controller firmware synchronization failed | Critical |
| FQXDE2604M | Persistent controller memory parity error | Critical |
| FQXDE2607M | Inconsistent security (FDE) storage array lock key | Critical |
| FQXDE2705M | Multiple mismatched key ids found | Critical |
| FQXDE2801M | Storage array running on UPS battery | Critical |
| FQXDE2803M | UPS battery - two minutes to failure | Critical |
| FQXDE280AM | Controller tray component removed | Critical |
| FQXDE280BM | Controller tray component failed | Critical |
| FQXDE280DM | Drive tray component failed or removed | Critical |
| FQXDE2816M | Tray ID conflict - duplicate IDs across drive trays | Critical |
| FQXDE281BM | Nominal temperature exceeded | Critical |
| FQXDE281CM | Maximum temperature exceeded | Critical |
| FQXDE281DM | Temperature sensor removed | Critical |
| FQXDE281EM | IOM (ESM) firmware mismatch | Critical |
| FQXDE2823M | Drive by-passed | Critical |
| FQXDE2829M | Controller redundancy lost | Critical |
| FQXDE282BM | Drive tray path redundancy lost | Critical |
| FQXDE282DM | Drive path redundancy lost | Critical |
| FQXDE282FM | Incompatible version of IOM (ESM) firmware detected | Critical |
| FQXDE2830M | Mixed drive types out of compliance | Critical |
| FQXDE2831M | Uncertified IOM (ESM) detected | Critical |
| FQXDE2832M | Uncertified drive tray detected | Critical |
| FQXDE2833M | Controller host interface card ID mismatch | Critical |
| FQXDE2835M | Drive trays not cabled correctly | Critical |
| FQXDE2836M | Discrete lines diagnostic failure | Critical |
| FQXDE2838M | Interconnect/battery canister removed | Critical |
| FQXDE283BM | Power supply failed | Critical |
| FQXDE2841M | Controller submodel mismatch | Critical |
| FQXDE2849M | IOM (ESM) Hardware mismatch | Critical |
| FQXDE284BL | Link Speed (data rate) switch position has changed | Critical |
| FQXDE284EM | Redundant power-fan canisters required - only one power-fan canister detected | Critical |
| FQXDE284FM | Misconfigured tray | Critical |
| FQXDE2852M | IOM (ESM) configuration settings version mismatch | Critical |
| FQXDE2854M | Drive port bypassed - Error thresholds exceeded | Critical |
| FQXDE2855M | Controller cannot read alternate controller board ID | Critical |
| FQXDE2856M | Drawer failed | Critical |
| FQXDE2857M | Drawer open or removed | Critical |
| FQXDE285DM | Expansion tray thermal shutdown | Critical |
| FQXDE285FM | A drawer in the tray has become degraded | Critical |
| FQXDE2861M | A drawer was detected that is not valid | Critical |
| FQXDE2862M | A drawer was removed | Critical |
| FQXDE2863M | Host-side SFP failed | Critical |
| FQXDE2864M | Host-side SFP unsupported | Critical |
| FQXDE2900L | Entering invalid system configuration | Critical |
| FQXDE3604M | SSD cache failed due to cache size mismatch on the two controllers | Critical |
| FQXDE3605M | SSD cache has associated non-optimal drives | Critical |
| FQXDE3803M | Disk pool reconstruction reserved drive count is below threshold | Critical |
| FQXDE3804M | Disk pool utilization exceeded the warning threshold | Critical |
| FQXDE3805M | Disk pool utilization exceeded the critical threshold | Critical |
| FQXDE3809M | All of the disk pool's free capacity was used | Critical |
| FQXDE380CM | Disk pool configuration has insufficient memory | Critical |
| FQXDE380DL | Disk pool has corrupted database record | Critical |
| FQXDE4011M | Volume not on preferred path due to AVT/RDAC failover | Critical |
| FQXDE5005M | Place controller offline | Critical |
| FQXDE5038L | Storage array 10-minute lockout; maximum incorrect passwords attempted | Critical |
| FQXDE5040M | Place controller in service mode | Critical |
| FQXDE506DM | Security (FDE) key failed validation attempts due to excessive tries | Critical |
| FQXDE5100M | Base controller diagnostic failed | Critical |
| FQXDE5101M | Base controller diagnostic on alternate controller failed | Critical |
| FQXDE5102M | IOC fault diagnostic failure was detected | Critical |
| FQXDE5103L | SAS PHY disabled bypassed port | Critical |
| FQXDE5104L | SAS PHY disabled bypassed drive | Critical |
| FQXDE5105M | SAS PHY disabled local wide port | Critical |
| FQXDE5106M | SAS PHY disabled shared wide port | Critical |
| FQXDE5222M | Invalid host OS index detected | Critical |
| FQXDE5223M | Invalid default OS index detected | Critical |
| FQXDE5224M | Inactive host port registered | Critical |
| FQXDE5225M | Inactive initiator registered | Critical |
| FQXDE5402M | Premium feature out of compliance | Critical |
| FQXDE5403M | Premium feature exceeds limit | Critical |
| FQXDE5405M | Gold Key - mismatched settings | Critical |
| FQXDE5406M | Mixed drive types - mismatched settings | Critical |
| FQXDE5409M | Feature evaluation period expiration is imminent | Critical |
| FQXDE560DM | Diagnostics read test failed on controller | Critical |
| FQXDE560EM | This controller's alternate failed diagnostics read test | Critical |
| FQXDE560FM | Diagnostics write test failed on controller | Critical |
| FQXDE5610M | This controller's alternate failed diagnostics write test | Critical |
| FQXDE5616M | Diagnostics rejected configuration error on controller | Critical |
| FQXDE5617M | Diagnostics rejected - configuration error on this controller's alternate | Critical |
| FQXDE6101L | Internal configuration database full | Critical |
| FQXDE6107M | This controller's alternate is non-functional and is being held in reset | Critical |
| FQXDE6109M | The controller is booting up in database recovery mode | Critical |
| FQXDE610BM | The subrecord validation failed and could not be fixed | Critical |
| FQXDE6400M | Dual primary volume conflict | Critical |
| FQXDE6401M | Dual secondary volume conflict | Critical |
| FQXDE6402M | Data on mirrored pair unsynchronized | Critical |
| FQXDE6411M | Mirror relationship has inconsistent write mode | Critical |
| FQXDE6503M | Communication to remote volume down | Critical |
| FQXDE6505M | Failed to communicate storage array's world-wide name | Critical |
| FQXDE6600M | Volume copy operation failed | Critical |
| FQXDE6700M | Unreadable sectors detected data loss occurred | Critical |
| FQXDE6703M | Overflow in unreadable sector database | Critical |
| FQXDE6800L | Serial port recovery activated | Critical |
| FQXDE6801L | Serial port recovery had an incorrect password | Critical |
| FQXDE6900M | Diagnostic data is available | Critical |
| FQXDE7001M | Feature pack key file required | Critical |
| FQXDE7300M | Battery backup unit overheated | Critical |
| FQXDE7301M | Insufficient learned battery capacity | Critical |
| FQXDE7306M | Battery missing | Critical |
| FQXDE7308M | Battery expired | Critical |
| FQXDE7500M | Persistent cache backup device failed | Critical |
| FQXDE7501M | Cache backup device is write-protected | Critical |
| FQXDE7506L | Backup component status unknown | Critical |
| FQXDE7800M | Snapshot image rollback paused | Critical |
| FQXDE7802M | Snapshot group repository full | Critical |
| FQXDE7803M | Snapshot group failed | Critical |
| FQXDE7805M | Snapshot volume repository full | Critical |
| FQXDE7806M | Snapshot volume repository failed | Critical |
| FQXDE7807M | Snapshot image purged | Critical |
| FQXDE7B01M | A thin volume repository is full | Critical |
| FQXDE7B02M | A thin volume repository failed | Critical |
| FQXDE7C02M | An asynchronous mirror group was suspended internally | Critical |
| FQXDE7C03M | The asynchronous mirror group has a role (primary or secondary) conflict | Critical |
| FQXDE7C04M | A recovery point for an asynchronous mirror group was lost | Critical |
| FQXDE7C06M | Asynchronous mirror group member failed | Critical |
| FQXDE7C09M | An asynchronous mirror group secondary member repository is full | Critical |
| FQXDE7C34M | An asynchronous mirror group's synchronization has paused because the alternate state is preventing synchronization from proceeding | Critical |
| FQXDE7C37M | Controller firmware detected a role change for an AMG was paused | Critical |
| FQXDE7D00M | SMART Command Transfer (SCT) commands unsupported | Critical |
| FQXDE9102M | Loss of host-side connection redundancy detected | Critical |
| FQXDE9103M | Host multipath driver configuration error detected | Critical |
| FQXDE9200M | Security Audit Log reached its maximum capacity and cannot record new security audit events until it is cleared | Critical |
| FQXDE9204M | A Directory Services server is unreachable or misconfigured | Critical |
| FQXDE9207L | The certificate was revoked | Critical |
| FQXDE9208L | Unable to contact the OCSP responder server | Critical |
| FQXDE9301M | An installed certificate used for KMIP server authentication has expired | Critical |
| FQXDE9302M | A certificate error was returned by the KMIP server | Critical |
| FQXDE9303M | Authentication to the KMIP server failed | Critical |
| FQXDE9304M | A failure occurred on the connection to a KMIP server | Critical |
| FQXDE9305M | A general error was returned when communicating with the KMIP server | Critical |
| FQXDE9600M | Impending Drive Failure (High Data Availability Risk) | Critical |
| FQXDE9601M | Impending Drive Failure (Medium Data Availability Risk) | Critical |
| FQXDE9602M | Impending Drive Failure (Unassigned or Standby Hot Spare) | Critical |
| FQXDE9603M | Incompatible PI-Type Drive | Critical |
| FQXDE9604M | Degraded Drive Channel | Critical |
| FQXDE9605M | Controller Reboots Detected | Critical |
| FQXDE9606M | ESM Canister Miswire | Critical |
| FQXDE9607M | Degraded Drive Path | Critical |
| FQXDE9608M | Drive Channel Data Rate Detection Mismatch | Critical |
| FQXDE9609M | Critical | |
| FQXDE9610M | Fibre Channel Trunking - Incompatible ESM | Critical |
| FQXDE9611M | Fibre Channel Trunking Miswire | Critical |
| FQXDE9612M | SAS Device Miswire | Critical |
| FQXDE9614M | SAS Loop Miswire | Critical |
| FQXDE9616M | SAS Host Miswire | Critical |
| FQXDE9618M | SAS Device Miswire | Critical |
| FQXDE9619M | Failed or Degraded SAS Port | Critical |
| FQXDE9620M | Failed or Degraded SAS Port | Critical |
| FQXDE9624M | Tray - Loss of External Redundancy | Critical |
| FQXDE9625M | Failed Host I/O Card | Critical |
| FQXDE9626M | Host Switch Card Problem | Critical |
| FQXDE9627M | Missing Drives Lockdown | Critical |
| FQXDE9628M | A controller detected that the combination of host interface cards are out of compliance with limitations of the controller or the firmware. | Critical |
| FQXDE9629M | Failed Drive | Critical |
| FQXDE9630M | Redundancy Group Not Consistent | Critical |
| FQXDE9633M | Cache Memory Mismatch | Critical |
| FQXDE9634M | Battery Failed | Critical |
| FQXDE9635M | Cache Data Loss | Critical |
| FQXDE9636M | Battery Nearing Expiration | Critical |
| FQXDE9637M | Battery Settings Mismatch | Critical |
| FQXDE9638M | Unsupported Cache Memory Size | Critical |
| FQXDE9639M | Insufficient Cache Backup Device Capacity | Critical |
| FQXDE9640M | Insufficient processor memory for cache | Critical |
| FQXDE9641M | Dedicated Mirror Channel Failed | Critical |
| FQXDE9642M | Write-Back Caching Disabled | Critical |
| FQXDE9644M | Controller Degraded to Preserve Offline Volume Data | Critical |
| FQXDE9646M | Incompatible Drive Due to Unsupported Sector Size | Critical |
| FQXDE9648M | Failed Volume | Critical |
| FQXDE9649M | Uncertified Drive | Critical |
| FQXDE9650M | Replaced Drive - Wrong Type | Critical |
| FQXDE9651M | Volume Modification Operation Failed | Critical |
| FQXDE9652M | Configuration Database Adoption Failed - RAID Level Not Supported | Critical |
| FQXDE9653M | Configuration Database Adoption Failed - One or More Limit(s) Exceeded | Critical |
| FQXDE9654M | Incompatible Drive Due to Older Configuration Database | Critical |
| FQXDE9656M | Incompatible Drive Due to Newer Configuration Database | Critical |
| FQXDE9657M | Foreign Drive Has Inconsistent Configuration | Critical |
| FQXDE9658M | Foreign Drive Refers to Native Drive | Critical |
| FQXDE9659M | Replaced Drive - Wrong Type | Critical |
| FQXDE9660M | Failed Legacy Drive | Critical |
| FQXDE9661M | Configuration Database Adoption Failed - Multiple Configuration Databases Detected | Critical |
| FQXDE9662M | Native Volume Group And Foreign Drive Refer to Each Other | Critical |
| FQXDE9664M | Volume Group Clones | Critical |
| FQXDE9665M | Multiple Volume Groups Refer to Foreign Drive | Critical |
| FQXDE9666M | Multiple Volume Groups Refer to Foreign Drive (Scenario 2) | Critical |
| FQXDE9667M | Unsupported SATA Protocol Connection | Critical |
| FQXDE9669M | Security Key Needed | Critical |
| FQXDE9671M | Missing Hot Spare Drive | Critical |
| FQXDE9672M | Solid State Disk - End of Life | Critical |
| FQXDE9673M | Unsupported Drive Capacity | Critical |
| FQXDE9674M | Volume - Hot Spare in Use | Critical |
| FQXDE9675M | Missing Volume Group or Disk Pool | Critical |
| FQXDE9676M | Incomplete Volume Group or Disk Pool | Critical |
| FQXDE9677M | Incompatible Interposer Firmware | Critical |
| FQXDE9678M | Incompatible Drive Alignment | Critical |
| FQXDE9679M | Impending Drive Failure (Waiting for Hot Spare) | Critical |
| FQXDE9682M | Unable to Resolve NTP Server's IP Address | Critical |
| FQXDE9683M | NTP Query Failed | Critical |
| FQXDE9684M | Unable to Contact NTP Servers | Critical |
| FQXDE9685M | Invalid Power Supply | Critical |
| FQXDE9686M | Mismatched Midplane EEPROMs | Critical |
| FQXDE9687M | Failed I2C Bus | Critical |
| FQXDE9688M | Corrupt VPD EEPROM | Critical |
| FQXDE9689M | Controller Removed | Critical |
| FQXDE9690M | Drive Security Key Mismatch | Critical |
| FQXDE9691M | Mismatching Security Key IDs | Critical |
| FQXDE9692M | Lost AC Power | Critical |
| FQXDE9693M | Removed Power-Fan Canister | Critical |
| FQXDE9694M | Failed Interconnect-Battery Canister | Critical |
| FQXDE9695M | Power Supply - No Power Input | Critical |
| FQXDE9696M | Storage Array Component - Loss of Communication | Critical |
| FQXDE9697M | Removed ESM Canister | Critical |
| FQXDE9699M | Tray ID Conflict | Critical |
| FQXDE9700M | Nominal Temperature Exceeded | Critical |
| FQXDE9701M | Maximum Temperature Exceeded | Critical |
| FQXDE9702M | Removed Power-Fan Canister | Critical |
| FQXDE9703M | ESM Firmware Mismatch | Critical |
| FQXDE9704M | Bypassed Drive | Critical |
| FQXDE9705M | Drive Tray - Loss of Path Redundancy | Critical |
| FQXDE9706M | Bypassed Drive | Critical |
| FQXDE9707M | Drive - Loss of Path Redundancy | Critical |
| FQXDE9708M | ESM Hardware Type Mismatch | Critical |
| FQXDE9709M | Mixed Drive Types - Out of Compliance | Critical |
| FQXDE9710M | Uncertified ESM Canister | Critical |
| FQXDE9711M | Uncertified Drive | Critical |
| FQXDE9712M | Controller Mismatch | Critical |
| FQXDE9713M | Drive Trays Not Cabled Correctly | Critical |
| FQXDE9714M | Discrete Lines Diagnostic Failure | Critical |
| FQXDE9716M | Removed Interconnect-Battery Canister | Critical |
| FQXDE9717M | Failed Power Supply | Critical |
| FQXDE9718M | Controller Mismatch | Critical |
| FQXDE9720M | Redundant Power Supplies Required | Critical |
| FQXDE9721M | Misconfigured Tray | Critical |
| FQXDE9722M | ESM Configuration Settings Version Mismatch | Critical |
| FQXDE9724M | Controller Model or Submodel Identifier Cannot Be Determined | Critical |
| FQXDE9725M | Failed Drawer | Critical |
| FQXDE9726M | Missing or Open Drawer | Critical |
| FQXDE9727M | Thermal Shutdown | Critical |
| FQXDE9728M | Degraded Drawer | Critical |
| FQXDE9729M | Invalid Drawer Type | Critical |
| FQXDE9730M | Drawer Removed | Critical |
| FQXDE9731M | Failed GBIC/SFP | Critical |
| FQXDE9734M | Non-Optimal SSD Cache | Critical |
| FQXDE9735M | Preservation Capacity Below Threshold | Critical |
| FQXDE9736M | Disk Pool Capacity - Warning Threshold Exceeded | Critical |
| FQXDE9737M | Disk Pool Capacity - Critical Threshold Exceeded | Critical |
| FQXDE9738M | Disk Pool Capacity - Full | Critical |
| FQXDE9739M | Insufficient Disk Pool Memory | Critical |
| FQXDE9742M | Too Many Security Key Validation Attempts | Critical |
| FQXDE9743M | Offline Controller | Critical |
| FQXDE9744M | Controller Diagnostics Failed | Critical |
| FQXDE9746M | Unknown Component Failure | Critical |
| FQXDE9747M | Unknown Shared Component Failure | Critical |
| FQXDE9748M | Invalid Host Type | Critical |
| FQXDE9750M | Inactive host port registered | Critical |
| FQXDE9751M | Inactive Host Port Identifier | Critical |
| FQXDE9752M | External Key Management System - Out of Compliance | Critical |
| FQXDE9753M | Snapshot Premium Feature - Out Of Compliance | Critical |
| FQXDE9754M | Gold Key - mismatched settings | Critical |
| FQXDE9755M | Mixed drive types - mismatched settings | Critical |
| FQXDE9756M | Premium Feature Trial Nearing Non-Compliant State | Critical |
| FQXDE9757M | Offline Controller | Critical |
| FQXDE9758M | Storage Array in Recovery Mode | Critical |
| FQXDE9759M | Dual Primary Volume Conflict | Critical |
| FQXDE9760M | Dual Secondary Volume Conflict | Critical |
| FQXDE9761M | Mirror Data Unsynchronized | Critical |
| FQXDE9762M | Mirror relationship has inconsistent write mode | Critical |
| FQXDE9763M | Mirror Communication Error - Unable to Contact Storage Array | Critical |
| FQXDE9764M | Unable to Update Remote Mirror | Critical |
| FQXDE9765M | Failed Copy Operation | Critical |
| FQXDE9766M | Unreadable Sectors Detected | Critical |
| FQXDE9767M | Unreadable Sectors Log Full | Critical |
| FQXDE9768M | Controller Diagnostic Data Collected | Critical |
| FQXDE9769M | Premium Feature - Out of Compliance | Critical |
| FQXDE9770M | Battery Temperature - Critical Limit Exceeded | Critical |
| FQXDE9771M | Battery Replacement Required | Critical |
| FQXDE9772M | Battery Removed | Critical |
| FQXDE9773M | Battery Expired | Critical |
| FQXDE9774M | Cache Backup Device Failed | Critical |
| FQXDE9775M | Cache Backup Device in Write-Protect Mode | Critical |
| FQXDE9776M | Snapshot Image Rollback Paused | Critical |
| FQXDE9778M | Repository - Full | Critical |
| FQXDE9779M | Snapshot Group or CG Member Volume Failed | Critical |
| FQXDE9781M | Snapshot Volume Repository - Full | Critical |
| FQXDE9782M | Snapshot Volume Failed | Critical |
| FQXDE9783M | Snapshot Image Purged | Critical |
| FQXDE9787M | Thin Volume Repository - Full | Critical |
| FQXDE9788M | Thin Volume Failed | Critical |
| FQXDE9791M | Synchronization Suspended | Critical |
| FQXDE9792M | Mirror Group Role Conflict | Critical |
| FQXDE9793M | Synchronization Recovery Point Lost | Critical |
| FQXDE9795M | Failed Mirror | Critical |
| FQXDE9798M | Mirrored Secondary Volume Repository - Full | Critical |
| FQXDE9801M | Synchronization Paused | Critical |
| FQXDE9802M | Mirror Communication Error - Unable to Contact Storage Array | Critical |
| FQXDE9803M | Incompatible SATA Drive | Critical |
| FQXDE9804M | Host Redundancy Lost | Critical |
| FQXDE9805M | Host Multipath Driver Incorrect | Critical |
| FQXDE9806M | Audit Log Full | Critical |
| FQXDE9808M | Directory Services Server Connection Failed | Critical |
| FQXDE9810M | Key Management Certificate Expired | Critical |
| FQXDE9811M | Key Management Client Certificate Invalid | Critical |
| FQXDE9812M | Key Management Server Certificate Invalid | Critical |
| FQXDE9813M | Key Management Server Connection Failed | Critical |
| FQXDE9814M | Key Management Server Error | Critical |
| FQXST0001W | The disk group is online but cannot tolerate another disk failure. | Critical |
| FQXST0003M | The specified disk group went offline. | Critical |
| FQXST0006W | A failure occurred during the initialization of the specified disk group. | Critical |
| FQXST0007M | In a testing environment, a controller diagnostic failed and reported a product-specific diagnostic code. | Critical |
| FQXST0008W | A disk group is down, a disk group failed, or a disk group reported that it has no life remaining. | Critical |
| FQXST0021M | Disk group verification completed. Errors were found but not corrected. | Critical |
| FQXST0021W | Disk group verification did not complete due to an internally detected condition, such as a failed disk. If a disk fails, data might be at risk. | Critical |
| FQXST0039W | The sensors monitored a temperature or voltage in the warning range. When the problem is resolved, event 47 is logged for the component that logged event 39. | Critical |
| FQXST0040M | The sensors monitored a temperature or voltage in the failure range. When the problem is resolved, event 47 is logged for the component that logged event 40. | Critical |
| FQXST0044W | The controller contains cache data for the specified volume but the corresponding disk group is not online. | Critical |
| FQXST0050M | A correctable ECC error occurred in cache memory more than 10 times during a 24-hour period, indicating a probable hardware fault. | Critical |
| FQXST0050W | A correctable ECC error occurred in cache memory. | Critical |
| FQXST0051M | An uncorrectable ECC error occurred in cache memory more than once during a 48-hour period, indicating a probable hardware fault. | Critical |
| FQXST0051W | An uncorrectable ECC error occurred in cache memory. | Critical |
| FQXST0053W | Too many errors occurred during disk group expansion to allow the expansion to continue. | Critical |
| FQXST0055W | The specified disk reported a SMART event. | Critical |
| FQXST0058M | A disk drive detected a serious error, such as a parity error or disk hardware failure. | Critical |
| FQXST0058W | A disk drive reset itself due to an internal logic error. | Critical |
| FQXST0059W | The controller detected a parity event while communicating with the specified SCSI device. The event was detected by the controller, not the disk. | Critical |
| FQXST0061M | The controller reset a disk channel to recover from a communication error. This event is logged to identify an error trend over time. | Critical |
| FQXST0062W | The specified global or dedicated spare disk failed. | Critical |
| FQXST0065M | An uncorrectable ECC error occurred in cache memory on startup. | Critical |
| FQXST0078W | The controller could not use an assigned spare for a disk group because the spare's capacity is too small. | Critical |
| FQXST0084W | The current controller that logged this event forced the partner controller to fail over. | Critical |
| FQXST0087W | The mirrored configuration retrieved by this controller from the partner controller has a bad cyclic redundancy check (CRC). The local flash configuration will be used instead. | Critical |
| FQXST0088W | The mirrored configuration retrieved by this controller from the partner controller is corrupt. The local flash configuration will be used instead. | Critical |
| FQXST0089W | The mirrored configuration retrieved by this controller from the partner controller has a configuration level that is too high for the firmware in this controller to process. The local flash configuration will be used instead. | Critical |
| FQXST0091M | In a testing environment, the diagnostic that checks hardware reset signals between controllers in Active-Active mode failed. | Critical |
| FQXST0095M | Both controllers in an Active-Active configuration have the same serial number. Non-unique serial numbers can cause system problems. For example, WWNs are determined by serial number. | Critical |
| FQXST0107M | A serious error was detected by the controller. In a single-controller configuration, the controller will restart automatically. In an Active-Active configuration, the partner controller will stop the controller that experienced the error. | Critical |
| FQXST0112W | The link for the specified host port went down unexpectedly. | Critical |
| FQXST0116M | After a recovery, the partner controller was stopped while mirroring write-back cache data to the controller that logged this event. The controller that logged this event was restarted to avoid losing the data in the partner controller's cache, but if the other controller does not restart successfully, the data will be lost. | Critical |
| FQXST0117W | This controller module detected or generated an error on the specified host channel. | Critical |
| FQXST0127W | The controller detected a disk dual-port connection that is not valid. This event indicates that a controller host port is connected to an expansion port, instead of to a port on a host or a switch. | Critical |
| FQXST0136W | Errors detected on the specified disk channel have caused the controller to mark the channel as degraded. | Critical |
| FQXST0152W | The Management Controller (MC) has not communicated with the Storage Controller (SC) for 15 minutes and might have failed. | Critical |
| FQXST0156W | The Management Controller (MC) was restarted from the Storage Controller (SC) for the purpose of error recovery. | Critical |
| FQXST0157M | A failure occurred when trying to write to the Storage Controller (SC) flash chip. | Critical |
| FQXST0158M | A correctable ECC error occurred in Storage Controller CPU memory more than once during a 12-hour period, indicating a probable hardware fault. | Critical |
| FQXST0158W | A correctable ECC error occurred in Storage Controller CPU memory. | Critical |
| FQXST0161C | One or more enclosures do not have a valid path to an enclosure management processor (EMP). All enclosure EMPs are disabled. | Critical |
| FQXST0162W | The host WWNs (node and port) previously presented by this controller module are unknown. | Critical |
| FQXST0163W | The host WWNs (node and port) previously presented by the partner controller module, which is currently offline, are unknown. | Critical |
| FQXST0166W | The RAID metadata level of the two controllers does not match, which indicates that the controllers have different firmware levels. | Critical |
| FQXST0167W | A diagnostic test at controller boot detected an abnormal operation, which might require a power cycle to correct. | Critical |
| FQXST0172W | The specified disk group was quarantined because some its disks are not accessible. | Critical |
| FQXST0203W | An environmental change occurred that allows write-back cache to be enabled, but the auto-write-back preference is not set. The environmental change is also logged at approximately the same time as this event (event 191, 193, 195, 199, 201, or 241). | Critical |
| FQXST0204M | An error occurred with either the NV device itself or the transport mechanism. The system may attempt to recover itself. | Critical |
| FQXST0204W | While starting, the system found an issue with the NV device. The system will attempt to recover itself. | Critical |
| FQXST0207M | Disk group scrub completed and found an excessive number of errors for the specified disk group. | Critical |
| FQXST0207W | Disk group scrub did not complete because of an internally detected condition, such as a failed disk. | Critical |
| FQXST0209M | A scrub-disk job logged with event 208 has completed and found one or more media errors, SMART events, or hard (non-media) errors. If this disk is used in a non-fault-tolerant disk group, data might have been lost. | Critical |
| FQXST0209W | A scrub-disk job logged with event 208 has been stopped by a user, or has reassigned a disk block. These bad-block replacements are reported as "other errors". If this disk is used in a non-fault-tolerant disk group, data might have been lost. | Critical |
| FQXST0211W | SAS topology has changed. No elements are detected in the SAS map. | Critical |
| FQXST0217M | A supercapacitor failure occurred in the controller. | Critical |
| FQXST0218W | The supercapacitor pack is near the end of life. | Critical |
| FQXST0232W | The maximum number of enclosures allowed for the current configuration has been exceeded. | Critical |
| FQXST0233W | The specified disk type is not valid and is not allowed in the current configuration. | Critical |
| FQXST0235M | An enclosure management processor (EMP) detected a serious error. | Critical |
| FQXST0236M | A special shutdown operation started. These special shutdown operations indicate an incompatible feature. | Critical |
| FQXST0237M | A firmware update attempt was stopped because of general system health issue(s), or because unwritable cache data that would be lost during a firmware update. | Critical |
| FQXST0238W | A licenses feature cannot be installed because the license is not valid. | Critical |
| FQXST0239W | A timeout occurred while flushing the CompactFlash. | Critical |
| FQXST0240W | A failure occurred while flushing the CompactFlash. | Critical |
| FQXST0242M | The controller module's CompactFlash card has failed. | Critical |
| FQXST0246W | The coin battery is not present, is not properly seated, or has reached end-of-life. | Critical |
| FQXST0247W | The FRU ID SEEPROM for the specified field replaceable unit (FRU) cannot be read. FRU ID data might not be programmed. | Critical |
| FQXST0250W | A license could not be installed. | Critical |
| FQXST0263W | The specified spare disk is missing. Either it was removed, or it is not responding. | Critical |
| FQXST0267M | While cleaning up resources in metadata at the end of a volume-copy operation, the firmware found at least one error for the specified volume. | Critical |
| FQXST0269M | A partner firmware upgrade attempt stopped because of either general system health issue(s) or unwritable cache data that would be lost during a firmware update. | Critical |
| FQXST0270W | A problem occurred while reading or writing the persistent IP data from the FRU ID SEEPROM, or the data read from the FRU ID SEEPROM were not valid. | Critical |
| FQXST0274W | The specified PHY was disabled, either automatically or by a user. | Critical |
| FQXST0298W | The controller's real-time clock (RTC) setting is not valid. | Critical |
| FQXST0307C | A temperature sensor on a controller FRU detected an over-temperature condition that caused the controller to shut down. | Critical |
| FQXST0313M | The specified controller module failed. This event can be ignored for a single-controller configuration. | Critical |
| FQXST0314M | The specified FRU failed, or is not operating properly. This event follows some other FRU-specific event indicating a problem. | Critical |
| FQXST0315C | The controller module is not compatible with the enclosure. | Critical |
| FQXST0316W | The temporary license for a feature has expired. | Critical |
| FQXST0317M | A serious error has been detected on the disk interface of the Storage Controller. The controller will be stopped by its partner. | Critical |
| FQXST0319W | The specified available disk failed. | Critical |
| FQXST0322W | The controller has an older Storage Controller (SC) version than the version used to create the CHAP authentication database in the flash memory of the controller. | Critical |
| FQXST0354W | The SAS topology has changed on a host port. At least one PHY went down. For example, the SAS cable connecting a controller host port to a host was disconnected. | Critical |
| FQXST0355W | The debug button on the controller module was found to be stuck in the On position during boot. | Critical |
| FQXST0356W | This event can only result from tests that are run in the manufacturing environment. | Critical |
| FQXST0357W | This event can only result from tests that are run in the manufacturing environment. | Critical |
| FQXST0358C | All PHYs are down for the specified disk channel. The system is degraded and is not fault tolerant because all disks are in a single-ported state. | Critical |
| FQXST0358W | Some PHYs are down for the specified disk channel. | Critical |
| FQXST0361C | The scheduler experienced a problem with the specified schedule. | Critical |
| FQXST0361M | The scheduler experienced a problem with the specified schedule. | Critical |
| FQXST0361W | The scheduler experienced a problem with the specified schedule. | Critical |
| FQXST0362C | The scheduler experienced a problem with the specified task. | Critical |
| FQXST0362M | The scheduler experienced a problem with the specified task. | Critical |
| FQXST0362W | The scheduler experienced a problem with the specified task. | Critical |
| FQXST0363M | When the Management Controller (MC) is restarted, firmware versions that are currently installed are compared against those in the bundle that was most recently installed. | Critical |
| FQXST0365M | An uncorrectable ECC error occurred in Storage Controller CPU memory more than once, indicating a probable hardware fault. | Critical |
| FQXST0365W | An uncorrectable ECC error occurred in Storage Controller CPU memory. | Critical |
| FQXST0401W | The specified log has filled to a level at which diagnostic data will be lost if the log is not transferred to a log-collection system. | Critical |
| FQXST0402M | The specified log has wrapped and has started to overwrite the oldest diagnostic data. | Critical |
| FQXST0412W | One disk in the specified RAID-6 disk group failed. The disk group is online, but it has a status of FTDN (fault tolerant with a down disk). | Critical |
| FQXST0442W | Power-On Self Test (POST) diagnostics detected a hardware error in a UART chip. | Critical |
| FQXST0455W | The controller detected that the configured host-port link speed exceeded the capability of an FC SFP. The speed has been automatically reduced to the maximum value supported by all hardware components in the data path. | Critical |
| FQXST0456W | The IQN of the system was generated from the default OUI because the controllers could not read the OUI from the midplane FRU ID data during startup. If the IQN is not correct for the system, iSCSI hosts might be unable to access the system. | Critical |
| FQXST0460M | The specified disk group is missing from the specified virtual pool. This may be caused by missing disk drives, or unconnected or powered-off enclosures. | Critical |
| FQXST0462M | The specified virtual pool reached its storage limit. | Critical |
| FQXST0462W | The specified virtual pool exceeded its high threshold for allocated pages, and the virtual pool is overcommitted. | Critical |
| FQXST0464W | A user inserted an unsupported cable or SFP into the specified controller host port. | Critical |
| FQXST0469W | The speed of buses connecting the FPGA to downstream adapters was reduced to compensate for an FPGA over-temperature condition. The storage system is operational but I/O performance is reduced. | Critical |
| FQXST0476W | The CPU temperature exceeded the safe range so the CPU entered its self-protection state. IOPS were reduced. The storage system is operational, but I/O performance is reduced. | Critical |
| FQXST0479M | The controller reporting this event was not able to flush data to or restore data from non-volatile memory. | Critical |
| FQXST0480M | An IP address conflict was detected for the specified iSCSI port of the storage system. The specified IP address is already in use. | Critical |
| FQXST0481M | The periodic monitor of CompactFlash hardware detected an error. The controller was put in write-through mode, which reduces I/O performance. | Critical |
| FQXST0482W | One of the PCIe buses is running with fewer lanes than is optimal. | Critical |
| FQXST0483M | The expansion-module connection for the specified disk channel is not valid. An egress port is connected to an egress port, or an ingress port is connected to an incorrect egress port. | Critical |
| FQXST0484W | No compatible spares are available to reconstruct this disk group if it experiences a disk failure. Only disk groups that have dedicated or suitable global spares will start reconstruction automatically. | Critical |
| FQXST0485W | The specified disk group was quarantined to prevent writing outdated data that might exist in the controller that logged this event. | Critical |
| FQXST0486W | A recovery process was initiated to prevent writing outdated data that might exist in the controller that logged this event. | Critical |
| FQXST0495W | The algorithm for best-path routing selected the alternate path to the specified disk because the I/O error count on the primary path reached its threshold. | Critical |
| FQXST0496W | An unsupported disk vendor was found. | Critical |
| FQXST0501M | The enclosure hardware is not compatible with the I/O module firmware. The Expander Controller firmware detected an incompatibility with the midplane type. As a preventive measure, disk access was disabled in the enclosure. | Critical |
| FQXST0502W | The specified SSD has 5% or less of its life remaining. | Critical |
| FQXST0505W | The specified virtual pool was created with a size smaller than 500 GB, which can lead to unpredictable behavior. The storage system might not perform correctly. | Critical |
| FQXST0508M | The specified virtual pool went offline. All of its volumes also went offline. | Critical |
| FQXST0509M | The metadata volume for the specified virtual pool went offline. Volume mappings and persistent reservations are inaccessible or lost. | Critical |
| FQXST0516M | An FDE disk was placed in the unavailable state. | Critical |
| FQXST0518M | An FDE disk operation failed. | Critical |
| FQXST0521M | An error occurred while accessing the midplane SEEPROM to store or fetch Full Disk Encryption keys. The midplane's memory is used to store the FDE lock key. | Critical |
| FQXST0522W | A scrub-disk-group job encountered an error at the specified logical block address. | Critical |
| FQXST0524M | A temperature or voltage sensor reached a critical threshold. | Critical |
| FQXST0527M | Expander Controller (EC) firmware is incompatible with the enclosure. | Critical |
| FQXST0528M | Expander Controller firmware detected that the partner Expander Controller (EC) firmware is incompatible with the enclosure. | Critical |
| FQXST0529M | The local Expander Controller (EC) is incompatible with the enclosure. | Critical |
| FQXST0530M | The local Expander Controller (EC) firmware detected a level of incompatibility with the partner Expander Controller (EC). This incompatibility could be due to unsupported hardware or firmware. | Critical |
| FQXST0531M | The specified controller module was unable to recover from a stall. The system will need to be recovered manually. | Critical |
| FQXST0531W | The specified controller module detected a stall. The system will perform corrective actions. | Critical |
| FQXST0533M | This event provides details about the result of the MC test of the specified component. | Critical |
| FQXST0545W | A controller module is connected to a legacy enclosure midplane, resulting in degraded performance. | Critical |
| FQXST0546M | The controller that logged this event stopped the partner controller because it has an incompatible host port configuration. | Critical |
| FQXST0548W | Disk group reconstruction failed. | Critical |
| FQXST0549C | The specified controller module detected that it recovered from an internal processor fault. | Critical |
| FQXST0550C | The read data path between the Storage Controller and the disk drives was detected to be unreliable. The Storage Controller took action to correct this. | Critical |
| FQXST0551M | An error condition was found for a power supply unit (PSU). | Critical |
| FQXST0551W | An EMP reported that a power supply unit (PSU) was uninstalled. | Critical |
| FQXST0552M | An EMP reported an alert condition. A hardware failure has been detected and all fans in the specified FRU have failed. | Critical |
| FQXST0552W | An EMP reported one of the following: | Critical |
| FQXST0553M | A temperature sensor is not within the normal operating range, but it is within safe operating limits; or, a temperature sensor has been removed. | Critical |
| FQXST0553W | A temperature sensor is not within normal operating temperature thresholds but is within safe operating limits; or, a temperature sensor has been uninstalled. | Critical |
| FQXST0554M | A voltage sensor is outside a critical voltage threshold in the specified FRU. | Critical |
| FQXST0554W | A voltage sensor is not within the normal operating range but is within safe operating limits; or, a voltage sensor was removed. | Critical |
| FQXST0555M | The local Expander Controller firmware has detected a level of incompatibility with the partner Expander Controller firmware or hardware. As a preventive measure, the local Expander Controller might disable all the PHYs. | Critical |
| FQXST0555W | An expander in a controller module, expansion module, or drawer is mated but is not responding; or, an expander in an expansion module has been removed. | Critical |
| FQXST0556W | An expander in a controller module, expansion module, or drawer is mated but is not responding; or, an expander in an expansion module has been removed. | Critical |
| FQXST0557M | An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. | Critical |
| FQXST0557W | An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. | Critical |
| FQXST0565W | One of the PCIe buses is running at less than optimal speed. | Critical |
| FQXST0569W | A SAS host cable mismatch was detected for the specified port number. The specified alternate PHYs have been disabled. | Critical |
| FQXST0571M | Snapshot space exceeded the configured percentage limit of the virtual pool. | Critical |
| FQXST0571W | Snapshot space exceeded the high snapshot space threshold. | Critical |
| FQXST0573W | Snapshot space for a virtual pool cannot be reduced because no snapshots can be deleted. | Critical |
| FQXST0590M | A disk group has been quarantined. | Critical |
Give documentation feedback