VMware Communities
akhelifa
Contributor
Contributor

Cannot start VM - file is already in use

Hi,

I have installed VMware Workstation 6.0 and created a VM which is housing Windows XPPro and installed various pieces of software that I needed making a couple snapshots along the way. Yesterday I booted my machine and tried to make a clone of one the snapshot. It did not let me do that and now whenever I try to start the VM I get the following error message:

"Unable to open file C:\VMWareFiles\WinXP-BaseDisk2.0000001.vmdk. One of the disks in this virtual machine is already in use by a virtual machine or by a snapshot".

I have searched this forum without finding any answers to my problems thus this posting. Can anyone help on this issue?

Many thanks in advance

Abdel

Reply
0 Kudos
90 Replies
cogumel0
Enthusiast
Enthusiast

>>This was a dangerous advice (since snaphots were used)

Not quite, his VM would have been working, only without snapshots. As for the snapshots? Even though the VM was no longer looking for them, they would not be deleted from the disk. Which means that by simply changing the VMX, he would have gotten them back.

Again, no data would have been lost. He ended up manually editing files anyway.

So, in what way was it dangerous?

Reply
0 Kudos
continuum
Immortal
Immortal

>>> VM would have been working, only without snapshots.




>>> Which means that by simply changing the VMX, he would have gotten them back.




!http://sanbarrow.com/gifs/hysterical.gif!

Oliver -we are wasting our time


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
cogumel0
Enthusiast
Enthusiast

>>> VM would have been working, only without

snapshots.

>>> Which means that by simply changing the VMX, he

would have gotten them back.

Oliver -we are wasting our time

Tested and working. Sorry to disappoint you. And who said you are wasting time? Only thing I say is that your methods are not the only ones that work.

I'm not the one saying that by doing what you suggested he will ruin his VM or even VMDK, or even that windows doesn't know how to properly copy or rename a file without damaging it. That was all you mate.

I never said your ways would damage anything nor that they would not work. Simply that they were too time consuming. It's sad when you refuse to hear the truth and admit others might be right and think you are a guru on everything. Even after you said that by simply copying a VMDK or VM you will ruin it.

Reply
0 Kudos
oreeh
Immortal
Immortal

Oliver -we are wasting our time

You are right.

>>> VM would have been working, only without snapshots.

>>> Which means that by simply changing the VMX, he would have gotten them back.

That was one of the best jokes lately - I only fear it wasn't meant as a joke.

Reply
0 Kudos
cogumel0
Enthusiast
Enthusiast

This just proves to show you much you know and you much you think you know.

The problem is I got this working just like I said.

Guess that tomorrow I'll have to make some screenshots of how I managed to miraculously do that and still get it back working by pointing to the snapshots.

Perhaps I'll name it "Damn, I'm good!"

Or maybe I should rename it "Damn, I'm GOD!" seeing as I'll be doing something impossible.

Reply
0 Kudos
oreeh
Immortal
Immortal

Using a disk, which has snapshots, in another VM breaks the CID chain - therefore

>>> simply changing the VMX

isn't sufficient

Reply
0 Kudos
continuum
Immortal
Immortal

God - don't use screenshots - make a video - that can't be faked so easily.

Can't wait to see it.


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
continuum
Immortal
Immortal

Couldn't stand the tension and created the video myself - here is the last screenshot:


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
cogumel0
Enthusiast
Enthusiast

Ohh, I see why... wrong name, you had to use the name 'he is GOD', that's why.

No worries, when the weekend comes I'll make a video of HIM doing it properly.

Reply
0 Kudos
continuum
Immortal
Immortal

Oops - I hope his majesty will gracefully overlook that typo.

May I offer to host the video of HIM doing it properly[/u] on sanbarrow.com so that it can enlighten us lesser mortals still struggling with the mysteries HIM has already solved ?

See you later , GOD


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
FCGuy
Contributor
Contributor

Oliver et al,

I have a similar issue that has happened twice now and I don't want to have to make changes to my image for the third time. I downloaded the tools and ran the report which I am posting here. The way this all began is I had an image and took a snapshot of it. Then made about two days worth of work and decided to clone the image at that point. The internet connection went down and when I logged back into the host server the clone had the correct changes, but the original did not, it had reverted back to the previous snapshot since I could not get into the current one as I was getting the "file already in use message". It was a full clone. I would have used the clone, but we made some changes to demote the clone server from a domain controller and now it was not functioning correctly.

I made my same changes again to the orignal's previous snapshot since the current state of the original had been lost somehow. After I got it back to where I was before cloning, I took a new snapshot and things were looking good. Then the Internet connection went down again and when I logged in a second time the system told me that I could not log into the VM because the vmdk file was already in use. I could see on the VM server that there were two remote desktop logins to the server so I logged one of them out and rebooted the server but still I could not access the VM, I deleted the lck files and I read all through this thread trying not to get too distracted by cujo's snide remarks here and there about how it should be done. I think he was trying to help in his weird way, but it just kept distracting me from what we are trying to do here. I tried some of HIS ideas to see if the file was Locked by the files system, etc. Nothing seems to indicate that the file should be locked and yet it is locked in its own way and it is driving me insane. I have requested a VPC image of the same server be sent to me from my partner company because I cannot hardly deal with this VMWare locking issue. Any help would be greatly appreciated.

Here is my vmreport.txt: I think most of those vmdk files were created from me trying to get one snapshot or another to work and going back and forth and nothing would allow me to get to my current state or to my previous working snapshot which I called: "Added Document Class".

VM report created 2/6/2008 4:2 UTC

OS: Win2003 MSWin32

##############################

      1. directory contents of E:/K2KL_IMG

##############################

Date (modified) | Size | Permissions | Filename

-


----


--
+
--


Wed Jan 23 20:11:31 2008 | 18911 | rw-rw-rw- |K2BP 1.3-Snapshot1.vmsn

Wed Feb 27 14:55:27 2008 | 1887436800 | rw-rw-rw- |K2BP 1.3-Snapshot2.vmem

Wed Feb 27 14:55:27 2008 | 17935077 | rw-rw-rw- |K2BP 1.3-Snapshot2.vmsn

Fri Feb 29 21:12:03 2008 | 18986 | rw-rw-rw- |K2BP 1.3-Snapshot3.vmsn

Tue Mar 4 02:03:50 2008 | 18986 | rw-rw-rw- |K2BP 1.3-Snapshot4.vmsn

Wed Mar 5 16:54:49 2008 | 8684 | rw-rw-rw- |K2BP 1.3.nvram

Wed Mar 5 16:54:49 2008 | 1785 | rw-rw-rw- |K2BP 1.3.vmsd

Wed Mar 5 16:54:49 2008 | 2056 | rw-rw-rw- |K2BP 1.3.vmx

Mon Mar 3 16:21:47 2008 | 304 | rw-rw-rw- |K2BP 1.3.vmxf

Fri Feb 29 21:11:09 2008 | 2715287552 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk

Fri Feb 29 17:34:06 2008 | 881197056 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000002.vmdk

Mon Mar 3 18:02:22 2008 | 170852352 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000003.vmdk

Mon Mar 3 18:02:47 2008 | 4128768 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000004.vmdk

Mon Mar 3 22:16:28 2008 | 168558592 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000005.vmdk

Mon Mar 3 22:34:58 2008 | 4128768 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000006.vmdk

Mon Mar 3 22:49:49 2008 | 136183808 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000007.vmdk

Mon Mar 3 22:58:12 2008 | 4128768 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000008.vmdk

Tue Mar 4 02:01:02 2008 | 278200320 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk

Wed Mar 5 12:51:06 2008 | 4128768 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000010.vmdk

Wed Mar 5 16:13:22 2008 | 4128768 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000011.vmdk

Wed Mar 5 16:18:27 2008 | 118226944 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000012.vmdk

Wed Mar 5 16:39:41 2008 | 4128768 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000013.vmdk

Wed Mar 5 16:51:25 2008 | 4128768 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000014.vmdk

Wed Mar 5 16:52:00 2008 | 4128768 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000015.vmdk

Wed Mar 5 16:54:11 2008 | 7274496 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk

Wed Mar 5 19:25:54 2008 | 4128768 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1-000017.vmdk

Mon Dec 17 15:25:14 2007 | 8154185728 | rw-rw-rw- |K2BP-000003-cl1-000004-cl1-000001-cl1.vmdk

Wed Mar 5 23:02:36 2008 | 1175618 | rwxrwxrwx |vmreport.exe

Wed Mar 5 23:02:57 2008 | 0 | rw-rw-rw- |vmreport.txt

Wed Mar 5 16:51:25 2008 | 59043 | rw-rw-rw- |vmware-0.log

Wed Mar 5 16:18:28 2008 | 51055 | rw-rw-rw- |vmware-1.log

Tue Mar 4 02:01:04 2008 | 52892 | rw-rw-rw- |vmware-2.log

Wed Mar 5 16:53:10 2008 | 49470 | rw-rw-rw- |vmware.log

##############################

      1. vmxfile K2BP 1.3.vmx

      2. Created: Mon Feb 25 20:30:25 2008

      3. Modified: Wed Mar 5 21:54:49 2008

##############################

config.version = "8"

virtualHW.version = "6"

memsize = "1800"

MemAllowAutoScaleDown = "FALSE"

MemTrimRate = "30"

displayName = "K2BP 1.3"

guestOS = "winnetstandard"

tools.remindInstall = "FALSE"

sound.present = "TRUE"

sound.virtualDev = "es1371"

sound.filename = "-1"

sound.autodetect = "TRUE"

floppy0.present = "TRUE"

floppy0.autodetect = "TRUE"

floppy0.filename = ""

usb.present = "TRUE"

ethernet0.present = "TRUE"

ethernet0.addressType = "generated"

ethernet0.connectionType = "bridged"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "K2BP-000003-cl1-000004-cl1-000001-cl1-000017.vmdk"

pciBridge0.present = "TRUE"

ehci.present = "FALSE"

ide0:0.present = "TRUE"

ide0:0.autodetect = "TRUE"

ide0:0.filename = "auto detect"

ide0:0.deviceType = "cdrom-raw"

scsi0.present = "TRUE"

scsi0.virtualDev = "buslogic"

floppy0.startConnected = "FALSE"

virtualHW.productCompatibility = "hosted"

tools.upgrade.policy = "manual"

usb.generic.autoconnect = "FALSE"

numvcpus = "1"

isolation.tools.hgfs.disable = "FALSE"

ide0:0.startConnected = "FALSE"

ethernet0.generatedAddress = "00:0c:29:91:4c:8a"

uuid.location = "56 4d ef 2c fe ec 9b 33-df a5 3b 04 cb 91 4c 8a"

uuid.bios = "56 4d ef 2c fe ec 9b 33-df a5 3b 04 cb 91 4c 8a"

scsi0:0.redo = ""

pciBridge0.pciSlotNumber = "17"

scsi0.pciSlotNumber = "16"

ethernet0.pciSlotNumber = "32"

sound.pciSlotNumber = "33"

ethernet0.generatedAddressOffset = "0"

checkpoint.vmState = ""

floppy0.fileType = "device"

floppy0.clientDevice = "FALSE"

tools.syncTime = "FALSE"

checkpoint.vmState.readOnly = "FALSE"

sharedFolder.option = "alwaysEnabled"

RemoteDisplay.vnc.enabled = "FALSE"

RemoteDisplay.vnc.port = "25225"

RemoteDisplay.vnc.key = "GCsEKDkyESkaLAAiMzUDJSwXDQonMBgQJyUCARwmCQUPGCUEFRsQMBI8IgMrOgEGPBsUBA8hDDIHBxISPicBADUzABYnBiASKxsyIBguKAgVPAg0Gx0GAhgjOAgqOQAJPTcBECQHJgMrDhEoPAwQDDI0DBETHyIELioNCR0bICg="

nvram = "K2BP 1.3.nvram"

extendedConfigFile = "K2BP 1.3.vmxf"

inVMTeam = "FALSE"

sound.startConnected = "FALSE"

ethernet0.vnet = "VMnet1"

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=8717acf8

parentCID=ffffffff

createType="monolithicSparse"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1.vmdk"

  1. The Disk Data Base

#DDB

ddb.geometry.biosSectors = "63"

ddb.geometry.biosHeads = "255"

ddb.geometry.biosCylinders = "4079"

ddb.virtualHWVersion = "6"

ddb.toolsVersion = "7238"

ddb.geometry.cylinders = "4079"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.adapterType = "buslogic"

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1.vmdk has wrong size! Expected size: 33554432000 - Actual size: 8154185728

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=9fe5a21b

parentCID=8717acf8

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk"

  1. The Disk Data Base

#DDB

ddb.toolsVersion = "7238"

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk has wrong size! Expected size: 33554432000 - Actual size: 2715287552

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000002.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=2ed960c3

parentCID=22200de9

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000002.vmdk"

  1. The Disk Data Base

#DDB

ddb.toolsVersion = "7238"

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000002.vmdk has wrong size! Expected size: 33554432000 - Actual size: 881197056

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000003.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=884c275e

parentCID=9fe5a21b

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000003.vmdk"

  1. The Disk Data Base

#DDB

ddb.toolsVersion = "7238"

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000003.vmdk has wrong size! Expected size: 33554432000 - Actual size: 170852352

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000004.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=9fe5a21b

parentCID=9fe5a21b

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000004.vmdk"

  1. The Disk Data Base

#DDB

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000004.vmdk has wrong size! Expected size: 33554432000 - Actual size: 4128768

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000005.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=0b132a79

parentCID=9fe5a21b

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000005.vmdk"

  1. The Disk Data Base

#DDB

ddb.toolsVersion = "7238"

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000005.vmdk has wrong size! Expected size: 33554432000 - Actual size: 168558592

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000006.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=9fe5a21b

parentCID=9fe5a21b

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000006.vmdk"

  1. The Disk Data Base

#DDB

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000006.vmdk has wrong size! Expected size: 33554432000 - Actual size: 4128768

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000007.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=b4d5842e

parentCID=9fe5a21b

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000007.vmdk"

  1. The Disk Data Base

#DDB

ddb.toolsVersion = "7238"

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000007.vmdk has wrong size! Expected size: 33554432000 - Actual size: 136183808

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000008.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=9fe5a21b

parentCID=9fe5a21b

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000008.vmdk"

  1. The Disk Data Base

#DDB

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000008.vmdk has wrong size! Expected size: 33554432000 - Actual size: 4128768

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=e5c58736

parentCID=9fe5a21b

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk"

  1. The Disk Data Base

#DDB

ddb.toolsVersion = "7238"

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk has wrong size! Expected size: 33554432000 - Actual size: 278200320

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000010.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=e5c58736

parentCID=e5c58736

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000010.vmdk"

  1. The Disk Data Base

#DDB

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000010.vmdk has wrong size! Expected size: 33554432000 - Actual size: 4128768

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000011.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=e5c58736

parentCID=e5c58736

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000011.vmdk"

  1. The Disk Data Base

#DDB

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000011.vmdk has wrong size! Expected size: 33554432000 - Actual size: 4128768

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000012.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=c05be0a6

parentCID=9fe5a21b

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000012.vmdk"

  1. The Disk Data Base

#DDB

ddb.toolsVersion = "7238"

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000012.vmdk has wrong size! Expected size: 33554432000 - Actual size: 118226944

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000013.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=e5c58736

parentCID=e5c58736

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000013.vmdk"

  1. The Disk Data Base

#DDB

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000013.vmdk has wrong size! Expected size: 33554432000 - Actual size: 4128768

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000014.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=9fe5a21b

parentCID=9fe5a21b

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000014.vmdk"

  1. The Disk Data Base

#DDB

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000014.vmdk has wrong size! Expected size: 33554432000 - Actual size: 4128768

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000015.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=e5c58736

parentCID=e5c58736

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000015.vmdk"

  1. The Disk Data Base

#DDB

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000015.vmdk has wrong size! Expected size: 33554432000 - Actual size: 4128768

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=b921a3d7

parentCID=9fe5a21b

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk"

  1. The Disk Data Base

#DDB

ddb.toolsVersion = "7238"

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk has wrong size! Expected size: 33554432000 - Actual size: 7274496

If this is a sparse disk you can ignore this warning

##############################

      1. K2BP-000003-cl1-000004-cl1-000001-cl1-000017.vmdk

##############################

  1. Disk DescriptorFile

version=1

CID=e5c58736

parentCID=e5c58736

createType="monolithicSparse"

parentFileNameHint="K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk"

  1. Extent description

RW 65536000 SPARSE "K2BP-000003-cl1-000004-cl1-000001-cl1-000017.vmdk"

  1. The Disk Data Base

#DDB

The following problems where detected:

- Extent K2BP-000003-cl1-000004-cl1-000001-cl1-000017.vmdk has wrong size! Expected size: 33554432000 - Actual size: 4128768

If this is a sparse disk you can ignore this warning

##############################

      1. logfile vmware.log

##############################

Mar 05 16:52:32.859: vmx| Log for VMware Workstation pid=660 version=6.0.2 build=build-59824 option=Release

Mar 05 16:52:33.812: vmx| DISK: OPEN scsi0:0 'E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk' persistent R[(null)]

Mar 05 16:52:34.125: vmx| DISKLIB-DSCPTR: Opened : "K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk" (0xa)

Mar 05 16:52:34.125: vmx| DISKLIB-LINK : Opened 'E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk' (0xa): monolithicSparse, 65536000 sectors / 32000 Mb.

Mar 05 16:52:34.140: vmx| DISKLIB-DSCPTR: Opened : "K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk" (0xe)

Mar 05 16:52:34.140: vmx| DISKLIB-LINK : Opened 'E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk' (0xe): monolithicSparse, 65536000 sectors / 32000 Mb.

Mar 05 16:52:34.171: vmx| DISKLIB-DSCPTR: Opened : "K2BP-000003-cl1-000004-cl1-000001-cl1.vmdk" (0xe)

Mar 05 16:52:34.171: vmx| DISKLIB-LINK : Opened 'E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1.vmdk' (0xe): monolithicSparse, 65536000 sectors / 32000 Mb.

Mar 05 16:52:34.171: vmx| DISKLIB-LIB : Opened "E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk" (flags 0xa). 196333C

Mar 05 16:52:34.171: vmx| DISK: OPEN 'E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk' Geo (4079/255/63) BIOS Geo (4079/255/63) freeSpace=10730Mb, buslogic

Mar 05 16:52:34.390: vmx| DISKUTIL: scsi0:0 : capacity=65536000

Mar 05 16:52:34.390: vmx| DISKUTIL: scsi0:0 : geometry=4079/255/63

Mar 05 16:52:34.390: vmx| DISKUTIL: scsi0:0 : toolsVersion = 7238

Mar 05 16:52:37.218: vmx| VMX_PowerOn: ModuleTable_PowerOn = 1

Mar 05 16:52:37.578: vcpu-0| DISKUTIL: scsi0:0 : toolsVersion = 7238

Mar 05 16:52:37.812: vcpu-0| DISKUTIL: scsi0:0 : toolsVersion = 7238

Mar 05 16:52:38.484: vcpu-0| DISKUTIL: scsi0:0 : toolsVersion = 7238

Mar 05 16:52:38.656: vcpu-0| DISKUTIL: scsi0:0 : toolsVersion = 7238

##############################

      1. VMDKs mentioned in vmware.log

##############################

Mar 05 16:52:33.453: vmx| DICT scsi0:0.fileName = K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk

Mar 05 16:52:33.812: vmx| DISK: OPEN scsi0:0 'E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk' persistent R[(null)]

Mar 05 16:52:34.125: vmx| DISKLIB-DSCPTR: Opened : "K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk" (0xa)

Mar 05 16:52:34.125: vmx| DISKLIB-LINK : Opened 'E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk' (0xa): monolithicSparse, 65536000 sectors / 32000 Mb.

Mar 05 16:52:34.125: vmx| FILE: ScanDirectory discarding file 'E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk.lck\M53718.lck'; invalid executionID.

Mar 05 16:52:34.140: vmx| DISKLIB-DSCPTR: Opened : "K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk" (0xe)

Mar 05 16:52:34.140: vmx| DISKLIB-LINK : Opened 'E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk' (0xe): monolithicSparse, 65536000 sectors / 32000 Mb.

Mar 05 16:52:34.140: vmx| FILE: ScanDirectory discarding file 'E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1.vmdk.lck\M48751.lck'; invalid executionID.

Mar 05 16:52:34.171: vmx| DISKLIB-DSCPTR: Opened : "K2BP-000003-cl1-000004-cl1-000001-cl1.vmdk" (0xe)

Mar 05 16:52:34.171: vmx| DISKLIB-LINK : Opened 'E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1.vmdk' (0xe): monolithicSparse, 65536000 sectors / 32000 Mb.

Mar 05 16:52:34.171: vmx| DISKLIB-LIB : Opened "E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk" (flags 0xa). 196333C

Mar 05 16:52:34.171: vmx| DISK: OPEN 'E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk' Geo (4079/255/63) BIOS Geo (4079/255/63) freeSpace=10730Mb, buslogic

Mar 05 16:52:34.171: vmx| USBGW: Skipping disk backing for file (E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk).

Mar 05 16:52:34.171: vmx| USBGW: Skipping disk backing for file (E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk).

Mar 05 16:52:34.171: vmx| USBGW: Skipping disk backing for file (E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1.vmdk).

Mar 05 16:52:34.234: vmx| USBGW: Skipping disk backing for file (E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1.vmdk).

Mar 05 16:52:34.265: vmx| USBGW: Skipping disk backing for file (E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk).

Mar 05 16:52:34.296: vmx| USBGW: Skipping disk backing for file (E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk).

Mar 05 16:52:34.312: vmx| USBGW: Skipping disk backing for file (E:\K2KL_IMG\K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk).

##############################

      1. disk descriptor tables

##############################

Filename | CID | pCID | createType | parentFileNameHint

-


----


--
+

+
--


K2BP-000003-cl1-000004-cl1-000001-cl1.vmdk | 8717acf8 | ffffffff | monolithicSparse | -none-

K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk| 9fe5a21b | 8717acf8 | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000002.vmdk| 2ed960c3 | 22200de9 | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000003.vmdk| 884c275e | 9fe5a21b | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000004.vmdk| 9fe5a21b | 9fe5a21b | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000005.vmdk| 0b132a79 | 9fe5a21b | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000006.vmdk| 9fe5a21b | 9fe5a21b | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000007.vmdk| b4d5842e | 9fe5a21b | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000008.vmdk| 9fe5a21b | 9fe5a21b | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk| e5c58736 | 9fe5a21b | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000010.vmdk| e5c58736 | e5c58736 | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000011.vmdk| e5c58736 | e5c58736 | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000012.vmdk| c05be0a6 | 9fe5a21b | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000013.vmdk| e5c58736 | e5c58736 | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000014.vmdk| 9fe5a21b | 9fe5a21b | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000015.vmdk| e5c58736 | e5c58736 | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000016.vmdk| b921a3d7 | 9fe5a21b | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000001.vmdk

K2BP-000003-cl1-000004-cl1-000001-cl1-000017.vmdk| e5c58736 | e5c58736 | monolithicSparse | K2BP-000003-cl1-000004-cl1-000001-cl1-000009.vmdk

##############################

      1. CID chain(s) according to vmdks

##############################

8717acf8 - -> 9fe5a21b -> 2ed960c3 -> 884c275e -> 9fe5a21b -> 0b132a79 -> 9fe5a21b -> b4d5842e -> 9fe5a21b -> e5c58736 -> e5c58736 -> e5c58736 -> c05be0a6 -> e5c58736 -> 9fe5a21b -> e5c58736 -> b921a3d7 -> e5c58736

      1. END OF REPORT ###

Reply
0 Kudos