Storage VMotion (SVMotion) Failed ... Now what??

[bill_french]

I was storage vmotioning two vms using akutz's plugin, when apparently the migration failed. The reason stated in virtual center: "the parent virtual disk has been modified since the child was created."

Now the virtual machine will not power on. Suggestions?

[opbz]

never used akutz's plugin but from what I know of storage vmotion

here are the steps of what it does to your VMDKs.

pDisk relocation uses snapshot technology to move virtual disks

pSnapshot VM disks to create child disks

pCopy read-only base disks to new location

pCommit disk snapshots into copied base disks

As a final step after everything else is done it deletes the original VMDKs.

So in your case check your original datastore do you still have the VMDKs? If you have any snapshots on there are you able to delete them using snapshot manager?

Are you able to power VM on from original datastore?

[TonyF]

Just had similar storage vMotion failure. In viewing the source and target LUNs, noticed all files appeared to have transferred from source to target successfully. Here's what worked for me (probably just dumb luck).

• Created new virtual machine using the custom option and added an existing virtual disk (i.e., the .vmdk file on the target LUN).

Powered on new target machine successfully. Deleted remnants on source.