Import Jumps from 1-5% to 97% and fails /w Error vim.fault.NotFound

[RogerAli]

Hey all,

We've recently gotten our ESX Farm setup. We are running version 3.0.1 and have the VM Server used for Converter (v 2.0.0 Build 39557). I've successfully imported 3-5 Servers (Win 2003) into our Datastore without issue.

Earlier this week, I've been asked to convert a W2K Server SP4 to a VM. I started up Converter as I normally have and start the process. I noticed the cool warning about the SCSIport.sys issue (very slick). Once the process starts, it gets to Step 2: Creating target virtual machine and importing data...

At this point, it shows progress of 1-5% and jumps to 97% with a failed status. Reading through the log on the Source Server, I found the following error lines:

\[#9] \[2007-02-12 08:28:18.664 'App' 2352 error] \[cloneTask,210] Cloning failed!

\[#9] \[2007-02-12 08:28:18.664 'App' 2352 error] \[imageProcessingTaskImpl,552] CloneTask::task\{30}: Image processing task has failed with MethodFault::Exception: vim.fault.NotFound

\[#9] \[2007-02-12 08:28:18.664 'App' 2352 verbose] \[imageProcessingTaskImpl,154] CloneTask::task\{30}: SetState to error

\[#9] \[2007-02-12 08:28:18.664 'App' 2352 verbose] \[imageProcessingTaskWrapper,886] Remote task CloneTask::task\{30} completed[/i]

I've searched the forum and found other suggestions and wanted to point out that we've run a ChkDisk on the drive and the disks are not dynamic disks.

Any ideas on how to fix this issue would be greatly appreciated.

Thanks,

Roger

[admin · Accepted solution]

Did you resize the volumes on this machine when converting? If so, what happens when you preserve the original volume sizes?

[PRJ]

We have exactly the same problem and it happens also with the original volume sizes.

[jdl1]

I get the same error on Windows 2000 Pro SP 4 when using original volume sizes or when resizing.

[The_Chris]

I have the exact same problem and I have tried all the different ways of resizing and leaving the volume the same.

Any ideas? Anyone?

[jlandrith]

Ditto - Same problem.

[aleph0]

Finally solved for me, without passing in Virtual Center but pointing directly to ESXHOST on which the vm Clone will be created.

cheers

mf

[sysadmin_surf]

I am having the same problem here as well. I am not using Virtual Center and am pointing directly to the ESX host. Does anyone have any new learning on this?

[sfdandreas]

I seem to run into this problem when trying to use VMWare Converter 3.0, importinga physical Windows Server 2000 machine (running SQL Server 2000).

Different import settings for grow/allocate-now/split-files doesn't seem to matter.

the vmware-converter-0.log file on the source machine contains these errors (among other things):

...

\[#1] \[2007-04-04 08:50:25.345 'App' 1288 verbose] \[disposable,68] Registering disposable session object id=localFile=

\[??] \[2007-04-04 08:50:25.345 'App' 1564 info] \[stub,42] Info\[Windisk_GetVolumeDeviceNumber]: IOCTL_GET_STORAGE_DEVICE_NUMBER for volume
?\Volume\{29692442-f4ea-11d7-8290-806d6172696f}\ is not supported .... Trying NT method.

\[??] \[2007-04-04 08:50:25.345 'App' 1564 info] \[stub,42] Error\[Windisk_GetVolumeDeviceNumber]:Failed to get
?\Volume\{29692442-f4ea-11d7-8290-806d6172696f}\ Volume's disk number

\[#1] \[2007-04-04 08:50:25.345 'App' 1288 verbose] \[disposable,79] Associating disposable session object id=localFile= with session id=0B4C6DA3-D2A0-4897-B50F-B6AB1E456706

\[#1] \[2007-04-04 08:50:25.345 'App' 1288 verbose] \[extendedOsInfo,389] \[boot loader]

...

\[#1] \[2007-04-04 08:50:26.126 'App' 992 verbose] \[extendedOsInfo,389] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Server" /fastdetect

\[#1] \[2007-04-04 08:50:26.126 'App' 992 verbose] \[disposable,121] object explicitly disposed: localFile=

\[#1] \[2007-04-04 08:50:26.126 'App' 992 info] \[extendedOsInfo,453] SwagNTInfoFromString has Microsoft Windows 2000 Server

\[??] \[2007-04-04 08:50:26.126 'App' 1564 info] \[stub,42] Error\[Windisk_GetVolumeDeviceNumber]:Failed to get
?\Volume\{29692442-f4ea-11d7-8290-806d6172696f}\ Volume's disk number

\[#1] \[2007-04-04 08:50:26.126 'App' 992 info] \[extendedOsInfo,176] Returning OS as display Microsoft Windows 2000 Server

...

\[#1] \[2007-04-04 08:50:26.267 'App' 1580 verbose] \[imageProcessingTaskImpl,514] VmiQuerySourceInfoTask::task\{0}: Image processing task has succeeded

\[#1] \[2007-04-04 08:50:26.376 'App' 992 verbose] \[disposable,121] object explicitly disposed: VmiQuerySourceInfoTask::task\{0}

\[#1] \[2007-04-04 08:50:26.376 'App' 992 verbose] \[imageProcessingTaskImpl,123] VmiQuerySourceInfoTask::task\{0} being destroyed

\[2007-04-04 08:50:45.470 'VmdbAdapter' 716 error] GetParameters failed: not well-formed (invalid token)

\[2007-04-04 08:50:45.486 'VmdbAdapter' 716 error] (backtraces not supported)

\[2007-04-04 08:50:49.798 'VmdbAdapter' 1244 error] GetParameters failed: not well-formed (invalid token)

\[2007-04-04 08:50:49.798 'VmdbAdapter' 1244 error] (backtraces not supported)

\[2007-04-04 08:51:10.923 'VmdbAdapter' 992 error] GetParameters failed: not well-formed (invalid token)

\[2007-04-04 08:51:10.923 'VmdbAdapter' 992 error] (backtraces not supported)

\[2007-04-04 08:51:26.001 'VmdbAdapter' 684 error] GetParameters failed: not well-formed (invalid token)

\[2007-04-04 08:51:26.001 'VmdbAdapter' 684 error] (backtraces not supported)

\[#1] \[2007-04-04 08:51:32.391 'App' 684 info] \[vmImporter,150] Entering UFAD at CheckDestAvailable

...

[harrytoole]

I had the same problem. I ended up defragging the drives and running chkdsk to fix the problem. Also have seen that after applying patch2 will not allow convertor to p2v to a 2.x host from VC2.

[Sif]

I had the same error when I tried to import an existing VM with lastest Converter 3.0 . The server (W2k3) that I used for run Converter had many active VLAN (802.1q). It was a multi-home server. I suppress other VLAN and after that my converter's machine had only 1 ip address, my import was successful. It's great, I have import 5 VM on same time with 100%.

Cool

Marc Lebrun

[rsteagall]

I'm having the same issue. What kind of things should I look for? I'm not making much from these logs.

[aleph0]

defrag your disk(s), chkdsk /F and do not change target virtual disk size

it works for me.

HTH

http://virtualaleph.blogspot.com