<?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: Disks Get Replaced? in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909875#M281740</link>
    <description>&lt;P&gt;I've attached the vmkernel log.&lt;/P&gt;</description>
    <pubDate>Wed, 18 May 2022 21:34:28 GMT</pubDate>
    <dc:creator>mrlizard08</dc:creator>
    <dc:date>2022-05-18T21:34:28Z</dc:date>
    <item>
      <title>Disks Get Replaced?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909728#M281710</link>
      <description>&lt;P&gt;I have a really strange problem that has affected two VM's so far.&amp;nbsp; We have a single host setup with ESXI and a VMWare Essentials license.&amp;nbsp; The ESXI version is 7.0.2 and its installed on a HP ProLiant DL380 Gen9, there are 5 VM's, 4 windows and 1 linux.&amp;nbsp; The problem started last around last Sunday, for some reason all of the disks on the VM were replaced with 40 GB disks that didn't exist anywhere.&amp;nbsp; When you tried to turn on the VM it would give a getfileattributes error.&amp;nbsp; I was able to remove those disks then re-add the original VMDK, but whenever this happened it corrupted the OS, so I had to restore from back up.&amp;nbsp; Then today, at some point early in the morning I'm guessing, the same thing happened to another VM.&amp;nbsp; Luckily this time it wasn't corrupted, so I was able to add the VMDK back and it booted up.&amp;nbsp; Both affected machines were windows if it matters.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone seen this before?&amp;nbsp; Does ESXI have any logs I can check?&amp;nbsp; I checked the events under monitor but they don't go back far enough.&amp;nbsp; I've gotta get this figured soon cause if it affects the SQL server like it did the first one, we are gonna be in a world of hurt waiting on a restore.&lt;/P&gt;&lt;P&gt;One other thing, I don't know if it matters, but we use an Acronis appliance (thats the linux VM) with a Virtual Host License.&amp;nbsp; It backs up the machines at the VM level, or in other words it doesn't need an agent installed on any of the OS's&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 13:27:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909728#M281710</guid>
      <dc:creator>mrlizard08</dc:creator>
      <dc:date>2022-05-18T13:27:39Z</dc:date>
    </item>
    <item>
      <title>Re: Disks Get Replaced?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909732#M281712</link>
      <description>&lt;P&gt;Read the vmware.log files that are stored in the home directory of each VM. If you did not start the "broken" VM too often you can look up the history of the VMs from those logs- including the changes with snapshots created by the automatic Acronis backuptool.&lt;/P&gt;&lt;P&gt;Ulli&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 13:44:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909732#M281712</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2022-05-18T13:44:19Z</dc:date>
    </item>
    <item>
      <title>Re: Disks Get Replaced?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909775#M281717</link>
      <description>&lt;P&gt;ATTEMPT TO REPLY NUMBER 4 &amp;lt;--(for my records)&lt;/P&gt;&lt;P&gt;I keep trying to post a portion of the log and my reply keeps disappearing.&amp;nbsp; I'm going to try posting a screen shot of it and see if it stays&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;EDIT: Ok this one seems to have stayed...hopefully.&amp;nbsp; The issue seems to be related to snapshot consolidation.&amp;nbsp; It got stuck on 99 percent for 7.5 hours.&amp;nbsp;&amp;nbsp; Afterwards I saw these errors in the log&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mrlizard08_0-1652887395946.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/95371iA78F1850F807C623/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="mrlizard08_0-1652887395946.png" alt="mrlizard08_0-1652887395946.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 15:24:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909775#M281717</guid>
      <dc:creator>mrlizard08</dc:creator>
      <dc:date>2022-05-18T15:24:51Z</dc:date>
    </item>
    <item>
      <title>Re: Disks Get Replaced?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909787#M281720</link>
      <description>&lt;P&gt;That log is truncated - it shows how your Acronis tool tried to create a snapshot and then failed.&lt;BR /&gt;Try to attach the log files rather than showing them as screenshots.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ulli&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 16:24:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909787#M281720</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2022-05-18T16:24:36Z</dc:date>
    </item>
    <item>
      <title>Re: Disks Get Replaced?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909792#M281721</link>
      <description>&lt;P&gt;I've attached the log file.&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 16:33:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909792#M281721</guid>
      <dc:creator>mrlizard08</dc:creator>
      <dc:date>2022-05-18T16:33:20Z</dc:date>
    </item>
    <item>
      <title>Re: Disks Get Replaced?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909797#M281722</link>
      <description>&lt;P&gt;Wow - this is one of the strangest VMs I have ever seen.&lt;BR /&gt;It uses delta AND sesparse type snapshots which is quite bizarre.&lt;BR /&gt;Snapshot-consolidation takes days !!!&lt;BR /&gt;To add to it the vmdks also report disk I/O errors.&lt;BR /&gt;Where you located ? - I would like to see this monster myself - preferably via Teamviewer.&lt;BR /&gt;For now I would suggest NOT to touch this VM - any move might finally kill it.&lt;BR /&gt;Call me via skype if you like ...&lt;/P&gt;&lt;P&gt;Ulli&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 16:57:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909797#M281722</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2022-05-18T16:57:40Z</dc:date>
    </item>
    <item>
      <title>Re: Disks Get Replaced?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909839#M281730</link>
      <description>&lt;P&gt;I found a potential cause.&amp;nbsp; I was going through the Acronis logs and found a backup that has been stuck running since February, one of the stuck tasks of that backup was "Deleting hypervisor snapshot".&amp;nbsp; If its been stuck that long could that be a cause of this weirdness?&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 19:28:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909839#M281730</guid>
      <dc:creator>mrlizard08</dc:creator>
      <dc:date>2022-05-18T19:28:56Z</dc:date>
    </item>
    <item>
      <title>Re: Disks Get Replaced?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909856#M281732</link>
      <description>&lt;P&gt;Yes - that will cause problems.&lt;BR /&gt;I am worried about this errors:&lt;/P&gt;&lt;LI-SPOILER&gt;022-05-18T07:47:31.494Z| vcpu-0| | I005: Unable to find file /vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: FILE: File_GetVMFSFSType : Could not open /vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV : Input/output error&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: FILE:open error on /vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk: Input/output error&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: OBJLIB-FILEBE : FileBEOpen: can't open '/vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk' : Input/output error (327684).&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: DISKLIB-DSCPTR: DescriptorOpenInt: failed to open '/vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk' with flags 0x21: Input/output error (50004)&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: DISKLIB-LINK : "/vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk" : failed to open (Input/output error).&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: DISKLIB-CHAIN : "/vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk" : failed to open (Input/output error).&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: DISKLIB-LIB : Failed to open '/vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk' with flags 0x8 Input/output error (327689).&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: SNAPSHOT:Failed to open disk /vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk : Input/output error (327689)&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: DISK: Failed to open disk for consolidate '/vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk' : Input/output error (327689) 8542&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: FILE: File_GetVMFSFSType : Could not open /vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV : Input/output error&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: FILE:open error on /vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk: Input/output error&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: OBJLIB-FILEBE : FileBEOpen: can't open '/vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk' : Input/output error (327684).&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: DISKLIB-DSCPTR: DescriptorOpenInt: failed to open '/vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk' with flags 0x21: Input/output error (50004)&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: DISKLIB-LINK : "/vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk" : failed to open (Input/output error).&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: DISKLIB-CHAIN : "/vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk" : failed to open (Input/output error).&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: DISKLIB-LIB : Failed to open '/vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk' with flags 0xa Input/output error (327689).&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | E002: DISK: Cannot open disk '/vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk': Input/output error (327689).&lt;BR /&gt;2022-05-18T07:47:31.494Z| vcpu-0| | I005: CPT: error syncing group SCSI0&lt;BR /&gt;2022-05-18T07:47:31.495Z| vcpu-0| | I005: CPT: vm was stunned for 10866643 us&lt;BR /&gt;2022-05-18T07:47:31.495Z| vcpu-0| | I005: Msg_Post: Error&lt;BR /&gt;2022-05-18T07:47:31.495Z| vcpu-0| | I005: [vob.fssvec.GetFileAttributes.file.failed] File system specific implementation of GetFileAttributes[file] failed&lt;BR /&gt;2022-05-18T07:47:31.495Z| vcpu-0| | I005: [vob.fssvec.GetFileAttributes.file.failed] File system specific implementation of GetFileAttributes[file] failed&lt;BR /&gt;2022-05-18T07:47:31.495Z| vcpu-0| | I005: [vob.fssvec.GetFileAttributes.file.failed] File system specific implementation of GetFileAttributes[file] failed&lt;BR /&gt;2022-05-18T07:47:31.495Z| vcpu-0| | I005: [vob.fssvec.GetFileAttributes.file.failed] File system specific implementation of GetFileAttributes[file] failed&lt;BR /&gt;2022-05-18T07:47:31.495Z| vcpu-0| | I005: [vob.fssvec.GetFileAttributes.file.failed] File system specific implementation of GetFileAttributes[file] failed&lt;BR /&gt;2022-05-18T07:47:31.495Z| vcpu-0| | I005: [vob.fssvec.GetFileAttributes.file.failed] File system specific implementation of GetFileAttributes[file] failed&lt;BR /&gt;2022-05-18T07:47:31.495Z| vcpu-0| | I005: [vob.fssvec.GetFileAttributes.file.failed] File system specific implementation of GetFileAttributes[file] failed&lt;BR /&gt;2022-05-18T07:47:31.495Z| vcpu-0| | I005: [msg.literal] Input/output error&lt;BR /&gt;2022-05-18T07:47:31.495Z| vcpu-0| | I005: [msg.disk.noBackEnd] Cannot open the disk '/vmfs/volumes/c329d5b9-1078b333/APPSRV/APPSRV/APPSRV_1-000005.vmdk' or one of the snapshot disks it depends on.&lt;BR /&gt;2022-05-18T07:47:31.495Z| vcpu-0| | I005: [msg.checkpoint.continuesync.error] An operation required the virtual machine to quiesce and the virtual machine was unable to continue running.&lt;/LI-SPOILER&gt;&lt;P&gt;Ulli&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 20:37:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909856#M281732</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2022-05-18T20:37:45Z</dc:date>
    </item>
    <item>
      <title>Re: Disks Get Replaced?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909860#M281734</link>
      <description>&lt;P&gt;That vmdk its referring to, 0005, doesn't exist, I looked all over for it.&amp;nbsp; Thats most likely why its getting i/o errors.&amp;nbsp; The VMDK that machine uses didn't report any errors that I saw (APPSRV.vmdk)&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 20:43:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909860#M281734</guid>
      <dc:creator>mrlizard08</dc:creator>
      <dc:date>2022-05-18T20:43:48Z</dc:date>
    </item>
    <item>
      <title>Re: Disks Get Replaced?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909869#M281737</link>
      <description>&lt;P&gt;Hmmm - from all my experience with VMFS recovery this smells like a VMFS-volume in pretty poor shape to me.&lt;BR /&gt;If this was my host I would start to rebuild the datastore from scratch as long as that is still possible.&lt;BR /&gt;May I see the latest vmkernel.log please ?&lt;BR /&gt;&lt;BR /&gt;Ulli&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 21:06:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909869#M281737</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2022-05-18T21:06:32Z</dc:date>
    </item>
    <item>
      <title>Re: Disks Get Replaced?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909875#M281740</link>
      <description>&lt;P&gt;I've attached the vmkernel log.&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 21:34:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Disks-Get-Replaced/m-p/2909875#M281740</guid>
      <dc:creator>mrlizard08</dc:creator>
      <dc:date>2022-05-18T21:34:28Z</dc:date>
    </item>
  </channel>
</rss>

