michele_distasi
Enthusiast
Enthusiast

Convert W2k hang at 2%

When converting this w2k server ,the converter hang at 2% . This is the log. Could you help me ?

Tags (1)
0 Kudos
4 Replies
J_Wright
Enthusiast
Enthusiast

Have you ran a chkdsk /f and a defrag on the drive?

0 Kudos
vmroyale
Immortal
Immortal

I've corrected this problem on HP servers by upgrading the controller firmware and drivers on the source server to the latest levels.

Brian Atkinson | vExpert | VMTN Moderator | Author of "VCP5-DCV VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550" | @vmroyale | http://vmroyale.com
0 Kudos
theegg
Contributor
Contributor

I had the same problem once. I found that the services-agent were not running on the physical machine to be copied. I installed the converter on the machine itself, rebooted it, and ran the converter from the Windows 2K machine, and that solved the problem.

0 Kudos
admin
Immortal
Immortal

Firstly you should use the latest version of VMware Converter which is 3.0.3 and it can be downloaded from http://www.vmware.com/download/converter/

As suggested in this thread already, you should upgrade the firmware of the RAID controller in your server and also run a "chkdsk" on all of the volumes that exist in this machine.

The try the conversion again, but this time do not include the OEM / Diagnostic partition in the conversion. These volumes / partitions are identified in the converter logs as driveLetter = "
?\Volume{72d19a10-7fca-11d6-9e5d-806d6172696f}". You can see by the question mark,that it has no drive mapping. These OEM partitions should never be included in a conversion, because they will not be needed in the new VM. They are only used by the hardware of the physical server.

If it fails, then either post the new "vmware-converter-x.log" here in this thread or else open support request with VMware.

Regards,

Graham

0 Kudos