---
type: Sensor Reference
title: "SNMP Disk / Storage OIDs: hrStorageTable Reference"
description: "The SNMP OIDs for disk and storage — hrStorageTable columns and the UCD dskTable — with a snmpwalk example and the allocation-unit conversion."
resource: "https://snmp-monitoring.info/sensors/disk/"
tags: [sensors]
timestamp: 2026-07-11T00:00:00Z
---

# SNMP Disk / Storage OIDs: hrStorageTable Reference

The SNMP OIDs for disk and storage — hrStorageTable columns and the UCD dskTable — with a snmpwalk example and the allocation-unit conversion.

## Related concepts

- Up: [SNMP Sensors & OID Catalog: Every Metric You Can Monitor](/sensors/index.md)

## Frequently asked questions

### What is the OID for disk usage in SNMP?

hrStorageUsed at 1.3.6.1.2.1.25.2.3.1.6 (in allocation units, per row) is the portable answer; pair it with hrStorageSize (.5) and hrStorageAllocationUnits (.4). On Net-SNMP hosts, dskPercent (1.3.6.1.4.1.2021.9.1.9) gives percent-used directly.

### How do I find my disk's row?

Walk hrStorageDescr (1.3.6.1.2.1.25.2.3.1.3) and match the mount or label you want, or filter hrStorageType (.2) to hrStorageFixedDisk to drop RAM/swap rows. Use that row's index for size and used. Don't assume a fixed index — it can change across reboots.

### hrStorageTable or UCD dskTable — which should I use?

Use hrStorageTable for cross-vendor portability; it's on almost everything. Use the UCD dskTable (1.3.6.1.4.1.2021.9.1) on Net-SNMP hosts when you want a ready-made dskPercent and clean mount paths without allocation-unit math. Note it must be configured in snmpd.conf to appear.

### How do I convert the value to GB?

Multiply by the allocation units, then by the usual byte scale: bytes = value × hrStorageAllocationUnits, and divide by 1,000,000,000 for GB (or 1,073,741,824 for GiB). For a used percentage you can skip all of that, since hrStorageUsed ÷ hrStorageSize is already unitless.

## Source

Concept generated from https://snmp-monitoring.info/sensors/disk/ — the SNMP Monitoring vendor-neutral knowledge base. Content is limited to what that page states (no external claims added here).
