Failed in 2% (Creating cloning to target)

[mssc97]

We installed ESX 3.5 in DL580 G5 and we failed convert a Win2003 SP2 physical system (DL380 G4).

1. Try convert using Hot Clone --> failed. Vmware converter agent not up.

2. Try convert using cold clone default size disk --> Failed in 2% (Creating cloning to target)

3. Try convert using cold clone with min disk size --> Progress seems stack in 6% progress (creating cloning to target)

Not sure if the below issue causes the issue, pls help and comment:

vmware-client-0.log:

...

Unsetting unknown path: /vmomi/

Making sure that UFAD interface has version vmware-ufad-p2v30-build-62456

UFAD interface version is vmware-ufad-p2v30-build-62456

Shutting down VMDB service...

Unregistering callback...

...

vmware-converter-0.log:

...

Unsetting unknown path: /vmomi/

Making sure that UFAD interface has version vmware-ufad-p2v30-build-62456

UFAD interface version is vmware-ufad-p2v30-build-62456

Shutting down VMDB service...

Unregistering callback

...

Thanks.

[mssc97]

attach the client log as well.

[theanykey]

Opening file vm_name/vm_name.vmdk (ha-nfc://[xxx-xx] vm_name/vm_name.vmdk@x.x.x.x:902)

timed out waiting for data

x.x.x.x:902 with error invalid NBD error code.

NfcNetTcpWrite: bWritten: -1 err: 10053

send failed:

Can you verify that ports 443 and 902 are open between the physical machine and ESX? You can do so using telnet such as:

telnet x.x.x.x 902

A success is anything other then an unsuccessful failure message such as "host is not reachable".

[mssc97]

Thanks for the reply and suggestion.

We have tried the telnet from the physical machine (Win 2003 SP2) to the ESX with port 902, no problem was found. And also we have checked the network connection from the physical machine to VC and ESX, and VC to the physical machine and ESX, everything works correctly.

Any other suggestion?

[theanykey]

Can you try again without resizing? Also, ensure all NIC settings on all end-points are correctly set to full duplex.

[vmroyale]

I had an HP blade (bl20p) do something similar. It would never move past 2%, no matter how long I waited. Updating the firmware and drivers for the array controller on the source box was what finally did the trick for that P2V.

Good Luck!

[mssc97]

Thanks for suggestion.

We have resolved the issue by converting the physical machine to workstation first then converted again to ESX.