NVME-SNDK-GET-UNS(1)

📦
version 3.2 · 9 versions
, in arch rolling

💅 NVME-SNDK-GET-UNS(1) — the nvme manual, but make it make sense ✨

okay so bestie, you're looking at a page from the NVMe Manual (yes, that NVMe manual), and it's all about one very specific little plugin command. stay with me, it's actually cute 🎀

🌸 NAME 🌸

nvme-sndk-get-unsupported-reqs-log — this sends the NVMe sndk get-unsupported-reqs-log plugin command, and then hands you back the parsed log output. that's the whole vibe. 🦋

✨ SYNOPSIS ✨

nvme [<global-options>] sndk get-unsupported-reqs-log <device>
                        [--output-format=<normal|json> | -o <normal|json>]

like, you give it a device, you optionally tell it how you want the output formatted, done. slay. 💅

💖 DESCRIPTION 💖

so for the NVMe device you hand over, it sends a sndk plugin get-unsupported-reqs-log command and outputs the unsupported requirements log data. the --output-format option will format the output exactly as you specified. no cap. ✨

the <device> parameter is mandatory — not optional, not "eh maybe later", mandatory — and it may be either the NVMe character device (ex: /dev/nvme0). 🫶

real talk: this will only work on Sandisk devices supporting this log page. results for any other device are undefined — and undefined is not a cute look, okay? 😭

on success it returns the parsed unsupported requirements log page data, and an error code otherwise. periodt. 💀

🌈 OPTIONS 🌈

👑 GLOBAL OPTIONS 👑

the following options are defined at the top-level nvme command and are available to this subcommand:

  • --dry-run — prints the command that would be executed, but does not actually execute it. it's giving "just looking, not touching" energy. 🙈
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support.
  • --no-retries — disables retry logic on transient errors.
  • -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, 'json, or binary. only one output format may be used at a time — pick one, bestie, you can't have all four. 💅
  • --output-format-version=<version> — selects the output format version. version 1 uses the original field naming, while version 2 (default) provides more consistent and script-friendly field names. other versions are rejected, so don't even try it. 🚫
  • --quiet — suppresses informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. like, it's literally the mute button but for vibes. 🤫
  • --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). the "no rush babe" option. 🕰️
  • -v, --verbose — increases the level of detail in the output. may be specified multiple times to further increase verbosity. go off, stack those flags. 🔥

these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file — the flag is the main character here, iykyk. 👑

🦋 EXAMPLES 🦋

  • has the program issue the sndk get-unsupported-reqs-log plugin command:
# nvme sndk get-unsupported-reqs-log /dev/nvme0

look at that. immaculate. ate and left no crumbs. 🍓

⭐ NVME ⭐

part of the nvme-user suite. 🌸

okay that's the whole page!! source/version and date for the record: NVMe, dated 10/30/2026, on page NVME-SNDK-GET-UNS(1). mwah, go get that log data bestie 💜🧚‍♀️🎀

📦 where this page comes from