NVME-SOLIDIGM-ID-(1)

📦
version 3.2 · 10 versions
, in arch rolling

💖 NAME 💖

nvme-solidigm-id-ctrl — bestie, this is the Solidigm-specific glow-up of the NVMe Identify Controller command 🎀 it sends the command, hands you back the result and the structure, no crumbs left behind ✨

🌸 SYNOPSIS 🌸

nvme [<global-options>] solidigm id-ctrl <device>
                        [--raw-binary | -b]
                        [--vendor-specific | -V]
                        [--human-readable | -H]

🦋 DESCRIPTION 🦋

Okay so listen 👑 this command is a Solidigm-specific extension of the NVMe Identify Controller command. It sends an NVMe Identify Controller command to whatever device you point at, and gives you back the result plus the returned structure. That's the whole vibe check, and it passes 💅

The <device> parameter is mandatory — like, non-negotiable, main character requirement — and it can be either:

  • the NVMe character device (ex: /dev/nvme0), or
  • a namespace block device (ex: /dev/nvme0n1)

Either one slays, pick whichever you've got 🫶

✨ OPTIONS ✨

  • -H, --human-readable — displays values in a human-readable format where possible. Heads up bestie: this one's deprecated, use --verbose instead 🙈

💜 GLOBAL OPTIONS 💜

These live at the top-level nvme command and are totally available to this subcommand too — shared custody, we love to see it 🌈

  • --dry-run — prints the command that would be executed but doesn't actually execute it. All the fantasy, none of the commitment 😌
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support.
  • --no-retries — disables retry logic on transient errors. One shot, no do-overs 💀
  • -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, json, or binary. Only one output format at a time, don't get greedy 🍓
  • --output-format-version=<version> — selects the output format version. Version 1 uses the original field naming, while version 2 (the default) gives you more consistent and script-friendly field names. Other versions are rejected — it's giving strict parents, but respectfully ✋
  • --quiet — suppresses informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. Quiet mode said "not me being the louder one" 😭
  • --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this invocation. Supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir.
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). Literally forever, iykyk ⏳
  • -v, --verbose — increases the level of detail in the output. May be specified multiple times to further increase verbosity — stack it, queen 👑

These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file — CLI stays the main character, periodt 💅

🎀 EXAMPLES 🎀

Here's where it gets fun, bestie:

  • Send the Identify Controller command and interpret the output:
# nvme solidigm id-ctrl /dev/nvme0
  • Print the raw output to stdout:
# nvme solidigm id-ctrl /dev/nvme0 --raw-binary
  • Print the output in JSON format:
# nvme solidigm id-ctrl /dev/nvme0 -o json
  • Display the vendor-specific fields:
# nvme solidigm id-ctrl /dev/nvme0 --vendor-specific
# nvme solidigm id-ctrl /dev/nvme0 -V
  • Use human-readable output:
# nvme solidigm id-ctrl /dev/nvme0 --human-readable
# nvme solidigm id-ctrl /dev/nvme0 -v

👑 SEE ALSO 👑

nvme-id-ctrl(1) — go read that one too, it's the og 🧚

⭐ NVME ⭐

Part of the nvme-user suite.

And that's the whole page, bestie — go forth and identify those controllers 💖

signing off with love from the NVMe manual, dated 10/30/2026 — part of the nvme-user suite, no cap 🫶✨

📦 where this page comes from