<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ESXi 6.5U1 5969303 - Can't mount iSCSI VMFS 6 volume in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231532#M216999</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have 400GB VMFS6 volume hosted on FreeNAS 9.3 and connected via iSCSI. The device and partition are visible if I inspect via the ESXi Web UI on the host. I've tried UI, vim-cmd, and esxcli methods to rescan HBAs, refresh devices, etc. and the volume will NOT mount. The same volume mounts correctly on build 5310538.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the old vSphere Client, I would select Add Storage, Keep Existing Signature, etc. to mount the missing volume. As of the 27 July 2017 update, this is no longer possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How do I mount an existing VMFS6 volume via the Web UI (can't find any feature), or via the command line?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The annoying thing is that I have multiple volumes, and some mounted automatically, and some didn't.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(Side rant: Who's idea was it to force users into a substandard experience via the Web UI? It's incomplete, buggy, crash prone, F-grade, poorly tested, bloatware, unworthy of "release" status, etc.&amp;nbsp; Whoever at VMware is responsible for these decisions should be FIRED).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 28 Jul 2017 18:52:15 GMT</pubDate>
    <dc:creator>grantph</dc:creator>
    <dc:date>2017-07-28T18:52:15Z</dc:date>
    <item>
      <title>ESXi 6.5U1 5969303 - Can't mount iSCSI VMFS 6 volume</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231532#M216999</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have 400GB VMFS6 volume hosted on FreeNAS 9.3 and connected via iSCSI. The device and partition are visible if I inspect via the ESXi Web UI on the host. I've tried UI, vim-cmd, and esxcli methods to rescan HBAs, refresh devices, etc. and the volume will NOT mount. The same volume mounts correctly on build 5310538.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the old vSphere Client, I would select Add Storage, Keep Existing Signature, etc. to mount the missing volume. As of the 27 July 2017 update, this is no longer possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How do I mount an existing VMFS6 volume via the Web UI (can't find any feature), or via the command line?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The annoying thing is that I have multiple volumes, and some mounted automatically, and some didn't.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(Side rant: Who's idea was it to force users into a substandard experience via the Web UI? It's incomplete, buggy, crash prone, F-grade, poorly tested, bloatware, unworthy of "release" status, etc.&amp;nbsp; Whoever at VMware is responsible for these decisions should be FIRED).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Jul 2017 18:52:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231532#M216999</guid>
      <dc:creator>grantph</dc:creator>
      <dc:date>2017-07-28T18:52:15Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 6.5U1 5969303 - Can't mount iSCSI VMFS 6 volume</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231533#M217000</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On closer inspection it appears that ESXi 6.5U1 is NOT reading partitions properly. Below, I've dumped the partitions via UI and esxcli. The UI shows the partition as &amp;lt;blank&amp;gt; AND the diagram as being correct - bizarre. There's something &lt;STRONG&gt;SERIOUSLY WRONG&lt;/STRONG&gt; with this update. esxcli shows the same partition tables on both builds, and the volume continues to work correctly on the '538 build.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's the output on both builds of ESXi 6.5 ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ON BUILD 5969303 HOST&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Web UI&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FreeNAS iSCSI Disk (naa.6589cfc000000bcff79a34187f94af3a)&lt;/P&gt;&lt;P&gt;Type: Disk&lt;/P&gt;&lt;P&gt;Model: iSCSI Disk&lt;/P&gt;&lt;P&gt;Path: /vmfs/devices/disks/naa.6589cfc000000bcff79a34187f94af3a&lt;/P&gt;&lt;P&gt;Capacity: 400 GB&lt;/P&gt;&lt;P&gt;Partition Format: gpt&lt;/P&gt;&lt;P&gt;UUID: 010003000030303063323961373930363631360000695343534920&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Partitions&lt;/P&gt;&lt;P&gt;&amp;lt;blank&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Partition diagram&lt;/P&gt;&lt;P&gt;1. VMFS (400 GB)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;esxcli storage core device partition list&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;naa.6589cfc000000bcff79a34187f94af3a 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; 838860800&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; 429496729600&lt;/P&gt;&lt;P&gt;naa.6589cfc000000bcff79a34187f94af3a 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 128&amp;nbsp;&amp;nbsp; 838860767&amp;nbsp;&amp;nbsp;&amp;nbsp; fb&amp;nbsp;&amp;nbsp; 429496647168&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ON BUILD 5310538 HOST&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Web UI&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Type: Disk&lt;/P&gt;&lt;P&gt;Model: iSCSI Disk&lt;/P&gt;&lt;P&gt;Path: /vmfs/devices/disks/naa.6589cfc000000bcff79a34187f94af3a&lt;/P&gt;&lt;P&gt;Capacity: 400 GB&lt;/P&gt;&lt;P&gt;Partition Format: gpt&lt;/P&gt;&lt;P&gt;UUID: 010003000030303063323961373930363631360000695343534920&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Partitions&lt;/P&gt;&lt;P&gt;1: VMFS&lt;/P&gt;&lt;P&gt;Type VMFS&lt;/P&gt;&lt;P&gt;Start block 0&lt;/P&gt;&lt;P&gt;End block 409599&lt;/P&gt;&lt;P&gt;Block size 1 MB&lt;/P&gt;&lt;P&gt;Size 400 GB (409599 blocks)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Partition diagram&lt;/P&gt;&lt;P&gt;1. VMFS (400 GB)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;esxcli storage core device partition list&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;naa.6589cfc000000bcff79a34187f94af3a 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; 838860800&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; 429496729600&lt;/P&gt;&lt;P&gt;naa.6589cfc000000bcff79a34187f94af3a 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 128&amp;nbsp;&amp;nbsp; 838860767&amp;nbsp;&amp;nbsp;&amp;nbsp; fb&amp;nbsp;&amp;nbsp; 429496647168&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Jul 2017 19:32:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231533#M217000</guid>
      <dc:creator>grantph</dc:creator>
      <dc:date>2017-07-28T19:32:46Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 6.5U1 5969303 - Can't mount iSCSI VMFS 6 volume</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231534#M217001</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Wow - that really looks weired.&lt;BR /&gt;Can you please post the result of&lt;/P&gt;&lt;P&gt;partedUtil getptbl /dev/disks/naa.6589cfc000000bcff79a34187f94af3a&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Jul 2017 23:56:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231534#M217001</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2017-07-28T23:56:59Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 6.5U1 5969303 - Can't mount iSCSI VMFS 6 volume</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231535#M217002</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry - but I ended up rolling back to &lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;5310538 for now - which works perfectly fine with the same drives (yay!). Don't really have time to mess with this kind of fault. I can run partedUtil on that build - if you think it's of any value.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 29 Jul 2017 01:25:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231535#M217002</guid>
      <dc:creator>grantph</dc:creator>
      <dc:date>2017-07-29T01:25:19Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 6.5U1 5969303 - Can't mount iSCSI VMFS 6 volume</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231536#M217003</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Okay - you got my curiosity - here is partedUtil on &lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;5310538:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;gpt&lt;/P&gt;&lt;P&gt;52216 255 63 838860800&lt;/P&gt;&lt;P&gt;1 128 838860766 AA31E02A400F11DB9590000C2911D1B8 vmfs 0&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 29 Jul 2017 01:27:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231536#M217003</guid>
      <dc:creator>grantph</dc:creator>
      <dc:date>2017-07-29T01:27:37Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 6.5U1 5969303 - Can't mount iSCSI VMFS 6 volume</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231537#M217004</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Interesting - I assumed that this problem had been fixed already.&lt;BR /&gt;The VMFS-partition you have is not properly alligned and will not perform well.&lt;BR /&gt;See &lt;A href="https://communities.vmware.com/thread/558386"&gt;Why does ESXi 6.5 GUI creates VMFS-volumes that are not alligned to 1MB blocks ?&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 29 Jul 2017 02:19:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231537#M217004</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2017-07-29T02:19:55Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 6.5U1 5969303 - Can't mount iSCSI VMFS 6 volume</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231538#M217005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I suspect you're right - and misaligned partitions are not being read properly by the latest version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll need to perform further tests to confirm. Could be a while before I get back to this. Thanks for the insight!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 29 Jul 2017 08:10:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231538#M217005</guid>
      <dc:creator>grantph</dc:creator>
      <dc:date>2017-07-29T08:10:18Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 6.5U1 5969303 - Can't mount iSCSI VMFS 6 volume</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231539#M217006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Recommendation: &lt;/STRONG&gt;Check for 1MB partition misalignment &lt;EM&gt;&lt;STRONG&gt;BEFORE&lt;/STRONG&gt; &lt;/EM&gt;upgrading to 5969303&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can confirm that we used earlier builds of 6.5 that incorrectly created partitions on 128K boundaries, instead of 1M. Unfortunately for us, that means 39 volumes that are incorrectly aligned - &lt;EM&gt;not happy&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A quick way to identify suspect alignment is with the following quick &amp;amp; nasty command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;EM&gt;esxcli storage core device partition list | grep "128"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We won't be upgrading to 5969303 until all our alignment issues are resolved.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 29 Jul 2017 16:34:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231539#M217006</guid>
      <dc:creator>grantph</dc:creator>
      <dc:date>2017-07-29T16:34:26Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 6.5U1 5969303 - Can't mount iSCSI VMFS 6 volume</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231540#M217007</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Some quick notes:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The partition alignment has been fixed with Fling v1.17 of the Host Client (Build 5310538 contains v1.19).&lt;/LI&gt;&lt;LI&gt;The latest version (I tested with the Fling version v1.21) indeed seems to have a bug with displaying the partitions in the GUI. However, to me it seems to be a display issue only.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;@ &lt;B&gt;grantph&lt;/B&gt;​&lt;/P&gt;&lt;P&gt;Are the datastores - which were mounted - aligned to 2048 blocks (1MB), and the ones which didn't show up to 128 blocks, i.e. was it related to the alignment?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;André&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Jul 2017 09:57:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231540#M217007</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2017-07-31T09:57:37Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 6.5U1 5969303 - Can't mount iSCSI VMFS 6 volume</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231541#M217008</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had already rolled back to '538 before I was aware of the buggy alignment issue. So, I can't confirm if it was the 128 blocks preventing mounting. However, I do know that the problem we experienced was both UI AND command line - the &lt;EM&gt;missing&lt;/EM&gt; volumes would NOT mount - and in my original post I was looking for guidance on different methods to mount via command line.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I &lt;EM&gt;suspect&lt;/EM&gt; that the volumes were 128, but I wasn't looking for that at the time. A working environment is far more important to us than identifying bugs/causes for VMware.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Until we fix the alignment problems created by the earlier buggy builds, we &lt;STRONG&gt;won't&lt;/STRONG&gt; be trying '303 again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Jul 2017 16:05:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231541#M217008</guid>
      <dc:creator>grantph</dc:creator>
      <dc:date>2017-07-31T16:05:46Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 6.5U1 5969303 - Can't mount iSCSI VMFS 6 volume</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231542#M217009</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In case it helps anyone else, I wanted to resurrect this old thread with a me too and some additional information.&amp;nbsp; In my case, I was working with a copy of 5969303 as a fresh install that doesn't have internet connectivity yet, nor is it hooked to vcenter yet.&amp;nbsp; I wanted to test that some iSCSI LUN snapshots were replicating successfully from one data center to another, so all I wanted to do was boot this copy of 6.5 5969303, mount the snapshot LUN on the local array, boot a VM.&amp;nbsp; No matter what I did in the GUI, or CLI, I could not mount the iSCSI LUN.&amp;nbsp; It would show as a storage device in the web interface, but I could not do anything with it, and the actions only allow me to add a new vmfs datastore which would partition and format it.&amp;nbsp; The GUI did reflect the correct partition size.&amp;nbsp; esxcfg-volume -l showed nothing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I got some internet for this host and updated to 7388607.&amp;nbsp; Reboot.&amp;nbsp; esxcfg-volume -l and now it shows as available; used -M and successfully mounted.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Perhaps there's some VMFS versioning issue that affects certain builds?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jan 2018 21:32:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-5U1-5969303-Can-t-mount-iSCSI-VMFS-6-volume/m-p/2231542#M217009</guid>
      <dc:creator>hostasaurus</dc:creator>
      <dc:date>2018-01-24T21:32:58Z</dc:date>
    </item>
  </channel>
</rss>

