Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Storage vMotion fails with a generic DMotion error (1009113)

Last Updated: 4/7/2021Categories: TroubleshootingTotal Views: 30910Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Storage vMotion fails or is interrupted.

Storage vMotion fails at 99% and throws the following message: ERROR: A specified parameter was not correct. spec"

A generic DMotion error displays on the console in the Remote Command-Line Interface (RCLI).

In VirtualCenter or VMware Infrastructure (VI) Client connected directly to an ESX host, the virtual machine appears running or stopped in the Inventory.

If you right-click the virtual machine and select one of the hard disks, it references a DMotion file instead of the VMDK.

If you right-click the virtual machine in VirtualCenter, the Power and Snapshot options are not available.

If you right-click the virtual machine in VirtualCenter, the Complete Migration option is available, but it does not work.

The .vmx and vmware.log files are moved to the destination datastore but have duplicates in the original datastore. The files in the original datastore contain original virtual machine information.

The DMotion*-delta.vmdk and the VMName*-flat.vmdk files may remain on the source volumes or may be moved to the destination datastore.

Resolution

If this issue occurs, power-down the virtual machine and try to cold migrate the disks.

If cold migration fails, you must restore the original VMDK file.

To restore the original VMDK file without data loss, perform the following steps in order. If step 1 does not resolve the issue, proceed to Step 2. If Step 2 does not resolve the issue, proceed to Step 3. Do not skip a step.

If the virtual machine has independent persistent disks, you must shut the virtual machine down and change the setting to not independent. When you have gone through the following steps, you may revert the disk configuration back to being independent persistent. For more information, see Storage VMotion Requirements and Limitations in the Basic System Administration guide for your version of the VMware product.

Step 1

If the orphaned virtual machine appears in the Inventory, remove it from VirtualCenter.

Alternatively, try to re-register the virtual machine to the ESX host:

Open VI Client and log in as root directly to the ESX host on which you want to register the virtual machine.

Use the datastore browser and navigate to the .vmx file for the virtual machine.

Right-click on the .vmx file and choose Add to Inventory.

Use the wizard to register the virtual machine on the host. This entry replaces the orphaned entry in VirtualCenter.

Note: If this procedure fails, then remove the virtual machine from the VirtualCenter Inventory.

Verify the DMotion chain by checking the CID and Parent CID of the DMotion disks. Look at the .vmdk files of the virtual machine disks referenced in the Destination datastore .vmx file.

Note: A virtual machine disk may not have a DMotion disk. You are looking for DMotion files that were left behind.

If the DMotion chains are not broken, run these commands on the destination .vmx file.

To confirm that the virtual machine does not have any snapshots, run the command:

vmware-cmd vm-cfg-path hassnapshot

The output hassnapshot()= confirms that there are no snapshots.

To create a valid snapshot, run the command:

vmware-cmd vm-cfg-path createsnapshot name description quiesce memory

To delete all snapshots, run the command:

vmware-cmd vm-cfg-path removesnapshots

This command commits the DMotion snapshot and the snapshot you created in step 3b.

Step 2

From VI Client pointed at the ESX host directly, go into the snapshot manager and delete all snapshots.

If the virtual machine is stuck in Virtual Center, you may be unable to remove the virtual machine from the inventory and may have to remove the ESX host that the virtual machine is registered to.

Backup the . vmx file in the destination datastore.

Edit the .vmx file to remove all references to DMotion parents:

scsiX:X.DMotionParent = ""

The destination .vmx file now contains accurate information.

Delete the VMSD Snapshot Database file in the destination datastore.

Remove the virtual machine from the ESX host with the command:

vmware-cmd -s unregister vm-cfg-path

If you removed the ESX host from Virtual Center, add it back.

Add the virtual machine back to VirtualCenter using the datastore browser.

Note: If there are duplicate files (such as vmx, vmsd, logs, vmxf, nvram) in the source directory, they can now be deleted.

Step 3

Use the vmkfstools -i command on the original disk to copy the hard drive.

Remove the new VMDK files from the new datastore by removing the reference to them in the .vmx file.

Open an SSH session to the host and run a command similar to:

vmkfstools -i /src/original.vmdk /dest/copyof.vmdk

When the clone of the VMDK is completed, edit virtual machine settings to add the new copy of the original disk in the destination folder.

Power on the virtual machine.

Related Information

For related information, see:

Moving virtual machines with Storage vMotion (1005544)

Storage vMotion operation fails with the error: Insufficient disk space on datastore (1008171)

Moving a single virtual disk using Storage vMotion using the command line
Moving virtual machines with Storage vMotion
Storage vMotion operation fails with the error: Insufficient disk space on datastore

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Error: Não é possível conectar-se ao MKS durante a conexão com o Remote Console (2150981)

KB
•
Error: No se puede conectar al MKS mientras se conecta a la consola remota (2150981)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant