PowerStoreOS 4.1.0.x Patch Release Notes
Summary: This document describes the issues resolved in the patch releases of PowerStoreOS.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Instructions
Known issues, environmental and system requirements, and installation or update considerations associated with these patch releases are the same as the parent release. For more information, see the Dell PowerStoreOS 4.1.0.0 Release Notes on the PowerStore Info Hub.
Release Revision History
| Release | Description |
| 4.1.0.4 |
|
| 4.1.0.3 |
|
| 4.1.0.2 |
|
| 4.1.0.1 |
|
| 4.1.0.0 |
|
PowerStoreOS 4.1.0.4 (Build: 2633110)
Resolved issues
| Issue ID | Description |
| PSSLDF-34194 | In rare cases, if a NAS replication session fails over to the destination side and the source side comes back online, the NAS server on the source side may report a Production Mode of true instead of false. |
| PSSLDF-25330 | System Manager (SYM) may become unresponsive and restart while handling SYM agent messages. |
| PSSLDF-23124 | A PowerStore 3200Q or 5200Q storage system may experience a Data Unavailable (DU) event while the secondary M.2 drive is replaced or repaired. |
| PSSLDF-20041 | When the load on a PowerStore system is very high, the scripts responsible with bringing up NAS services on a node may encounter an internal timing issue that causes the NAS container to restart multiple times. |
| PSSLDF-8516 | If a PowerStore cluster was deployed using PowerStoreOS 2.x or earlier, Data Path (DP) trace collection may be disabled on the cluster after it is upgraded to PowerStoreOS 4.0 or later. |
| PSSLDF-7018 | In rare cases, performing a non-disruptive upgrade (NDU) may fail if gates are closed during metro reservation synchronization because SCSI-3 Persistent Reserve Release (PRR) operations are blocked. |
| PSSLDF-5336 | Performing a non-disruptive upgrade (NDU) from PowerStoreOS 3.6.1.3 to 4.0.1.3 may fail due to a node becoming unresponsive and failing to reboot. |
| PSSLDF-4571 | Hardware fencing may be mistakenly disabled after performing a non-disruptive upgrade (NDU) from PowerStoreOS 2.1.x to PowerStoreOS 3.5 or 3.6. |
| PSSLDF-4389 | In rare cases, the Data Path (DP) on a destination PowerStore system may become unresponsive and restart when asynchronous replication, synchronous replication, metro replication, or migration is performed. |
| PSSLDF-3286 | In rare cases, performing a non-disruptive upgrade (NDU) may fail due to an issue with the worker locking mechanism that allows two workers to run simultaneously. |
| PSSLDF-2852 | When an NVRAM drive with the part number 005033035 or 005053655 is replaced, the PowerStore cluster may raise the false alert The drive does not meet FIPS requirements, even though the drive is online and functioning normally. |
| PSSLDF-2442 | Event sequence numbers for the Data Path (DP) and Control Path (CP) may become misaligned, which can result in missed DP events and cause the CP to restart unexpectedly. |
| PSSLDF-2087 | If a PowerStore 500T appliance incorrectly determines that a node reboot was caused by a power failure, the node may fail to stop in service mode and enter a reboot loop. |
| PSSLDF-1883 | A PowerStore cluster may raise the alert DATA_PATH_SCHEDULE_MAPPER_RECOVERY_LATER (0x00200f02) after a node reboot or system outage occurs. |
| PSSLDF-1436 | Error handling in logical merge processing may fail when a metadata inconsistency occurs in the logical copy count. |
| PSSLDF-1428 | If the automatic download of software upgrades is enabled on a PowerStore system, a malformed manifest file can cause multiple software packages to be downloaded, leading to an out-of-space issue on the root partition. |
| PSSLDF-478 | Information about metro volumes may be missing from Data Collection files because the Data Collect utility fails to collect metro volume data. |
| PSSLDF-255 | A false metadata corruption message may appear in PowerStore system logs due to incorrect error handling during an internal metadata update process. |
| PSSL14K-485 | If newly supported drives are present in a system running PowerStoreOS 4.0 or earlier, performing a non-disruptive upgrade (NDU) may fail and result in a Data Unavailable (DU) event. |
| PSSL14I-192 | One or more Ethernet interfaces may become unavailable on a node after performing a non-disruptive upgrade (NDU). |
| PSSL08C-569 | When a new drive is added to an appliance, manufacturing metadata on the drive may be lost. If both appliance nodes are rebooted after the metadata is lost, a Data Unavailable (DU) condition may occur. |
| PSSL03L-545 | NVRAM resiliency mode may be unnecessarily triggered when a non-disruptive upgrade (NDU) fails. |
| PSSL01B-513 | PowerStore systems only support increasing the size of vVols. However, in rare cases, a rollback scenario may attempt to decrease the size of a vVol, which can cause the Data Path (DP) to become unresponsive and restart. |
Upgrade Package
If automatic download is not enabled on your PowerStore cluster, download the PowerStore upgrade package from the Dell Technologies Support site.
The name of the upgrade package on the support site is PowerStore T OS Upgrade LTS2025-4.1.0.4-2633110, and the file name of the downloadable upgrade package is PowerStoreT-LTS2025-4.1.0.4-2633110-retail.tgz.bin.
PowerStoreOS 4.1.0.3 (Build: 2596462)
Resolved issues
| Issue ID | Description |
| PSSLDF-20147 | Upgrading the firmware on Intel SSDs may fail because of a timing issue during firmware activation, resulting in a Data Unavailable (DU) event. |
| PSSLDF-3640 | A metro outage may occur after performing a non-disruptive upgrade (NDU) from PowerStoreOS 3.6 or earlier to PowerStoreOS 4.0 or later on the first appliance of a cluster because SCSI reservation synchronization between the metro appliances may be blocked. |
Upgrade Package
If automatic download is not enabled on your PowerStore cluster, download the PowerStore upgrade package from the Dell Technologies Support site.
The name of the upgrade package on the support site is PowerStore T OS Upgrade LTS2025-4.1.0.3-2596462, and the file name of the downloadable upgrade package is PowerStoreT-LTS2025-4.1.0.3-2596462-retail.tgz.bin.
PowerStoreOS 4.1.0.2 (Build: 2567482)
Resolved issues
| Issue ID | Description |
| PSSLDF-20249 | Adjusted the Crypto-J library configuration to improve system stability and maintain consistent performance. |
| PSSLDF-15242 | If a PowerStore appliance is deployed using PowerStoreOS 2.x or earlier, performing a nondisruptive upgrade (NDU) to PowerStoreOS 4.1 may cause the first node of the appliance to enter service mode. |
| PSSLDF-4055 | On a PowerStore 500T appliance, performing a non-disruptive upgrade (NDU) to PowerStoreOS 4.1 may cause the fru_use_state of the 4-port card to be incorrectly set to fru_not_in_use. |
Upgrade Package
If automatic download is not enabled on your PowerStore cluster, download the PowerStore upgrade package from the Dell Technologies Support site.
The name of the upgrade package on the support site is PowerStore T OS Upgrade LTS2025-4.1.0.2-2567482, and the file name of the downloadable upgrade package is PowerStoreT-LTS2025-4.1.0.2-2567482-retail.tgz.bin.
PowerStoreOS 4.1.0.1 (Build: 2529516)
Resolved issues
| Issue ID | Functional area | Description |
| MDT-692523 | Install or Upgrade | A non-disruptive upgrade (NDU) to PowerStoreOS 4.1 may fail during post-upgrade operations due to a missing NDU-related code change in PowerStoreOS 4.1. |
| PSSLDF-327 | Storage - Block | Running an XCOPY command with invalid metadata may cause the Data Path (DP) service to become unresponsive and restart during a cache flush operation. This condition may cause the nodes of the appliance to reboot and result in a Data Unavailable (DU) condition. |
| MDT-707329 | Storage - Block | If an initiator object is deleted and a new initiator object with the same name is created, the deleted object may be restored after the System Manager (SYM) restarts. This condition can result in an "initiator name not unique" error and cause SYM to restart repeatedly until a Data Unavailable (DU) condition occurs. |
| MDT-700713 | Storage - Block | If a drive fails after both appliance nodes reboot, a Data Unavailable (DU) condition may occur, and the appliance may fail to recover automatically. |
| MDT-699337 | Storage - Block | A metadata page inconsistency may lead to an internal I/O timeout on a volume with snapshots enabled. This condition can cause appliance nodes to become unresponsive and reboot. |
| MDT-696700 | Storage - Block | If a TCP replication session repeatedly reconnects, the Data Path (DP) service may become unresponsive and restart. |
| MDT-694064 | Storage - Block | If a volume in a metro session experiences a high rate of unmap requests, I/O requests may exceed the token pool capacity, causing I/O to queue. If the I/O is queued for too long, the Data Path (DP) service may become unresponsive and restart. |
| MDT-689736 | Storage - Block | An internal timing issue in PowerStoreOS may cause a node to unexpectedly reboot. |
| MDT-617719 | Storage - Block | When a node is removed and reinserted into an appliance, the NVRAM drives may experience an issue that can lead to a faulted NVRAM pair and result in a Data Unavailable (DU) condition. |
| MDT-705861 | Storage - File | A Unified appliance may become unresponsive and reboot due to a segmentation fault caused by invalid memory access. |
| MDT-691358 | Support Connectivity | On a PowerStore cluster running PowerStoreOS 4.0 or later, enabling Support Connectivity using a Secure Connect Gateway connection may fail due to a failed health check. |
Upgrade Package
If automatic download is not enabled on your PowerStore cluster, download the PowerStore upgrade package from the Dell Technologies Support site.
The name of the upgrade package on the support site is PowerStore T OS Upgrade LTS2025-4.1.0.1-2529516, and the file name of the downloadable upgrade package is PowerStoreT-LTS2025-4.1.0.1-2529516-retail.tgz.bin.
PowerStoreOS 4.1.0.0 (Build: 2435323)
See the Dell PowerStoreOS 4.1.0.0 Release Notes on the PowerStore Info Hub.
Affected Products
PowerStore 1000T, PowerStore 1200T, PowerStore 3000T, PowerStore 3200T, PowerStore 5000T, PowerStore 500T, PowerStore 5200T, PowerStore 7000T, PowerStore 9000T, PowerStore 9200TArticle Properties
Article Number: 000347814
Article Type: How To
Last Modified: 06 Jan 2026
Version: 6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.