<?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: Problem with LUN in MSA Storage</title>
    <link>https://community.hpe.com/t5/msa-storage/problem-with-lun/m-p/775983#M3045</link>
    <description>Sounds like the VMFS paths have changed and the system somehow beleives the original data is a snapshot or clone. Do you have new "vmhba" names or did you present the virtual disk on a different LUN address?&lt;BR /&gt;&lt;BR /&gt;It sounds like you need to write a new VMFS signature to fix this problem. Please check "VMFS Volume Resignaturing" starting on page 112:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.vmware.com/pdf/vi3_esx_san_cfg.pdf" target="_blank" rel="nofollow"&gt;http://www.vmware.com/pdf/vi3_esx_san_cfg.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;read EVERYTHING up and including page 115.</description>
    <pubDate>Wed, 11 Apr 2007 11:40:35 GMT</pubDate>
    <dc:creator>Uwe Zessin</dc:creator>
    <dc:date>2007-04-11T11:40:35Z</dc:date>
    <item>
      <title>Problem with LUN</title>
      <link>https://community.hpe.com/t5/msa-storage/problem-with-lun/m-p/775982#M3044</link>
      <description>Hello, I have a server blade 25p with Vmware, this server this connected EVA 4000,  the server him damage the fiber channel card, reason why when putting to him the new fiber card we must present/display lun again to him, but when presenting/displaying to him the LUN to the server requests to give format to me to the LUN, but we cannot format it because it has information, exists some form to present/display lun without giving format?</description>
      <pubDate>Wed, 11 Apr 2007 10:57:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/problem-with-lun/m-p/775982#M3044</guid>
      <dc:creator>Ignacio Renteria Franco</dc:creator>
      <dc:date>2007-04-11T10:57:47Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with LUN</title>
      <link>https://community.hpe.com/t5/msa-storage/problem-with-lun/m-p/775983#M3045</link>
      <description>Sounds like the VMFS paths have changed and the system somehow beleives the original data is a snapshot or clone. Do you have new "vmhba" names or did you present the virtual disk on a different LUN address?&lt;BR /&gt;&lt;BR /&gt;It sounds like you need to write a new VMFS signature to fix this problem. Please check "VMFS Volume Resignaturing" starting on page 112:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.vmware.com/pdf/vi3_esx_san_cfg.pdf" target="_blank" rel="nofollow"&gt;http://www.vmware.com/pdf/vi3_esx_san_cfg.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;read EVERYTHING up and including page 115.</description>
      <pubDate>Wed, 11 Apr 2007 11:40:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/problem-with-lun/m-p/775983#M3045</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2007-04-11T11:40:35Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with LUN</title>
      <link>https://community.hpe.com/t5/msa-storage/problem-with-lun/m-p/775984#M3046</link>
      <description>thanks, already I did it but it has not worked, some other idea?</description>
      <pubDate>Wed, 11 Apr 2007 16:50:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/problem-with-lun/m-p/775984#M3046</guid>
      <dc:creator>Ignacio Renteria Franco</dc:creator>
      <dc:date>2007-04-11T16:50:08Z</dc:date>
    </item>
  </channel>
</rss>

