Hi,
I have upgrade my mac to Big Sur and also VMware Fusion 12 and this is what I found after restarting.
File not found: /Users/suthipornangsuwaree/Documents/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk.vmdk
This file is required to power on this virtual machine. If this file was moved, specify the new location.
I am not a tech guy and I have spends hours solving this problem and I failed. I am asking for help. Thank you
Moderator: Moved to Fusion Discussions
> I am not a tech guy
Dont think too much. I bet you have already developed problem solving strategies for this type of problems in many many other areas.
Use that experience !
Boiled down this problem is just another occurance of the "Fun stops unexpectedly - then somebody says why" scenario.
Pick an easy one ....
You enjoy a party and look forward to get really drunk later. Then suddenly the mood changes and somebody says "No more beer in the fridge- nix, nada, njet"
Here we have exactly the same problem. And most humans have practised the best approach thousands of times before.
First - go to the fridge and check if it is really empty.
Second - question the motivs of the guy that announced that there is no more beer.
Some folks prefer to start with questioning the motivs of the dude who stopped the fun first.
Others open the fridge first.
For a final conclusion trying both seems to be the most popular strategy.
In this case open the fridge (/Users/suthipornangsuwaree/Documents/Virtual Machines.localized/Windows 10 x64.vmwarevm/)
Is the beer (Virtual Disk.vmdk) there ?
If the beer is there question the motivation of the dude that crashed the party (Fusion application)
Maybe the beer is to hot ? or is the bottle broken .... ?
Ulli
Upgrading with suspended VMs often causes issues, and is therefore not supported.
What you may do is to reset the VM (pull the power plug), by e.g. deleting its .vmss, .vmem files, and the .lck folder.
Alternatively https://kb.vmware.com/s/article/1006215 may help:
"In Fusion 6.x and above, you can force shutdown a suspended virtual machine by pressing the Option Key on the keyboard and selecting Force Shutdown in power options."
Remember that both option may cause some data corruption, and/or loss in the guest OS!
André
Hi,
Luckily you have the two experts that are able to repair your VM -if at all possible- already replying to this thread (Ulli & André)
However they do need more info from you in order to determine if it is possible to repair the VM.
In terminal run the following command:
ls -lisa "/Users/suthipornangsuwaree/Documents/Virtual Machines.localized/Windows 10 x64.vmwarevm/" > ~/Desktop/Windows10FileList.log
This will put a file "Windows10FileList.log" on your desktop with all the files that are currently in your virtual machine folder.
Attach that here to a reply.
--
Wil
the file .log is not supported to attach so I copied and pasted in down here
total 94899600
1033587 0 drwxr-xr-x@ 39 suthipornangsuwaree staff 1248 Dec 13 20:06 .
1033474 0 drwxr-xr-x@ 5 suthipornangsuwaree staff 160 Jan 21 2017 ..
1238040 0 drwxr-xr-x 72 suthipornangsuwaree staff 2304 Dec 8 20:15 Applications
1033604 7485312 -rw-------@ 1 suthipornangsuwaree staff 3763994624 Dec 10 13:35 Virtual Disk-s001.vmdk
1033605 8323072 -rw-------@ 1 suthipornangsuwaree staff 4255383552 Dec 10 13:35 Virtual Disk-s002.vmdk
1033606 8323072 -rw-------@ 1 suthipornangsuwaree staff 4260888576 Dec 10 13:35 Virtual Disk-s003.vmdk
1033607 8355840 -rw-------@ 1 suthipornangsuwaree staff 4254662656 Dec 10 13:35 Virtual Disk-s004.vmdk
1033608 8355840 -rw-------@ 1 suthipornangsuwaree staff 4261937152 Dec 10 13:35 Virtual Disk-s005.vmdk
1033609 7181184 -rw-------@ 1 suthipornangsuwaree staff 3626696704 Dec 10 13:35 Virtual Disk-s006.vmdk
1033610 7320704 -rw-------@ 1 suthipornangsuwaree staff 3701932032 Dec 10 13:35 Virtual Disk-s007.vmdk
1033611 6800256 -rw-------@ 1 suthipornangsuwaree staff 3430088704 Dec 10 13:35 Virtual Disk-s008.vmdk
1033612 6253824 -rw-------@ 1 suthipornangsuwaree staff 3150577664 Dec 10 13:35 Virtual Disk-s009.vmdk
1033613 4616960 -rw-------@ 1 suthipornangsuwaree staff 2311520256 Dec 10 13:35 Virtual Disk-s010.vmdk
1033614 4130944 -rw-------@ 1 suthipornangsuwaree staff 2082537472 Dec 10 13:35 Virtual Disk-s011.vmdk
1033615 3100928 -rw-------@ 1 suthipornangsuwaree staff 1562116096 Dec 10 13:35 Virtual Disk-s012.vmdk
1033616 2664320 -rw-------@ 1 suthipornangsuwaree staff 1312030720 Dec 10 13:35 Virtual Disk-s013.vmdk
1033617 6464256 -rw-------@ 1 suthipornangsuwaree staff 3274047488 Dec 10 13:35 Virtual Disk-s014.vmdk
1033618 1319552 -rw-------@ 1 suthipornangsuwaree staff 623247360 Mar 30 2020 Virtual Disk-s015.vmdk
8599493907 8 -rw-------@ 1 suthipornangsuwaree staff 1166 Dec 10 13:23 Virtual Disk.vmdk
8599500990 4194304 -rw------- 1 suthipornangsuwaree staff 2147483648 Dec 10 13:35 Windows 10 x64-ba9a08f7.vmem
8599500989 6192 -rw------- 1 suthipornangsuwaree staff 2247357 Dec 10 13:35 Windows 10 x64-ba9a08f7.vmss
1033726 24 -rw------- 1 suthipornangsuwaree staff 8684 Dec 8 20:24 Windows 10 x64.nvram
8599500960 8 -rw-r--r-- 1 suthipornangsuwaree staff 859 Dec 10 13:34 Windows 10 x64.plist
1033631 0 -rw-r--r-- 1 suthipornangsuwaree staff 0 Jan 4 2017 Windows 10 x64.vmsd
8599587877 16 -rwxr-xr-x 1 suthipornangsuwaree staff 5761 Dec 10 16:42 Windows 10 x64.vmx
8599617245 0 drwxrwxrwx 3 suthipornangsuwaree staff 96 Dec 13 19:55 Windows 10 x64.vmx.lck
1033632 8 -rw-r--r-- 1 suthipornangsuwaree staff 377 Dec 8 20:24 Windows 10 x64.vmxf
1238028 0 drwxr-xr-x 7 suthipornangsuwaree staff 224 Jan 21 2017 appListCache
1033900 0 drwxr-xr-x 3 suthipornangsuwaree staff 96 Dec 13 19:55 caches
8599593018 184 -rw-r----- 1 suthipornangsuwaree staff 92022 Dec 10 17:10 mksSandbox-0.log
8599592923 184 -rw-r----- 1 suthipornangsuwaree staff 92022 Dec 10 17:10 mksSandbox-1.log
8599592829 184 -rw-r----- 1 suthipornangsuwaree staff 92022 Dec 10 17:10 mksSandbox-2.log
8599593111 184 -rw-r----- 1 suthipornangsuwaree staff 92022 Dec 10 17:10 mksSandbox.log
1428020 0 -rw-r--r-- 1 suthipornangsuwaree staff 0 Jan 28 2017 quicklook-cache.png
8599599031 1344 -rw-r--r-- 1 suthipornangsuwaree staff 684094 Dec 10 17:57 startMenu.plist
8599593010 224 -rw-r--r-- 1 suthipornangsuwaree staff 113031 Dec 10 17:10 vmware-0.log
8599592915 224 -rw-r--r-- 1 suthipornangsuwaree staff 113030 Dec 10 17:10 vmware-1.log
8599592821 224 -rw-r--r-- 1 suthipornangsuwaree staff 113246 Dec 10 17:10 vmware-2.log
8599593103 224 -rw-r--r-- 1 suthipornangsuwaree staff 113030 Dec 10 17:10 vmware.log
Could anyone help me a bit more on this?
The .vmem, and .vmss files still exist!? Didn't the reset work with deleting these two files, as suggested in my previous reply?
André
Please compress/zip "Virtual Disk.vmdk", and attach it to a reply post.
Also verify that all other .vmdk files start with "KDMV" by running e.g.
for i in *-s???.vmdk;do echo "++++ $i ++++"; hexdump -C -n 16 "$i";done
André
Last login: Mon Dec 14 19:15:58 on ttys000
The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
Suthiporns-MacBook-Pro:~ suthipornangsuwaree$ for i in *-s???.vmdk;do echo "++++ $i ++++"; hexdump -C -n 16 "$i";done
++++ *-s???.vmdk ++++
hexdump: *-s???.vmdk: No such file or directory
hexdump: *-s???.vmdk: Bad file descriptor
Suthiporns-MacBook-Pro:~ suthipornangsuwaree$
Hi,
Andre's script gives these errors because you didn't change the directory.
So the full sequence of commands is:
cd "/Users/suthipornangsuwaree/Documents/Virtual Machines.localized/Windows 10 x64.vmwarevm/"
for i in *-s???.vmdk;do echo "++++ $i ++++"; hexdump -C -n 16 "$i";done
and then it should work and print out something similar to this:
for i in *-s???.vmdk;do echo "++++ $i ++++"; hexdump -C -n 16 "$i";done
++++ Virtual Disk-000001-s001.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-000001-s002.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-000001-s003.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-000001-s004.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-000001-s005.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-000001-s006.vmdk ++++
etcetera...
hope this helps,
--
Wil
Thank you very much, Wila. And this is what it is displayed.
Last login: Sun Dec 27 21:48:40 on ttys000
The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
Suthiporns-MacBook-Pro:~ suthipornangsuwaree$ cd "/Users/suthipornangsuwaree/Documents/Virtual Machines.localized/Windows 10 x64.vmwarevm/"
Suthiporns-MacBook-Pro:Windows 10 x64.vmwarevm suthipornangsuwaree$ for i in *-s???.vmdk;do echo "++++ $i ++++"; hexdump -C -n 16 "$i";done
++++ Virtual Disk-s001.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s002.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s003.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s004.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s005.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s006.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s007.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s008.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s009.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s010.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s011.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s012.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s013.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s014.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s015.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
Suthiporns-MacBook-Pro:Windows 10 x64.vmwarevm suthipornangsuwaree$
According to the .vmdk file that you've posted, one of the required files "Virtual Disk-s016.vmdk" is missing.
Do you have a recent a backup of this file?
If you don't have a backup, it may be an option to create a dummy VM with the exact same virtual disk size, and use its "...-s016.vmdk" to replace the missing file. To verify the correct size, check whether the dummy VM's block size matches the missing file's size.
RW 983040 SPARSE "Virtual Disk-s016.vmdk"
Remember that this will help to make the VM work again, but you will most likely see some file system corruption within the guest OS. So what I recommend is that you create at least a snapshot before you power on the VM!
André
Hi @wila @a_p_ Hope you are well. I am having same issue and this my output below. Am I missing s025? Also what does G mean next KDMV?
(base) rbakhishli1@UK-C02XX0CTJG5L Windows 10 x64.vmwarevm % for i in *-s???.vmdk;do echo "++++ $i ++++"; hexdump -C -n 16 "$i";done
++++ Virtual Disk-s012.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s013.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s014.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s015.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s016.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 0f 00 |KDMV............|
00000010
++++ Virtual Disk-s017.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s018.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s019.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s020.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s021.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s022.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s023.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 7f 00 |KDMV............|
00000010
++++ Virtual Disk-s024.vmdk ++++
00000000 4b 44 4d 56 01 00 00 00 03 00 00 00 00 00 47 00 |KDMV..........G.|
00000010
Hi,
The "G" is not a letter, it just happens to render like that.
It's part of the size structure in the vmdk file.
In other words, the -s025.vmdk file is a different size than the -s024.vmdk and earlier files in your listing.
What I wonder about is where the -s001.vmdk until -s011.vmdk files are.
--
Wil
I believe I have deleted them couple of weeks ago. But I was able to use my vmware on Friday(which is weird). But I had a mac update yesterday aswell. Looking at the log i can see that :
2021-10-06T09:28:31.351Z| vmx| I005: DISK: OPEN nvme0:0 '/Users/rbakhishli1/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk.vmdk' persistent R[]
2021-10-06T09:28:31.353Z| vmx| I005: AIOGNRC: Failed to open '/Users/rbakhishli1/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk-s001.vmdk' : Could not find the file (60003) (0x3).
2021-10-06T09:28:31.353Z| vmx| I005: OBJLIB-FILEBE : FileBEOpen: can't open '/Users/rbakhishli1/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk-s001.vmdk' : Could not find the file (393218).
2021-10-06T09:28:31.353Z| vmx| I005: DISKLIB-SPARSE: "/Users/rbakhishli1/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk-s001.vmdk" : failed to open (25): ObjLib_Open failed
2021-10-06T09:28:31.353Z| vmx| I005: DISKLIB-LINK : "/Users/rbakhishli1/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk.vmdk" : failed to open (The system cannot find the file specified).
2021-10-06T09:28:31.353Z| vmx| I005: DISKLIB-CHAIN : "/Users/rbakhishli1/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk.vmdk" : failed to open (The system cannot find the file specified).
2021-10-06T09:28:31.353Z| vmx| I005: DISKLIB-LIB : Failed to open '/Users/rbakhishli1/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk.vmdk' with flags 0xa The system cannot find the file specified (25).
I mistakenly deleted this file while trying to delete some unwanted files virtual disk.vmdk How do i get it back, i couldn't find it in Trash