VMware workstation vmdk file not found

[thalmo]

I restarted my Windows Server VM today cause i had to do a AD assignment for school. But every time i try to start the VM i get the message which says that my vmdk file is not found, but it is in this folder. When i reassign it i get another error message (attached a screenshot of it in this question)? Does anyone know why this happens or how to fix it?

Thanks Per-Luca

[continuum]

>> When i reassign it i get another error message 

Stop it. Trying to fix a "file not found" issue by reassigning the vmdk will very likely mess up your existing snapshot-chain.

First troubleshooting step for "file not found" issues is always: read latest vmware.log and figure out which file actually is not detected.

So we need a list of all the files in your VMs directory - list full names - file size and timestamps.
Next we need the latest vmware.log and the latest vmx-file.

[thalmo]

thanks for the answer

As i said i am a student with zero experience. But i attached a picture of the files. The number of Windows Server 2019-s007 goes up to s016. And i dont know which log text i should upload here the first from today or the last? 

Vmx file: 

.encoding = "windows-1252"
config.version = "8"
virtualHW.version = "18"
pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
hpet0.present = "TRUE"
nvram = "Windows Server 2019.nvram"
virtualHW.productCompatibility = "hosted"
powerType.powerOff = "soft"
powerType.powerOn = "soft"
powerType.suspend = "soft"
powerType.reset = "soft"
displayName = "Windows Server 2019"
firmware = "efi"
guestOS = "windows2019srv-64"
tools.syncTime = "FALSE"
sound.autoDetect = "TRUE"
sound.virtualDev = "hdaudio"
sound.fileName = "-1"
sound.present = "TRUE"
numvcpus = "8"
cpuid.coresPerSocket = "2"
vcpu.hotadd = "TRUE"
memsize = "4096"
mem.hotadd = "TRUE"
sata0.present = "TRUE"
nvme0.present = "TRUE"
nvme0:0.fileName = "Windows Server 2019.vmdk"
nvme0:0.present = "TRUE"
sata0:1.deviceType = "cdrom-raw"
sata0:1.fileName = "auto detect"
sata0:1.present = "TRUE"
usb.present = "TRUE"
ehci.present = "TRUE"
usb_xhci.present = "TRUE"
ethernet0.connectionType = "nat"
ethernet0.addressType = "generated"
ethernet0.virtualDev = "e1000e"
serial0.fileType = "thinprint"
serial0.fileName = "thinprint"
floppy0.fileType = "device"
floppy0.fileName = ""
ethernet0.present = "TRUE"
serial0.present = "TRUE"
extendedConfigFile = "Windows Server 2019.vmxf"
floppy0.clientDevice = "FALSE"
uuid.bios = "56 4d ac 44 df 3f 69 16-8c a2 91 4d 64 a7 07 f7"
uuid.location = "56 4d ac 44 df 3f 69 16-8c a2 91 4d 64 a7 07 f7"
vm.genid = "6563895522593341168"
vm.genidX = "7763714752350823733"
nvme0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
usb.pciSlotNumber = "32"
ethernet0.pciSlotNumber = "160"
sound.pciSlotNumber = "33"
ehci.pciSlotNumber = "34"
usb_xhci.pciSlotNumber = "192"
vmci0.pciSlotNumber = "35"
sata0.pciSlotNumber = "36"
nvme0.pciSlotNumber = "224"
svga.vramSize = "268435456"
vmotion.checkpointFBSize = "4194304"
vmotion.checkpointSVGAPrimarySize = "268435456"
vmotion.svga.mobMaxSize = "268435456"
vmotion.svga.graphicsMemoryKB = "262144"
ethernet0.generatedAddress = "00:0c:29:a7:07:f7"
ethernet0.generatedAddressOffset = "0"
vmci0.id = "1688668151"
monitor.phys_bits_used = "45"
cleanShutdown = "TRUE"
softPowerOff = "TRUE"
floppy0.autodetect = "TRUE"
sata0:1.autodetect = "TRUE"
sata0:1.clientDevice = "FALSE"
svga.guestBackedPrimaryAware = "TRUE"
tools.remindInstall = "FALSE"
toolsInstallManager.updateCounter = "1"
toolsInstallManager.lastInstallError = "0"
guestOS.detailed.data = ""
checkpoint.vmState = ""
floppy0.present = "FALSE"
scsi0.virtualDev = "lsisas1068"
scsi0.present = "TRUE"
scsi0:0.fileName = "Windows Server 2019.vmdk"
scsi0:0.present = "TRUE"
scsi0:2.fileName = "Windows Server 2019-2.vmdk"
scsi0:2.present = "TRUE"
scsi0:3.fileName = "Windows Server 2019-3.vmdk"
scsi0:3.present = "TRUE"
scsi0:3.redo = ""
scsi0:0.redo = ""
scsi0:2.redo = ""
scsi0.pciSlotNumber = "256"
scsi0.sasWWID = "50 05 05 64 df 3f 69 10"
usb_xhci:4.present = "TRUE"
usb_xhci:4.deviceType = "hid"
usb_xhci:4.port = "4"
usb_xhci:4.parent = "-1"
scsi0:1.fileName = "Windows Server 2019-4.vmdk"
scsi0:1.present = "TRUE"
scsi0:1.redo = ""
fileSearchPath = "D:;."
workingDir = "."

[continuum]

Your attempt to reassign the vmdk had a poor but still harmess result.

Remember that WS complained about a locked file ....

Now read the vmxfile you posted. 

The problem you produced with your reassigning stunt can be found by carefully reading the vmx file.

You assigned the vmdk in question twice 

That will obviously fail  ....

i will post in a few minutes again — but try to find the problem yourself first.

It really is easy — you can do it ...

Ulli

[thalmo]

Is it cause Windows Server 2019.vmdk is on time assignened to an scsi and on time to nvme, because this is the only thing i can find. And this does not solve the vmdk can not find error just the second one, if i am right...

I dont understand the most lines in my vmx file 😅

[continuum]

Right - this only fixes the locked file issue.

Search through the latest vmware.logs - start from the end of the log and scroll up until you find the message that complains about a missing file.

Post that error message

Ulli

[thalmo]

Do i have to delete one row in the vmx file when i assigned it twice?

The first thing i found in the log file which says cannot open:

021-04-14T15:03:37.729+02:00| worker-1872| I005: FILE: FileLockWaitForPossession timeout on 'D:\Windows Server 2019.vmdk.lck\M07318.lck' due to a local process '4780-132628790128966907(vmware-vmx.exe)'
2021-04-14T15:03:37.729+02:00| worker-1872| W003: FILE: FileIO_Lock on 'D:\Windows Server 2019.vmdk' failed: Unknown error 11 (0xb)
2021-04-14T15:03:37.729+02:00| worker-1872| I005: DISKLIB-DSCPTR: Couldn't lock descriptor file D:\Windows Server 2019.vmdk: Error (2).
2021-04-14T15:03:37.729+02:00| worker-1872| I005: DISKLIB-LINK : "D:\Windows Server 2019.vmdk" : failed to open (Unknown error 33 (0x21)).
2021-04-14T15:03:37.729+02:00| worker-1872| I005: DISKLIB-CHAIN : "D:\Windows Server 2019.vmdk" : failed to open (Unknown error 33 (0x21)).
2021-04-14T15:03:37.729+02:00| worker-1872| I005: DISKLIB-LIB : Failed to open 'D:\Windows Server 2019.vmdk' with flags 0xa Unknown error 33 (0x21) (2162697).
2021-04-14T15:03:37.729+02:00| worker-1872| I005: DISK: Cannot open disk 'D:\Windows Server 2019.vmdk': Unknown error 33 (0x21) (2162697).
2021-04-14T15:03:37.729+02:00| vmx| I005: DISK: Opening disks took 4115 ms.
2021-04-14T15:03:37.730+02:00| vmx| I005: Module 'Disk' power on failed.