Hi,
when I try to clone a vmdk-file from a local vmfs to a RDM in physical mode I get the following error:
# vmkfstools -i /vmfs/volumes/vm1-local/vmvc/vmvc.vmdk -d rdmp:/vmfs/devices/disks/vmhba1\:0\:0\:1 /vmfs/volumes/vmware-vol/vmvc/vmvc.vmdk
Destination disk format: pass-through raw disk mapping to '/vmfs/devices/disks/vmhba1:0:0:1'
Cloning disk '/vmfs/volumes/vm1-local/vmvc/vmvc.vmdk'...
Failed to clone disk : Invalid argument (1441801).
I have made this due to
http://communities.vmware.com/message/506045
and the man-page from vmkfstools ... but it doesn't work.
Thanks for Help
put the source vmdk as the first argument then the -i option. Usually vmkfstools expects a disk file for the first argument and then the options.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This doesn't work. I get "usage error" and vmkfstools -h displays this syntax:
-i --clonevirtualdisk srcDisk -d --diskformat rdm:
I guess, that something is not working in creating the rdmp-file. It is not created and I have found this thread, when I look for "Invalid argument (1441801)":
http://communities.vmware.com/message/868345
I am on vmfs Filesystem, so something else is not working.
Regards
Hi,
I get the same error, when I just try to create a rdm-disk:
vmkfstools -r /vmfs/devices/disks/vmhba1\:0\:0\:1 /vmfs/volumes/vmware-vol/vmvc/vmvc.vmdk
Failed to create virtual disk: Invalid argument (1441801).
Hi,
my fault ...:
I mixed up the path to the LUN:
After Rescanning, vmhba1 showed vmhba1:0:0 and vmhba1:0.1 as LUN ID's.
vmhba1:0.0 was already an existing vmfs-fs.
the correct Syntax is
vmkfstools -r /vmfs/devices/disks/vmhba1\:0\:1\:0 /vmfs/volumes/vmware-vol/vmvc/vmvc.vmdk
for creating the rdm-file and
vmkfstools -i /vmfs/volumes/vm1-local/vmvc/vmvc.vmdk -d rdmp:/vmfs/devices/disks/vmhba1\:0\:1\:0 /vmfs/volumes/vmware-vol/vmvc/vmvc.vmdk
for cloning
Regards
Hey!
I've got a similar problem.
I had a local LUN with an vmfs on it and for testing purposes I deleted the vmfs on it to test RDMs. Now I cant map this local LUN as an RDM. Neither with the VC nor in the console.
The Option for mapping an RDM to an VM is simply grayed out.
In the console I get the following error when I send the following command:
The funny thing is, that the ESX-Host still can see the LUN because he suggests it if I would want to create a datastore on it.
Is there anybody who has encountered this promblem already and/or knows how to solve it, or better, where my mistake is?
Thanks,
Nick
I have the same issue. What's odd is that I can run the command on another ESX server without issue but this one just returns the Invalid argument (1441801) error.
Here's what I have tried;
vmkfstools -z (or -r) /vmfs/devices/disks/vmhba0\:1\:0:\0 /vmfs/volumes/store_name/disk_name.vmdk
I have also tried;
vmkfstools -z (or -r) /vmfs/devices/disks/vmhba0:1:0:0 /vmfs/volumes/store_name/disk_name.vmdk
Eric
Hi, i have the same problem:
vmkfstools -r /vmfs/devices/disks/vmhba0:1:0:0 /vmfs/volumes/esx-demo02-bci\:storage1/SDS2/SDS2RDM.vmdk
Failed to create virtual disk: Invalid argument (1441801).
vmkfstools -z /vmfs/devices/disks/vmhba0:1:0:0 /vmfs/volumes/esx-demo02-bci\:storage1/SDS2/SDS2RDM.vmdk
Failed to create virtual disk: Invalid argument (1441801).
any hints ?