Wil - your first idea was correct. In fact there are only the 2 slices missing that you already listed.
But your good suggestion was a lucky guess. What you missed was the fact that the basedisk was created when the max-size per slice was smaller than the max size per slice was when the snapshots were created.
Looks like the basedisk was created with an older workstation version.
So the two missing slices still have to be replaced.
The general idea when missing slices have to be replaced is to pick an existing slice which in an ideal case has not been written to.
Looking through the file list for both workstation versions an "empty slice" had a size of 786,432 bytes.
So I would suggest to use Windows 7 Pro x64-cl1-s041.vmdk and copy that one to
Windows 7 Pro x64-cl1-s005.vmdk
and to
Windows 7 Pro x64-cl1-000002-s002.vmdk.
And in this case I believe that the damage that obviously will occur when ever a used slice is replaced with a blank one will be quite small.
Anyway - after replacing both slices I would suggest to add another snapshot before starting the VM again.
When it starts as I assume it will, run a checkdisk and then evaluate if anything important is missing.
But as mentioned before I assume that in this lucky case the damage will be minimal.
Ulli
________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...
