Dell PowerVault ME5 Series Storage Controller Firmware ME5.1.2.2.1

Restart required

Driver Id : XH0X3

Importance : Optional

Version : ME5.1.2.2.1, A11 Latest version Recommended version Latest and Recommended version

Release Date : 13 Mar 2026

Download Type : Software Utilities

Category : Storage Controller

ME50XX Controller firmware

Download Files

File Format: This file contains a compressed (or zipped) set of files. Download the file to a folder on your hard drive, then double-click it to unzip the set of files. Follow the install instructions below to complete the installation.

File Name: ME5.1.2.2.1.zip

File size: 217.72 MB

To ensure the integrity of your download, please verify the checksum value.

MD5: c54e086528754c0f4af6d0f913f9bebb

SHA1: fd6f7ead731925b86f055e2a55dcf0351ba8ee0b

SHA-256: 7a5ee932cec99b49e21158db4f563539a838fd3148aae5c63b7f52e375d946b6

Download .ZIP

Fixes & Enhancements

Fixes:
-Fixed performance issue when taking snapshot
-Fixed issue where LDAP was unable to authenticate with multiple OU(user-groups)
-Fixed issue where controller A went through an unexpected reboot due to page fault
-Fixed issue where changing brand to OEM caused GUI issue in non-English language
-Fixed issue where older versions of firmware had removed host-phy-statistics from CLI command
-Fixed issue where a non-English language GUI cannot show NTP and Dynamic Spare Configuration settings correctly
-Fixed issue to show FIPS status capability for KIOXIA drives that support FIPS (see "Dell PowerVault ME5 Series Storage System Support Matrix" for supported drives)
-Fixed issue where scrub detected a parity error and was unable to fix it
-Fixed issue for an illegal access to memory by the CPU found in previous releases
-Fixed issue where expected payloads such as the Support bundle and CloudIQ telemetry data are not being sent by the ME5 firmware following FW updates
-Fixed issue where next scheduled time of replication was incorrect
-Fixed issue where snapshot deletion was causing VM corruption (fragmentation issue)
-Fixed issue where controllers rebooting with a detected Assert or OSM debug error.
-Fixed issue with controller reboot unreliable with disk read path meta Scrub Error
-Fixed issue where snapshot doesn't follow set schedule | Task is not being executed
-Fixed issue where disk group creation in GUI does not work correctly when using Select All
-Fixed issue where ME5 GUI was stuck at "the application is loading"
-Fixed Security issue - VRT-27804 Downstream Notification: Embedded Service Enabler - Multiple Vulnerabilities
-Fixed issue where controllers reboot from recovery stall
-Fixed issue where Dell AIOps scheduler is stuck
-Fixed issue where snapshot uniquedata values reporting 18.4EB.
-Fixed Security issue - CVE-2025-0938
-Fixed Security issue - CVE-2025-31115
-Fixed issue where after SSH connection to RIOM-B, CLI can't work
-Fixed issue for an openssh version update related query
-Fixed issue where "Syslog Timestamp Format" seems not to be compliant with RFC
-Fixed issue where a virtual pool detected a reference error
-Fixed an issue where a right PSU alert was occurring

Enhancements:
-Added feature to recognize drive PPIDs in hardware alerts to enable auto dispatch and simplify part identification
-Changed Cloud IQ name to "Dell AIOPs throughout product documentation

Important Information

While upgrading from ME5.1.0.1.0 to any version, please disable - Partner Firmware Upgrade - option before proceeding . For detailed information, Visit this page.
-While ME5.1.2.1.1 firmware will prevent the issue from occurring, any customer who believes they are currently experiencing the over-provisioning of space allocation will need to backup all data, delete, then re-create the pool and volumes and then restore the data to correct the usage.

Compatible Systems

PowerVault ME5012

PowerVault ME5024

PowerVault ME5084

Installation instructions

Before performing a firmware update, see Best practices for updating firmware. While upgrading from ME5.1.0.1.0 to any version, please disable - Partner Firmware Upgrade - option before proceeding. For detailed information, Visit this page..
Both controllers must run the same firmware version. Storage systems with peer connections should run the same or compatible firmware versions.
In the System tab, the process to update firmware is to install firmware bundles obtained from Dell and then activate a particular bundle. For a dual-controller system, the following controller firmware-update scenarios are supported
-Automatic The partner firmware update PFU option is enabled the default. When you activate controller module firmware on one controller, the firmware is automatically copied over and activated on the partner controller first, and then activated on the current controller. PFU provides for updating expansion module firmware in similar fashion.
NOTE: Dell recommends enabling the PFU option for controller firmware updates. PFU is enabled by default and should remain enabled. Disable this option only if instructed to do so by a qualified service technician or when upgrading specifically from FW version ME5.1.0.1.0 as described the Knowledge Base article linked above.
-Manual PFU is disabled. When you update controller module or enclosure IOM firmware on one controller, you must log into the partner controller and manually perform the same updates.
When a controller module is installed into an enclosure at the factory, the enclosure midplane serial number and firmware-update timestamp are recorded for each firmware component in controller flash memory, and will not be erased when the configuration is changed or is reset to defaults. These two pieces of data are not present in controller modules that are not factory-installed and are used as replacements. Updating controller firmware with the PFU option enabled will ensure that the same firmware version is installed in both controller modules. Access this option by clicking Settings-System-Properties-Firmware Properties.
PFU uses the following algorithm to determine which controller module will update its partner:
-If both controllers are running the same firmware version, no change is made.
-The controller installed first will send its configuration and settings to the partner controller. Similarly, if a controller is replaced, it will receive configuration information from the partner controller. In both cases, subsequent firmware update behavior for both controllers is determined by the system's unified PFU setting
-If both controllers were already installed in the system, then the controller with firmware installed first will send its configuration and settings to the partner controller.
-If both controllers are newly installed, then controller A is transferred to controller B.
To install a firmware bundle, follow the on-screen directions and Best practices for updating firmware.
To activate a firmware bundle, click its Activate this Version link to display the Activate Firmware dialog and then follow the on-screen directions to enable activation to proceed. As part of the activation process the system will perform these steps: check bundle integrity, check system health, update firmware on the partner controller module, restart the partner controller module, update firmware on the local controller module, and restart the local controller module.
After the local controller module has restarted, the PowerVault Manager login screen will reappear. After you log back in, the Maintenance-Firmware panel will show that the new firmware is active on the system. An alert will also be generated to inform you that the firmware has been upgraded.