<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>VMDK on Nico Maas</title>
        <link>https://www.nico-maas.de/tags/vmdk/</link>
        <description>Recent content in VMDK on Nico Maas</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Fri, 29 Jun 2018 08:00:54 +0000</lastBuildDate><atom:link href="https://www.nico-maas.de/tags/vmdk/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>Cannot start Virtual Machine on ESXi 6.5</title>
            <link>https://www.nico-maas.de/posts/2018-06-29-cannot-start-virtual-machine-on-esxi-6-5/</link>
            <pubDate>Fri, 29 Jun 2018 08:00:54 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2018-06-29-cannot-start-virtual-machine-on-esxi-6-5/</guid>
            <description>&lt;p&gt;As described by JC-LAN, I had a lot of trouble with one particular &amp;ldquo;special&amp;rdquo; VMDK on a ESXi 6.5 system, which did not start after a reboot of the ESXi host.&lt;/p&gt;&#xA;&lt;p&gt;The power-on failed with &amp;ldquo;File system specific implementation of LookupAndOpen[&amp;hellip;] failed&amp;rdquo; - however in the end it just gave me the overall error that it failed to start the machine. As it turned out, the VMDK was corrupted.&lt;/p&gt;&#xA;&lt;p&gt;1.) Enable SSH on the ESXi host with the corrupted VMDK - and login&lt;/p&gt;</description>
        </item></channel>
</rss>
