recreating a descriptor file with using Virtual Disk Manager-fusion 2.07

[peterparamo]

I'm unable to open a vm that has been stable for the past 2 years.  I'm getting an 'operation on file xxx-flat.vmdk failed' error as well as 'xxx-flat.vmdk may be inconsistent' message when I terminate the session (see attached pngs).  The descriptor file, along with the flat.vmk file are in the package contents and seem to be intact.  I am trying to create a new descriptor file using Virtual Disk Manager to see if that will fix it, but I get the error

'Diskname or some other argument is missing.'

when I use the

vmware-vdiskmanager -c -a buslogic -s 348127232KB -t 0 -d thin temp.vmdk

command from a terminal window.  The diskname is 'temp.vmdk'.  What other argument could be missing?  Anyone have any experience with this?  Is there a better way to try to fix/recover this vm.

10.6.8

Fusion 2.0.7

Thanks.

Peter

[continuum]

What is -d thin good for ? - you already defined the type with -t 0

Please post the current vmdk descriptor and the latest vmware.logs - I will check it for you

[WoodyZ]

'Diskname or some other argument is missing.'

when I use the

vmware-vdiskmanager -c -a buslogic -s 348127232KB -t 0 -d thin temp.vmdk

That is a malformed command!  There is no -d option when using the -c option.

Example: vmware-vdiskmanager -c -s 850MB -a ide -t 0 myIdeDisk.vmdk

Also if the disk is pre-allocated as I suspect it is since you said "well as 'xxx-flat.vmdk" then the -t option should be: -t 2