NVME-SNDK-VS-ERRO(1)

📦
version 3.2 · 9 versions
, in arch rolling

🦋 NVME-SNDK-VS-ERRO(1) — the NVMe Manual, bestie edition 🦋

okay so this is a page from the NVMe Manual (yes, that one, the nvme-user suite manual) and it's all about one very specific little subcommand. buckle up 💖

✨ NAME ✨

nvme-sndk-vs-error-reason-identifier — literally retrieves a sndk device's telemetry log error reason identifier field. that's the whole job. that's the vibe. 🎀

✨ SYNOPSIS ✨

nvme [<global-options>] sndk vs-error-reason-identifier <device>
                        [--log-id=<NUM>, -i <NUM>]
                        [--file=<FILE>, -O <FILE>]

✨ DESCRIPTION ✨

so for the NVMe device you hand over, this pulls the telemetry log error reason id field — either from the host generated log or from the controller initiated log. 🫶 heads up though: for the controller initiated telemetry log page, that option has to be enabled before you can get the error reason id for that log page id. no enabling, no goodies. iykyk.

the <device> parameter is mandatory and it has to be the NVMe character device (ex: /dev/nvme0). not a block device, not a vibe, the char device. periodt.

this will only work on Sandisk devices that support this feature. results for any other device are undefined — like, genuinely undefined, not cute-undefined. don't come for me if you try it elsewhere. 💀

on success it returns 0. otherwise you get an error code. that's the deal.

✨ OPTIONS ✨

  • -i <id>, --log-id=<id> — tells it which telemetry log id to grab the error reason identifier from. use id 7 for the host generated log page, use id 8 for the controller initiated log page. the default is 7/host generated, so if you don't say anything it goes host mode. slay. ⭐
  • -O <FILE>, --file=<FILE> — the output file! defaults to "<device serial number>_error_reason_identifier_host_<date>_<time>.bin" for the host generated log, or "<device serial number>_error_reason_identifier_ctlr_<date>_<time>.bin" for the controller initiated log. the serial number and timestamp just slot themselves in, main character energy fr fr. 🎀

✨ GLOBAL OPTIONS ✨

these are defined up at the top-level nvme command and they're available to this subcommand too. group chat rules: everyone gets them. 💅

  • --dry-run — prints the command that would be executed but does not actually execute it. a little preview era, no consequences. 🙈
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support. no probing, no asking, just vibes. ✨
  • --no-retries — disables the retry logic on transient errors. one shot, one opportunity. 😭
  • -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, 'json, or binary. only one output format at a time please, we don't do multitasking here. (yes, the original really does have that stray quote before json, i'm keeping it exactly, no cap. 🫶)
  • --output-format-version=<version> — picks the output format version. version 1 uses the original field naming, while version 2 (default) gives you more consistent and script-friendly field names. any other version gets rejected, sorry bestie. 🚫
  • --quiet — suppresses informational messages. errors still get reported, and --quiet cancels any --verbose for the library log level. it's giving "i'm not reading the group chat but i'll still answer if it's urgent". 💀
  • --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. mix and match, comma-separated, go off. 🌈
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). patience is a virtue, or whatever. ⏳
  • -v, --verbose — increases the level of detail in the output. can be specified multiple times to crank the verbosity even further. stacking buffs, iconic. 🔥

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

✨ EXAMPLES ✨

  • retrieves the host generated error reason identifier field and saves it in file host_gen_error_reason_id.bin.
# nvme sndk vs-error-reason-identifier /dev/nvme0 -i 7 -O host_gen_error_reason_id.bin
  • retrieves the controller initiated error reason identifier field and saves it in file ctlr_init_error_reason_id.bin.
# nvme sndk vs-error-reason-identifier /dev/nvme0 -i 8 -O ctlr_init_error_reason_id.bin

look at us, two whole examples, both ate. 💖

✨ NVME ✨

part of the nvme-user suite. family. 🫶

okay that's the whole page, thanks for coming to my ted talk 💜 this gem is from the NVMe manual, version dated 10/30/2026 — go forth and retrieve those error reason identifiers, bestie. NVME-SNDK-VS-ERRO(1) out. 🦋🌸

📦 where this page comes from