Dell EMC PowerVault ME4 Series Storage Controller Firmware GT280R014-01
hi testing
Driver Id : V0VTD
Importance : Critical
Version : GT280014-01, A11 Latest version Recommended version Latest and Recommended version
Release Date : 03 Jan 2024
Download Type : Firmware
Category : Storage Controller
Dell EMC PowerVault ME4 Series Storage Array Controller firmware
Download Files
File Name: GT280R014-01-dellemc.zip
File size: 54.74 MB
To ensure the integrity of your download, please verify the checksum value.
MD5: b1ab7ce9ca93b18dbbf0a15e73def47c
SHA1: 2edd60f7b0cdbf077edd05775970e47a12ac7e7a
SHA-256: 203ad077c0362f6d1cd62cbf203d5c6be3a78e9ea0f76290055cd02ae919a35a
Fixes & Enhancements
Security enhancements
implemented, and Features:
In the CLI, the clear degraded-disk command can now be used to set a degraded disk's health to OK and clear the
disk's error count. After this command is run, error counts used to measure disk medium errors are restarted. The minimum role to
use the command is Standard. The syntax is clear degraded-disk. For information about specifying disks, see the
command syntax topic in the CLI Reference Guide.
Added firmware support for 764W AC PCMs and updated firmware for 764W DC PCMs.
In the USM update utility (UUT), the --frus no_logical_phy_remap option can now be used to disable logical
PHY mapping.
Fixes:
Fixed an issue where an EMP reported an alert condition on a voltage sensor.
Fixed an issue where a pool was offline due to inconsistent metadata.
Fixed an issue where, after a brief power loss, disks in an expansion enclosure became inaccessible though disks in the
controller enclosure remained accessible.
Fixed an issue with ADAPT spare capacity after disk replacement.
Fixed an issue with replication in a single-controller configuration.
Fixed an issue where the customer could not repurpose a foreign FDE-capable disk in a secured system.
Fixed an issue where SED disks went into an Unusable/Leftover state after the system was power-cycled.
Fixed an issue where FDE disks were not detected when a system was power-cycled.
Fixed an issue described as "A virtual pool was offline because a metadata volume is unreadable or missing."
Fixed an issue related to upgrading the GEM version in 5U84 enclosures having Lattice sideplanes.
Fixed an issue that caused the system to display an FDE protocol error.
Fixed an issue where missing VPD values caused an improper health warning to appear for 764W DC PCMs.
Fixed an issue where storage performance was degraded and the controller restarted automatically.
Fixed an issue where a dual-controller crash occurred while performing a rebalance operation.
Fixed an issue where physical PHY mapping was not enabled for Lattice sideplanes.
Fixed an issue where firmware update failed for a system with a mixed Lattice and Intel IOM configuration.
Fixed an issue where a misleading health message led to the wrong part being replaced. For health reason "A midplane
SGPIO bus failure was detected" the health recommendation has changed to "Contact technical support."
Fixed an issue where the disk count shown for a disk group was wrong after replacement of a failed disk.
Fixed a VPD issue that prevented zoning for 2U enclosures using certain midpanes.
Fixed an issue where both virtual pools were offline with health reason "The virtual pool is too large."
Fixed an issue where, after disk replacement and disk-group rebuild and rebalance, system performance was
degraded.
Fixed an issue where, after changing the password of a default user, the old password still worked.
Fixed an issue where attempting to update 5U84 JBOD IOM firmware failed due to a firmware mismatch.
Fixed an issue where updating to UUT 6.23 on a 5U84 system changed PHY mappings.
Fixed an issue where a disk group remained in a degraded state after replacement of a faulty disk.
Fixed an issue where a system using mixed-size disks in an ADAPT disk group had a failure that left multiple disks in a
leftover state.
Fixed an issue where, after disk firmware updates, an ADAPT disk group became quarantined.
Fixed an issue recorded as "Unexpected HW power state or mismatch between EBOD and Midplane CPLD power
states for drive" in controller logs that caused a disk group to be quarantined.
implemented, and Features:
In the CLI, the clear degraded-disk command can now be used to set a degraded disk's health to OK and clear the
disk's error count. After this command is run, error counts used to measure disk medium errors are restarted. The minimum role to
use the command is Standard. The syntax is clear degraded-disk
command syntax topic in the CLI Reference Guide.
Added firmware support for 764W AC PCMs and updated firmware for 764W DC PCMs.
In the USM update utility (UUT), the --frus no_logical_phy_remap option can now be used to disable logical
PHY mapping.
Fixes:
Fixed an issue where an EMP reported an alert condition on a voltage sensor.
Fixed an issue where a pool was offline due to inconsistent metadata.
Fixed an issue where, after a brief power loss, disks in an expansion enclosure became inaccessible though disks in the
controller enclosure remained accessible.
Fixed an issue with ADAPT spare capacity after disk replacement.
Fixed an issue with replication in a single-controller configuration.
Fixed an issue where the customer could not repurpose a foreign FDE-capable disk in a secured system.
Fixed an issue where SED disks went into an Unusable/Leftover state after the system was power-cycled.
Fixed an issue where FDE disks were not detected when a system was power-cycled.
Fixed an issue described as "A virtual pool was offline because a metadata volume is unreadable or missing."
Fixed an issue related to upgrading the GEM version in 5U84 enclosures having Lattice sideplanes.
Fixed an issue that caused the system to display an FDE protocol error.
Fixed an issue where missing VPD values caused an improper health warning to appear for 764W DC PCMs.
Fixed an issue where storage performance was degraded and the controller restarted automatically.
Fixed an issue where a dual-controller crash occurred while performing a rebalance operation.
Fixed an issue where physical PHY mapping was not enabled for Lattice sideplanes.
Fixed an issue where firmware update failed for a system with a mixed Lattice and Intel IOM configuration.
Fixed an issue where a misleading health message led to the wrong part being replaced. For health reason "A midplane
SGPIO bus failure was detected" the health recommendation has changed to "Contact technical support."
Fixed an issue where the disk count shown for a disk group was wrong after replacement of a failed disk.
Fixed a VPD issue that prevented zoning for 2U enclosures using certain midpanes.
Fixed an issue where both virtual pools were offline with health reason "The virtual pool is too large."
Fixed an issue where, after disk replacement and disk-group rebuild and rebalance, system performance was
degraded.
Fixed an issue where, after changing the password of a default user, the old password still worked.
Fixed an issue where attempting to update 5U84 JBOD IOM firmware failed due to a firmware mismatch.
Fixed an issue where updating to UUT 6.23 on a 5U84 system changed PHY mappings.
Fixed an issue where a disk group remained in a degraded state after replacement of a faulty disk.
Fixed an issue where a system using mixed-size disks in an ADAPT disk group had a failure that left multiple disks in a
leftover state.
Fixed an issue where, after disk firmware updates, an ADAPT disk group became quarantined.
Fixed an issue recorded as "Unexpected HW power state or mismatch between EBOD and Midplane CPLD power
states for drive" in controller logs that caused a disk group to be quarantined.
Important Information
This update is urgent and strongly recommended for all Dell EMC PowerVault ME4 Series Storage Arrays.
Compatible Systems
Supported Operating Systems
Citrix XenServer 7.1
Red Hat® Enterprise Linux 6
Red Hat® Enterprise Linux 7
Red Hat® Enterprise Linux 8
SUSE Linux ES 12
SuSE Linux ES 15
Windows Server 2012 R2
Windows Server 2019 LTSC
Windows Server 2022 LTSC
Windows Server 2016
VMware ESXi 6.5
VMware ESXi 6.7
VMware ESXi 7.0
Installation instructions
1. Perform one of the following:
In the banner, click the system panel and select Update Firmware.
In the System topic, select Action > Update Firmware.
The Update Firmware panel opens. The Update Controller Modules tab shows versions of firmware components that are currently installed in each controller.
2. Click the Bundle or Controller Firmware File button to select the firmware file to install.
3. Optionally, select (enable) or clear (disable) the PFU check box and confirm the action.
NOTE: For information about which controller module will update the other when a controller module is replaced, see About firmware update.
4. Click OK. A panel shows firmware-update progress.
The process starts by validating the firmware file:
If the file is invalid, verify that you specified the correct firmware file. If you did, try downloading it again from the source location.
If the file is valid, the process continues.
CAUTION: Do not perform a power cycle or controller restart during a firmware update. If the update is interrupted or there is a power failure, the module might become inoperative. If this occurs, contact technical support. The module
might need to be returned to the factory for reprogramming.
Firmware update typically takes 10 minutes for a controller with current CPLD firmware, or 20 minutes for a controller with downlevel CPLD firmware. If the controller enclosure has connected enclosures, allow additional time for each expansion module's enclosure management processor (EMP) to be updated. This typically takes 2.5 minutes for each EMP in a drive enclosure.
If the Storage Controller cannot be updated, the update operation is canceled. Verify that you specified the correct firmware file and repeat the update. If this problem persists, contact technical support.
When firmware update on the local controller is complete, users are automatically signed out and the MC restarts. Until the restart is complete, sign-in pages say that the system is currently unavailable. When this message is cleared, you may sign in again.
If PFU is enabled, allow from 10 through 20 minutes for the partner controller to be updated.
5. Clear your web browser cache, then sign in to the MESM. If PFU is running on the controller you sign in to, a panel shows PFU progress and prevents you from performing other tasks until PFU is complete.
NOTE: If PFU is enabled for the system, after firmware update has completed on both controllers, check the system health. If the system health is Degraded and the health reason indicates that the firmware version is incorrect, verify that you specified the correct firmware file and repeat the update. If this problem persists, contact technical support.
In the banner, click the system panel and select Update Firmware.
In the System topic, select Action > Update Firmware.
The Update Firmware panel opens. The Update Controller Modules tab shows versions of firmware components that are currently installed in each controller.
2. Click the Bundle or Controller Firmware File button to select the firmware file to install.
3. Optionally, select (enable) or clear (disable) the PFU check box and confirm the action.
NOTE: For information about which controller module will update the other when a controller module is replaced, see About firmware update.
4. Click OK. A panel shows firmware-update progress.
The process starts by validating the firmware file:
If the file is invalid, verify that you specified the correct firmware file. If you did, try downloading it again from the source location.
If the file is valid, the process continues.
CAUTION: Do not perform a power cycle or controller restart during a firmware update. If the update is interrupted or there is a power failure, the module might become inoperative. If this occurs, contact technical support. The module
might need to be returned to the factory for reprogramming.
Firmware update typically takes 10 minutes for a controller with current CPLD firmware, or 20 minutes for a controller with downlevel CPLD firmware. If the controller enclosure has connected enclosures, allow additional time for each expansion module's enclosure management processor (EMP) to be updated. This typically takes 2.5 minutes for each EMP in a drive enclosure.
If the Storage Controller cannot be updated, the update operation is canceled. Verify that you specified the correct firmware file and repeat the update. If this problem persists, contact technical support.
When firmware update on the local controller is complete, users are automatically signed out and the MC restarts. Until the restart is complete, sign-in pages say that the system is currently unavailable. When this message is cleared, you may sign in again.
If PFU is enabled, allow from 10 through 20 minutes for the partner controller to be updated.
5. Clear your web browser cache, then sign in to the MESM. If PFU is running on the controller you sign in to, a panel shows PFU progress and prevents you from performing other tasks until PFU is complete.
NOTE: If PFU is enabled for the system, after firmware update has completed on both controllers, check the system health. If the system health is Degraded and the health reason indicates that the firmware version is incorrect, verify that you specified the correct firmware file and repeat the update. If this problem persists, contact technical support.
Applies to
ME4012