Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Good People,
I was trying to diagnose a LUN space issue on my Windows host today when i wanted to use the CMDLet "Get-NaHostDisk" in Powershell Toolkit 2.3 but would only get the below error message:
Environment:
Windows Server 2008 R2 sp1 VM running on VMware ESXi 4.1
Exchange 2010 installed
SnapDrive 6.5 installed
SnapManger for Exchange 6.04 installed
PS H:\> Get-NaHostDisk
Get-NaHostDisk : Non-negative number required.
Parameter name: byteCount
At line:1 char:15
+ Get-NaHostDisk <<<<
+ CategoryInfo : NotSpecified: (:) [Get-NaHostDisk], ArgumentOutOfRangeException
+ FullyQualifiedErrorId : System.ArgumentOutOfRangeException,DataONTAP.PowerShell.SDK.Cmdlets.Windows.GetHostDisk
PS H:\> Get-NaHostDisk -DataOntap
Get-NaHostDisk : Non-negative number required.
Parameter name: byteCount
At line:1 char:15
+ Get-NaHostDisk <<<< -DataOntap
+ CategoryInfo : NotSpecified: (:) [Get-NaHostDisk], ArgumentOutOfRangeException
+ FullyQualifiedErrorId : System.ArgumentOutOfRangeException,DataONTAP.PowerShell.SDK.Cmdlets.Windows.GetHostDisk
Any help with this is most welcome.
4 REPLIES 4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
RDM to the VM? Are you using DB/LOG mount points?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- It's a FC RDM to the VM.
- I'm using Drive letters for LUN's
- There are 7 LUN's contected to a Data ONTAP 7.3.5 filer
- I have multiple server with similar setup with same problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Having the same issue, although bizarrely it does work on other servers with exact same PS versions and toolkit versions.
Server 1 - Working
Server 2 - Fails
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Investigating further it seems the error is related to two disks in particular. These are located on a different vServer to the other disks, although the user running the command has access to both and both are set up within SnapDrive.
