Change Summary
This page was deprecated on 18 August 2025. Refer to the SANsymphony WebHelp for the latest and updated documentation.
For the latest version of the FAQ, refer to DataCore FAQ 838.
Changes since June 2023
| Section(s) | Content Changes |
|---|---|
| Known Issues - DataCore Servers running in Virtual Machines (HCI) |
Added Affects ESXi 8.x and 7.x DataCore Servers running in ESXi Virtual Machines may experience unexpected mirror IO failure causing loss of access for some or all paths to a DataCore Virtual Disk This problem has been reported as resolved in the following VMware Knowledge base article: “3rd party Hyper Converged Infrastructure setups experience a soft lock up and goes unresponsive indefinitely” https://kb.vmware.com/s/article/88856 However, DataCore working with VMware discovered that the problem still existed in the version listed in the article (i.e. ESXi 7.0.3i) and that it was not until ESXi 7.0.3o the problem had been fixed. DataCore recommends a minimum ESXi version of:
This problem does not apply to DataCore Servers running in ‘physical’ Windows servers or when running in non-VMware Virtual Machines (e.g. Hyper-V). |
| Known Issues - Fibre Channel Adaptors |
Updated Hosts with Fibre Channel HBAs that are FC-NVME capable may report their storage adapters twice in ESXi and be unable to discover SANsymphony Virtual Disks served to them FC-NVME is not supported for SANsymphony Virtual Disk mappings. Turn off the FC-NVME feature on the ESXi host’s HBA driver by using one of the following commands: Qlogic HBAs: esxcfg-module -s 'ql2xnvmesupport=0' qlnativefc Emulex HBAs: esxcli system module parameters set -m lpfc -p lpfc_enable_fc4_type=1 A reboot of the ESXi host is required in both cases. |
See Previous Changes section that lists the earlier changes made to this FAQ.