VMware Communities
DanlOfRI
Contributor
Contributor
‎06-21-2017 05:28 AM

Clone failure - The parent of this virtual disk could not be opened

I have a virtual machine where I added a second hard drive. I mapped this drive to a folder in the Windows OS. However, since I added the second hard drive, cloning of the machine fails with the error indicated above.

I can create snapshots correctly.

Cloning is an important part of resiliency for our build workflow, and adding the second drive is also important as I cannot expand the drive.

I am fairly certain this relates to the second disk I added. Is there anything I can do to fix this short of deleting the drive?

Looking at the VM, I see 'seconddrive.vmdk', which I assume is the parent of the second drive.

Contents of SecondDrive.vmdk

# Disk DescriptorFile

version=1

encoding="windows-1252"

CID=b2aba194

parentCID=ffffffff

isNativeSnapshot="no"

createType="twoGbMaxExtentSparse"

# Extent description

RW 4192256 SPARSE "SecondDrive-s001.vmdk"

RW 4192256 SPARSE "SecondDrive-s002.vmdk"

RW 4192256 SPARSE "SecondDrive-s003.vmdk"

RW 4192256 SPARSE "SecondDrive-s004.vmdk"

RW 4192256 SPARSE "SecondDrive-s005.vmdk"

RW 4192256 SPARSE "SecondDrive-s006.vmdk"

RW 4192256 SPARSE "SecondDrive-s007.vmdk"

RW 4192256 SPARSE "SecondDrive-s008.vmdk"

RW 4192256 SPARSE "SecondDrive-s009.vmdk"

RW 4192256 SPARSE "SecondDrive-s010.vmdk"

RW 4192256 SPARSE "SecondDrive-s011.vmdk"

RW 4192256 SPARSE "SecondDrive-s012.vmdk"

RW 4192256 SPARSE "SecondDrive-s013.vmdk"

RW 4192256 SPARSE "SecondDrive-s014.vmdk"

RW 4192256 SPARSE "SecondDrive-s015.vmdk"

RW 4192256 SPARSE "SecondDrive-s016.vmdk"

RW 4192256 SPARSE "SecondDrive-s017.vmdk"

RW 4192256 SPARSE "SecondDrive-s018.vmdk"

RW 4192256 SPARSE "SecondDrive-s019.vmdk"

RW 4192256 SPARSE "SecondDrive-s020.vmdk"

RW 40960 SPARSE "SecondDrive-s021.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "5221"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "3ccf9c09120efb7d998f303db2aba194"

ddb.uuid = "60 00 C2 95 01 eb f8 5b-d2 63 58 21 70 8e 74 8b"

ddb.virtualHWVersion = "10"

Note that in the file directory, there are 176 files listed as SecondDrive-s. I suspect that the 'extra' related to previous snapshots, but I am not sure of that.

0 Kudos
2 Replies
continuum
Immortal
Immortal
‎06-21-2017 07:03 AM

The info you provide is insufficient.
Please post a complete filelisting, current vmx-file of the VM you try to clone and last 2 vmware.logs.
Please use the "attach" function rather than pasting the content.


________________________________________________
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
DanlOfRI
Contributor
Contributor
‎07-10-2017 05:41 AM

My solution was as follows:

  1. I restored a cloned Virtual Machine prior to creating the second hard drive.
  2. I then expanded the current hard drive to meet my needs. This was the original reason I added the second hard drive in the first place.
  3. Now cloning and creating snapshots works correctly.
0 Kudos