VMware Communities
zaphod2
Contributor
Contributor
Jump to solution

Vmware Workstation Snapshot not visable

Hello!

I got a big problem with vmware workstation 12.5.9 build-7535481:

In snapshot manager I wanted to delete a snapshot.

A message has occourred that there is not enough disk space to do this.

Now the snapshot is not longer visable in snapshotmanager.

The snapshot is not visible running:

C:\Users\hhussy\Documents\Virtual Machines\MONTEVELO3>"c:\Program Files (x86)\VMware\VMware Workstation"\vmrun listsnapshots montevelo3.vmx

Total snapshots: 0

The snapshot-chain seems to be fully functional, because the virtual machine is running correctly.

Directory listing of the VM:

C:\Users\hhussy\Documents\Virtual Machines\MONTEVELO3>dir

Volume in Laufwerk C: hat keine Bezeichnung.

Volumeseriennummer: 0868-16A2

Verzeichnis von C:\Users\hhussy\Documents\Virtual Machines\MONTEVELO3

15.01.2019  01:02    <DIR>          .

15.01.2019  01:02    <DIR>          ..

15.01.2019  01:01     6.509.559.808 564dfb59-31dd-eb2a-471f-3dc98f82ede4.vmem

15.01.2019  01:01    <DIR>          564dfb59-31dd-eb2a-471f-3dc98f82ede4.vmem.lc

k

22.12.2018  14:10    <DIR>          caches

15.01.2019  01:01   473.174.245.376 MONTEVELO3-000002.vmdk

15.01.2019  01:01    <DIR>          MONTEVELO3-000002.vmdk.lck

09.01.2019  09:05     6.509.559.808 MONTEVELO3-2f819631.vmem

09.01.2019  18:54    <DIR>          MONTEVELO3-2f819631.vmem.lck

15.01.2019  00:57             8.684 MONTEVELO3.nvram

08.01.2019  13:39    43.189.731.328 MONTEVELO3.vmdk

15.01.2019  01:01    <DIR>          MONTEVELO3.vmdk.lck

15.01.2019  00:11               112 MONTEVELO3.vmsd

15.01.2019  01:02             4.197 MONTEVELO3.vmx

15.01.2019  01:01    <DIR>          MONTEVELO3.vmx.lck

08.01.2019  13:51             3.404 MONTEVELO3.vmxf

15.01.2019  00:57           362.385 vmware-0.log

15.01.2019  00:17           363.362 vmware-1.log

15.01.2019  00:11           361.491 vmware-2.log

15.01.2019  01:01           200.189 vmware.log

              12 Datei(en), 529.384.400.144 Bytes

               8 Verzeichnis(se), 460.121.530.368 Bytes frei

C:\Users\hhussy\Documents\Virtual Machines\MONTEVELO3>

The original disk is MONTEVELO3.vmdk. It is growable but not splitted.

Seems, that the snapshot-manager has edited the .vmsd- file and afterwards recognized that it is not possible to commit the snapshot

I would need urgent help.

Does anybody has an idea?

Yours

Holger

0 Kudos
1 Solution

Accepted Solutions
continuum
Immortal
Immortal
Jump to solution

Hello Holger
Plan A:
1. power off the VM
2. create new directory on a drive with enough free space like D:\VMs\montevelo3
3. run
"c:\Program Files (x86)\VMware\VMware Workstation\vmware-vdiskmanager.exe"  -r  C:\Users\hhussy\Documents\Virtual Machines\MONTEVELO3\MONTEVELO3-000002.vmdk" -t 0 D:\VMs\montevelo3\new-base.vmdk
4. copy vmx-file to new directory
5. edit vmx-file:
change
scsi0:0.fileName = "MONTEVELO3-000002.vmdk"
to scsi0:0.fileName = "new-base.vmdk"

6.done
Plan B:

1. free space on C: drive - you need additional 500GB to be on the safe side

2. create new snapshot
3. use snapshotmanager "delete all" function
----------------
I highly recommend plan A as it is failsafe.If plan B fails - the VM might get corrupted.

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

View solution in original post

0 Kudos
2 Replies
continuum
Immortal
Immortal
Jump to solution

Hello Holger
Plan A:
1. power off the VM
2. create new directory on a drive with enough free space like D:\VMs\montevelo3
3. run
"c:\Program Files (x86)\VMware\VMware Workstation\vmware-vdiskmanager.exe"  -r  C:\Users\hhussy\Documents\Virtual Machines\MONTEVELO3\MONTEVELO3-000002.vmdk" -t 0 D:\VMs\montevelo3\new-base.vmdk
4. copy vmx-file to new directory
5. edit vmx-file:
change
scsi0:0.fileName = "MONTEVELO3-000002.vmdk"
to scsi0:0.fileName = "new-base.vmdk"

6.done
Plan B:

1. free space on C: drive - you need additional 500GB to be on the safe side

2. create new snapshot
3. use snapshotmanager "delete all" function
----------------
I highly recommend plan A as it is failsafe.If plan B fails - the VM might get corrupted.

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

0 Kudos
zaphod2
Contributor
Contributor
Jump to solution

Hello Ulli!

Very thanks a lot!!!

I have used PLAN A successfully.

My Workstation Version does not have "delete all" button.

Everything ok now.

Remains the question, if this snapshot Manager bug still exists in most recent version.

Yours

Holger

0 Kudos