Issues Resolved in DataCore SANsymphony 10.0 PSP20 - Preview 1

Crash During Mirror Recoveries

The DataCore server crashes during recovery with the error: "PNP_DETECTED_FATAL_ERROR - Duplicate PDO".

DataCore Management Console

The Passthrough virtual disks could not be deleted when using the DataCore Management Console.

DataCore Management Console UI Issues on Low Resolution Screens

The DataCore Management Console does not display all UI elements when using the 'Purge Physical Disk' wizard on low resolutions or small window sizes.

Disk Devices Becoming Locked After Restart or Loopback Creation Due to Race Condition

Disk devices that were previously released or used for loopback virtual disks become locked in the DataCore Management Console after a system restart or during the creation of loopback virtual disks. This prevents third-party access to the devices.

DataCore Driver Issue with QLogic QLE26xx/QLE27xx HBAs

Fibre Channel ports report as "Not Started" in the DataCore Management Console immediately after installing the DataCore QLogic Driver.

DataCore Management Console Saved Credentials are Not Retained After Signing Out

When you select “Remember Password” in the DataCore Management Console, signing out of Windows causes the saved password to be lost.

Delayed ACK Inconsistency in the DataCore Management Console

For ESX hosts not managed by DataCore's vCenter integration, the 'Delayed ACK' column may display incorrect information.

Excessive Memory Allocation in NONPAGED_AREA Causing System Instability

A race condition during target port discovery can lead to excessive memory allocation, potentially causing a system crash.

iSCSI Ports Missing After Server Restart

After a server restart, DataCore SANsymphony may show iSCSI ports as missing, even though they are active and transferring data.

Manual Reclamation Issue

Manual Reclamation may appear to never complete or take longer than expected while Automatic Reclamation is also being detected on the same virtual disk.

Missing Commands in DataCore Server Panel for Virtual Disk Group

Certain commands were missing from the right-click context menu for virtual disk groups in the DataCore Server Panel.

Missing Warning Message When Toggling Encryption

A warning message did not appear when toggling encryption on a virtual disk.

Mirror Path Status Incorrect After Server Reboot

After a server restarts in large setups, some virtual disks may show missing mirror paths that do not reconnect automatically.

Support Bundle Collection Termination

The support bundle collection could terminate unexpectedly.

Some FC Ports Incorrectly Show as "Not Present" While Active

Some host FC connections appear as “Not Present” in the DataCore Management Console, even though they are active and transferring data.

Unnecessary Log Message for Disk Replacement

An unexpected alert appeared in the DataCore Management Console stating, "A physical disk has been replaced, which may cause problems with the configuration," even when no change had occurred.

Unnecessary Logstore Disk Failure Alerts

The DataCore Management Console triggers unnecessary alerts stating, "The Logstore disk is currently failed," when the logstore logical disk loses access due to normal reasons.

Unclosed DataCore Cmdlets Sessions Cause DCSX Service Unresponsiveness

When an active DataCore cmdlets session is closed (either by script exit or module unload), the active connections are not properly closed. Over time, this leads to the accumulation of unused sessions, potentially causing the DCSX service to become unresponsive.

Unable to Set Disk Pool to Single Tier

When Capacity Optimization is enabled on a disk pool, you cannot reduce the maximum number of disk tiers to 1.

Virtual Disk Templates

Dual virtual disk templates previously allowed CDP or sequential storage, which is not supported.

Virtual Disks Unserved During Host Conversion

While moving existing ESX host mappings to a vCenter-managed host, virtual disks may become unserved.

Windows Device Manager Issue

Windows Device Manager misidentified the 'DataCore Emulex LPe32000-X' as 'DataCore Emulex LPe32200-X' due to a typo in the configuration file used for device identification.