ESXi indicate iSCSI device as “Not consumed”
Recently, I created a new LUN in Huwawi Storage and then went to the VMware vCenter to create the corresponding datastore. I created this datastore on one of the ESXi hosts and went to the other hosts and scanned the adapter. The Environment includes 3 ESXi hosts. Although the datastore was created successfully, when I looked at the other two ESXi hosts, They couldn’t recognize the new datastore and show the corresponding Lun with a label called “No consumed”. I also performed a rescan of the storage on an ESXi host to look for any change in Storage Device or VMFS Volumes. However, in my opinion, scanning for new VMFS Volumes is sufficient while I have the LUN with VMFS formatted and just need to detect this volume.
No consumed means that the datastore has not yet been formatted as a VMFS datastore, but I have formatted it by using another ESXi host in the Cluster. after googling and testing in my environment, I come up with two solutions for this problem. The problem is that other hosts can not mount this datastore and you have to do it manually. And let me add that I have 3 versions of ESXi in the cluster with EVC enabled. ESXi 6.7 and ESXi 6 and 6.5. ESXi 6.7 works fine but the remaining two ESXi not working.
You need to manually mount the datastore however it mounts successfully on other hosts. Therefore, enable SSH on the ESXi host and run the following command to list datastores and find your LUN UUID.
write down the LUN UUID and run the following command to mount the datastore manually.
esxcfg-volume -m <VMFS UUID|label>
Great! That works for me, but it just worked on ESXi 6.5 and the ESXi 6 does not respond to the command “esxcfg-volume -l” and it shows me nothing, so I went to Solution 2!
Before I go into the solution, why it works in two ESXi versions but one still has the problem, it is because I created the datastore version 6 which is not supported by ESXi 6! That was my mistake! I just removed (deleted) it and I created a new datastore in ESXi 6 which has a problem with “esxcfg-volume -l” command. Since VMFS 5 is supported by ESXi 5 and later, the issue is gone!