strange vmdk files

[aurfalien]

Hi all,

So I was poking around my Fusion install because although my XP guest is sized at 15GB, the VMware Fusion dir is showing ~30GB.

I notice 3 files;

Windows XP.vmdk - 15GB

Windows XP-000001.vmdk - 1.4GB

Windows XP-000002.vmdk - 12GB

My vmx files has this;

scsi0:0.fileName = "Windows XP-000001.vmdk"

When I rename the other files, XP won't start.

I assume the OS file is really Windows XP.vmdk because its 15GB in size just like XP shows when booted.

So I tried to back it up via Norton Ghost and NT Backup but they both hang midway through with an error from Fusion it self saying something like failed to read Windows XP-000002.vmdk with three options;

Continue

Retry

Abort

I would REALLY hate to start over with XP install as my current image is very custom and I don't have all the install software available to duplicate it.

I don't want my virtual machine taking up ~30GB sinc ethe OS itselff is only 15GB.

Anyone care to enlighten me?

[continuum]

the *-000001.vmdk and the *-000002.vmdk files are snapshots - do NOT rename them manually - this will cause problems.

Can you still start the VM ?




___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[aurfalien]

Hi,

I don't think they are snap shots, as a matetr of fact they aren't.

Recall that the line in the vmx file;

scsi0:0.fileName = "Windows XP-000001.vmdk"

And I have no snapshots according the my snapshot manager.

The vm starts fine.

Whenever I try to combine my vmdk files using this line;

vmware-vdiskmanager -r "Windows XP-000001.vmdk" -t 2 new.vmdk

I get this error 72% through the process;

Convert: 72% done.Failed to convert disk: A file access error occurred on the host or guest operating system (0x5000900000007).

When I run the vmware-vmdiskmanager command, I notice a .lck at the end of those 3 vmdk files I mentioned in my initial post.

So I really doubt they are snapshots, why would my VM start based on a snapshpot file?

Is there any way I can treat the error above?

[continuum]

trust me - this are snapshots and snapshot manager does not tell you the truth

for further investigation we need all last vmware.logs , the vmsd-file, the vmx-file and a filelisting of the directory zipped together




___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[aurfalien]

Hi,

Ok, I have no other choice at this point so I'll take your word for it.

I've attahed zip file, lemme know if you need more.

And thanks again for answering my post, I really appreciate it.

[continuum]

as expected - this are really snapshots you still need - see

scsi0:0.fileName = "Windows XP-000001.vmdk" in the vmx-file

both of the 00000*.vmdk files are needed !

can you please make a new zip ? - several of the files are truncated

it is 5 o clock in the morning here - see you later

Ulli




___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[aurfalien]

Isn't the scsi0:0.fileName option line supposed to be followed by the actual guest file itself and not by a snapshot?

If I replace the arument with any one of the other vmdk files, it won;t boot.

A new zip is attached.

I unziped to test.

5AM, you graveyard shift?

[continuum]

Isn't the scsi0:0.fileName option line supposed to be followed by the actual guest file itself and not by a snapshot?

NO - the scsi0:0.fileName points to the latest snapshot-vmdk - and that file points to the second last snapshot and that again points to the original basedisk.

What is your current situation ?

The vmsd file is blank so snapshotmanager does not display correctly.

You use one piece growing disks which have the description embedded in the large binary file.

I would like to inspect them - can you please read me site http://sanbarrow.com/vmdk-howtos.html#editvmdk

and provide the descriptor.txt from all 3 vmdk-files you have ?

5AM, you graveyard shift?

LOL - yes - I waste a lot of time doing the night shift at VMTN 😉




___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[aurfalien]

It does?

Well, that explains the behavior alright but seems counter intuative to me anyways.

Hope this is what you need;

UPDATE; you have a horrable text editor on this forum.

Files attached.

[continuum]

UPDATE; you have a horrable text editor on this forum.

Please don't use "you" - I have nothing to do with VMware Inc. - I am a user like you

Your latest snapshot is the 000001.vmdk - this one needs the 000002.vmdk - which then needs the basedisk.

The snapshot chain in itself seems to be ok for me.

To get rid of your snapshots I would power off teh VM. Then create a new snapshot - this usually populates the display of the snapshotmanager again.

Once that is done you could delete the snapshots using snapshotmanager one by one.

Do you have enough free disk space ?

___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[aurfalien]

O man, u don't get paid for this?

Hell, I owe your atleast a nice bottle of Scotch!

Ok, vmware has a crappy forum editor

I have enough free space. Once I power off and create a new snapshot, am I free to mod the vmx file to use the correct vmdk file?

I'll move the other files rather then delete until al is well.

I never delete until I am triple certain.

[continuum]

Once I power off and create a new snapshot, am I free to mod the vmx file to use the correct vmdk file?

Wait - there is a big missunderstanding here I guess. There is no reason to correct the vmx-file - not at all.

Please explain why you think so ...




___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[aurfalien]

Because the vmx file goes to the snap shot vmdk (Windows XP-000001.vmdk) instead of the actual vmdk (Windows XP.vmdk).

I thought you said the both teh 000001 and 00002 are snapshots. However my vmx file refs 000001.

Or am I misunderstanding that line? Its not a line that tells Fusion which is the boot vmdk file fpr the OS?

[aurfalien]

I took a snap shot and now have a 3frd file called Windows XP-000003.vmdk being 27GB in size.

This looks to be the sum total of 000001, 000002 and the strait vmdk file.

Do i need atht scsi line in my vmx file calling the 000001.vmdk file.

I'm at a loss.

[continuum]

strange - the new snapshot should be very small at this time.

Does snapshotmanager display snapshots now ?

Do i need atht scsi line in my vmx file calling the 000001.vmdk file.

NO - it should use the 000003.vmdk now

___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[aurfalien]

You are right, the line in my vmx file has been changed to use 000003.vmdk.

Its gonna take a while, but I'm removing the snapshot via the snapshot manager and will report back what it does tomorrow.

Man, the behavior of my Fusion is utter horse pooopy, I mean seriously.

[continuum]

it should be better when all snapshots are removed




___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[aurfalien]

I'll bet you a beer that it will be the same crap-o-doodle and that I have the same 3 vmdk files totalling 27GB even though my OS is only 15GB.

I think I already owe you a bottle of Scotch anyways

[continuum]

if it is still the same after deleting the snapshots with snapshotmanager I would be very surprised

by the way - I hope you don't use "autoprotect"




___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[aurfalien]

When trying to del the snapshot, I keep getting disk errors on reading the 000002.vmdk file.

Is there any way to eliminate the dependacny on this bloody 000001 and 000002 vmdk files? I need to do this by hand.

O, now there are a total of 6 vmdk files, 1-5 and the base file.