topic Re: Failure: Get-NaHostDisk : Non-negative number required. in Microsoft Virtualization Discussions

Failure: Get-NaHostDisk : Non-negative number required.

PADMANTECH — Thu, 05 Jun 2025 06:03:40 GMT

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.

Re: Get-NaHostDisk : Non-negative number required.

JGPSHNTAP — Fri, 03 May 2013 12:17:13 GMT

RDM to the VM? Are you using DB/LOG mount points?

Re: Get-NaHostDisk : Non-negative number required.

PADMANTECH — Fri, 03 May 2013 12:27:46 GMT

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

Re: Failure: Get-NaHostDisk : Non-negative number required.

GRAEMEOGDEN — Mon, 20 May 2013 15:14:10 GMT

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

Re: Failure: Get-NaHostDisk : Non-negative number required.

GRAEMEOGDEN — Wed, 22 May 2013 11:19:03 GMT

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.