PowerStoreOS 4.3.1.x Service Pack and Patch Release Notes
Summary: This document describes the issues resolved in the service pack and 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
The known issues, environmental and system requirements, and installation or update considerations associated with these service pack and patch releases are the same as the parent release. For more information, see the Dell PowerStoreOS 4.3.0.0 Release Notes on the PowerStore Info Hub.
Release Revision History
| Release | Description |
| 4.3.1.1 |
|
| 4.3.1.0 |
|
| 4.3.0.0 |
|
PowerStoreOS 4.3.1.1 (Build: 2726662)
Resolved issues
| Issue ID | Description |
| PSSLDF-67466 | A node on a long-running system with high memory utilization may become unresponsive and restart if memory reclamation overlaps with a disruption in internal communication. This issue may result in a temporary Data Unavailable (DU) condition if the peer node is unavailable during this time. |
| PSSLDF-64956 | If a PowerStore appliance is in NVRAM resiliency mode, the appliance nodes may repeatedly reboot and enter service mode due to incorrect internal device metadata in the Data Path (DP). |
| PSSLDF-62194 | During a non-disruptive upgrade (NDU) from PowerStoreOS 3.x to 4.x, some Pre-Upgrade Health Checks may fail to run and issues that would prevent the NDU from running are not detected. If the NDU proceeds, the issues that were not found during the Pre-Upgrade Health Check may cause the upgrade to fail. |
| PSSLDF-59683 | Creating an import connection to a Unity system running Unity OE 5.5.3 may fail because OE 5.5.3 is not supported on PowerStoreOS 4.3. |
| PSSLDF-59238 | Ethernet devices may fail to power-up and the ports fail to come online after a node reboot is performed as part of a non-disruptive upgrade (NDU) to PowerStoreOS 4.1 or later, or a power cycle. |
| PSSLDF-59169 | After performing a non-disruptive upgrade (NDU) to PowerStoreOS 4.3, a node may restart and cause the NAS server to fail over to the peer node. This issue occurs when a Kerberos ticket expires during an active SMB2 session and the client is unable to renew the ticket. |
| PSSLDF-56597 | Importing external storage from a remote system may cause a node to become unresponsive and restart if the I/O load from the host to the importing volumes is very high. |
| PSSLDF-55465 | In rare cases, a non-disruptive upgrade (NDU) failure or unexpected node reboot may occur due to a startup sequence issue. The issue can occur after a node is upgraded during an NDU or after a node reboot. |
| PSSLDF-54805 | In rare cases, if a single NFSv4 client holds multiple open file state handles with delegations, a locking condition could lead to a self‑deadlock in the delegation mechanism, causing the node to panic and restart. |
| PSSLDF-54162 | Clicking the AIOps link in PowerStore Manager may fail to open Dell AIOps. |
| PSSLDF-53424 | When the In-band Migration Tool (IMT) is used to migrate file data from a Unity system to a PowerStore cluster, a deadlock between the IMT and background file operations may occur, causing the NAS servers to become inaccessible. |
| PSSLDF-53418 | When the In-band Migration Tool (IMT) is used to migrate file data from a Unity system to a PowerStore cluster, an issue may occur with a file that was created before the cutover, modified during the cutover, and deleted after the cutover that prevents a new file with the same name from being created. |
| PSSLDF-52127 | Performing a non-disruptive upgrade (NDU) to PowerStoreOS 4.3 may impact NAS server access when an Active Directory Restricted Groups group policy object (GPO) is used to add external users or groups as members of a local group on the NAS server. |
| PSSLDF-52096 | On large-scale PowerStore clusters, the automatic removal of metrics archive data may fail, potentially causing space issues on /cyc_cfs. |
| PSSLDF-50801 | If large volumes are migrated from an IBM Storwize v5000 system to a PowerStore appliance over an unstable network connection, volume discovery may timeout, causing the appliance nodes to reboot and resulting in a Data Unavailable (DU) condition. |
| PSSLDF-47873 | In rare cases, performing a non-disruptive upgrade (NDU) may fail because a software component attempts to read data from a table before the data is populated. |
| PSSLDF-46954 | If a non-disruptive upgrade (NDU) fails due to a hardware issue on a mezzanine card, the NDU rollback may fail to complete because a drive database issue causes some drives to appear offline. When the drive database is corrected, the drives become healthy, but the process of clearing offline drives is skipped. As a result, the Data Path (DP) fails to fully start, and the cluster enters a Data Unavailable (DU) condition. |
| PSSLDF-45774 | In rare cases, performing a non-disruptive upgrade (NDU) may fail due to repeated communication timeouts with the peer node. The communication timeouts can cause a large number of scheduler history files to accumulate, which can consume all available space on the root partition and prevent the node from booting successfully. |
| PSSLDF-44534 | A parsing issue may cause node health to be misinterpreted on a PowerStore appliance with multi-digit Pacemaker node IDs, leading to incorrect Global Storage Discovery IP (GSIP) address handling. |
| PSSLDF-43528 | If the nodes of an appliance are manually rebooted during a non-disruptive upgrade (NDU) from PowerStoreOS 4.1 or earlier to a later version of PowerStoreOS 4.1 or 4.2, the resulting NDU failure may cause the NTP server list in PowerStore Manager to appear empty. |
| PSSLDF-42166 | In-band Migration Tool (IMT) cutover may fail in environments where a NAS server contains a large combination of production interfaces and file systems, such as 50 interfaces with 125 file systems. During cutover, bringing all interfaces online may exceed the Network Lock Manager (NLM) reclaim timeout window, causing the operation to fail. |
| PSSLDF-41154 | Certain I/O patterns, including burst scatter I/O (over 2048 burst I/O with scatter mode), may cause the Data Path (DP) on both nodes to restart, resulting in a Data Unavailable (DU) condition. |
| PSSLDF-40849 | In rare cases, a node may reboot unexpectedly during a battery backup unit (BBU) replacement due to an issue with NVRAM drives. |
| PSSLDF-40829 | The Data Path (DP) service may become unresponsive and restart due to an internal timing issue. |
| PSSLDF-36875 | If a non-disruptive upgrade (NDU) fails on the secondary node of an appliance due to a failed NVRAM drive, the NDU recovery procedure may fail and the system may be left in a degraded state. |
| PSSLDF-33037 | A non-disruptive upgrade (NDU) from PowerStoreOS 4.1 to 4.2 may cause System Health Checks (SHC) to fail due to an out-of-memory error. |
| PSSLDF-26955 | In rare cases, if the network becomes unstable while data is being transferred using asynchronous replication, synchronous replication, Metro replication, or migration, the Data Path (DP) on the source system may become unresponsive and restart. |
| PSSLDF-3649 | If a Storage Access Module (SAM) in an NVMe expansion enclosure is replaced, the drives in the enclosure may fail to connect to the PowerStore system after a non-disruptive upgrade (NDU) or node reboot is performed. |
| PSSL13C-506 |
If password credentials are changed while a migration is in progress, the migration may fail with the following errors during cutover:
|
| PSSL09D-473 | Metro volumes may become fractured and inaccessible from the host because an internal component stops responding. |
| PSSL09A-433 | During a non-disruptive upgrade (NDU) from PowerStoreOS 3.x to 4.x, some Pre-Upgrade Health Checks may fail to run and issues that would prevent the NDU from running are not detected. If the NDU proceeds, the issues that were not found during the Pre-Upgrade Health Check may cause the upgrade to fail. |
Known issues
| Issue ID | Description | Workaround |
| PSSLDF-57929 | In rare cases, performing a non-disruptive upgrade (NDU) from PowerStoreOS 4.1.0.1 to 4.1.0.4 may fail and cause a node to become unresponsive and restart due to an issue with the Fibre Channel driver. | Perform the upgrade during a period of extremely low activity on the PowerStore cluster. Remove hosts from the PowerStore cluster or balance the hosts across the available ports to prevent the overutilization of a single port. |
| PSSLDF-37227 | In rare cases, the Historical Capacity widget on the Capacity dashboard may fail to display data when Last 24 hours is selected from the View menu. | Select a different value from the View drop-down, go to a different page and then go back to the Capacity dashboard page, or refresh the Capacity dashboard page. |
| PSSLDF-32866 | When Windows Server Failover Clustering (WSFC) is used with Metro volumes that are configured on ESXi hosts using Raw Device Mappings (RDMs), arbitration errors may appear in the Windows host log if a WSFC disk fails over. If a Windows node fails over, I/O may be interrupted. | Use Windows Cluster Failover Manager to bring the failed disk online. |
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 LTS2026-4.3.1.1-2726662, and the file name of the downloadable upgrade package is PowerStoreT-LTS2026-4.3.1.1-2726662-retail.tgz.bin.
PowerStoreOS 4.3.1.0 (Build: 2662695)
Resolved issues
| Issue ID | Description |
| PSSLDF-51435 | Manually licensing a PowerStore cluster using a Transformational License Agreement (TLA) license may fail with the error Failed to obtain the product registration data (0xE0D010030008) because the license type is unrecognized. |
| PSSLDF-47625 | The Dell PowerStore Plug-In for Veeam Backup & Replication may stop working after upgrading to PowerStoreOS 4.3. |
| PSSLDF-46070 | When recovering from a failed non-disruptive upgrade (NDU), performing the NDU again may cause the PowerStore cluster to incorrectly report that the upgrade ended in a Cluster Rollback state. However, the cluster is still in a failed upgrade state. |
| PSSLDF-45492 | A PowerStore system may experience authentication failures when connecting to a Data Domain system that is configured as an Encryption Disabled Project (EDP) device. |
| PSSLDF-39570 | Evicting a drive and replacing it with a higher capacity drive may cause the Data Path (DP) to restart, resulting in a Data Unavailable (DU) condition. |
| PSSLDF-39498 | If a cluster was originally deployed with PowerStoreOS 2.1 or earlier, the secondary node of an appliance may enter service mode during a non-disruptive upgrade (NDU) from PowerStoreOS 4.2.x to a later version. |
| PSSLDF-39003 | An error may occur while accessing an appliance performance chart after performing a non-disruptive upgrade (NDU) from PowerStoreOS 4.2 to 4.3. This error can occur if the charting preferences in the appliance performance chart were modified and saved while running an older version of PowerStoreOS. |
| PSSLDF-37601 | If a node on the preferred side of a Metro session goes down or reboots, the status of the Metro session may change to Fractured. |
| PSSLDF-33876 | A node may fail to boot if a non-disruptive upgrade (NDU) from PowerStoreOS 3.6 or earlier to PowerStoreOS 4.0 or later is rolled back. |
| PSSLDF-32566 | Issuing an NVMe command on a volume without valid mappings can cause the command to fail, which may lead to a Data Path (DP) failure and cause the node to enter Service Mode. |
| PSSLDF-27370 | After performing a non-disruptive upgrade (NDU) to PowerStoreOS 4.1 or replacing the internal M.2 boot module, the local NTP servers on the appliance nodes may enter an unsynchronized state when the external NTP server is inaccessible. |
Known issues
| Issue ID | Description | Workaround |
| PSSLDF-52127 | After performing a non-disruptive upgrade (NDU) to PowerStoreOS 4.3, NAS server access may be impacted when an Active Directory Restricted Groups group policy object (GPO) is used to add external users or groups as members of a local group on the NAS server. | Disable the Restricted Groups GPO and manually add the external users or groups to the local group on the NAS server using the Microsoft Management Console (MMC) snap-in. For more information, see KB article 000424100. |
| PSSLDF-37227 | In rare cases, the Historical Capacity widget on the Capacity dashboard may fail to display data when Last 24 hours is selected from the View menu. | Select a different value from the View drop-down, go to a different page and then go back to the Capacity dashboard page, or refresh the Capacity dashboard page. |
| PSSLDF-32866 | When Windows Server Failover Clustering (WSFC) is used with Metro volumes that are configured on ESXi hosts using Raw Device Mappings (RDMs), arbitration errors may appear in the Windows host log if a WSFC disk fails over. If a Windows node fails over, I/O may be interrupted. | Use Windows Cluster Failover Manager to bring the failed disk online. |
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 LTS2026-4.3.1.0-2662695, and the file name of the downloadable upgrade package is PowerStoreT-LTS2026-4.3.1.0-2662695-retail.tgz.bin.
PowerStoreOS 4.3.0.0 (Build: 2611831)
See the Dell PowerStoreOS 4.3.0.0 Release Notes on the PowerStore Info Hub.
Affected Products
PowerStore, PowerStore 1000T, PowerStore 1200T, PowerStore 3000T, PowerStore 3200Q, PowerStore 3200T, PowerStore 5000T, PowerStore 500T, PowerStore 5200Q, PowerStore 5200T, PowerStore 7000T, PowerStore 9000T, PowerStore 9200TArticle Properties
Article Number: 000427228
Article Type: How To
Last Modified: 12 ذو الحجة 1447
Version: 8
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.