Attention: Removing a logical volume destroys all data in the specified file systems and logical volume. A host can discover storage devices to which it has access and format them as datastores. Since VSAN does not make use of SCSI-2 reservations, it did not make sense to support it and hence the issue.

The configuration that determines the association between storage device and ESXi host is stored on the storage array, and the array vendor may need to be engaged. ESXi hosts use storage space on a variety of physical storage systems, including internal and external devices and networked storage. A single VMFS volume can contain one or more LUNs from a local SCSI disk array on a physical host, a Fibre Channel SAN disk farm, or iSCSI SAN disk farm.The ESX/ESXi system detects new LUNS that are added to any of the physical storage subsystems. Datastores can span multiple physical storage devices. The much anticipated release of vSphere 6.5 has officially GA'ed and you can find all the release notes and downloads over here.Just like prior releases, I have created a new Nested ESXi Virtual Appliance to aide in quickly setting up a vSphere 6.5 environment … However, if you do not have access to the vSphere Client or you wanted to format additional VMFS volumes via a kickstart, you can do so using the CLI and the partedUtil under /sbin. ~ # /sbin/partedUtil Even though VMFS-5 no longer uses SCSI-2 reservations, the underlying LVM (Logical Volume Manager) driver for VMFS still requires it. Use this procedure to remove a logical volume with a different type of file system mounted on it or a logical volume that does not contain a file system. VMware always recommends formatting and creating a new VMFS volume using the vSphere Client as it automatically aligns your VMFS volume. If the storage array responds with a list, but the list does not contain the desired logical units (LUNs), this may indicate an issue associating the Initiator with the device.