P2V - Standalone Converter Fails - Failed to clone c:

[billbearden]

I am new to VMware and converting.

In the log file, it says

error = (converter.agent.internal.fault.PlatformError) {

dynamicType = ,

faultCause = (vmodl.MethodFault) null,

errCode = 6,

msg = "A system error encountered during an operation.",

I am trying to convert from an IBM ISX blade to a ESXi 4.1.0 server. I have successfully converted another ISX blade (it won't boot, but that is another issue).

Every time I have tried to convert this server, it dies with Failed to clone volume c:. The log says system error. Sometimes, it fails at 33%. When I just copied a failure from earlier today and tried it again, it failed almost immediately with the same error. It has also failed at 7% and 63% in the past.

[golddiggie]

Are you trying to do a cold, or hot, clone? What's the OS on the target (source)? Have you also tried using third party conversion tools such as the VizionCore vConverter or vConverter SC? What storage is the conversion process going to? Is it local to the host, a SAN, NAS, etc?? Did you install the standalone VMware Converter directly onto the source server (the one to be converted)??

VMware VCP4

Consider awarding points for "helpful" and/or "correct" answers.

[billbearden]

Thanks for the reply.

I don't know the difference between cold and hot. I am trying to convert a powered on server. Is that what you mean?

The OS is Win2k.

I have not tried 3rd party converters. I have only tried the standalone one from VMware.

The storage on the target is local to the server.

I didn't install the converter on the source server. I installed and ran the converter from my pc. I installed the Converter Agent on the source server.

[golddiggie]

You're trying the 'hot' route (live with power is considered "hot")... Install it onto the source server and try again. That eliminates any connection issues between your PC, the source server and the ESX/ESXi host that will be running it.

Which converter version are you using?? As already mentioned, you could try an older release to see if that behaves better. OR a third party converter (install it onto the source if possible).

Typically, I'll use the VMware Converter that's part of the vCenter Server first. IF that doesn't fly, I'll install the current standalone product onto the source server. IF that doesn't work, I'll use the VizionCore vConverter product on the server. Using that process path, I've had great success... Since I don't recall which way I did a server going back to Win2K, you'll need to try the above methods until you get to one that works... I would try booting from the cold clone CD so that you also eliminate any software running on the host being the cause for the failures. Otherwise, stop all but critical services (for the OS) on the source before you kick off the next attempt... The VizionCore product has a section where you can do that within it, before the conversion actually starts (if I recall correctly, not sure about the VMware converter)...

VMware VCP4

Consider awarding points for "helpful" and/or "correct" answers.

[billbearden]

Thanks to everyone for the help. I know this is an old topic but I thought it might help someone in the future.

I think the thing that did the trick was to run the converter on the source (physical) server.

The issues we ran into after the conversion were related to software licensing. I assume that is pretty standard. The software didn't recognize the new hardware.

[AndreTheGiant]

Welcome to the community...

Which version of Convert are your using and which type of OS is the source machine?

I suggest to use old Converter (3.0.3) for Windows 2000 and 2003 Servers, and the new one for latest OS.

As written, have you installated the Converter on the source machine?

Do you have enought free space on C:?

Is there any running service that lock some files on C:?

Andre