home       vmx       vmdk        about this site        forum        downloads  


 

When it is too late ...


1. DON'T PANIC
2. do not try to start the VM again
3. do not mount disks from other VMs
4. do not use the vmware-mount tool or vmware-vdiskmanager
5. do not use vdk in read/write mode
6. make a copy of all vmware-log files

7. find out what has gone wrong
     - if you find something related to your problem listed below
     - try to follow the suggested procedure.



often used procedures ...
disktypes-table ...

 
desaster description chances trickiness suggested procedure
       
cannot resume moved VM (CPU-messages) like
hard reboot		 very easy remove *.vmss or disable
cpu-compat-test
cannot start (in-use or locked messages)   very easy remove stale lockdirs/lockfiles
       
       
descriptor vmdk is lost good easy use sample from list
restore entries from last log
see howto
vmx is lost
 good very easy restore from last log
embedded descriptor is lost
 unknown average use sample from list
restore entries from log
see howto
inject with dsfi.exe
basedisk is lost - only snapshots are left
 restore advanced fake basedisk
mount with vdk
restore data
       
parent has been changed
 depends average fix CID-chain
parent has been changed - embedded descriptor
 depends average extract with dsfo.exe
fix CID-chain
inject with dsfi.exe
       
parent has been expanded
 depends very advanced cut
fix geometry
fix CID-chain
parent has been expanded - embedded descriptor
 depends very,very advanced extract with dsfo.exe
cut
fix geometry
fix CID-chain
inject with dsfi.exe
       
one or more flat chunks of a
"twoGbMaxExtentFlat" -disk is missing		 restore average fake chunks
mount with vdk
one or more sparse chunks of a
"twoGbMaxExtentSparse" - disk is missing		 restore advanced fake chunks
mount with vdk
       
"monolithicSparse" is too small
after running out of disk-space		 restore advanced copy to location with disk-space
Plan B
restore data
one or more chunks of a
"twoGbMaxExtentFlat" is too small
after running out of disk-space		 restore advanced copy to location with disk-space
expand
mount with vdk
restore data
"monolithicFlat" is too small
after running out of disk-space		 restore advanced copy to location with disk-space
expand
mount with vdk
restore data
one or more chunks of a
"twoGbMaxExtentSparse" is too small
after running out of disk-space		 restore advanced copy to location with disk-space
Plan B
restore data

     
disk has holes (needs repair) restore advanced mount with vdk
restore data
messed up original VM after starting a Copy
- and deleting the Copy		 bad very advanced restore still usable branches
       


DISCLAIMER:

The procedures I suggest for some typical problem often require advanced skills.
I can't take any responsibilty when you mess up your data following this tips.
This just lists up what I would do in such a case.
Please also note that official VMware support will very likely claim that those cases listed as "restore" are lost.
Don't give up too early - you may still be able to rescue some data.

For in depth discussion of the listed procedure use the search function at VMTN , german forum and sanbarrow forum.
Search for username "continuum" and terms from desaster description table.



 top 

 


   home       vmx       vmdk        about this site        forum        downloads