<?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 Re: iSCSI Extent missing in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/iSCSI-Extent-missing/m-p/1297161#M116540</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The problem that you see is that the new LUN is not the same as the old LUN.&amp;nbsp; It will have a different signature, actual vs what's on the disk itself, so the LUN will not match what ESX is expeting, which is why the extent is not added back to the host itself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If there is data you need to recover, you'll need to open an SR with vmware to see if they can get data off the LUN.&amp;nbsp; You may be able to open that VMFS with a 3rd party tool that can ready vmfs, but if the LUN's don't match exactly, you won't be able to recover the "hole" in your existing datastore.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KjB&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 09 Apr 2012 14:18:44 GMT</pubDate>
    <dc:creator>kjb007</dc:creator>
    <dc:date>2012-04-09T14:18:44Z</dc:date>
    <item>
      <title>iSCSI Extent missing</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/iSCSI-Extent-missing/m-p/1297158#M116537</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I currently have 1 datastore which consists of a raid 1 in the server itself and a raid 1 on a NAS device which is provides storage trough iSCSI.&lt;/P&gt;&lt;P&gt;Today the NAS died, so I got another NAS and placed the iSCSI files on there. On the NAS everything seems Ok, configuration is exactly as the NAS that died.&lt;/P&gt;&lt;P&gt;The iscsi volume shows correctly in storage adapters but does not show up under extents.&lt;/P&gt;&lt;P&gt;The goal is to be able to copy the VM to another iscsi LUN with no extents, any idea's on how this could be acomplished are greatly appriciated!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Apr 2012 04:00:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/iSCSI-Extent-missing/m-p/1297158#M116537</guid>
      <dc:creator>moppentappers</dc:creator>
      <dc:date>2012-04-09T04:00:05Z</dc:date>
    </item>
    <item>
      <title>Re: iSCSI Extent missing</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/iSCSI-Extent-missing/m-p/1297159#M116538</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE&gt;The iscsi volume shows correctly in storage adapters but does not show up under extents&lt;/BLOCKQUOTE&gt;&lt;P&gt;Can you please explain this? What do you mean by "does not show up under extents". Do you just mean it does not show up as a datastore under "Storage" or did you configure a datastore with multiple extents on the storage system?&lt;/P&gt;&lt;P&gt;In case you just don't see the datastore, you may check whether it is detected as a snaphot. see e.g. &lt;SPAN style="font-family: Arial;"&gt;&lt;A href="http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;amp;externalId=1011387" target="_blank"&gt;vSphere handling of LUNs detected as snapshot (1011387)&lt;/A&gt;&lt;/SPAN&gt;&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, 09 Apr 2012 10:52:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/iSCSI-Extent-missing/m-p/1297159#M116538</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2012-04-09T10:52:45Z</dc:date>
    </item>
    <item>
      <title>Re: iSCSI Extent missing</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/iSCSI-Extent-missing/m-p/1297160#M116539</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The selected LUN in storage adapters.png is the LUN contains the data that was transferred from the faulty NAS device.&lt;/P&gt;&lt;P&gt;As you can see in datastore.png, this LUN is absent.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I try to use add storage according to the guide you provided ISCSI, I get the screen shown in add storage.&lt;/P&gt;&lt;P&gt;To me it seems that the lun is not considered as an existing ISCSI lun.&lt;/P&gt;&lt;P&gt;Select disk-lun shows that no VMFS label is present.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Apr 2012 14:02:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/iSCSI-Extent-missing/m-p/1297160#M116539</guid>
      <dc:creator>moppentappers</dc:creator>
      <dc:date>2012-04-09T14:02:03Z</dc:date>
    </item>
    <item>
      <title>Re: iSCSI Extent missing</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/iSCSI-Extent-missing/m-p/1297161#M116540</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The problem that you see is that the new LUN is not the same as the old LUN.&amp;nbsp; It will have a different signature, actual vs what's on the disk itself, so the LUN will not match what ESX is expeting, which is why the extent is not added back to the host itself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If there is data you need to recover, you'll need to open an SR with vmware to see if they can get data off the LUN.&amp;nbsp; You may be able to open that VMFS with a 3rd party tool that can ready vmfs, but if the LUN's don't match exactly, you won't be able to recover the "hole" in your existing datastore.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KjB&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Apr 2012 14:18:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/iSCSI-Extent-missing/m-p/1297161#M116540</guid>
      <dc:creator>kjb007</dc:creator>
      <dc:date>2012-04-09T14:18:44Z</dc:date>
    </item>
  </channel>
</rss>

