I have an intermittent issue where the Get-NaHostDisk cmdlet will not return all the correct information on both 1.6 and 1.7 versions of the module.
For example, in the screenshot below no HostDrivePath's are returned and for Disk 7 no Controller Path is returned despite this being a LUN.
We use Get-NaHostDisk when cleaning up flexcloned database volumes to get the vol path and ensure it is offlined and deleted. At the moment this sometimes fails due to incomplete information and we have to manually offline/destroy the volume once the disk has been removed.
As your stock broker will tell you, past performance is not indicative of future results. However, since its initial release, the Toolkit has been updated approximately quarterly. 1.7 shipped on 1 February 2012.
I found the workaround I posted above didn't always succeed due to this bug. However Get-NaHostDisk will always give you the LUN serial, even if other fields are empty so you can pass this to Get-NaLUN to get the path and work the volume name from that.
Hi Graeme, currently running with Toolkit v18.104.22.168 and seems this still has not been solved. In your case you had Snapdrive disks returned (not complete though) but in my case I had no SD Luns returned at all - eventhough 5 LUNs were created, connected and configured on the Win2008 host.
If I run as follows, I get the non-negative number required message in return.
I downloaded version 3.1.1 and did some testing. You are correct, Get-NaHostDisk and Get-NcHostDisk does not display information for RDM LUNs. However it does display for VMDKs and Guest OS iSCSI connected LUNs.
I can still run Invoke-NaHostVolumeSpaceReclain on the RDM LUNs though. Hopefully a member of the development team will see this post and can debug the issue.