<?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: Merging VMDK failure: vmware-vdiskmanager quits with error 0x3e80 in VMware Workstation Pro Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830161#M108779</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks André.&lt;/P&gt;&lt;P&gt;We _could_ patch that... or we could just implement pvscsi in Workstation&amp;nbsp;&amp;nbsp; ‍&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@A060E4B8E9B50EA999911CFF4E572714/emoticons/2642.png" alt=":male_sign:" title=":male_sign:" /&gt;&lt;/P&gt;&lt;P&gt;I guess both would require a patch... Consider it noted &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@BDE1C7A967AC45D8A4A4C2AFE83F7C64/emoticons/1f603.png" alt=":grinning_face_with_big_eyes:" title=":grinning_face_with_big_eyes:" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 17 Jun 2019 21:11:18 GMT</pubDate>
    <dc:creator>Mikero</dc:creator>
    <dc:date>2019-06-17T21:11:18Z</dc:date>
    <item>
      <title>Merging VMDK failure: vmware-vdiskmanager quits with error 0x3e80</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830155#M108773</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On WS 15.1.0 host=Windows 10 guest=Windows 10, attempting to merge split vmdk files &lt;SPAN style="font-family: courier new,courier;"&gt;w10.vmdk, w10-s001.vmdk ... w10-s011.vmdk&lt;/SPAN&gt; with this command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;vmware-vdiskmanager.exe -r w10.vmdk -t 0 w10-new.vmdk&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It fails with this message&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Failed to convert disk:&amp;nbsp; One of the parameters supplied is invalid (0x3e80).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The vm files are all normal.&amp;nbsp; For example, &lt;SPAN style="font-family: courier new,courier;"&gt;vmware-vdiskmanager.exe -k w10.vmdk&lt;/SPAN&gt;&amp;nbsp; or&amp;nbsp; &lt;SPAN style="font-family: courier new,courier;"&gt;vmware-vdiskmanager.exe -d w10.vmdk&lt;/SPAN&gt;&amp;nbsp; executes without error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What am I doing wrong?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 15 Jun 2019 15:03:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830155#M108773</guid>
      <dc:creator>htoh</dc:creator>
      <dc:date>2019-06-15T15:03:37Z</dc:date>
    </item>
    <item>
      <title>Re: Merging VMDK failure: vmware-vdiskmanager quits with error 0x3e80</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830156#M108774</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you have a good reason to create a monolithic virtual disk? I'ts basically up to you to do so, but IMO staying with split files have several benefits (less disk space needed for compacting, can easily be increased, ...).&lt;/P&gt;&lt;P&gt;Anyway, please &lt;SPAN style="text-decoration: underline;"&gt;attach&lt;/SPAN&gt; the &lt;SPAN style="font-family: courier new,courier;"&gt;w10.vmdk&lt;/SPAN&gt; descriptor file to a reply post to see how it looks like.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;André&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 15 Jun 2019 15:12:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830156#M108774</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2019-06-15T15:12:46Z</dc:date>
    </item>
    <item>
      <title>Re: Merging VMDK failure: vmware-vdiskmanager quits with error 0x3e80</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830157#M108775</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for having a look at the descriptor file&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(some identifiers have been randomized)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 15 Jun 2019 15:59:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830157#M108775</guid>
      <dc:creator>htoh</dc:creator>
      <dc:date>2019-06-15T15:59:59Z</dc:date>
    </item>
    <item>
      <title>Re: Merging VMDK failure: vmware-vdiskmanager quits with error 0x3e80</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830158#M108776</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't use version 15.x myself, so this is more of a guess.&lt;/P&gt;&lt;P&gt;What I think is that the adapterType "pvscsi" may cause the issue. Does "pvscsi" show up as valid adapter type (option &lt;EM&gt;-a&lt;/EM&gt;) when you run &lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;EM&gt;vmware-vdiskmanager -h&lt;/EM&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;What may be worth a try, is to backup &lt;EM&gt;w10.vmdk,&lt;/EM&gt; then change the adapterType to "lsilogic", and run the conversion with the modified header file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume that you have sufficient free disk space to clone (that's what the conversion actually does) the virtual disk.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;André&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 15 Jun 2019 19:04:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830158#M108776</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2019-06-15T19:04:00Z</dc:date>
    </item>
    <item>
      <title>Re: Merging VMDK failure: vmware-vdiskmanager quits with error 0x3e80</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830159#M108777</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Incredible, it worked, like black magic!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just had to change:&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;ddb.adapterType = "pvscsi"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;to&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;ddb.adapterType = "lsilogic"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why or how this works is a mystery. Now, I must change pvscsi to lsilogic, merge, then change it back.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 15 Jun 2019 19:18:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830159#M108777</guid>
      <dc:creator>htoh</dc:creator>
      <dc:date>2019-06-15T19:18:39Z</dc:date>
    </item>
    <item>
      <title>Re: Merging VMDK failure: vmware-vdiskmanager quits with error 0x3e80</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830160#M108778</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Glad that works. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That's probably something that &lt;B&gt;Mikero&lt;/B&gt;​ may consider to put on the ToDo/ToFix list for an upcoming patch.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;André&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 15 Jun 2019 19:30:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830160#M108778</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2019-06-15T19:30:04Z</dc:date>
    </item>
    <item>
      <title>Re: Merging VMDK failure: vmware-vdiskmanager quits with error 0x3e80</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830161#M108779</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks André.&lt;/P&gt;&lt;P&gt;We _could_ patch that... or we could just implement pvscsi in Workstation&amp;nbsp;&amp;nbsp; ‍&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@A060E4B8E9B50EA999911CFF4E572714/emoticons/2642.png" alt=":male_sign:" title=":male_sign:" /&gt;&lt;/P&gt;&lt;P&gt;I guess both would require a patch... Consider it noted &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@BDE1C7A967AC45D8A4A4C2AFE83F7C64/emoticons/1f603.png" alt=":grinning_face_with_big_eyes:" title=":grinning_face_with_big_eyes:" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Jun 2019 21:11:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830161#M108779</guid>
      <dc:creator>Mikero</dc:creator>
      <dc:date>2019-06-17T21:11:18Z</dc:date>
    </item>
  </channel>
</rss>

