I am trying to convert a pysical server with Windows 2003 and 2 drives. I have been able to convert similar servers before with no trouble, but this one keeps failing with the error attached. I have tried both the stand alone converter and using converter through vCenter. I have looked through the forums and none of the other post with similiar errors seems to work for me. Any ideas how I can get to converted.
please tell us at which percentage and with which error message it failed
___________________________________
VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay
Volume bitmap retuned offset 4FB30 while requested offset is 4FB32
NfcNetTcpRead: bRead: -1 err: 10054
Error 5666 writing to the destination volume
NfcFssrvrRecv: failed with code = 8
NfcFssrvr_DiskIo: failed to receive io reply
DISKLIB-LIB : RWv failed ioId: #33394 (5666) (34) .
NFC - Network File Copy
Looks like it's having an issue sending the data to the destination. Is there a firewall in place anywhere in between the phys system and dest ESX host? Going across WAN or non-gigabit links anywhere along the way? Also, try changing duplex/speed to/from auto to manual settings on the phys.
Are you converting the server straight into vCenter ? If so have you tried using converter to capture the machine into vcenter server 2.0 template and then running the converter again to upload the image into vcenter ?
It gets stuck around 2%, yes I am trying to import it directly from vCenter 4, I have also tried vconverter directly and it fails with an error that it was unable to clone volume c
The is no firewall between the Host and physical server, they are on the same network same VLAN.
You could also try booting the system from coldclone.iso and see if that works. You can get it from the vcenter server download page and is called VMware vCenter Converter BootCD
Have you got any Software RAID in your server?
Thank you to eveyone who responded but I got it to work. Looks like there was an issue on our network that kept causing it to fail, once that was fixed it went through with no problems.
What was the problem on the network that caused it to fail?