NVME-WDC-VS-ERROR(1)

📦
version 3.2 · 14 versions
, in arch rolling

💖 nvme-wdc-vs-error-reason-identifier(1) — like, the WDC telemetry error reason identifier page, bestie 💖

okay so first things first: this is part of the NVMe Manual, and the command itself is nvme-wdc-vs-error-reason-identifier — say that five times fast, I dare you 😭

✨ NAME ✨

nvme-wdc-vs-error-reason-identifier — grab the error reason identifier field out of a WDC device's telemetry log. that's the whole vibe 🎀

🦋 SYNOPSIS 🦋

nvme [<global-options>] wdc 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 for the host generated log or the controller initiated one. your choice, main character energy 💅

⚠️ real talk: the controller initiated telemetry log page option must be enabled to retrieve the error reason id for that log page id. no option, no id, no cap.

the <device> parameter is mandatory — not optional, not vibes-based — and it has to be the NVMe character device, like /dev/nvme0 for example.

💀 also: this only works on WDC devices that support this feature. results for any other device are undefined — literally undefined, don't come for me.

on success it returns 0, and an error code otherwise. slay ✨

💜 OPTIONS 💜

  • -i <id>, --log-id=<id> — tells it which telemetry log id's error reason identifier to go get. use id 7 for the host generated log page, use id 8 for the controller initiated log page. the default? 7/host generated, periodt 🫶
  • -O <FILE>, --file=<FILE> — output file, duh. 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. yes the whole long filename, that's the bit 🎀

🌈 GLOBAL OPTIONS 🌈

these ones live at the top-level nvme command and are available to this subcommand too. iykyk 👑

  • --dry-run — prints the command that would be executed, but doesn't actually execute it. manifesting the command without running the command, honestly iconic ✨
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support. no probing, no problem 💅
  • --no-retries — disables 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, bestie — pick a lane 🌸
  • --output-format-version=<version> — picks 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. any other versions get rejected — not invited to the party 🙈
  • --quiet — suppresses informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. it's giving "shh, i'm in my quiet era" 🤫
  • --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this invocation. the supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. keys and values, keys and values 💖
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). time is a construct anyway ⏳
  • -v, --verbose — increases the level of detail in the output. can be specified multiple times to increase verbosity even further. more v's, more lore 🔥
💡 these options can also be set as machine-wide defaults in nvme-cli.conf(5). and a command-line flag always overrides the file. always. no exceptions. periodt 👑

🍓 EXAMPLES 🍓

  • retrieves the host generated error reason identifier field and saves it in the file host_gen_error_reason_id.bin:
# nvme wdc 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 the file ctlr_init_error_reason_id.bin:
# nvme wdc vs-error-reason-identifier /dev/nvme0 -i 8 -O ctlr_init_error_reason_id.bin

🧚 NVME 🧚

part of the nvme-user suite. family 💖

okay that's the whole page! 🎀 this one's from the NVMe suite, dated 10/30/2026, and the page id is NVME-WDC-VS-ERROR(1) — go forth and retrieve those error reason identifiers, bestie, you're gonna slay 🦋✨👑

📦 where this page comes from