Cannot change the size of the virtual disk in a converted VM

Hi, I have converted many physical machines into virtual machines using the VM converter. All off them were converted using the minimum for their HDs size so that the conversion process minutes last as little as possible. Because now there are in all readers of 'C' for all virtual machines only 1 GB of free space I want to resize their virtual disks. The problem is that I can resize them to a larger size, but Windows does not allow me to expand the volume inside Windows. When I want to expand the size of the Windows volume shows me a message saying "the selected volume is a system disk or a boot disk, or it was created in an earlier version of Windows, a basic disk. It cannot be extended.

I am attaching two files. The first is the configuration of the VM. The second is the error that appears inside of Windows. The message is in Spanish cause that Windows is in that languaje, but I have translated from English in the previous paragraph.

Is anyone of you know why this kind of errors appear? Does perform a work around? It seems that the problem is because the converted Convert the HD as a base virtual HD. In this format (Basic) Windows does not allow to expand. You have to change its format in Dynamics to develop, but when you try this error appeard.

The first work-around, I thought to do is to make a picture of this disc with Ghost and try to paste this image into a new hard drive for the virtual machine, but I don't know if it will work.

Thank you.

Warlock.

I have had success in utility Dell ExtPart help to resize on the fly without interruption of service to initialize volumes (drives C :).  Other methods such as attaching the drive as a data volume to another server or using GParted require at least downtime of this virtual machine and often down more than one time.  With ExtPart, I was able to avoid it completely.

Check out this blog for more information post:

http://blogs.kraftkennedy.com/index.php/2009/06/30/expand-virtual-machine-boot-volumes-with-no-downtime/

Tags: VMware

Similar Questions

  • Cannot change the HARD disk parameters in the Bios on Satellite A200

    I can't change the hard disk parameters in the bios for my satellite A200-1The
    This bios does not support changing the parameters of the hard disk for example SATA to IDE?
    BIOS version is: 5.6

    AFAIK in BOS advanced settings you can change mode SATA controller only. You can use the AHCI mode or compatibility.

    I put t understand why do you think you can use IDE mode. What you want to do exactly?

  • cannot resize the virtual disk (vmdk) after successful hyper-v conversion

    Hello

    We are experiencing an environment vSphere 4.1. I have a problem on the Ramdisk resizing.

    We had managed to convert a hyper v VM. Virtual machine operating system is Windows 2008.

    After that, I can't resize the virtual disk (GB in disk options was gray-ed out, even when the virtual machine is power down)

    It's strange

    I have attached several screenshot of the virtual machine.

    Need your advice.

    Thank you

    His grace is on the IDE interface and you can not resize. the only way is to reclone using vmware converter and resize in the wizard. For more information: http://www.yellow-bricks.com/2010/05/28/resizing-your-ide-virtual-harddisk/

  • New OS displays cannot see the virtual disk drive

    I am creating a new of Windows XP virtual machine on a standalone ESX Server using local storage.  After crossing the start of initial installation and learn how to "To install windows press" the next screen says

    «the installation program found no hard disk units installed in your computer»

    I read in a few places this may be due to the poor selection of bus or logic LSI logic when creating the virtual machine, but I tried them both and they both have the same error.

    Is it possible that the problem is the installation media that I use?  Other Installtion disks seem to find storage that I installed a 2003 server.

    Yep for XP, you must:

    VM-> change settings-> disk-> existing Floppy image in the data store-> Browse-> vmimages-> disk-> vmiscsi *.flp

    vcbMC - 1.0.6 Beta

    Lite vcbMC - 1.0.7

    http://www.no-x.org

  • Cannot resize the virtual disk, the virtual machine by using a «child» vmdk file

    Release: VMWare workstation 9

    SE host: Windows 7 64-bit

    Screenshots below.

    I want to resize my VM from 50 GB to 100 GB.

    It seems that VMware workstation 9 uses a child for my VM vmdk.  In my case, using its "Windows Server 2008 R2 x 64 - 000001.vmdk" for its virtual disk file.  The correct file should be "Windows Server 2008 R2 x64.vmdk", I think.

    There are currently no snapshots registered for this virtual machine, I see.

    The virtual machine works well as is, but I can't resize the disk without the VMWare gui, saying I should be perform the operation on the parent vmdk file.

    It seems that I do run a snapshot that is not really a snapshot?  How to merge with the older files - Sxx.vmdk to 0000xx - Sxxx.vmdk

    I also tried to use the command line tool to manually resize the vmdk parent, but I get permission "access denied" errors.

    Kind regards

    Matt

    -------------------------------------------

    Parameters of the HARD disk:

    settings.jpg

    Error:

    Error.jpg

    Files:

    Files.jpg

    He no snapshots are displayed in the Manager of snapshot with the check box 'Show AutoProtect snapshots' verified then the snapshot is an orphan and the best way I use normally to fix this if I want the contents of the snapshot of orphan to be among the basic disk is with tab of the virtual machine in VMware Workstation GUI closed I simply delete the .vmsd file and then open the virtual machine tab in the VMware Workstation GUI and cover and immediately remove a snapshot in the Snapshot Manager.  This will force the orphan snapshot to merge with the parent disk.  Then to clean I still remove the .vmsd file and orphans, .vmsn and .vmem file.

    Note: Before the procedure you have a good backup of the virtual machine in case you accidentally mess something up.

  • Cannot resize the virtual disk

    My vm upgraded allows no expansion vdisk in the pane settings; said must delete all snapshots, yet no old clichés exist. Version 2.0.2 (147997) to run on a MBP 17 "intel 2.16 g.

    Based on list stamps and the date/time of file on the files, you have a snapshot in place and you can try to remove it by trying the following with the not suspended, and Virtual Machine within Windows to stop.

    Take a snapshot, and then immediately delete the snapshot.

    Note: I personally don't do without first making sure that I have all the user data saved from within the Virtual Machine from a store outside of the Virtual Machine and or a manual full copy of all of the Virtual Machine.  Just in case!

  • Please help: the virtual disk parent has changed...

    After a few days of research about this error, I decided that I had to ask for some evidence of your experts to help me recover from this error.

    Thank you!

    It is a small desktop application:

    -Dell T410 esxi Server 5

    -a virtual machine, Windows Server 2003 with 2 discs, no fixed size

    I was help this office by managing services and updates on this Server 2003.  I ran updates on Friday and restarted.  When he came I open vSphere and found the virtual machine does not.  I tried to start it and got the error.  So, it seems I may have the CID issue that needs to be corrected.

    I don't have a direct access to this server so I'm remoting with RDS on 2003 VM server and vSphere on the esxi.  Did I make the right diagnosis and is it possible for me to make the necessary corrections to distance or I need direct access to the server?  Everything I've read has files of people editing CID numbers and it seems that they directly access the esxi server.

    Shows the data store:

    hard 'server '.

    hard 'server_1.

    'server' - 000001.vmdk

    "server_1" - 000001.vmdk

    'server' - snapshot1.vmsn

    I stuck a few newspapers below...

    DISC: Scsi0:0 [OPEN ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' persistent R]
    2012-08 - 05T 20: 00:06.022Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001-delta.vmdk ': open with success (10) size = 5620404224, hd = 213826. Type 8
    2012-08 - 05T 20: 00:06.022Z | VMX | DISKLIB-DSCPTR: open [0]: "Server-000001 - delta.vmdk ' (0xa)
    2012-08 - 05T 20: 00:06.022Z | VMX | DISKLIB-LINK: open ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' (0xa): vmfsSparse, 35526656 sectors / 16.9 GB.
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-flat.vmdk ': open with success (14) size = 18189647872, hd = 181059. Type 3
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-DSCPTR: open [0]: 'server - flat hard' (0xe)
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-LINK: open ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server.vmdk' (0xe): vmfs, 35526656 sectors / 16.9 GB.
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB LINK: DiskLinkIsAttachPossible: incompatibility of the content ID (parentCID f72e60c7! = f05537b3) /vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server.vmdk.
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-STRING: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server.vmdk ': cannot open (the virtual disk parent has changed since the child was created.) The content of the virtual disk ID parent does not match the ID of parent for children's content).
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001-delta.vmdk ': closed.
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-flat.vmdk ': closed.
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-LIB: can't open ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' with the virtual disk 0xa flags parent has changed since the child was created. The content of the virtual disk ID parent does not match the ID of parent for children (18) content.
    2012-08 - 05T 20: 00:06.035Z | VMX | DRIVE: Cannot open disk ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk ': the virtual disk parent has changed since the child was created. The content of the virtual disk ID parent does not match the ID of parent for children (18) content.
    2012-08 - 05T 20: 00:06.035Z | VMX | Msg_Post: error
    2012-08 - 05T 20: 00:06.035Z | VMX | [msg.disk.noBackEnd] unable to open drive ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' or one of the snapshot disks it depends on.
    2012-08 - 05T 20: 00:06.035Z | VMX | [msg.disk.configureDiskError] reason: the virtual disk parent has changed since the child was created. The content of the virtual disk ID parent does not match the ID of parent matching the child content.
    2012-08 - 05T 20: 00:06.035Z | VMX |

    Thanks again for any direction you can provide!

    / r

    John

    The parentCID of the snapshot must match the CID from its parent, as shown in the log file

    "... The content ID mismatch (parentCID f72e60c7! = f05537b3)... »

    Server.VMDK

    CID = f05537b3
    parentCID = ffffffff

    Server - 000001.vmdk

    CID = a2b9ba8b
    parentCID = f72e60c7---> f05537b3

    Make sure you change the file on the host using the vi editor or - if you want to change the file in Windows - use an editor who is aware of the line breaks Unix (do not use Notepad!)

    Once this is done, I highly recommend that you take another cliché before you on the virtual computer. This prevents existing virtual disk files to be modified, so that you can return to this State where you need. After that everything works as expected, consider deleting all snapshots.

    André

  • VMDKMounter gets error "could not open the virtual disk.

    I have two Win7 x 64 virtual machines running fine with VMware Fusion 4.1.2.  I installed VMDKMounter from VMware 3.1.3 and OSXFuse 2.3.9.  I can ride one of the files hard with VMDKMounter very well, but others told "Cannot open the virtual disk" when I try to mount it.

    8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: could not parse the instant string ' / Users/finchr/Documents/VirtualMachines.localized/hoth.univ.dir.wwu.edu.vmwarevm/hoth.univ.dir.wwu.edu.vmx '. 8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: will not be able to take an informed decision, based on partial information. 8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: mount the drive read-only instead. 8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: failed to open the disc: disc encoding error (261993021117)

    The virtual machine that VMDKMounter fails to mount was created by VMware vCenter Converter 5.0 of a physical machine.  The virtual machine that works was created in VMware Fusion 4.

    Of course, the hard I really want to ride with VMDKMounter is he who fails.  No idea how to make so that he can get?

    Well, I see nothing in the disc DescriptorFile which prevents the hard mounted.

    So right now, you can mount other hard files, but not this one, then I have two suggestions...

    It would be to use vmware-vdiskmanager to create a new hard that will not go up and the other would create a new empty hard, then add it to a virtual machine, as well as one that will not go up and then start with appropriate optical disk or an ISO Image containing the appropriate tools/utilities in order to image the drive to the new empty.  I usually use Symantec Norton Ghost for operations like this.  Then maybe a new mounts with VMDKMounter.

  • Cannot change the size of the disk of one of my VM

    Hello

    I use VMCloud to manage the virtual machines for my team. For couple of virtual machines, I am unable to change the size of the disc while reconfiguration. Note that these virtual machines are the clone of one of the other virtual machines.

    EditDiskspaceVM.JPG

    Please suggest.

    Thank you and best regards,

    Françoise

    Post edited by: Abdeali Mandviwala

    Check if virtual machines are instant delete all if present. Snapshots will prevent you from being able to increase the size of the virtual disk to virtual machines.

  • How can I change the size of the virtual disk by default?

    Hello

    At work, we decided to start to allocate more disk space for new virtual machines that we create. and every time I create a new virtual machine, and I pass by the Configuration, the name and location, storage, reviews of operating system and network options. I get to create a disc of the options and the size of the virtual disk is set to 16 GB by default. and then I would need to change before the new virtual machine to a larger number. I thought to myself whence this 16 GB by default is set and is it possible for me to change this value by default for example 30 GB, so whenever I have create a VM I wouldn't need to change this to 30 GB.

    Thank you for taking the time to read this discussion.

    Best regards

    S.A

    It would be a feature "nice to have", if we could set up by default to different operating systems. However, I am not aware of a way to do it. The only thing you can do in a cluster is to create a VM template and clone the new virtual machines from the model.

    André

  • The virtual disk parent has changed since the child was created

    Hi all, need your help with this one.

    I deleted two snapshots and now I can not start the virtual machine.

    Get the following error:

    Reason: The virtual disk parent has changed since the child was created.
    Cannot open disk ' / vmfs/volumes/4c483d34-a8c778c4-46a5-001cc460f09e/WEBPDXXXY/WEBPDXXXY_1-000003.vmdk' or one of the snapshot disks it depends on.

    I tried that link but still did not work KB: http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 1007969

    I can still see the WEBPDXXXY_1 - 000003.vmdk, WEBPDXXXY_1 - 000002.vmdk and WEBPDXXXY_1 - 000001.vmdk when I browse the data store.

    WEBPDXXXY_1 - 000003.vmdk

    # Disk DescriptorFile
    version = 1
    Encoding = 'UTF-8 '.
    CID = 59fab513
    parentCID = a4a63bd5
    isNativeSnapshot = 'no '.
    createType = "vmfsSparse."
    parentFileNameHint = "WEBPDXXXY_1 - 000002.vmdk".
    # Description of the measure
    RW 157286400 VMFSSPARSE ' WEBPDWEBPDXXXY_1-000003 - delta.vmdk.

    # The database disk
    #DDB

    WEBPDXXXY_1 - 000002.vmdk
    # Disk DescriptorFile
    version = 1
    Encoding = 'UTF-8 '.
    CID = a4a63bd5
    parentCID = 0f8995f3
    isNativeSnapshot = 'no '.
    createType = "vmfsSparse."
    parentFileNameHint = "WEBPDXXXY_1 - 000001.vmdk".
    # Description of the measure
    RW 157286400 VMFSSPARSE ' WEBPDXXXY_1-000002 - delta.vmdk.

    # The database disk
    #DDB

    DDB. Deletable = 'true '.
    ddb.longContentID = "ab1b7008e386c884ae920930a4a63bd5".

    WEBPDXXXY_1 - 000001.vmdk

    # Disk DescriptorFile
    version = 1
    Encoding = 'UTF-8 '.
    CID = 0f8995f3
    parentCID = 926f96fa
    isNativeSnapshot = 'no '.
    createType = "vmfsSparse."
    parentFileNameHint = "WEBPDXXXY_1.vmdk".
    # Description of the measure
    RW 157286400 VMFSSPARSE ' WEBPDXXXY_1-000001 - delta.vmdk.

    # The database disk
    #DDB

    ddb.longContentID = "0336846d9f849b4b97ad028f0f8995f3".
    DDB. Deletable = 'true '.

    WEBPDXXXY_1.VMDK

    # Disk DescriptorFile
    version = 1
    Encoding = 'UTF-8 '.

    CID = 926f96fa

    parentCID = ffffffff
    isNativeSnapshot = 'no '.
    createType = "vmfsRawDeviceMap."

    # Description of the measure
    RW 209715200 VMFSRDM ' WEBPDXXXY_1 - rdm.vmdk '.

    # The database disk
    #DDB

    ddb.toolsVersion = "8295.
    ddb.adapterType = "free".
    DDB. Geometry.sectors = "63".
    DDB. Geometry.Heads = "255".
    DDB. Geometry.Cylinders = "13054.
    DDB. UUID = "60 00 C2 92 41 62 5 d 8f-10 59 12 60 53 0 to a8 94.
    ddb.longContentID = "b204c5bc523bbc83c01dd3ed926f96fa".
    ddb.virtualHWVersion = "7".
    DDB. Deletable = 'true '.

    Is there a chance to run ls-lisa from the command line (SSH) in the virtual machine folder and provide the output!

    I ask because I'm a little worried about the timestamp of the hard (May 2011). Depending on the size of the files in the snapshot, it seems that the second virtual disk is not really used by the guest operating system and we could come back manually (by editing the .vmx file) on the resized basic disk (100 GB compared to 75 GB for snapshots) without losing important data!

    If you want to revert manually,

    • delete the virtual machine of the inventory
    • backup and then edit the .vmx file (replace "WEBPDMAPPD_1 - 000003.vmdk" with "WEBPDMAPPD_1.vmdk")
    • Move 3 snapshots in a directory temporary sub
    • Add the virtual machine to inventory
    • create a new snapshot to prevent the current hard files to be modified
    • Turn on the virtual machine

    If everything works as expected, you can delete the snapshot files moved and remove the snapshot created in the Snapshot Manager again.

    André

  • "The virtual disk parent has changed..." "after removing a few shots

    Hey!

    I'm using VMWare Workstation and deleted a few shots via the Snapshot Manager. I used a .vhd Image from the Microsoft Site (Windows Server 2003, x 86). VMWare has created a link to this image at the beginning. I was working on this virtual machine for 2 weeks.

    Now, I have deleted 2 snapshots, including the first snapshot. When I try to start all the existing snapshots the error which is entered in the subject line of this discussion. Detailed error explains that his "cannot open disk 0 - 0000004.vmdk or one of the snapshot disks it costs on.» Reason: the virtual disk parent... »

    How can I access any of the existing snapshots in the future? I read that it is necessary to open the virtual disk images and change the CID of this disk image virtual to who should be the one parent. But how do I edit these virtual disk in windows vista? I have no command line tool that extracts only the first 20 lines of a file so that it will be impossible for me to open a vhdk with 600 or 700 MB. Another problem is that (I don't know why) my virtual disks are splitet in so many parts (I said at the beginning that the virtual disk must be a file, but I think splitet VMWare Workstation it because she had to be converted to .vhd (Microsoft) .vhdk... might be?)

    Here's a screenshot of my file of VMWare this virtual machine sorted by type and sorted by size (for a better overview, I think):

    na ja... Falls die Datei ist - wurde neulich, als VirtualPC platte used sharp available?

    Wenn nein - und nur dann!

    ersetz

    disk-0 - 000002.vmdk

    disk-0 - 000004.vmdk

    mit den editierten aus dem Anhang versions.

    Falls from the dir unsicher bist - nach frag!

    Ulli

    ___________________________________

    VMX-settings- VMware-liveCD - VM-infirmary

  • Save the number of the Virtual Machine: expand the size of the virtual disk of Guest OS affect the physical disk on the host operating system files?

    People,

    Hello. I use 3 Player VM and Guest OS Windows Server 2003. The host OS is Windows 7. I need to increase the size of the VM disk, so who can install several systems in the guest OS. If something bad happens during the expansion of the size of the virtual disk, the guest operating system and its Applications will not work. Thus, before expanding the size of the virtual disk, I need to back up the virtual machine hard disk external.

    I have check the disk hard host operating system Windows 7, the path is C:\VirtualMachine\WindowsServer2003\... When I get to the top of the virtual machine on the external hard drive, simply select the 'VirtualMachine' folder and save automatically. I have 3 questions as follows:

    First of all, if something bad happens during the expansion of the size of the virtual disk, the guest operating system and its Applications do not work. Can I just delete the folder 'VirtualMachine' in the host operating system?

    Secondly, the problem of the first question does not affect files in the physical hard disk to host operating system?

    Third, if something wrong happens during expand the size of the virtual disk of OS guest, I simply delete the folder 'VirtualMachine' in the host operating system and load the original 'VirtualMachine' from the external hard drive in the host operating system. Works correctly as long as one is the Virtual Machine before Stude the virtual disk size?

    Thank you.

    First of all, if something bad happens during the expansion of the size of the virtual disk, the guest operating system and its Applications do not work. Can I just delete the folder 'VirtualMachine' in the host operating system?

    Yes.

    Secondly, the problem of the first question does not affect files in the physical hard disk to host operating system?

    N °

    Third, if something wrong happens during expand the size of the virtual disk of OS guest, I simply delete the folder 'VirtualMachine' in the host operating system and load the original 'VirtualMachine' from the external hard drive in the host operating system. Works correctly as long as one is the Virtual Machine before Stude the virtual disk size?

    Yes.

    That's right, as long as you have not added and other virtual disks of different folders on the host of the virtual machine, you can probably did not.

    After developing the size of the virtual disk, you must also change the size of the partition in the guest operating system.

    André

  • the virtual disk parent changed

    I just did something really stupid and hope someone here could help me...

    I have a virtual host named dev4, that has a snapshot created a year ago.  It has several virtual disks, one of them is dev4 - 000001.vmdk, who has a parent disk dev4.vmdk.

    Today I come to create a new virtual machine named dev5.   My intention was to disparage dev4 and use dev5 moving forward, so I want all my data in the virtual disks of dev4 is available in dev5.

    Now, it's the stupid part.  I added two dev4 - 000001.vmdk and dev4.vmdk (one at a time) to the new machine virtual (dev5) and mounted to them (I was running Fedora in two virtual machines).    It's really successful, but then I can't repeat this process and dev4 won't boot either.  "I got the error message was.

    Details: Cannot open the disc "C:\Virtual Machines\dev4\dev4-000001.vmdk" or one of the snapshot disks it depends on.

    Reason: The virtual disk parent has changed since the child was created.

    "

    Apparently the action to add the dev4.vmdk drive to dev5 or mount in dev5 led her to change.  I have a lot of data in dev4 - 000001.vmdk which are not saved.  Is it possible I could get these restored data?  Right now I can not open this vmdk due the above error.    Any help would be much appreciated!

    Sorry Peter - I guess I was kinda hard...

    It's just that in so many cases users who have encountered a problem with the snapshots do themselves more damage by acting in quick.

    Please read my full vmdk-manual so that you are better prepared next time.

    And now - please read this

    http://sanbarrow.com/VMDK-HOWTOs.html#editvmdk

    We will need it then

    _________________________

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

  • repair broken CID-String > the virtual disk parent has changed since the child was created.

    Hello

    We have ESX 3.5 Update2

    During the withdrawal of one of the many snapshots, the process has been crushed and the CID string seems to be corrupted.

    Now the last work of x file - 000006.vmdk cannot start because the file is based on x - 000004.vmdk.

    Now, I get this message:

    Cannot open disk /vmfs/volumes...x-000007.vmdk or one of the Flash disk that it depends on.

    Reason: The virtual disk parent has changed since the child was created.

    If you provide vmdk small text files, all the vmware.logs, the vmsd file and the vmx file I can look into it

    ___________________________________

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

Maybe you are looking for