wila
Immortal
Immortal

Hi,

Stop messing with vmware-vdiskmanager.. it won't fix this.
It's how you lost the disk slice in the first place.

Also fix back your -000004.vmdk file back to the original state with the missing slice.
You can't just remove a disk slice and expect things to work. It won't.

Finally ... in order to resolve:

Create a new VM with the EXACT same disk size as your current VM with problems.
It should have the same data in the .vmdk file as your -000004.vmdk.
Same amount of slices and same size. The "8323072" in your original RW 8323072 SPARSE "Windows 10 Dev-000004-s017.vmdk" line.

When that's true... take slice 17 and rename it "Windows 10 Dev-000004-s017.vmdk".

Copy it into your broken VM.

Note that there will be data loss as a whole slice has gone missing.
But with the notes above you should be able to get the VM to be recognized again.

 

Oh and .. yes DO MAKE A BACKUP before you start making changes and experiment.

--
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