Windows 2008 not seeing drive above 16 TB correctly

[kmayhue]

I have cacti version 8.8a installed on a window 2008 R2 server and just upgraded our NAS to 20TB (was 5TB), but Cacti is reporting the drive to be over 140TB.
I did a verbose query below (removed SNMP private info), which I believe is index #5. What am I missing?

Running data query [8].
+ Found type = '6' [Script Query - Script Server].
+ Found data query XML file at 'C:/inetpub/wwwroot/cacti/resource/script_server/host_disk.xml'
+ XML file parsed ok.
+ Executing script for num of indexes '"c:\php\php.exe" -q C:\inetpub\wwwroot\cacti\scripts\ss_host_disk.php 192.168.11.194 29 1:1611:10::::::: num_indexes'
+ Found number of indexes: 7
+ Executing script for list of indexes '"c:\php\php.exe" -q C:\inetpub\wwwroot\cacti\scripts\ss_host_disk.php 192.168.11.194 29 1:1611:10::::::: index' Index Count: 7
+ Found index: 1
+ Found index: 2
+ Found index: 3
+ Found index: 4
+ Found index: 5
+ Found index: 6
+ Found index: 7
+ Executing script query '"c:\php\php.exe" -q C:\inetpub\wwwroot\cacti\scripts\ss_host_disk.php 192.168.11.194 29 1:1611:10::::::: query index'
+ Found item [hrStorageIndex='1'] index: 1
+ Found item [hrStorageIndex='2'] index: 2
+ Found item [hrStorageIndex='3'] index: 3
+ Found item [hrStorageIndex='4'] index: 4
+ Found item [hrStorageIndex='5'] index: 5
+ Found item [hrStorageIndex='6'] index: 6
+ Found item [hrStorageIndex='7'] index: 7
+ Executing script query '"c:\php\php.exe" -q C:\inetpub\wwwroot\cacti\scripts\ss_host_disk.php 192.168.11.194 29 1:1611:10::::::: query description'
+ Found item [hrStorageDescr='C: index: 1
+ Found item [hrStorageDescr='D: index: 2
+ Found item [hrStorageDescr='E: index: 3
+ Found item [hrStorageDescr='F: index: 4
+ Found item [hrStorageDescr='N: index: 5
+ Found item [hrStorageDescr='Virtual Memory'] index: 6
+ Found item [hrStorageDescr='Physical Memory'] index: 7
+ Executing script query '"c:\php\php.exe" -q C:\inetpub\wwwroot\cacti\scripts\ss_host_disk.php 192.168.11.194 29 1:1611:10::::::: query sau'
+ Found item [hrStorageAllocationUnits='4096 Bytes'] index: 1
+ Found item [hrStorageAllocationUnits='4096 Bytes'] index: 2
+ Found item [hrStorageAllocationUnits='4096 Bytes'] index: 3
+ Found item [hrStorageAllocationUnits='4096 Bytes'] index: 4
+ Found item [hrStorageAllocationUnits='8192 Bytes'] index: 5
+ Found item [hrStorageAllocationUnits='65536 Bytes'] index: 6
+ Found item [hrStorageAllocationUnits='65536 Bytes'] index: 7

[BSOD2600]

Fresh install? Cacti 0.8.8f is the latest with lots of fixes - http://www.cacti.net/changelog.php

The verbose query will only show the fields displayed in the Data Query table, not those it gathers and stores in the rrd files. If you manually run net-snmp snmpwalk of the disk OID (.1.3.6.1.2.1.25.2.3.1), what does it display for the new NAS size?

[kmayhue]

Yeah, I need to look into some time/effort for upgrading my current installation, but I have to say this has been running great up until this issue.
Below is the snmpwalk and thanks for the help!

Name/OID: .1.3.6.1.2.1.25.2.3.1.1.1; Value (Integer): 1
Name/OID: .1.3.6.1.2.1.25.2.3.1.1.2; Value (Integer): 2
Name/OID: .1.3.6.1.2.1.25.2.3.1.1.3; Value (Integer): 3
Name/OID: .1.3.6.1.2.1.25.2.3.1.1.4; Value (Integer): 4
Name/OID: .1.3.6.1.2.1.25.2.3.1.1.5; Value (Integer): 5
Name/OID: .1.3.6.1.2.1.25.2.3.1.1.6; Value (Integer): 6
Name/OID: .1.3.6.1.2.1.25.2.3.1.1.7; Value (Integer): 7
Name/OID: .1.3.6.1.2.1.25.2.3.1.2.1; Value (OID): .1.3.6.1.2.1.25.2.1.4
Name/OID: .1.3.6.1.2.1.25.2.3.1.2.2; Value (OID): .1.3.6.1.2.1.25.2.1.4
Name/OID: .1.3.6.1.2.1.25.2.3.1.2.3; Value (OID): .1.3.6.1.2.1.25.2.1.4
Name/OID: .1.3.6.1.2.1.25.2.3.1.2.4; Value (OID): .1.3.6.1.2.1.25.2.1.4
Name/OID: .1.3.6.1.2.1.25.2.3.1.2.5; Value (OID): .1.3.6.1.2.1.25.2.1.4
Name/OID: .1.3.6.1.2.1.25.2.3.1.2.6; Value (OID): .1.3.6.1.2.1.25.2.1.3
Name/OID: .1.3.6.1.2.1.25.2.3.1.2.7; Value (OID): .1.3.6.1.2.1.25.2.1.2
Name/OID: .1.3.6.1.2.1.25.2.3.1.3.1; Value (OctetString): C:
Name/OID: .1.3.6.1.2.1.25.2.3.1.3.2; Value (OctetString): D:
Name/OID: .1.3.6.1.2.1.25.2.3.1.3.3; Value (OctetString): E:
Name/OID: .1.3.6.1.2.1.25.2.3.1.3.4; Value (OctetString): F:
Name/OID: .1.3.6.1.2.1.25.2.3.1.3.5; Value (OctetString): N:
Name/OID: .1.3.6.1.2.1.25.2.3.1.3.6; Value (OctetString): Virtual Memory
Name/OID: .1.3.6.1.2.1.25.2.3.1.3.7; Value (OctetString): Physical Memory
Name/OID: .1.3.6.1.2.1.25.2.3.1.4.1; Value (Integer): 4096
Name/OID: .1.3.6.1.2.1.25.2.3.1.4.2; Value (Integer): 4096
Name/OID: .1.3.6.1.2.1.25.2.3.1.4.3; Value (Integer): 4096
Name/OID: .1.3.6.1.2.1.25.2.3.1.4.4; Value (Integer): 4096
Name/OID: .1.3.6.1.2.1.25.2.3.1.4.5; Value (Integer): 8192
Name/OID: .1.3.6.1.2.1.25.2.3.1.4.6; Value (Integer): 65536
Name/OID: .1.3.6.1.2.1.25.2.3.1.4.7; Value (Integer): 65536
Name/OID: .1.3.6.1.2.1.25.2.3.1.5.1; Value (Integer): 31457279
Name/OID: .1.3.6.1.2.1.25.2.3.1.5.2; Value (Integer): 524287
Name/OID: .1.3.6.1.2.1.25.2.3.1.5.3; Value (Integer): 40952319
Name/OID: .1.3.6.1.2.1.25.2.3.1.5.4; Value (Integer): -1365148161
Name/OID: .1.3.6.1.2.1.25.2.3.1.5.5; Value (Integer): -1853440257
Name/OID: .1.3.6.1.2.1.25.2.3.1.5.6; Value (Integer): 149513
Name/OID: .1.3.6.1.2.1.25.2.3.1.5.7; Value (Integer): 130057
Name/OID: .1.3.6.1.2.1.25.2.3.1.6.1; Value (Integer): 7004126
Name/OID: .1.3.6.1.2.1.25.2.3.1.6.2; Value (Integer): 196822
Name/OID: .1.3.6.1.2.1.25.2.3.1.6.3; Value (Integer): 18165244
Name/OID: .1.3.6.1.2.1.25.2.3.1.6.4; Value (Integer): -1368752956
Name/OID: .1.3.6.1.2.1.25.2.3.1.6.5; Value (Integer): 426087687
Name/OID: .1.3.6.1.2.1.25.2.3.1.6.6; Value (Integer): 44657
Name/OID: .1.3.6.1.2.1.25.2.3.1.6.7; Value (Integer): 43281
Name/OID: .1.3.6.1.2.1.25.2.3.1.7.1; Value (Counter32): 0
Name/OID: .1.3.6.1.2.1.25.2.3.1.7.2; Value (Counter32): 0
Name/OID: .1.3.6.1.2.1.25.2.3.1.7.3; Value (Counter32): 0
Name/OID: .1.3.6.1.2.1.25.2.3.1.7.4; Value (Counter32): 0
Name/OID: .1.3.6.1.2.1.25.2.3.1.7.5; Value (Counter32): 0
Name/OID: .1.3.6.1.2.1.25.2.3.1.7.6; Value (Counter32): 0
Name/OID: .1.3.6.1.2.1.25.2.3.1.7.7; Value (Counter32): 0

[kmayhue]

I should have realized to "Rebuild" the poller cache, and now it is working correctly.
Again, thanks for the help.