Brand: Dell
Category: Storage Hardware
Document Type: Manual
Language: EN
Manual for PowerVault ME5
Uploaded: Sept. 12, 2025, 4:25 a.m.
Manual Publish Date: 2022-04-01
Warranty Information
Consult the warranty information for the specific warranty period applicable to your Dell PowerVault ME5 Series Storage System.
- System Power: Indicated by a steady green LED, signifying at least one PCM is supplying power. If off, the system is not operating.
- Status/Health: Steady blue indicates the system is powered on and the controller is ready. Blinking blue signals the enclosure management is busy (e.g., during boot or firmware update). Steady amber indicates a module fault. Blinking amber signals a logical fault.
- Unit Identification (UID): A dual seven-segment display showing the enclosure's position in the cabling sequence (enclosure ID). Controller enclosure ID is 0.
- Identity: Blinking blue activates the system ID locator. Off indicates a normal state.
- System Power On/Standby: Steady green for operational, constant amber for standby.
- Module Fault: Constant or blinking amber indicates a system hardware fault, potentially related to controller modules, IOMs, PSUs, FCMs, DDICs, or drawers.
- Logical Status LED: Constant or blinking amber indicates a fault not from the enclosure management system, possibly from the controller module or an external HBA.
- Top/Bottom Drawer Fault: Constant or blinking amber indicates a fault in the drive, cable, or sideplane of the respective drawer.
Troubleshooting and error codes
| Number | Severity | Description/Recommended actions |
|---|---|---|
| 612 | Info. | Email notification sent successfully. Please ask the recipients to confirm that they received the message. Recommended actions: Verify the configured parameters and ask the recipients to confirm that they received the message. |
| 613 | Error | An alert condition was detected on an IOM. Recommended actions: Either install the indicated IOM or attempt to reseat it. If the problem persists, replace the IOM. |
| 613 | Warning | An alert condition was detected on an IOM. Recommended actions: If uninstalled, install the indicated IOM otherwise attempt to reseat it. If the problem persists, replace the IOM. |
| 613 | Info. | An IOM was uninstalled. Recommended actions: No action is required. |
| 613 | Resolved | A previous Warning or Error condition for the IOM has been resolved. Recommended actions: No action is required. |
| 614 | Info. | Cleared the degraded state of the indicated disk. Recommended actions: No action is required. |
| 615 | Info. | A rebalance operation for an ADAPT disk group has started. Recommended actions: No action is required. |
| 616 | Warning | A rebalance operation for an ADAPT disk group has completed partially. Recommended actions: No action is required. |
| 616 | Info. | A rebalance operation for an ADAPT disk group has completed. Recommended actions: No action is required. |
| 617 | Warning | The spare capacity goal is not met. This event indicates that the available space in the system is insufficient to provide the level of full fault tolerance that is specified by the target spare capacity. Spare capacity availability can be influenced by operations that require available space in the system, such as reconstructing data from a failed disk. Recommended actions: Add disks to the disk group, or replace any disks that may have failed. The system will automatically increase the spare capacity to meet the requirements placed on the system by the target spare capacity. |
| 618 | Resolved | The spare capacity goal is met. Recommended actions: No action is required. |
| 619 | Info. | The controller has been injected with a fault to introduce a broadcast receiver (BR) link error. Recommended actions: No action is required. |
| 620 | Error | Expander zoning is enabled, which may limit disk access. Disk access will change depending on the port used to connect to the expander. Recommended actions: Load a valid firmware bundle to disable zoning. |
| 620 | Resolved | Expander zoning has been disabled for the indicated enclosure. Recommended actions: No action is required. |
| 621 | Info. | Degraded ADAPT rebalance operation started. This operation takes fault tolerant stripe zones and makes them degraded so critical stripe zones can be made degraded. Recommended actions: No action is required. |
| 622 | Info. | Degraded ADAPT rebalance operation completed. This operation takes fault tolerant stripe zones and makes them degraded so critical stripe zones can be made degraded. Recommended actions: No action is required. |
| 623 | Info. | Management Controller configuration parameters were set. One or more configuration parameters associated with the Management Controller (MC) have been changed, such as configuration for SNMP, SMI-S (not supported on the ME5084), email notification, and system strings (system name, system location, etc.). Recommended actions: No action is required. |
| 626 | Info. | Detected an unsupported TPID (midplane Type ID). Recommended actions: No action is required. |
| 628 | Error | A firmware mismatch has been identified for the expansion enclosure. A firmware mismatch could result from attaching an enclosure configured as a JBOD (instead of an EBOD) or installing a new IOM FRU with incompatible firmware. Recommended actions: Update the firmware to the appropriate level for connecting your expansion enclosures to the controller enclosure. |
| 630 | Info | • If you receive this event when no new enclosures or IOMs have been added, please contact support. A disk has started a remanufacture/rebuild operation. The operation will result in reduced capacity. Do not replace the disk until the remanufacture/rebuild operation is complete. This operation can take a long time, and the completion is indicated by event 631. Recommended actions: No action is required. |
| 631 | Warning | A remanufacture/rebuild operation failed. The disk should be replaced. Recommended actions: Replace the disk with one of the same type and the same or greater capacity. For continued optimum I/O performance, the replacement disk should have performance that is the same as or better than the disk it is replacing. |
| 631 | Info | A disk remanufacture/rebuild operation completed successfully. Recommended actions: No action is required. |
| 632 | Error | A flush restore failure occurred. An integrity check failed on data restored from cache. Recommended actions: Allow time for the partner controller to recover the data and unkill the controller. |
| 635 | Warning | An I/O controller PHY setting was changed by a user. Recommended actions: No action is required. |
| 636 | Error | The other controller killed this controller for an unknown reason. The system will automatically recover. Recommended actions: Collect the logs and contact technical support for further action. |
| 637 | Error | The other controller killed this controller because it stopped responding via the inter-controller heartbeat. The system will automatically recover. Recommended actions: Collect the logs and contact technical support for further action. |
| 638 | Error | This is an illegal access to memory by the CPU. The system will automatically recover. Recommended actions: Collect the logs and contact technical support for further action. |
| 639 | Error | Access violation in the software. The system will automatically recover. Recommended actions: Collect the logs and contact technical support for further action. |
| 640 | Error | The software attempted to divide by 0. The system will automatically recover. Recommended actions: Collect the logs and contact technical support for further action. |
| 641 | Error | Detected an Assert or OSM debug error. The system will automatically recover. Recommended actions: Collect the logs and contact technical support for further action. |
| 642 | Error | Detected a PCI fault error. The system will automatically recover. Recommended actions: Collect the logs and contact technical support for further action. |
| 643 | Error | Detected a non-maskable interrupt fault error. The system will automatically recover. Recommended actions: Collect the logs and contact technical support for further action. |
| 644 | Error | Unable to upload firmware to the system because the encryption or bundle signature is invalid. Recommended actions: Verify that you are using the correct firmware bundle. |
| 644 | Warning | Unable to upload firmware to the system because the firmware bundle is using an outdated format. Recommended actions: Verify that you are using the correct firmware bundle. |
| 644 | Info. | Successfully uploaded firmware to the system. Recommended actions: No action is required. |
| 645 | Critical | Could not retrieve valid FRU data. Recommended actions: Collect the logs and contact technical support for further action. |
| 646 | Info. | Indicates any of the following changes to SupportAssist: State changed, Contact information changed, Proxy settings changed or cleared, Operation mode changed, Settings changed. Recommended actions: No action is required. |
| 647 | Error | This Storage Controller is restarting due to an internal error. This Storage Controller experienced a management-interface hang and will restart to recover. Recommended actions: Collect the logs and contact technical support for further action. |
| 648 | Error | Failed to upload SupportAssist logs or CloudIQ configuration or performance data. Recommended actions: No action is required. |
| 649 | Warning | A controller firmware update is available for your system. Recommended actions: Go to https://dell.com/support, enter your service tag and download the update. You can then use the Update Firmware function in PowerVault Manager to perform the update. |
| 650 | Warning | A disk firmware update is available for your system. Recommended actions: Go to https://dell.com/support, enter your service tag and download the update. You can then use the Update Firmware function in PowerVault Manager to perform the update. |
| 655 | Info. | SupportAssist telemetry send failed/succeeded. (Payload type: CloudIQ Config) Recommended actions: No action is required. |