August 18, 2016

ESXi 6.0 / Synology / iSCSI & NFS Notes

https://miketabor.com/setup-nfs-on-synology-nas-for-vmware-esxi-lab/

https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Virtualization/How_to_set_up_Synology_NAS_as_VMware_server_datastore

https://www.synology.com/en-us/support/download/DS1515+

esxcli software vib install -v /vmfs/volumes/3c3e0416-6b44bd28-1208-001b211b1f56/patch/esx-nfsplugin.vib --no-sig-check

reboot
esxcli software vib list | more


https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1014165

ESXi 6.0 / Synology / iSCSI & NFS Notes

https://miketabor.com/setup-nfs-on-synology-nas-for-vmware-esxi-lab/

https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Virtualization/How_to_set_up_Synology_NAS_as_VMware_server_datastore

https://www.synology.com/en-us/support/download/DS1515+

esxcli software vib install -v /vmfs/volumes/3c3e0416-6b44bd28-1208-001b211b1f56/patch/esx-nfsplugin.vib --no-sig-check

reboot
esxcli software vib list | more


https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1014165

ESXi 6 does not mount iSCSI VMFS datastore after reboot

First reboot after upgrading to ESXi6.0 from 5.5 caused my iSCSI datastore to fail.

Storage adapter was still there

The device was still mounted under "Storage"

Errors in the logs showed:

2016-08-17T05:25:54.411Z cpu1:34670 opID=ca3ef949)WARNING: FSAts: 1498: Denying reservation access on an ATS-only vol 'NAS-ESX-VM-DATA'
2016-08-17T05:25:54.411Z cpu1:34670 opID=ca3ef949)WARNING: HBX: 2227: ATS-Only VMFS volume 'NAS-ESX-VM-DATA' is not mounted. This host does not support ATS, or ATS initialization failed.
2016-08-17T05:25:54.411Z cpu1:34670 opID=ca3ef949)WARNING: HBX: 2240: Failed to initialize VMFS distributed locking on volume 577dfaa1-39238aee-2aa5-f46d0475f288: Not supported

After a lot of googling, changing the following advanced settings

DataMover.HardwareAcceleratedMove = 0  
DataMover.HardwareAcceleratedInit = 0
VMFS3.HardwareAcceleratedLocking = 0
and then rebooting the host resolved the issue