NVME-SNDK-GET-ERR(1)

📦
version 3.2 · 9 versions
, in arch rolling

💖 NVME-SNDK-GET-ERR(1) 💖

okay so, straight from the NVMe Manual, this is the NVME-SNDK-GET-ERR(1) page — and we're making error recovery logs make sense, bestie. ✨

🌸 NAME 🌸

nvme-sndk-get-error-recovery-log — sends the NVMe sndk get-error-recovery-log plugin command and returns the parsed log output. Periodt. 💅

🦋 SYNOPSIS 🦋

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

✨ DESCRIPTION ✨

For the NVMe device you give it, this sends a sndk plugin get-error-recovery-log command and outputs the error recovery log data. The --output-format option will format the output as specified. Cute, right? 💖

The <device> parameter is mandatory — it may be either the NVMe character device (ex: /dev/nvme0). No device, no magic. 🪄

This will only work on Sandisk devices supporting this log page. Results for any other device are undefined, bestie — like, do not test fate. 😭

On success it returns the parsed error recovery log page data; otherwise, error code. Slay when it works, error code when it doesn't. 💀

🎀 OPTIONS 🎀

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

🌍 GLOBAL OPTIONS 🌍

  • --dry-run — Print the command that would be executed, but do not actually execute it. It's giving "look, don't touch." 🙈
  • --no-ioctl-probing — Disable probing for 64-bit IOCTL support.
  • --no-retries — Disable retry logic on transient errors. No second chances, periodt. 💅
  • -o <fmt>, --output-format=<fmt> — Set the reporting format to normal, tabular, 'json, or binary. Only one output format may be used at a time. Pick one, bestie — no multitasking. ✨
  • --output-format-version=<version> — Select 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. Version 2 is the main character here. 👑
  • --quiet — Suppress informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. Shhh, but not in a suspicious way. 🤫
  • --set-options=<key=value>[,<key=value>...] — Set libnvme library options for this invocation. Supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. Very customizable, very demure. 🎀
  • --timeout=<ms> — Set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). Patience is a virtue, iykyk. ⏳
  • -v, --verbose — Increase the level of detail in the output. May be specified multiple times to further increase verbosity. Say it louder for the people in the back. 🔥

These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file. File says one thing, flag says "not today" — flag wins. 💅

🌈 EXAMPLES 🌈

  • Has the program issue the sndk get-error-recovery-log plugin command :
# nvme sndk get-error-recovery-log /dev/nvme0

🦋 NVME 🦋

Part of the nvme-user suite. 💜

💌 Cute sign-off: NVMe source/version, dated 10/30/2026 — NVME-SNDK-GET-ERR(1), mwah! 💋
📦 where this page comes from