Problema vmdk eliminado

Similar Questions

• Problem VMDK file large cluster in a box

  So I've been running a flavor of vmware server 2.x since its release with little or no problems. Not that it matters but my host server is a Dell Poweredge 1900 with 32 GB of RAM, running windows server 2003 x 64.  I have also 2 Windows VM that I run as a cluster in a box, and they worked very well in this way for more than 3-4 years at the time of vmware 1.x. Both virtual machines have been set up exactly as such:

  SCSI 0:0 16GB & lt; - c drive

  1:0 500 MB & lt; - quorum SCSI cluster

  SCSI 1:1 12GB & lt; - the app cluster disk

  1:2 950 GB SCSI & lt; - storage of cluster disk

  SCSI 1:3) 12 GB & lt;-the sql cluster disk

  1:4 250 GB & lt; - disk SCSI storage of additional cluster

  What I did recently to set up a new file 2 TB since vmware server 2.x vmdk will now allow you to make files vmdk bigger than the old limit of 950 GB. This new 2 TB file was supposed to replace my 2 readers of old SCSI 1:2 and 1:4 SCSI cluster storage. After making the swap and copy all data to a vmdk file again, I noticed a problem at any moment I'm going to and move the resource cluster VMDK new 2 TB to the other server. Basically the two servers stop responding and it seems that vmware server choke on the 2 TB for some reason vmdk file any. Here's what I see in my logs any time that this happens.

  01:21:47.953 02 Dec: vmx | scsi0:0: READ command (10) took 23,142 seconds (ok)

  01:21:47.953 02 Dec: vmx | scsi0:0: READ command (10) took 23,142 seconds (ok)

  01:21:47.953 02 Dec: vmx | scsi0:0: READ command (10) took 23,142 seconds (ok)

  01:21:47.953 02 Dec: vmx | scsi0:0: READ command (10) took 23,142 seconds (ok)

  01:21:47.953 02 Dec: vmx | scsi0:0: READ command (10) took 23,142 seconds (ok)

  01:21:47.953 02 Dec: vmx | scsi0:0: READ command (10) took 23,142 seconds (ok)

  01:21:47.953 02 Dec: vmx | scsi0:0: READ command (10) took 23,142 seconds (ok)

  01:21:47.968 02 Dec: vmx | SCSI1:2: READ command (10) took 45,504 seconds (ok)

  01:22:46.062 02 Dec: vmx | SCSI1:2: RELEASE (6) command took 5,235 seconds (ok)

  01:22:46.093 02 Dec: vcpu-0 | DISC: Resync'ing disc scsi1:2.

  01:23:08.593 02 Dec: vcpu-0 | DISKLIB-DSCPTR: open : 'storage3.vmdk' (0x6a)

  01:23:08.593 02 Dec: vcpu-0 | DISKLIB-LINK: opened 'e:\virtual_machines\storage\storage3.vmdk' (0x6a): monolithicSparse, 4194304000 sectors / 2.0 TB.

  01:23:08.593 02 Dec: vcpu-0 | DISKLIB-LIB: open "e:\virtual_machines\storage\storage3.vmdk" (flags 0x6a).

  01:23:08.609 02 Dec: vmx | SCSI1:2: READ command (10) took 22,527 seconds (ok)

  01:24:15.640 02 Dec: 1 vcpu. DISC: Resync'ing disc scsi1:0.

  Has anyone ever ran across this or has anyone ever used a file vmdk of this size as a cluster resource? As I said before that I had 0 problems with my cluster before I added this new 2 TB vmdk file...

  I'm not at all surprised that you get this problems.

  You use monolithicSparse vmdk type!

  For cluster in a box, I highly recommend flat VMDK.

  I wonder that it worked for you all with the drive more sharing

  ___________________________________

  VMX-settings- VMware-liveCD - VM-infirmary

• Problem of cluster Failover MS after physical RDM conversion to VMDK

  Hello

  Last week I had to migrate 7 x 2-nodes virtual MS Failover clusters to a new data center. All clusters have been configured with the configuration of the cabin and all shared disks were in physical RDM mode.

  The target data center does not RDM disks so I had to convert all RDM disks VMDK files and use config before the migration of the IPC.

  I used vmkfstools to convert VMDK eagdrzeroedthick RDM files.

  5 clusters have been migrated successfully, but two cluster got strange question even if the procedure for all groups was the same.

  So in two groups, I have a problem where the second node in the cluster can not put online some of the shared disks. The first nodes in the clusters have no problem with the disks/SSP.

  But when I try to failover of all services, the second node may not bring online disc 1 or 2 shared, even if she can put the other shared disks online.

  VMKernel.log is not errors or warnings. I checked the configuration of virtual machines and everything seems OK.

  Any ideas what I could check?

  Just in case anyone else is facing the same problem.

  I could not find the root cause of the problem, even if it's without a doubt the conversion that triggered the problem. However, we found quite a simple solution - added new shared VMDK files, copied the files over and replaced the defective discs.

• Problem fixing existing vmdk to the new virtual machine

  Hello

  Just upgraded to Fusion 6 and things seem ok (except for the dreaded license bug, but it's ok now).

  I'm having a problem attaching a form of virtual disk existing a VM - operation - existing. Basically, all the vmdk files are grayed out and non-eligible, regardless of the option to share / copy / to support the disc.

  I checked that I have full R/W access to the fie (and it works fine if I fire up the other virtual machine).

  Any idea?

  Well I ended up adding another player new to the virtual machine, I wanted to and the drafting of the description of disk (Disk DescriptorFile #)

  in the manually - vmdk file works great...

• Problem after convertin vdi-> vmdk with vboxmanager

  Hello

  I've been using virtual box for a long period of time, and now I'm migrating to Vmware VSphere ESXi5. I've converted all the machines in the vdi in vmdk using the virtualbox tool called vboxmanage. After that, I was able to run these machines in ESXi5 without any problems after installing client tools to improve performance. I have only one question... Suppousing the name of the virtual machine was Client.vdi, then it is Client.vmdk. When I run the Client.vmdk in Vmware, it actually works a machine called Client - s001.vmdk, and then Client.vmdk a 0 KB, which gives the entire disk for the Client-a s001.vmdk new space. If I create a new virtual machine and delete the old I load disc customer - s001.vmdk as a whole disk space. If I do, Vmware then creates a new customer-s001 - s001.vmdk... and so on.

  What can I do to avoid generating this "snapshots" or something else?

  Thank you very much

  Kind regards

  Matias

  If jorge.vmdk really has a size of zero, something very strange happens here

  normally, you would use jorge.vmdk
  (jorge.vmdk and jorge - flat hard together actually form the virtual disk)

• VMDK + instant cause performance problems?

  Can think VMDK w / snapshots causing problems of performance by any chance?

  I'm on vSphere 4.1 (esxi)

  vmchr1s wrote:

  Can think VMDK w / snapshots causing problems of performance by any chance?

  I'm on vSphere 4.1 (esxi)

  Yes and no.

  Let's say you have VM - 1.  VM-1-snp (snapshot)

  If you have a database running on a virtual machine, and you create a snapshot, the data is READ in VM - 1.vmdk and WRITES to VM - 1 - snp.vmdk but databases need an AREA of IO, so go back and fourth could cause a problem.

  Otherwise performance is not normally a problem with the shots... space is the issue, and the time to commit data is the biggest problem, because your discs/SAN will take a major during the snapshot delete / validate the data.

• VM shrink and vmdk problem, please please help, thank you

  I have VM win Server r2, I have to shrink the virtual machine but I can't find VM tool in Control Panel. what I do to reduce its size it became now 30 GB!

  PS. vmdk is divided by 31 files in this virtual machine.

  Please your help is so appreciated, I have many virtual machine in the same status.

  The VMware Tools GUI has been removed because it has now integrated with the Virtual Machine settings, however you can still use the command line.  Note: The path on 64-bit Windows operating systems will be: C:\Program Files (x 86) \VMware\VMware Tools

  1. C:\Program VMware Tools > vmwaretoolboxcmd help
  2. Usage: vmwaretoolboxcmd [options] [AUTOMAGIC]
  3. Type ' help vmwaretoolboxcmd ' for help on a specific command.
  4. Type "vmwaretoolboxcmd - v" to see the version of VMware Tools.
  5. Use "-q" option to remove the output to stdout.
  6. Most orders take a subcommand.
  7. Available commands:
  8. device
  9. disc
  10. script
  11. STAT
  12. time
  13. Update (not available on all operating systems)

• Mount VMDK problem

  Hello

  I have a hard time with mount vmdk downloaded from the data store.

  I use VMware Virtual Disk Development Kit. (Tried other methods without success)

  I tried to mount the 3 existing vmdk.

  1 xyz.vmdk - 1 K

  2 xyz - flat hard - 60 GB

  3 xyz - ctk.vmdk - 3 MB

  As you can see below only xyz.vmdk mounting is successful and he set up the partition reserved Windows system (100 MB)

  What I am doing wrong. Of course, I need to access the files DISHES.

  Thank you.

  *************************************88

  c:\Program Files (x 86) \VMware\VMware Virtual Disk Development Kit\bin > vmware-soft
  NT j: e:\vmdk\xyz.vmdk

  c:\Program Files (x 86) \VMware\VMware Virtual Disk Development Kit\bin > vmware-soft
  NT k: e:\vmdk\xyz-flat.vmdk
  Impossible to mount the virtual drive. The disk can be used by a virtual
  machine, may not be enough volume or mounted under another drive
  letter. If this is not the case, check that the file is a valid virtual disk file.

  c:\Program Files (x 86) \VMware\VMware Virtual Disk Development Kit\bin > vmware-soft
  NT k: e:\vmdk\xyz-ctk.vmdk
  Impossible to mount the virtual drive. The disk can be used by a virtual
  machine, may not be enough volume or mounted under another drive
  letter. If this is not the case, check that the file is a valid virtual disk file.

  c:\Program Files (x 86) \VMware\VMware Virtual Disk Development Kit\bin >

  Thank you very much.

  Worked well.

• Problem with vmdk file based in Win7 - missing lost cause?

  Hello

  I have used VMWare for a good years now without incident, until today.

  I have a VM that today seems to have lost its base vmdk file.

  I think that the disk storage ran out of room when the pc has been closed for the last, but it seems odd this missing file.

  It is worth noting that the virtual machine was actually suspended rather close.

  Here's a screenshot of what looks like the directory.

  There was no 7.vmdk Windows' file and I could not recover despite some drive train recovery tools.

  So my question is, is it a lost cause?

  The file that is there now, I copied from one of the other virtual machines and renamed it (not that it works) in the hope that I could continue somehow.

  I have read that these files are linked and the parent / child ID must be defined, but all discussions talk about modifying the files and I don't seem to be able to do this in windows. Is there a tool for this or I'm wasting my time?

  I did a lot of research and reading without result, so thought I'd come and ask the experts

  I'm a little confused on the different vmdk files.

  Given the dates, I suppose it works actually in the file-000002, since the others do not appear to have been changed in a while.

  If this is the case, why I need another and somehow I can come back by using only a single file and release a load of disk space?

  It also means that the 000002 file displays the current status of the disk in it?

  None of the other virtual machines has more than a vmdk file.

  Any help would be greatly appreciated.

  Thank you very much

  John.

  

  replaced basedisk has done a good job - John is to copy its files to a second vmdk now - can't say anything about their status at the present time.

  The fact that the partition was visible and could not repair the partitiontable or bootsectors makes it look promising

  Ulli

• Problemas para fazer download vmdk

  Olá, bom dia

  Tenho duas maquinas tolls rodando em um servidor esx1 4.1 em um datacenter, preciso fazer o download dessas maquinas porque vou em configura las um outro servidor esxi 4.1, sempre as tento fazer o download recebo a mensagem "connection to server timeout".

  Hate me help a resolver esse problema?

  Grato pela usual colaboracao.

  Veja is you ajuda (num esx, mas pode dar but ideas pra voce esta):

  http://communities.VMware.com/thread/186287

• Problem in a mount vmdk file: could not get a VIM ticket for this virtual disk.

  Hello

  I have a virtual machine on ESX 3.0.1

  When I get the file vmdk directly from ESX, it gets mounted successfully from the command prompt using the mount utility.

  But when I try to mount the vmdk by VI file it displays error "Unable to get a VIM ticket for this virtual disk" on the command line.

  I tried this for other virtual machines also and most of them work.

  What is the reason for the error "unable to get a ticket for this virtual disk VIM.

  How can I get this vmdk file mounted by VI?

  Can you show the virtual computers view of inventory? The image you show of hosts and Clusters discovered.

  Thank you

  Annick

• Report on the VMDK way

  Hello all,.

  Had a problem last week which was extended because of troubleshooting the vmdk evil.  A new server has been online and was renamed in vCenter and the windows at the old production server name.  Because the name of the folder was not the same as the name of the server there was a confusion and ended up working on the bad vmdk. That is - this has been worse than the new server was updated to the data store same old production and has not yet been deleted, so when I watched the news of vFoglight he showed the same data store. Does anyone know if vFoglight has the path stored somewhere for each vmdk vmdk full?  It would have saved us about 2 hours of downtime.

  Thank you

  Craig

  Hello Craig,.

  Not sure if the path of the actual vmdk file is listed everywhere however you get the property vmPathName for each virtual machine in the Sctipt Console, which displays the path to the vmx file. I could be wrong, but I think that the folder contains a file vmdk as well.

  Concerning

  Additional accessories:

  • 
    Untitled.bmp
  • Untitled. JPG

• Recover a file VMDK Snapshoted / consolidate a snapshot

  Hello

  I have a very big problem and I don't know how to deal with in the right way, I had a few old server that was set up with the weekly snapshots.

  and we have some hardware problem with the server that cause some files to capture instant adeleted the data store ccidentally.

  We can recover some of the vmdk files.

  image attached with files you can find on the server.

  We tried a few steps in order to recover the machine (change on vm vmdk configure / create a new snapshot, and delete everything in the Snapshot Manager)-I was able to turn it on with the flat vmdk, but the data is less 6 months ago.

  I found a few articles on consolidate an instant snapshot and difficulty of string but I did not really understand how to go about it.

  What should I do? Is it possible to merge these files or extract files from them?

  

  Okay, so what I found in the files and file sizes I rebuilt an instant string possible.

  The string is: 5-> 4-> 1->->->-> db1.vmdk 6 2 14

  I had to modify two files hard (see attachment). The first fix was on no. 14 that indicated a snapshot does not exist n13. The (next) one parent that makes sense here is no. 2, so I went no. 14, no. 2. The second challenge was to change the parrentCID No. 6 to match the basic disk CID. The reason for this shift is more likely, because you have turned on on the virtual machine with db1. vmdk used as virtual virtual machine disk.

  What I recommend you do now, is to replace the two .. the VMDK (12 and 6) files with those that I have attached to this post and then clone the virtual disk from the command line by running vmkfstools-i db1 - 000005.vmdk db1 - clone.vmdk

  The next step is to attach the newly created clone as an additional virtual disk with a help of VM, or - if you want to see if the VM is able to start - fix it db1 - clone.vmdk directly on the virtual machine from db1. In the second case, please create a new snapshot before you turn the virtual machine with the cloned virtual disk. In this way that the db1 - clone.vmdk will not be changed.

  In no case be prepared there could be corruption in the file system of the client!

  André

• -files ctk.vmdk keep coming back.

  Hey guys,.

  I have problems with the ctk files - keep reappearing.  I am aware that this has to do with the change block Tracking (CBT) but I need it disabled.  With this licence, I am unable to properly use VMWARE JETTÉ TOOL COMMENTS BACK (get them).  I think that it is a tool to backup old Dr. VEEAM that allowed them in the first place, but since we moved to 6.0 VMWARE replication we need more CBT.  Here is what I do to turn it off, but it keeps turned on again.

  I downloaded and used the script from the following link:

  https://www.Veeam.com/kb1113

  Basically, it resets the CBT without having to stop the machine.  Sets the " " ctkEnabled "value to " false.

  After he is executed, the '-ctk.vmdk ' files disappear and I am able to use the tool COMMENTS BACK to the freespace Windows operating system through VMWARE, which in turn transmits the information to my SAN.  Whole slim and trim!

  After about one day, CBT gets reactivated on its own and the '-ctk, vmdk "files reappear.  I don't know if this has something to do with the way I'm disabling online or another software is kind of allow.  If it is because I have to stop the machine so he could stick so I'll do so during our next scheduled maintenance window.

  Any info will be appreciated.

  Thank you.

  The script you mentioned is usetr for the RESETTING of the CBT so it essentially disables CBT creates the snapshot and deletions of snapshots and activate CBT return.

• Format disk VSANS for 3.0 is not / / failure realign suite virtual items SAN / / due to the confinement or the absence of file descriptor vmdk, requiring a manual correction.

  Hi all

  After the upgrade of "6.0 Update 2" and try to update the disc format to version 3.0, I received the error message below.

  Impossible to change the route following the virtual items SAN:

  be4db256-0ab4-9801-c523-0cc47a3a34ca, c2bcb056-5d5f-0f02-f096-0cc47a3a3320, c0bcb056-70a6-180c-c583-0cc47a3a3320, e413b256-90b5-dd1a-cce6-0cc47a3a34ca, c2bcb056-64aa-ee1e-0bb3-0cc47a3a3320, c0bcb056-4b47-5529-b59d-0cc47a3a3320, 6644b256-e0f8-3338-737d-0cc47a3a34ca, d411b256-08ea-f83b-9774-0cc47a3a34ca, c0bcb056-a489-9541-efbe-0cc47a3a3320, 3f6abc56-28fd-4a48-4f8a-0cc47a3a34ce, d411b256-784F-a45a-714d-0cc47a3a34ca, c1bcb056-6671-c45c-2254-0cc47a3a3320, 3f6abc56-1061-ab60-e4c8-0cc47a3a34ce, f17bb356-fcdf-3469-502-a-0cc47a3a3320, cfe8b156-606f-ee6a-4356-0cc47a3a34ce, d411b256-4450-3777-e3bf-0cc47a3a34ca, c1bcb056-b24e-cb7a-7b1a-0cc47a3a3320, f17bb356-f008-9581-2468-0cc47a3a3320, 31bdb056-0a02-4882-9094-0cc47a3a34ca, c1bcb056-2a83-a596-ed2c-0cc47a3a3320, f17bb356-08a1-529f-c375-0cc47a3a3320, c1bcb056-4edc-FFAF-bf04-0cc47a3a3320, c1bcb056-c9e2-fec8-1930-0cc47a3a3320, c1bcb056-4e92-e4e4-9b92-0cc47a3a3320-e413b256-dcd0-f6fd-8ae2-0cc47a3a34ca,

  due to the confinement or the absence of file descriptor vmdk, requiring a manual correction.

  Does anyone has an idea to solve this problem?

  The articles and the script are now available to resolve this problem. A more permanent solution is in preparation.

  Details of the issue, including links to the scripts and KBs are here - http://cormachogan.com/2016/03/31/vsan-6-2-upgrade-failed-realign-objects/

  Thank you for your patience.