Merger of the snapshot disks failed

Similar Questions

• Could not open the vmdk disk or one of the snapshot disks it depends on

  I upgraded vmware fusion 1.x to 2.08, because I was getting the message

  Cannot open disk - hard or one of the snapshot disks it depends on.

  Reason: Cannot lock the file.

  So I thought that would fix it, but it didn't. I can't figure out how to fix it either. At home, I'm a PC user and use VMware player, but at work, we use Mac OS X and the merger.

  Here ARE THE CONTENTS of my VMX file

  ____________________________________

  . Encoding = 'UTF-8 '.
  config.version = '8 '.
  virtualHW.version = "7".
  MemAllowAutoScaleDown = "FALSE".
  pciBridge0.present = 'TRUE '.
  insulation. Tools.hgfs.Disable = "FALSE".
  deploymentPlatform = "windows".
  virtualHW.productCompatibility = "hosted".
  RemoteDisplay.vnc.port = '0 '.
  Tools.Upgrade.Policy = "upgradeAtPowerCycle".
  powerType.powerOff = 'soft '.
  powerType.powerOn = 'soft '.
  powerType.suspend = 'soft '.
  powerType.reset = 'soft '.
  gui.exitonCLIHLT = 'TRUE '.
  displayName = "WindowsXP_IE7."
  NVRAM = "WindowsXP_IE7.nvram."
  memsize = "664".
  guestOS = "winxppro.
  Sound.Present = 'TRUE '.
  sound.fileName = "-1".
  Sound.AutoDetect = "TRUE".
  sound.startConnected = 'TRUE '.
  USB. Present = 'TRUE '.
  EHCI. Present = 'TRUE '.
  USB. Generic.AutoConnect = "FALSE".
  ide0:0. Present = 'TRUE '.
  ide0:0. FileName = "winxp - 000001.vmdk".
  ide0:1.present = 'TRUE '.
  ide0:1.startConnected = 'TRUE '.
  ide0:1.DeviceType = "cdrom-raw"
  ide0:1.AutoDetect = 'TRUE '.
  ethernet0. Present = 'TRUE '.
  ethernet0. ConnectionType = "bridged".
  ethernet0.startConnected = 'TRUE '.
  ethernet0.wakeOnPcktRcv = "FALSE".
  floppy0. Present = 'TRUE '.
  floppy0.startConnected = "FALSE".
  floppy0.filetype = 'file '.
  floppy0. FileName = ' / Users/user/Library/Parallels/winxp/unattended.fdd '.
  floppy0.clientDevice = "FALSE".

  ethernet0. AddressType = 'generated '.
  UUID. Location = "56 4 d a7 74 d0 99 9 c - d2 70 b1 d0 25 18 9 c 5A ac"
  UUID. BIOS = "56 4 d a7 74 d0 99 9 c - d2 70 b1 d0 25 18 9 c 5A ac"
  extendedConfigFile = "WindowsXP_IE7.vmxf".
  ide0:0. Redo = «»
  pciBridge0.pciSlotNumber = "17".
  ethernet0.pciSlotNumber = "32".
  sound.pciSlotNumber = "33".
  ehci.pciSlotNumber = "34".
  ethernet0.generatedAddress = "00: 0C: 29.6 d: 01:00.
  ethernet0.generatedAddressOffset = '0 '.
  ide0:1.filename = "automatic detection".
  tools.syncTime = "FALSE".

  checkpoint.vmState = «»

  sharedFolder.option = "onetimeEnabled".
  sharedFolder.maxNum = '1 '.
  sharedFolder0.present = 'TRUE '.
  sharedFolder0.enabled = 'TRUE '.
  sharedFolder0.readAccess = 'TRUE '.
  sharedFolder0.writeAccess = 'TRUE '.
  sharedFolder0.hostPath = ' / users/person/SharedVMWare.
  sharedFolder0.guestName = "SharedVMWare".
  sharedFolder0.expiration = "never".

  pciBridge4.present = 'TRUE '.
  pciBridge4.virtualDev = "pcieRootPort"
  pciBridge4.pciSlotNumber = "21".
  pciBridge4.functions = '8 '.
  pciBridge5.present = 'TRUE '.
  pciBridge5.virtualDev = "pcieRootPort"
  pciBridge5.pciSlotNumber = "22".
  pciBridge5.functions = '8 '.
  pciBridge6.present = 'TRUE '.
  pciBridge6.virtualDev = "pcieRootPort"
  pciBridge6.pciSlotNumber = "23".
  pciBridge6.functions = '8 '.
  pciBridge7.present = 'TRUE '.
  pciBridge7.virtualDev = "pcieRootPort"
  pciBridge7.pciSlotNumber = "24".
  pciBridge7.functions = '8 '.
  vmci0. Present = 'TRUE '.

  MKS. Enable3D = 'TRUE '.

  ethernet0.linkStatePropagation.enable = 'TRUE '.

  Marked as supposed to answer

  André

• Could not open the drive or one of the snapshot disks it depends on.

  My becomes partition error "Cannot open the disc or one of the snapshot disks it depends on." and will not run. I could use some help, and after searching for similar entries in the support community, I decided to post my file "supported".  Any help would be appreciated.

  My com: MacBook Pro with Snow Leopard version 10.6.4

  Partition: Windows 7 Ultimate 64-bit

  Take a look on: Boot Camp virtual machine fails to power on

• Had to reinstall my CS3 because of faulty hard drive. It does not accept my serial number as it says it is already used the maximum number of activations and says I should turn off. I can't as the hard disk failed! Please help.

  Had to reinstall my CS3 because of faulty hard drive. It does not accept my serial number as it says it is already used the maximum number of activations and says I should turn off. I can't as the hard disk failed! Please help.

  Have already tried to contact Adobe and they told me to reinstall the program. I did this and the same issue. It's crazy. I can not turn off something that I did not more...

  Thank you.

  No - I had, of course, tried all these things. Finally, I had someone (after several days) on the personal chat group that could fix and it did it in a few minutes. Too bad that nobody else seemed to be able to do. Adobe is very soft.

  I can't thank enough the other person - it was amazing.

• When I tried to power on VM ends up in the right error: the specified file is not a virtual disk. Cannot open disk ' / vmfs/volumes/4d48ad95-ad5e027a-67f4-e41f1360cc9e/Iso/ser01/ser01.vmdk' or one of the snapshot disks it depends on.

  I stop a virtual machine after a certain time, I tried to power. Its has ended up in the following error message

  Reason: The specified file is not a virtual disk. Cannot open disk ' / vmfs/volumes/4d48ad95-ad5e027a-67f4-e41f1360cc9e/Iso/ser01/ser01.vmdk' or one of the snapshot disks it depends on.

  The machine was working fine before the closure.

  In the data store, the file type of the virtual machine is 'file' instead of 'virtual drive '.

  Help, please

  You are missing the file descriptor hard. The xxxx - flat hard is the file that contains the data effectively. But the xxxx.vmdk is missing, which is a text file that connects to the flat file.

  AWo

• Cannot open disk ' * hard ' or one of the snapshot disks it depends on. Reason: One of the parameters is not valid.

  I have 4 virtual servers running on a host ESX 4. 3. run OK but 1 gives the following error when you choose works in Vsphere client.

  Cannot open disk ' * hard ' or one of the snapshot disks it depends on. Reason: One of the parameters is not valid.

  I have attached the log file and the list of files in the folder of servers.

  Any help much appreciated.

  Welcome to the community,

  This virtual machine successfully powered on since July 23?

  To me, it seems that something went wrong with the clichés (I guess they are / were created by a backup application). Due to the size of the files I guess more that snapshots were created and not modified.

  If this is the case, you can delete the virtual machine to inventory, edit the vmx file by

  replacement of

  scsi0:1.filename = LHMU-VIC04_1 - 000004.vmdk

  with

  scsi0:1.filename = LHMU - VIC04_1.vmdk

  then right-click on the vmx file in browser data store and add it to the inventory.

  Before adding it to the inventory, delete the snapshot vmdk files (those with '00000 x' in their file names) as well as the vmsd file. BTW, you can also remove the zdump file if you want.

  If you are not sure if snapshots contain valid data, take a look at the (small) header files vmdk. If the CID and the parentCID match, snapshots were created while the virtual machine has been powered down.

  If you are not sure, please post back before doing anything.

  André

• Impossible to create capture instant for VM1, error-3941 (create the snapshot has failed)

  I vSphere 4.0.0 208111 using VDR 1.1.0.707 appliance for backup of a Windows Server 2003 SP2 with VMware tools installed (including the VSS component).

  I am unable to back up a VM, but can save all other virtual machines.

  Have tried to re - install VMware tools, ensuring Windows VSS patches are up to date.

  I can do a ntbackup to system within the virtual machine with success status.

  Impossible to find someone else suffer the same error with-3491, create the snapshot has failed.

  Any ideas?

  Paul

  To simulate a VDR initiated snapshot, try a manual snapshot of the virtual machine and see if it passes or fails.  If it fails, then that explains the error 3941.  Be sure to uncheck the memory status and check the comments of quiesce file system option during an attempt of the manual snapshot because it will mimic the snapshot operation that initiates the VDR.

• 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:

  

  Error:

  

  Files:

  

  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.

• On the deletion of the snapshot

  Hello

  I have a guest host ESXi 4.1 with a BONE (Cesto). The total space of the VMFS(data store) score is 550 GB. Out of 550 only 25 GB is now available. There are 4 snapshot of this OS (the last is 250 and the first 45 GB) Guest. I want to remove the snapshot 1.

  1. which is the best way to remove this snapshot?

  2. If I want to delete the snapshot using vSphere Client, what are the effects of negetive.

  The client is a server hosting with 200 clients, so I can't bare the downtime. Please give me a better way to do it. If possible, please provide the links to complete these steps.

  Thanks in advance.

  Basically, I agree with continuum and cloning would be the safest way to do this clean up. However if I understand the situation, you should be able to delete the snapshots with the virtual machine without interruption of service. What I realized, this is:

  • you run ESXi 4.1
  • data store size Go 550, 25 GB free
  • all snapshots appear in the Snapshot Manager
  • the virtual machine is the only VM on this data store
  • VM has a thick drive put in service (adding the size of the files, this should be the case)

  can you confirm this?

  In this case, you can remove the first snapshot (the one closest to the basic disk) without needing additional disk space, with the exception of the changes that go to the most recent snapshot. With 25 GB of free disk space, that should be ok! After the first snapshot was merged on the basic disk, you should have 80 additional GB of free disk space (according to timestamps, 000002.vmdk snapshot file is the oldest snapshot, the file names are not necessarily in ascending order), in which case you can now decide to continue to clean up snapshots by one or by using 'Delete All' to get rid of all snapshots.

  André

• Cannot issue the open disk

  Hi all

  I have ESXi installed on our server. I received a few VM folders with our test WHAT VM inside our office in europe. Using the vSphere Client I downloaded the files for the virtual machine for the farm data store, but when I try to start the virtual machine, I get one:

  Cannot open disk ' / vmfs/volumes/xxxxxxxx-xxxxxxxx-xxx-xxxxxxxxxxx/VM_files/BASE_VM_xxxxxxxx/xxxxxxxx/theapparentlymissingfile.vmdk ' or one of the snapshot disks it depends on.
  The system cannot find the specified file.

  I have gone through the forums here and on Google and tried several of the corrections proposed such as the removal of the. VMDK.lck file. There was another who proposed changing the vmx file and change the name of the file that is the same as the one I had.

  The file is there, but for some reason, he doesn't see it. y at - there something I am missing being new to VMware. I have to start from scratch, if I can't get these working locally.

  Thanks in advance

  You can download the http://kb.vmware.com/kb/1023856 tool (see "Accessories").

  To convert the virtual disk to an ESXi supported format run

  VMware - vdiskmanager.exe - r 'Digipos book PC SP1.vmdk' t 4 "Digipos book PC SP1 - new.vmdk.

  then download the two newly created files ("Digipos book PC SP1 - new.vmdk ' and Digipos book PC SP1-new - flat hard') on the ESXi host and change the settings for the virtual machine, i.e. to remove the bad virtual disk and add the right pair.

  Please be aware that the resulting virtual disk will have a size of 40GB.

  André

• Error: the capacity of the disk virtual parent and the child disk capacity are different (67).

  Hello

  I tried to increase the hard drive of a machine space of 10 GB for a 20 GB virtual linux. I closed down the VM, then ssh was in the ESXi server. From there on, I ran the command:

  vmkfstools x 20 G Apatite.vmdk

  The command was executed successfully. Then, when I turned on the virtual machine I had and still do me:

  Reason: The capacity of the disk virtual parent and the child disk capacity are different.
  Cannot open disk ' / vmfs/volumes/503fd5b8-d1cef086-eb4a-10bf487b38db/Apatite/Apatite-000001.vmdk' or one of the snapshot disks it depends on.

  I tried many things such as the cloning of the Apatite.vmdk of Apatite - repaired.vmdk. That works, however, I get an old version of the virtual machine. I do not receive my changes of Apatite - 000001.vmdk or Apatite-000001 - delta.vmdk.

  I have a very important job on my VM that I am restoring. I should have backed up before doing anything else I've done. Now, it seems that I pay the price.

  Can someone help me get my VM? Is it possible to increase the size of the snapshot (Apatite - 000001.vmdk) or reduce the size of the parent so that they match, and the virtual machine start?

  Help, please.

  Thank you

  Apatite - 000001.vmdk
  # Disk DescriptorFile
  version = 1
  Encoding = 'UTF-8 '.
  CID = 79c3c056
  parentCID = cf2ec09b
  isNativeSnapshot = 'no '.
  createType = "vmfsSparse."
  parentFileNameHint = "Apatite.vmdk"
  # Description of the measure
  RW 41943040 VMFSSPARSE ' Apatite-000001 - delta.vmdk.
  # The database disk
  #DDB
  ddb.longContentID = "11ad79de6b5a5fe9218cfd7179c3c056".
  ddb.toolsVersion = "9216.
  modified entries are marked in red
  After you have made the changes - do NOT start the virtual machine
  Instead, remove from inventory and run
  vmkfstools 'Apatite - 000001.vmdk'-i 'consolidated.vmdk' d slim
  When did edit the vmx file and replace
  scsi0:0. FileName = 'Apatite - 000001.vmdk ".
  with
  scsi0:0. FileName = "consolidated.vmdk".
  now, you can save the VM again.

• 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é

• 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é

• Cannot add the Flash disk

  Hello

  I came into work this morning to find one of our servers in a State that won't start plu.

  This virtual server is hosted on an ESXi 3.5.0 123629 server with two data warehouses.

  The following error occurred when trying to start the server.

  Please check that the path is valid and try again. Cannot open disk 'path to the file DEVSQL1_1 - 000001.vmdk' or one of the snapshot disks it depends on. Reason: The system cannot find the specified file.

  When you browse the data store, I could see the vmdk file.

  I learned later that the DEVSQL1_1.vmdk file has been moved to the another data store.

  Unfortunately, at this time, I removed the hard drive that was pointing to the file - 000001.vmdk if I could add a new hard disk that points the moved file from DEVSQL1_1.vmdk.

  Server started the first pop, except that the data stored on the disk problem are old.

  At this point, I stop the server and moved the DEVSQL1_1.vmdk file to its original location. Then, I removed the disc newly added and tried to add a hard drive pointing to the original DEVSQL1_1 - 000001.vmdk. When you do this I get the error "object reference is not set to an instance of an object" and I am unable to go further.

  When open the Snapshot Manager, I am unable to see relating to this disk snapshots.

  Anyone know how I can join the DEVSQL1_1 - 000001.vmdk disc in order to start the server and also have access to current data?

  Thank you very much

  Glen

  Glen - I don't think we should use this DEVSQL1 - 000001.vmdk snapshot

  I have no evidence that it has been used in the history of this virtual machine.
  It does not fit to the size of its parent disk.

  Do you remember if DEVSQL1.vmdk has been developed in the history of this virtual machine?

  Edit the vmx and change

  scsi0:0. FileName = 'DEVSQL1 - 000001.vmdk ".
  TO
  scsi0:0. FileName = "DEVSQL1.vmdk".

  It was also the State used when the machine virtual last started successfully.

  Honestly, I was a little surprised when you found this DEVSQL1 - 000001.vmdk

  You have an idea about this?

  After editing the vmx file the VM must start - when starting carefully inspect the condition = if it is out of date turn off directly.

  I doubt you'll see an out-of-date status - but if the first disk is expired I must expand the snapshot - that would be a bit strange

• 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