VMware Cloud Community
oops
Contributor
Contributor

vmkfstools -i: Unable to clone virtual disk : fault.RestrictedVersion.summary

Hello to everyone,

I'm trying to upgrade VMs from GSX 3.0 to ESX3i 3.5.0,

using the RCLI command: vmkfstools -i <old_disk> <new_disk>.

We have no VC, just the client and the RCLI.

Sincerely, the error message is not that clear. Also, not having the console doesn't help me to locate the filepath.

I have:

dir1/dir2 as the desired path for the new disk files.

dir3/dir4 is the filepath for he 2GBsparse old disk files.

Basically, I issue the command:

vmkfstools --server xxx -i '/vmkfs/volumes/datastore1/dir1/dir2/diskfile' '/vmkfs/volumes/datastore2/dir3/dir4'

that gives me that error message as result.

anyway, even if I change that filepaths, the result is always the same.

No different error messages, such as "file not found" or whatsoever.

Any idea? How is it supposed to work?

Reply
0 Kudos
9 Replies
oreeh
Immortal
Immortal

You need to add a filename in the second parameter and all of the folders have to exist

vmkfstools -i /vmfs/volumes/vol1/test/test.vmdk /vmfs/volumes/vol2/testclone/testclone.vmdk

Reply
0 Kudos
oops
Contributor
Contributor

Thank you for your reply,

yes, I've tried also that way, supplying tha second filename too. Nothing changes, unfortunately.

afaik, it seems acceptable to use the syntax: /vmfs/volumes/<datastore>/<folder1/<folder2>/<filename

but I'm not sure.

Surely it's correct to use instead: /vmfs/volumes/<vol-ID>/<folder1>/<filename>

but without console I don't know the vol-ID.

Anyway "fault.RestrictedVersion.summary" doesn't seem anything related to bad filenames/parameters, at least to me,

is it related with licensing?

Thanks in advance, bye

Reply
0 Kudos
oreeh
Immortal
Immortal

I don't think its related to licensing.

When supplying the source disk parameter are you using the descriptor file (the filename without the -flat part)?

If yes, post the contents of the descriptor file.

Reply
0 Kudos
oops
Contributor
Contributor

Hello,

I've to partially conceal the whole paths, anyway the command I launch is:

./vmkfstools --server a.b.c.d -i '/vmfs/volumes/datastore1/dir01/C_scsi' '/vmfs/volumes/datastore2/dir02/dir03/C_scsi.vmdk

the file C_scsi is that one starting with:

  1. Disk DescriptorFile

version=1

CID=1ed1d9f2

parentCID=ffffffff

createType="twoGbMaxExtentSparse"

  1. Extent description

RW 4192256 SPARSE "C_scsi-s001"

RW 4192256 SPARSE "C_scsi-s002"

RW 4192256 SPARSE "C_scsi-s003"

RW 4192256 SPARSE "C_scsi-s004"

.... cut ....

C_scsi hasn't the .vmdk suffix. The filename is just: C_scsi

Is it possible to test a given file path, I mean, to list the corresponding file, if it exist?

If I use vifs commands, I have to use a totally different syntax, like '[datastore1] dir01/filename' , that way I can't test the same path I need for vmkfstools...

Thanks, bye

Reply
0 Kudos
oreeh
Immortal
Immortal

Are all the other files (C_scsi-s001, C_scsi-s002, ...) available in the same folder?

If yes try to add the .vmdk extension to all of them and modify the descriptor file to reflect the changes.

Did you use a binary method to transfer the files to the vmfs datastore?

Lastly, you can omit the --server parameter.

oops
Contributor
Contributor

- yes, all the 2 GB slices are into the same directory as the descriptor file

- added .vmdk extension, doesn't work yet

- about binary method / file integrity, there is a possibility for a problem here, I'm gonna check it out in a short while

- it seems I cant' omit the --server parameter, if I omit it then vmkfstools tries to contact the localhost, that's not the right machine.

Thanks for your time, bye.

Reply
0 Kudos
oops
Contributor
Contributor

About the binary method issue,

just to be sure I've transferred another VM to the datastore1, this time I've also checked with md5sum that all the files uploaded onto the datastore1 are intact.

They also have all the .vmdk suffix

Then I've issue the command:

vmkfstools -i /vmfs/volumes/datastore1/dir1/C_scsi.vmdk /vmfs/datastore2/dir2/C_scsi.vmdk

again obtaining: Unable to clone virtual disk : fault.RestrictedVersion.summary

dir 1 and dir2 exist.

Thanks, bye

Reply
0 Kudos
bretti
Expert
Expert

Hello oops,

I'm curious, can you run any other commands from the RCLI successfully to your 3i server? Can you run esxcfg-vmhbadevs --query ?

Also, have you tried to use VMware Converter instead of an import command line?

Reply
0 Kudos
techdruid
Contributor
Contributor

I've found the following post about this support being removed for the free version of ESXi.  I used the advice to disable the free license and revert to the trial license and the convert worked for me.

http://vmetc.com/2009/03/31/esxi-u4-ends-free-version-read-and-write-access-from-the-rcli/

Reply
0 Kudos