It's actually not the devicePath that you're referencing there. It's actually physical devices that needs to be provided, take a look at this vSphere SDK for Perl script that provides an example:
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at:
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
Yes, I know, but you still need to pass in the right value 
Hence I was pointing to my script to give you and example.
Any reason you're using the MOB to perform operations? It's primarily there to help show you what some of the objects and data structures look like, would be easier to use one of the SDK's to perform some of these operations.
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at:
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
Nope, it should just be a string array (e.g. )
There's a good chance the syntax may have changed from VI 3.5 to vSphere 4.0
As mentioned in my original reply, the devicePath should something like /dev/cciss/c0d0 or /dev/sda, etc. which is the full device path seen from the Service Console on classic ESX or Busybox console of ESXi.
Here's some documentation around this new naming convention - http://pubs.vmware.com/vsp40u1/wwhelp/wwhimpl/js/html/wwhelp.htm#href=install/c_disk_device_names.ht...
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at:
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".