VMware Cloud Community
Derrick_V
Contributor
Contributor
Jump to solution

converter fails on xp wkstn

I'm trying to convert an xp wkstn from vmserver 1.0.6 to esxi and it keeps failing with "file is too large" error. The wkstn vm has a single 18 GB HD about 2/3 full. I was able to convert a 2003svr with 2 4GB drives with out problem. I'm using the latest converter v.3.0.3.

What seems to be the problem here?

Here is part of the log file:

Adding controller for IDE bus 0 with key 200.

Adding controller for IDE bus 1 with key 201.

LocalVirtualDiskSpec: Name=J:\Virtual Machines\STMDVOP1\STMDVOP1-000001.vmdk

Creating local connection to the co-located slave

DISKLIB-SPARSE: "J:\Virtual Machines\STMDVOP1\STMDVOP1-000001.vmdk" : failed to open (36872): Underlying file system does not support files that large.

DISKLIB-LINK : "J:\Virtual Machines\STMDVOP1\STMDVOP1-000001.vmdk" : failed to open (The file is too large).

DISKLIB-CHAIN : "J:\Virtual Machines\STMDVOP1\STMDVOP1-000001.vmdk" : failed to open (The file is too large).

DISKLIB-LIB : Failed to open 'J:\Virtual Machines\STMDVOP1\STMDVOP1-000001.vmdk' with flags 0xe (The file is too large).

Opening J:\Virtual Machines\STMDVOP1\STMDVOP1-000001.vmdk failed with error36872

Rethrowing MethodFault sysimage.fault.FileOpenError:

Failed to open J:\Virtual Machines\STMDVOP1\STMDVOP1-000001.vmdk

VmiQuerySourceInfoTask::task: Image processing task has failed with MethodFault::Exception: sysimage.fault.FileOpenError VmiQuerySourceInfoTask::task: SetState to error

object explicitly disposed: VmiQuerySourceInfoTask::task VmiQuerySourceInfoTask::task being destroyed

CloseSession called for session id=02CD31F8-B24D-470F-A86D-CFAFFC4E916F

Removed vmdb connection /db/connection/#3/

Reply
0 Kudos
1 Solution

Accepted Solutions
paragsha
Hot Shot
Hot Shot
Jump to solution

You need to move all the virtual disks (snapshots) and preserve the relative path hierarchy. (This can be impossible if a relative path does not exist). I would advice installting converter on the same machine where you have the vmserver installed.

View solution in original post

Reply
0 Kudos
6 Replies
paragsha
Hot Shot
Hot Shot
Jump to solution

The problem seems to be related to the filesystem. On which OS are you running Converter? On which OS are you running Server 1.0.6? If these are not the same machines how are you mouting the remote filesystem.

I believe the machine on which you are running converter is seeing the .vmdk files to be on FAT filesystem (i.e. J: in your case). That is the reason it is complaining when you are trying to open the VMDK.

Reply
0 Kudos
Derrick_V
Contributor
Contributor
Jump to solution

Thank you for the reply.

The converter is running on XP system with an NTFS. The VMserver was

running on a server2003 (also NTFS). The .VMDK files from the VMserver

were copied to a NAS drive. The XP system that is running the converter

sees the NAS drive as NTFS. I've tried to convert the VM when connected

to the NAS as a UNC share and I tried again as a mapped drive letter.

Each time I got the same error.

I'll try again, but this time I'll copy the VMDK file to the local file

system where the converter is running from.

Please let me know if you have any other ideas.

Thank you.

Derrick Vandekraats

direct: 250 962-3684

fax: 250 962-3619

Reply
0 Kudos
paragsha
Hot Shot
Hot Shot
Jump to solution

Hi Derrick,

Ya, I am not a NAS expert. But you could check it by trying to create a 10GB file on your SMB share/NAS from the machine on which you are running Converter (J:) and it will give you an idea if the filesystem is allowing you to work on large files.

Derrick_V
Contributor
Contributor
Jump to solution

I got pass the disk size issue by copying the files to another location,

however converter does not like the fact that the files have been moved

as it's trying to open files from the old location. Here is part of the

log file:

DISKLIB-DSCPTR:

Opened : "STMDVOP1-000001.vmdk" (0xe)

DISKLIB-LINK :

Opened 'E:\STMDVOP1\STMDVOP1-000001.vmdk' (0xe): monolithicSparse,

33554432 sectors / 16 GB.

DISKLIB-LINK :

"D:\Virtual Machines\STMDVOP1\STMDVOP1.vmdk" : failed to open (The

system cannot find the path specified).

DISKLIB-CHAIN

:"E:\STMDVOP1\STMDVOP1-000001.vmdk": Failed to open parent "D:\Virtual

Machines\STMDVOP1\STMDVOP1.vmdk": The system cannot find the path

specified.

DISKLIB-CHAIN :

"D:\Virtual Machines\STMDVOP1\STMDVOP1.vmdk" : failed to open (The

parent of this virtual disk could not be opened).

DISKLIB-LIB :

Failed to open 'E:\STMDVOP1\STMDVOP1-000001.vmdk' with flags 0xe (The

parent of this virtual disk could not be opened).

Opening

E:\STMDVOP1\STMDVOP1-000001.vmdk failed with error23

Rethrowing

MethodFault sysimage.fault.FileOpenError:

Failed to open E:\STMDVOP1\STMDVOP1-000001.vmdk

VmiQuerySourceInfoTask::task: Image processing task has failed with MethodFault::Exception: sysimage.fault.FileOpenError VmiQuerySourceInfoTask::task: SetState

to error

object explicitly disposed: VmiQuerySourceInfoTask::task VmiQuerySourceInfoTask::task being

destroyed

Thanks,

Derrick Vandekraats

direct: 250 962-3684

fax: 250 962-3619

Reply
0 Kudos
paragsha
Hot Shot
Hot Shot
Jump to solution

You need to move all the virtual disks (snapshots) and preserve the relative path hierarchy. (This can be impossible if a relative path does not exist). I would advice installting converter on the same machine where you have the vmserver installed.

Reply
0 Kudos
Derrick_V
Contributor
Contributor
Jump to solution

That made the difference. First the NAS drive did not appear to support large files to the converter program. Even if it did pass that test, i would have been bitten by the fact that I had moved the vmserver files from their original location. Once that was pointed out I placed the files in the same relative directory and drive structure on a spare 2003 server as they originally existed. The original vmserver and files were no longer available. Now the convert program is successful.

Reply
0 Kudos