<?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: My vm wont boot after changing the folder of its snapshop vmdk file in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907835#M281436</link>
    <description>&lt;P&gt;Virtual disk consist of two .vmdk files, a descriptor file, and a data file (as you just found out).&amp;nbsp; &lt;BR /&gt;Moving snapshot files will break the VM. In your case what happened is that due to the file lock on the data (sesparse) file, only the descriptor file got moved.&lt;BR /&gt;Unless moving the descriptor file back to the VM's folder fixes the issue, it may be necessary to manually do some manual modifications to recover from the issue.&lt;/P&gt;
&lt;P&gt;André&lt;/P&gt;</description>
    <pubDate>Sat, 07 May 2022 17:06:36 GMT</pubDate>
    <dc:creator>a_p_</dc:creator>
    <dc:date>2022-05-07T17:06:36Z</dc:date>
    <item>
      <title>My vm wont boot after changing the folder of its snapshop vmdk file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907809#M281435</link>
      <description>&lt;P&gt;HI there&lt;/P&gt;&lt;P&gt;I was runing my vm on&amp;nbsp; esxi6.7 platform and i had create a snapshop yestoday(so since them the vm is runing on the latest snapshot vmdk files)&lt;/P&gt;&lt;P&gt;and then i decide to move the my snapshot vmdk while the vm is running. after I've done this, I found the orginal snapshot vmdk file has changed from &lt;FONT color="#FF0000"&gt;vm1-000006.vmdk&lt;/FONT&gt; to &lt;FONT color="#0000FF"&gt;vm1-000006-sesparse.vmdk&lt;/FONT&gt;(&lt;FONT color="#FF9900"&gt;the size does not changed&lt;/FONT&gt;),with&amp;nbsp; a very small file (I belive is 400KB)located in the destination folder,same name as the&amp;nbsp;vm1-000006.vmdk file。i dont know what went wrong so I shutdown the vm and delete that 400KB file，then I try to boot my vm but it won't boot now.&lt;/P&gt;&lt;P&gt;any idear &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@F9D63535BA15A9D2A403526FF68D2E90/emoticons/1f628.png" alt=":fearful_face:" title=":fearful_face:" /&gt;?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 07 May 2022 11:33:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907809#M281435</guid>
      <dc:creator>QAQKent</dc:creator>
      <dc:date>2022-05-07T11:33:29Z</dc:date>
    </item>
    <item>
      <title>Re: My vm wont boot after changing the folder of its snapshop vmdk file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907835#M281436</link>
      <description>&lt;P&gt;Virtual disk consist of two .vmdk files, a descriptor file, and a data file (as you just found out).&amp;nbsp; &lt;BR /&gt;Moving snapshot files will break the VM. In your case what happened is that due to the file lock on the data (sesparse) file, only the descriptor file got moved.&lt;BR /&gt;Unless moving the descriptor file back to the VM's folder fixes the issue, it may be necessary to manually do some manual modifications to recover from the issue.&lt;/P&gt;
&lt;P&gt;André&lt;/P&gt;</description>
      <pubDate>Sat, 07 May 2022 17:06:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907835#M281436</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2022-05-07T17:06:36Z</dc:date>
    </item>
    <item>
      <title>Re: My vm wont boot after changing the folder of its snapshop vmdk file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907837#M281437</link>
      <description>&lt;P&gt;.. sorry, I missed the part that you deleted the descriptor file.&lt;/P&gt;
&lt;P&gt;In this case, enable SSH on the ESXi host, and use e.g. &lt;EM&gt;WinSCP&lt;/EM&gt; to connect to it. Then go the the VM's folder (e.g. "vmfs/volumes/&amp;lt;dataastore-name&amp;gt;/&amp;lt;vm-name&amp;gt;"). From there download all the small &lt;EM&gt;.vmdk&lt;/EM&gt; descriptor files that still exist, compress/zip them, and attach the &lt;EM&gt;.zip&lt;/EM&gt; archive to your next reply.&lt;/P&gt;
&lt;P&gt;André&lt;/P&gt;</description>
      <pubDate>Sat, 07 May 2022 17:12:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907837#M281437</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2022-05-07T17:12:14Z</dc:date>
    </item>
    <item>
      <title>Re: My vm wont boot after changing the folder of its snapshop vmdk file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907844#M281438</link>
      <description>&lt;P&gt;&amp;gt; i dont know what went wrong so I shutdown the vm and delete that 400KB file，then I try to boot my vm but it won't boot now.&lt;BR /&gt;&lt;BR /&gt;Strange strategy - if something fails you should rather NOT delete any file that you dont know the purpose of.&lt;BR /&gt;Next time first read the vmware.log - it would have explained what is wrong ...&lt;/P&gt;&lt;P&gt;Ulli&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 07 May 2022 19:01:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907844#M281438</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2022-05-07T19:01:17Z</dc:date>
    </item>
    <item>
      <title>Re: My vm wont boot after changing the folder of its snapshop vmdk file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907923#M281445</link>
      <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="QAQKent_0-1652062419932.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/95167i75C2DF34FEEA80F3/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="QAQKent_0-1652062419932.png" alt="QAQKent_0-1652062419932.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Thanks for the help!&lt;/P&gt;&lt;P&gt;I followed your instructions and as we can see from the ssh tool the descriptor file from 000001 to 000007 is deleted，I've download all the other remain descriptpor files and upload them down here，hope this would help us solve the problem.&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 02:18:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907923#M281445</guid>
      <dc:creator>QAQKent</dc:creator>
      <dc:date>2022-05-09T02:18:41Z</dc:date>
    </item>
    <item>
      <title>Re: My vm wont boot after changing the folder of its snapshop vmdk file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907924#M281446</link>
      <description>&lt;P&gt;That's very correct&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Hopefully&amp;nbsp; I could I fix the problem this time.&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 02:24:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907924#M281446</guid>
      <dc:creator>QAQKent</dc:creator>
      <dc:date>2022-05-09T02:24:21Z</dc:date>
    </item>
    <item>
      <title>Re: My vm wont boot after changing the folder of its snapshop vmdk file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907927#M281447</link>
      <description>&lt;P&gt;Thanks for the help&lt;/P&gt;&lt;P&gt;I've attached the descriptor files here.&lt;/P&gt;&lt;P&gt;And I've checked the Instruction here &lt;FONT color="#0000FF"&gt;&lt;A href="https://kb.vmware.com/s/article/1002511?lang=en_us" target="_blank" rel="noopener"&gt;https://kb.vmware.com/s/article/1002511?lang=en_us&lt;/A&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;From the webGUI here is the storage information of this vm&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="QAQKent_0-1652064457006.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/95168iAB688DB8614D98B0/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="QAQKent_0-1652064457006.png" alt="QAQKent_0-1652064457006.png" /&gt;&lt;/span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="QAQKent_1-1652064598168.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/95169i4EB64788385F185F/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="QAQKent_1-1652064598168.png" alt="QAQKent_1-1652064598168.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found the vm was running on two vmdk files :&lt;FONT color="#0000FF"&gt;LIVECLOUD_1_1-000006.vmdk (which&amp;nbsp; is missing!）and&amp;nbsp;LIVECLOUD_1-000024.vmdk (which is existed )&amp;nbsp;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;so I guess we just need to fix the file&amp;nbsp; for&amp;nbsp;&lt;FONT color="#0000FF"&gt;LIVECLOUD_1_1-000006.vmdk&amp;nbsp;&lt;FONT color="#000000"&gt;but I do not see its sesparse or decriptor file!&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;FONT color="#0000FF"&gt;&lt;FONT color="#000000"&gt;Then I noticed that the Size of these two vmdks&amp;nbsp; from the web GUI does not show correctly&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;FONT color="#0000FF"&gt;&lt;FONT color="#000000"&gt;Then I&amp;nbsp; typed in the following command&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;FONT color="#0000FF"&gt;&lt;FONT color="#000000"&gt;# ls -ltr to check the size&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT color="#000000"&gt;&lt;FONT color="#0000FF"&gt;&lt;FONT color="#000000"&gt;&lt;BR /&gt;and I get these result&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;FONT color="#0000FF"&gt;&lt;FONT color="#000000"&gt;-rw------- 1 root root &lt;FONT color="#FF0000"&gt;2989527040&lt;/FONT&gt; May 7 15:46 LIVECLOUD_1-000024-sesparse.vmdk&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;I think I did not delete any vmdk files after I found I get into troble,but the &lt;FONT color="#000000"&gt;LIVECLOUD_1_1-000006.vmdk is just missing.&amp;nbsp;&lt;/FONT&gt;Not sure what I can do next...&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@1C6E75E7C785988F2EA295D9769CEF91/emoticons/1f625.png" alt=":sad_but_relieved_face:" title=":sad_but_relieved_face:" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 04:29:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907927#M281447</guid>
      <dc:creator>QAQKent</dc:creator>
      <dc:date>2022-05-09T04:29:27Z</dc:date>
    </item>
    <item>
      <title>Re: My vm wont boot after changing the folder of its snapshop vmdk file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907942#M281449</link>
      <description>&lt;P&gt;I‘m pretty sure&amp;nbsp; the 000006_1_1.vmdk file (both sesparse and descritor file) was missing after the crash .I can find out in the vmkernel log(which i will attach down there.&lt;/P&gt;&lt;P&gt;So I'd like to show a whole picture of whats going on now.&lt;/P&gt;&lt;P&gt;The VM is hosted for a NAS use, a centos7.6 system with a Nextcloud NAS apps on it. In case something goes wrong, I create a new virtual DIsk to store my NAS files(I believe its 500GB), and another virtual disk runs the actual OS (40GB I believe) , incase I need expand my NAS space,I create another VG for the NAS virtual Disk.&lt;/P&gt;&lt;P&gt;On 2022/5/6 nghit(UTC+8), before&amp;nbsp; I'm off my work, I toke a snapshot for the VM (around 22:09 UTC8 and&amp;nbsp; the VM was still running) ,then I left the company&lt;/P&gt;&lt;P&gt;On 2022/5/7(UTC+8) moning around 10:00 am, I login to the ESXI web surface，and I get a message says "&lt;SPAN&gt;This virtual machine needs to have its disks consolidated. You should consolidate disks to improve performance and optimize disk utilization."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;So I started a disk utlization but the I get a failure message said "no&amp;nbsp; enough space for disk utilization".&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Then I decided to free some space for the datastore. I have two datastore, datastore1 and datastore2. the vm is running on datastore1.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;What I did is I try to move the vm-000000X.vmdk files to datastore2 (while the vm is still up and running )since I do not know if they are just some useless old snapshop files or not. But due to the file lock, what I moved is just the descriptor files( which I did not aware about and deleted)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Then I&amp;nbsp; click the reboot button of the vm and found the vm wont boot anymore.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;During the time of finding solutions, I tried&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1.click scroll back&amp;nbsp; to the snapshot I created last time --not able to scrollback &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2.unregister the vm and re-register&amp;nbsp; ---not able to boot or change the setting of the vm&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;3. create a temp.vmdk with same size of the vm-1_000006-sesparse.vmdk and rename the descriptor file to match that vm-1_000006-sesparse.vmdk---still wont boot, and seems like the vm is using&amp;nbsp;vm-1_1_000006.vmdk not&amp;nbsp;vm-1_000006.vmdk.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;4. check the remaining files of the vm: ssh to its dir and use ls -l command&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;and I got following result&lt;BR /&gt;total 1076104448&lt;BR /&gt;-rw-r--r-- 1 root root 53 Aug 31 2021 LIVECLOUD-a4ffb0ed.hlog&lt;BR /&gt;-rw------- 1 root root 8684 Dec 10 09:15 LIVECLOUD.nvram&lt;BR /&gt;-rw------- 1 root root 91211956224 May 7 10:12 LIVECLOUD_1-000001-sesparse.vmdk&lt;BR /&gt;-rw------- 1 root root 16310702080 May 7 09:02 LIVECLOUD_1-000002-sesparse.vmdk&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 6462459904 May 7 01:57 LIVECLOUD_1-000003-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 5489471488 May 7 01:57 LIVECLOUD_1-000004-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 10613239808 May 7 01:57 LIVECLOUD_1-000005-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw-------&lt;FONT color="#FF00FF"&gt; 1 root root 3937927168 May 7 01:57 LIVECLOUD_1-000006-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 460 May 9 03:37 LIVECLOUD_1-000006.vmdk&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 13089460224 May 7 01:57 LIVECLOUD_1-000007-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 2536579072 May 7 01:57 LIVECLOUD_1-000008-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 327 Jul 27 2021 LIVECLOUD_1-000008.vmdk&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 60904456192 May 7 01:57 LIVECLOUD_1-000009-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 327 Dec 10 08:35 LIVECLOUD_1-000009.vmdk&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 2848980992 May 7 01:57 LIVECLOUD_1-000010-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 327 Dec 10 04:49 LIVECLOUD_1-000010.vmdk&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 3301187584 May 7 01:57 LIVECLOUD_1-000011-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 327 Dec 9 09:23 LIVECLOUD_1-000011.vmdk&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 3176865792 May 7 01:57 LIVECLOUD_1-000012-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 327 Dec 9 09:23 LIVECLOUD_1-000012.vmdk&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 5472587776 May 7 01:57 LIVECLOUD_1-000013-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 327 Jul 28 2021 LIVECLOUD_1-000013.vmdk&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 24581804032 May 7 01:57 LIVECLOUD_1-000014-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 327 Sep 6 2021 LIVECLOUD_1-000014.vmdk&lt;BR /&gt;-rw-------&lt;FONT color="#FF00FF"&gt; 1 root root 206547492864 May 7 01:57 LIVECLOUD_1-000015-sesparse.vm&lt;/FONT&gt;dk&lt;BR /&gt;-rw------- 1 root root 327 Nov 24 02:58 LIVECLOUD_1-000015.vmdk&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 3814195200 May 7 01:57 LIVECLOUD_1-000016-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 327 Nov 25 03:47 LIVECLOUD_1-000016.vmdk&lt;BR /&gt;-rw------- 1 root root 294809133056 May 7 05:37 LIVECLOUD_1-000017-sesparse.vmdk&lt;BR /&gt;-rw------- 1 root root 327 Dec 3 05:27 LIVECLOUD_1-000017.vmdk&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 222418702336 May 7 01:57 LIVECLOUD_1-000018-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 327 Dec 10 05:43 LIVECLOUD_1-000018.vmdk&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 28023193600 May 7 01:57 LIVECLOUD_1-000019-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 327 Nov 25 06:29 LIVECLOUD_1-000019.vmdk&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 7279529984 May 7 01:57 LIVECLOUD_1-000020-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 327 Dec 6 05:38 LIVECLOUD_1-000020.vmdk&lt;BR /&gt;-rw-------&lt;FONT color="#FF00FF"&gt; 1 root root 2508328960 May 7 01:57 LIVECLOUD_1-000021-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 327 Dec 8 06:30 LIVECLOUD_1-000021.vmdk&lt;BR /&gt;-rw-------&lt;FONT color="#FF00FF"&gt; 1 root root 4466417664 May 7 01:57 LIVECLOUD_1-000022-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 327 Dec 7 06:29 LIVECLOUD_1-000022.vmdk&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 2436382720 May 7 01:57 LIVECLOUD_1-000023-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 327 Dec 21 02:54 LIVECLOUD_1-000023.vmdk&lt;BR /&gt;-rw------- 1 root root 2989527040 May 7 15:46 LIVECLOUD_1-000024-sesparse.vmdk&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 327 May 7 01:57 LIVECLOUD_1-000024.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- &lt;FONT color="#FF00FF"&gt;1 root root 30356422656 May 7 01:57 LIVECLOUD_1-000025-sesparse.vmdk&lt;/FONT&gt;&lt;BR /&gt;-rw------- 1 root root 327 May 6 14:09 LIVECLOUD_1-000025.vmdk&lt;BR /&gt;-rw------- 1 root root 8589934592 Dec 9 2020 LIVECLOUD_1-Snapshot1.vmem&lt;BR /&gt;-rw------- 1 root root 6012243 Dec 9 2020 LIVECLOUD_1-Snapshot1.vmsn&lt;BR /&gt;-rw------- 1 root root 8589934592 Jun 7 2021 LIVECLOUD_1-Snapshot2.vmem&lt;BR /&gt;-rw------- 1 root root 5805307 Jun 7 2021 LIVECLOUD_1-Snapshot2.vmsn&lt;BR /&gt;-rw------- 1 root root 21203 May 6 14:10 LIVECLOUD_1-Snapshot32.vmsn&lt;BR /&gt;-rw------- 1 root root 536870912000 Dec 9 2020 LIVECLOUD_1-flat.vmdk&lt;BR /&gt;-rw------- 1 root root 534 Nov 10 2020 LIVECLOUD_1.vmdk&lt;BR /&gt;-rw-r--r-- 1 root root 1237 May 7 11:11 LIVECLOUD_1.vmsd&lt;BR /&gt;-rwx------ 1 root root 4172 May 7 14:37 LIVECLOUD_1.vmx&lt;BR /&gt;-rw------- 1 root root 42949672960 May 6 16:10 LIVECLOUD_1_1-flat.vmdk&lt;BR /&gt;-rw------- 1 root root 453 May 6 16:10 LIVECLOUD_1_1.vmdk&lt;BR /&gt;-rw------- 1 root root 43008 Oct 30 2020 _deviceImage-0.iso&lt;BR /&gt;-rw------- 1 root root 3937927168 May 9 03:27 temp-flat.vmdk&lt;BR /&gt;-rw------- 1 root root 568286 May 6 13:54 vmware-48.log&lt;BR /&gt;-rw------- 1 root root 744707 May 7 02:08 vmware-49.log&lt;BR /&gt;-rw------- 1 root root 316428 May 7 02:11 vmware-50.log&lt;BR /&gt;-rw------- 1 root root 318896 May 7 02:43 vmware-51.log&lt;BR /&gt;-rw------- 1 root root 104398 May 9 03:37 vmware-52.log&lt;BR /&gt;-rw------- 1 root root 104312 May 9 03:41 vmware-53.log&lt;BR /&gt;-rw------- 1 root root 105776 May 9 04:49 vmware.log&lt;BR /&gt;-rw------- 1 root root 98566144 Mar 29 2021 vmx-LIVECLOUD_1-3569746826-1.vswp&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;SPAN&gt;The vmdks In color shows the same modified time as I create the last snapshot&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;SPAN&gt;when I try try to boot the vm I get these error message&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;State&lt;/SPAN&gt;&lt;DIV class=""&gt;&lt;P class=""&gt;Failed&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;- File LIVECLOUD_1_1-000006.vmdk was not found&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;Errors&lt;/SPAN&gt;&lt;DIV class=""&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;VMware ESX cannot find the virtual disk "LIVECLOUD_1_1-000006.vmdk". Verify the path is valid and try again.&lt;/LI&gt;&lt;LI&gt;File system specific implementation of MakeOID[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of MakeOID[file] failed&lt;/LI&gt;&lt;LI&gt;The system cannot find the file specified&lt;/LI&gt;&lt;LI&gt;Cannot open the disk 'LIVECLOUD_1_1-000006.vmdk' or one of the snapshot disks it depends on.&lt;/LI&gt;&lt;LI&gt;Module 'Disk' power on failed.&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;File system specific implementation of Ioctl[file] failed&lt;/LI&gt;&lt;LI&gt;The capacity of the parent virtual disk and the capacity of the child disk are different&lt;/LI&gt;&lt;LI&gt;Cannot open the disk '/vmfs/volumes/5f94679f-d5c0cb50-0f19-0894efaf4258/LIVECLOUD_1/LIVECLOUD_1-000024.vmdk' or one of the snapshot disks it depends on.&lt;/LI&gt;&lt;LI&gt;Failed to start the virtual machine.&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;SPAN&gt;Im assuming that I deleted the 1_1_000006.vmdk by accident&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@1C6E75E7C785988F2EA295D9769CEF91/emoticons/1f625.png" alt=":sad_but_relieved_face:" title=":sad_but_relieved_face:" /&gt;, is it possible to make the vm runs from&amp;nbsp; the very last snapshot?&amp;nbsp;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;SPAN&gt;not sure if these will help.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;SPAN&gt;best reguards.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 08:03:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2907942#M281449</guid>
      <dc:creator>QAQKent</dc:creator>
      <dc:date>2022-05-09T08:03:43Z</dc:date>
    </item>
    <item>
      <title>Re: My vm wont boot after changing the folder of its snapshop vmdk file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2908003#M281450</link>
      <description>&lt;P&gt;Hi&lt;BR /&gt;the timestamps of your files are very close to each other - that either means that you copied them manually - or that they were created by an automatic backup-tool which used a very short time for "retry after failure".&lt;BR /&gt;Second option would suggest that skipping some of them would do no harm.&lt;BR /&gt;&lt;BR /&gt;Another problem is the "File system specific implementation of Ioctl[file] failed"&lt;BR /&gt;Anyway - I think that I can bring your VM back to live but it would be way more reliable if I could do that with direct access via Teamviewer.&lt;BR /&gt;If that is an option for you - contact me via skype.&lt;BR /&gt;I expect that you have WinSCP and putty installed on your admin host.&lt;BR /&gt;&lt;BR /&gt;Ulli&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 10:46:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2908003#M281450</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2022-05-09T10:46:38Z</dc:date>
    </item>
    <item>
      <title>Re: My vm wont boot after changing the folder of its snapshop vmdk file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2908091#M281463</link>
      <description>&lt;P&gt;If we are lucky, the contents of the &lt;EM&gt;vmware*.log&lt;/EM&gt; files in the VM's folder might help with re-chaining at least one of the 2 virtual disks.&lt;BR /&gt;Please download these files from the VM's folder and attach them (compressed as a &lt;EM&gt;.zip&lt;/EM&gt; archive) to your next reply.&lt;/P&gt;
&lt;P&gt;André&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 19:12:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2908091#M281463</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2022-05-09T19:12:34Z</dc:date>
    </item>
    <item>
      <title>Re: My vm wont boot after changing the folder of its snapshop vmdk file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2908104#M281466</link>
      <description>&lt;P&gt;Andre - this VM was tortured by renaming innocent files ...&lt;BR /&gt;The first vmdk may already work again - but it took ages to boot.&lt;BR /&gt;The second vmdk is missing several snapshots - we may need to fall back to the basedisk.&lt;BR /&gt;Poor VM ...&lt;BR /&gt;&lt;BR /&gt;Ulli&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 20:11:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2908104#M281466</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2022-05-09T20:11:33Z</dc:date>
    </item>
    <item>
      <title>Re: My vm wont boot after changing the folder of its snapshop vmdk file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2908141#M281475</link>
      <description>&lt;P&gt;Okay maybe these logs can do some help&lt;/P&gt;</description>
      <pubDate>Tue, 10 May 2022 02:22:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2908141#M281475</guid>
      <dc:creator>QAQKent</dc:creator>
      <dc:date>2022-05-10T02:22:26Z</dc:date>
    </item>
    <item>
      <title>Re: My vm wont boot after changing the folder of its snapshop vmdk file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2908215#M281483</link>
      <description>&lt;P&gt;This logs are old - show the vmware.log from the start I launched yesterday.&lt;/P&gt;&lt;P&gt;Ulli&lt;/P&gt;</description>
      <pubDate>Tue, 10 May 2022 12:24:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2908215#M281483</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2022-05-10T12:24:07Z</dc:date>
    </item>
    <item>
      <title>Re: My vm wont boot after changing the folder of its snapshop vmdk file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2908674#M281547</link>
      <description>&lt;P&gt;there's no further logs for the VM&lt;BR /&gt;here's the vmkernel log may show what went wrong&lt;/P&gt;</description>
      <pubDate>Thu, 12 May 2022 10:45:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2908674#M281547</guid>
      <dc:creator>QAQKent</dc:creator>
      <dc:date>2022-05-12T10:45:11Z</dc:date>
    </item>
    <item>
      <title>Re: My vm wont boot after changing the folder of its snapshop vmdk file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2909682#M281706</link>
      <description>I managed to figure out how to get my data back here's the way I checked the vmkernel log and find out what the right Pid and Cid is , since i have all the seSpare files of the datastore disk remained I and ready to go. But I got no luck with the OS partition, it's broken. So I tried to migrade another mv's OS vmdks to this VM but it seems conflit with the old LV and VG settings. What I do next is load a Ubuntu iso disk and mount the old VG and LV then I got my files and folders back! I‘m now copy these data to somewhere safe and hopefully get my nas running again very shortly. CHEERS!</description>
      <pubDate>Wed, 18 May 2022 10:59:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/My-vm-wont-boot-after-changing-the-folder-of-its-snapshop-vmdk/m-p/2909682#M281706</guid>
      <dc:creator>QAQKent</dc:creator>
      <dc:date>2022-05-18T10:59:29Z</dc:date>
    </item>
  </channel>
</rss>

