Resources
Resources
Resources is the physical/infrastructure layer of a StorONE system: the drives, the drive pools built from them, the enclosures the drives sit in, and the network interfaces the system uses to talk to hosts and to other nodes. Everything in the Applications & Volumes chapter is built on top of what's described here — a volume can't exist without a drive pool, and a drive pool can't exist without approved drives.
This chapter is organized into the following pages:
- Drive Pools — grouping drives into pools that volumes are created on.
- Drives — approving, unapproving, reviving, and locating physical drives.
- Drive Enclosures — locating drives inside their physical chassis/JBOD.
- Self-Encrypting Drives — initializing and erasing SED drives.
- Network — enabling iSCSI/NVMeOF traffic on specific IPs, and testing connectivity.
- NVMeOF Enclosures — connecting to external NVMeOF-attached drive enclosures.
Hardware resources in general
Before getting into the specific resource types, two commands work across all resource types at once — useful when you want a single view of everything, or need to clean up after physically removing hardware.
Listing any type of hardware resource
resources list is a general-purpose inventory query. Unlike the drive-, pool-, and network-specific list commands in the rest of this chapter (which return rich, type-specific detail), this one gives you a flatter view across whichever resource type you ask for — including types that don't have their own dedicated chapter section, like CPUs and memory.
Using the web interface
- Open Inventory > Resources.
- Select the resource type you want from the overview (CPU, Memory, HBA, NIC, HDD, SSD, NVMe, or Chassis).
- Use the toolbar to filter by node, show only components with errors, or show advanced/sensor details.
Using the CLI
resources list --resourceType=<name> [--node=<name>] [--errors] [--details] [--sensors] [--ids=<numbers...>]
| Option | Description |
|---|---|
--resourceType=<name> |
The type of resource to list. Valid values: Cpu, Memory, Hba, Nic, HDD, SSD, NVMe, Chassis (case-insensitive). |
--node=<name> |
Filter by node name. |
--errors |
Show only components with errors. |
--details |
Show advanced information. |
--sensors |
Show sensor information (e.g. temperature, fan speed — where applicable to the resource type). |
--ids=<numbers...> |
Filter by resource ID. |
Examples
List all CPUs in the system:
resources list --resourceType Cpu
List memory modules with sensor information:
resources list --resourceType Memory --sensors
List only HBAs that currently have errors, on node1:
resources list --resourceType Hba --node node1 --errors
Cleaning up missing resources
When a piece of hardware is physically removed or stops responding, StorONE keeps a record of it marked as missing rather than silently forgetting about it — this is what lets you see, for example, that a NIC or drive that should be there no longer is. Once you've confirmed the removal was intentional (the drive was pulled, the card was removed, etc.), use resources delete to clear out those stale missing-resource entries.
This applies to any resource type, not just drives — a missing NIC or missing HBA entry is cleaned up the same way.
Using the web interface
- Open Inventory > Resources.
- Locate the resource marked as missing and select it (or select all missing resources).
- Click Delete.
Using the CLI
resources delete --entityIds=<numbers...>|--all
| Option | Description |
|---|---|
--entityIds=<numbers...> |
The missing resource IDs to delete. |
--all |
Delete all missing resources. |
Examples
Delete a specific missing resource:
resources delete --entityIds 42
Delete every missing resource in the system:
resources delete --all
Next: Drive Pools — grouping drives into pools that volumes are created on.