VMware Communities
hasenstein
Contributor
Contributor
Jump to solution

File not found: vmdk file - file exists, lock issues but there is no lck file

Foreword: I read several discussions here and Stackexchange. I know most people have the issue that can be solved by deleting .lck file and folder but I don't have any of those, so I have to ask this question here even though it appears that it has already been answered many times at first glance.

 

Yesterday after suspending and waiting for a minute I copied he entire guest system folder to a backup location. That's the only thing I did that was different from usual.

Today I cannot start the guest VM any more. I immediately get "File not Found: C:\some path\the vm.vmdk.

The file still is right there where it always was. Its contents is fine too, I opened it in an editor and checked. The 11 disk files mentioned in the vmdk descriptor file also are all there, and with contents.

 

I press "Browse" in that "not found" dialog and select the vmdk file that is right where it is supposed to be. When I select it the guest system is started - and after a few seconds I get

hasenstein_0-1634033285310.png

 

Again: There is no lck lock file. Here are all the files, screenshot taken (with F5 refresh) right after the above window popped up:

hasenstein_1-1634033389008.png

 

The vmdk descriptor file says this:

# Disk DescriptorFile
version=1
encoding="windows-1252"
CID=0f942834
parentCID=ffffffff
createType="twoGbMaxExtentSparse"
 
# Extent description
RW 8323072 SPARSE "Mint Uma-s001.vmdk"
RW 8323072 SPARSE "Mint Uma-s002.vmdk"
RW 8323072 SPARSE "Mint Uma-s003.vmdk"
RW 8323072 SPARSE "Mint Uma-s004.vmdk"
RW 8323072 SPARSE "Mint Uma-s005.vmdk"
RW 8323072 SPARSE "Mint Uma-s006.vmdk"
RW 8323072 SPARSE "Mint Uma-s007.vmdk"
RW 8323072 SPARSE "Mint Uma-s008.vmdk"
RW 8323072 SPARSE "Mint Uma-s009.vmdk"
RW 8323072 SPARSE "Mint Uma-s010.vmdk"
RW 4849664 SPARSE "Mint Uma-s011.vmdk"
 
# The Disk Data Base 
#DDB
 
ddb.adapterType = "lsilogic"
ddb.geometry.cylinders = "5482"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.longContentID = "a0ec47ef78c867a9cd96026c0f942834"
ddb.toolsInstallType = "4"
ddb.toolsVersion = "11333"
ddb.uuid = "60 00 C2 9a 79 9e 66 65-35 ae 9a 11 36 b8 0a 8a"
ddb.virtualHWVersion = "18"

 

The vmware.log file has this to say, which reports a problem but I can't quite interpret what it means (error highlighted):

2021-10-12T12:05:52.020+02:00| vmx| I005: DISK: OPEN scsi0:1 'C:\Users\mha\Virtual Machines SSD\Mint Uma\Mint Uma.vmdk' persistent R[]
2021-10-12T12:05:52.020+02:00| worker-11496| I005: DISK: OPEN scsi0:0 'C:\Users\mha\Virtual Machines SSD\Mint Uma\Mint Uma.vmdk' persistent R[]
2021-10-12T12:05:52.041+02:00| worker-11496| I005: DISKLIB-DSCPTR: Opened [0]: "Mint Uma-s001.vmdk" (0xa)
2021-10-12T12:05:52.042+02:00| worker-11496| I005: DISKLIB-DSCPTR: Opened [1]: "Mint Uma-s002.vmdk" (0xa)
2021-10-12T12:05:52.043+02:00| worker-11496| I005: DISKLIB-DSCPTR: Opened [2]: "Mint Uma-s003.vmdk" (0xa)
2021-10-12T12:05:52.044+02:00| worker-11496| I005: DISKLIB-DSCPTR: Opened [3]: "Mint Uma-s004.vmdk" (0xa)
2021-10-12T12:05:52.045+02:00| worker-11496| I005: DISKLIB-DSCPTR: Opened [4]: "Mint Uma-s005.vmdk" (0xa)
2021-10-12T12:05:52.045+02:00| worker-11496| I005: DISKLIB-DSCPTR: Opened [5]: "Mint Uma-s006.vmdk" (0xa)
2021-10-12T12:05:52.046+02:00| worker-11496| I005: DISKLIB-DSCPTR: Opened [6]: "Mint Uma-s007.vmdk" (0xa)
2021-10-12T12:05:52.047+02:00| worker-11496| I005: DISKLIB-DSCPTR: Opened [7]: "Mint Uma-s008.vmdk" (0xa)
2021-10-12T12:05:52.048+02:00| worker-11496| I005: DISKLIB-DSCPTR: Opened [8]: "Mint Uma-s009.vmdk" (0xa)
2021-10-12T12:05:52.049+02:00| worker-11496| I005: DISKLIB-DSCPTR: Opened [9]: "Mint Uma-s010.vmdk" (0xa)
2021-10-12T12:05:52.049+02:00| worker-11496| I005: DISKLIB-DSCPTR: Opened [10]: "Mint Uma-s011.vmdk" (0xa)
2021-10-12T12:05:52.049+02:00| worker-11496| I005: DISKLIB-LINK : Opened 'C:\Users\mha\Virtual Machines SSD\Mint Uma\Mint Uma.vmdk' (0xa): twoGbMaxExtentSparse, 88080384 sectors / 42 GB.
2021-10-12T12:05:52.050+02:00| worker-11496| I005: DISKLIB-LIB : Opened "C:\Users\mha\Virtual Machines SSD\Mint Uma\Mint Uma.vmdk" (flags 0xa, type twoGbMaxExtentSparse).
2021-10-12T12:05:52.050+02:00| worker-11496| I005: DISKLIB-LIB_MISC : DiskLib_GetStorageBlockSizes: Failed to get storage block sizes, The virtual disk requires a feature not supported by this program.
2021-10-12T12:05:52.050+02:00| worker-11496| I005: DiskGetGeometry: Reading of disk partition table
2021-10-12T12:05:52.050+02:00| worker-11496| I005: DISK: Disk 'C:\Users\mha\Virtual Machines SSD\Mint Uma\Mint Uma.vmdk' has UUID '60 00 c2 9a 79 9e 66 65-35 ae 9a 11 36 b8 0a 8a'
2021-10-12T12:05:52.050+02:00| worker-11496| I005: DISK: OPEN 'C:\Users\mha\Virtual Machines SSD\Mint Uma\Mint Uma.vmdk' Geo (5482/255/63) BIOS Geo (172706/255/2)
2021-10-12T12:05:52.054+02:00| worker-11496| I005: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Reported rotation rate = 1
2021-10-12T12:05:52.055+02:00| worker-11496| I005: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Reported rotation rate = 1
2021-10-12T12:05:52.058+02:00| worker-11496| I005: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Reported rotation rate = 1
2021-10-12T12:05:52.060+02:00| worker-11496| I005: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Reported rotation rate = 1
2021-10-12T12:05:52.061+02:00| worker-11496| I005: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Reported rotation rate = 1
2021-10-12T12:05:52.063+02:00| worker-11496| I005: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Reported rotation rate = 1
2021-10-12T12:05:52.065+02:00| worker-11496| I005: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Reported rotation rate = 1
2021-10-12T12:05:52.067+02:00| worker-11496| I005: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Reported rotation rate = 1
2021-10-12T12:05:52.069+02:00| worker-11496| I005: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Reported rotation rate = 1
2021-10-12T12:05:52.071+02:00| worker-11496| I005: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Reported rotation rate = 1
2021-10-12T12:05:52.072+02:00| worker-11496| I005: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Reported rotation rate = 1
2021-10-12T12:05:52.072+02:00| worker-11496| I005: DISK: DiskConfigureVirtualSSD: Disk 'scsi0:0' identified as Virtual SSD device.
2021-10-12T12:05:55.678+02:00| vmx| I005: FILE: FileLockWaitForPossession timeout on 'C:\Users\mha\Virtual Machines SSD\Mint Uma\Mint Uma.vmdk.lck\M28961.lck' due to a local process '7940-132785067512740178(vmware-vmx.exe)'
2021-10-12T12:05:55.678+02:00| vmx| W003: FILE: FileIO_Lock on 'C:\Users\mha\Virtual Machines SSD\Mint Uma\Mint Uma.vmdk' failed: An attempt was made to load a program with an incorrect format
2021-10-12T12:05:55.678+02:00| vmx| I005: DISKLIB-DSCPTR: Couldn't lock descriptor file C:\Users\mha\Virtual Machines SSD\Mint Uma\Mint Uma.vmdk: Error (2).
2021-10-12T12:05:55.678+02:00| vmx| I005: DISKLIB-LINK : "C:\Users\mha\Virtual Machines SSD\Mint Uma\Mint Uma.vmdk" : failed to open (The process cannot access the file because another process has locked a portion of the file).
2021-10-12T12:05:55.678+02:00| vmx| I005: DISKLIB-CHAIN : "C:\Users\mha\Virtual Machines SSD\Mint Uma\Mint Uma.vmdk" : failed to open (The process cannot access the file because another process has locked a portion of the file).
2021-10-12T12:05:55.678+02:00| vmx| I005: DISKLIB-LIB : Failed to open 'C:\Users\mha\Virtual Machines SSD\Mint Uma\Mint Uma.vmdk' with flags 0xa The process cannot access the file because another process has locked a portion of the file (2162697).
2021-10-12T12:05:55.678+02:00| vmx| I005: DISK: Cannot open disk 'C:\Users\mha\Virtual Machines SSD\Mint Uma\Mint Uma.vmdk': The process cannot access the file because another process has locked a portion of the file (2162697).
2021-10-12T12:05:55.679+02:00| vmx| I005: DISK: Opening disks took 3658 ms.
2021-10-12T12:05:55.679+02:00| vmx| I005: Module 'Disk' power on failed.

There is no lock (lck) file.

I checked with process explorer (Microsoft's procexp64.exe) and it found nothing for filename "Mint Uma.vmdk".(procexp: "Find Handle or DLL")

I had rebooted the PC to get rid of any lingering processes.

Reply
0 Kudos
1 Solution

Accepted Solutions
hasenstein
Contributor
Contributor
Jump to solution

SOLVED

 

I never edited the VM machine settings in ages, definitely not since yesterday.

And yet - looking at the hardware settings for the guest VM I just saw that the entry for the main hard disk was in there TWICE!

I looked at the .vmx file and sure enough, at the bottom the section for the hard disk was appended a second time. By something. I definitely didn't touch those settings in ages.

The main hard disk was "scsi0:0" and the appended entry was for the exact same virtual disk inserted at "scsi0:1".

I removed those duplicate lines and the VM starts fine now.

 

Thank you for your support. Even if I found it myself in the end, working with someone is a catalyst.

View solution in original post

11 Replies
wila
Immortal
Immortal
Jump to solution

Hi,

I pulled your post from the spam queue.

re. your issue.
Seems like you checked the most common things already.

The one part I'm missing if you're using an antivirus product (even if Windows Defender) and if you have already excluded the .vmdk files from scanning by antivirus.

--
Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
Reply
0 Kudos
hasenstein
Contributor
Contributor
Jump to solution

The anti-virus is default Defender, no extra product.

 

and if you have already excluded the .vmdk files from scanning by antivirus.

No, did not know I need to do that.

 

EDIT:

 

I added an exclusion for the entire folder with the guest VM files now. No change.

Reply
0 Kudos
wila
Immortal
Immortal
Jump to solution

Hi,

It should not be needed, but sometimes an antivirus product decides to scan virtual disks, which as you can guess is bad for a number of reasons. Excluding virtual disks from antivirus is good practice (note that the VM itself should run its own antivirus product)
Doesn't hurt to try, but somehow doubt that it will fix your problem.

Your error is actually pretty specific:
2021-10-12T12:05:55.678+02:00| vmx| I005: FILE: FileLockWaitForPossession timeout on 'C:\Users\mha\Virtual Machines SSD\Mint Uma\Mint Uma.vmdk.lck\M28961.lck' due to a local process '7940-132785067512740178(vmware-vmx.exe)'

These lock files are only made by VMware Workstation itself.
They can get out of sync and it looks like that you are having such an issue here.
The curious part is that your screenshot isn't showing the lock folder/file at all. So unless it is hidden.. that is peculiar.

One thing that comes to my mind is file/folder virtualisation also called file redirection in Windows itself.

Can you check the %userprofile%\AppData\Local\VirtualStore folder to see if it has the lock folder there?

--
Wil

 

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
Reply
0 Kudos
hasenstein
Contributor
Contributor
Jump to solution

Can you check the %userprofile%\AppData\Local\VirtualStore folder to see if it has the lock folder there?

 

There are two entries for folders 

  • Program Files (x86)
  • Windows

but nothing else. Just in case, I looked inside and what is in there is unrelated to anything vmware.

Reply
0 Kudos
hasenstein
Contributor
Contributor
Jump to solution

Also, the lock issue only comes second. The first error is "cannot find file" (the guest VM description file). The lock issue is then report after I click "Browse" and manually select that file.

Reply
0 Kudos
hasenstein
Contributor
Contributor
Jump to solution

More details:

With an empty VMware Workstation window I click "Open a Virtual Machine", select the VM file and the VM and its settings are displayed just fine.

When I then press on "Resume" I immediately get "File not Found" for the vmdk file.

 

PS: A lock file folder "Mint Uma.vmx.lck" exists why the VMware Workstation client is open and is removed when I close the app.

I think the locking issue is just a secondary issue from whatever causes this first one.

Reply
0 Kudos
wila
Immortal
Immortal
Jump to solution

Hi,

A file not found error that pops up and then let's you select a vmdk means that the vmdk descriptor file couldn't even be located.

Starts to smell like a file credentials issue.
Not clear to me how a copy process could have changed that though.

Another possibility is that your disk is having issues.

Sorry starting to run out of ideas, besides the above.

Have you tried putting back the backup you made?
Does it have the same issue?

--
Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
Reply
0 Kudos
hasenstein
Contributor
Contributor
Jump to solution

SOLVED

 

I never edited the VM machine settings in ages, definitely not since yesterday.

And yet - looking at the hardware settings for the guest VM I just saw that the entry for the main hard disk was in there TWICE!

I looked at the .vmx file and sure enough, at the bottom the section for the hard disk was appended a second time. By something. I definitely didn't touch those settings in ages.

The main hard disk was "scsi0:0" and the appended entry was for the exact same virtual disk inserted at "scsi0:1".

I removed those duplicate lines and the VM starts fine now.

 

Thank you for your support. Even if I found it myself in the end, working with someone is a catalyst.

wila
Immortal
Immortal
Jump to solution

Hi,

Yep, that would do it.

Hard to guess for us though as there was no log file to inspect.

Glad to hear that the issue is resolved.

--
Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
Reply
0 Kudos
hasenstein
Contributor
Contributor
Jump to solution

Hard to guess for us though as there was no log file to inspect.

 

The relevant part of the log file is in the original post 🙂

Reading it now it actually shows the issue. I was just completely caught off-guard and didn't see it because I didn't expect something like this.

Reply
0 Kudos
wila
Immortal
Immortal
Jump to solution


@hasenstein wrote:

Hard to guess for us though as there was no log file to inspect.

 

The relevant part of the log file is in the original post 🙂

Reading it now it actually shows the issue. I was just completely caught off-guard and didn't see it because I didn't expect something like this.


I would have to disagree on that. There's no configuration part of the vmx itself.
Snipped log files are rarely a good idea for troubleshooting.

But.. it doesn't matter anymore, the problem is solved and that -in the end- is the only thing that counts.

--
Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
Reply
0 Kudos