NVME-WDC-GET-DRIV(1)

πŸ’… NAME πŸ’…

okay so this is nvme-wdc-get-drive-status β€” it sends the NVMe WDC get-drive-status command and hands you back the result. that's it, that's the gig ✨


πŸŽ€ SYNOPSIS πŸŽ€

nvme [<global-options>] wdc get-drive-status <device>

πŸ¦‹ DESCRIPTION πŸ¦‹

So for the NVMe device you hand it, this sends the super-special WDC-only get-drive-status command and gives you back the extra drive status info. it's giving exclusive πŸ’…

The <device> parameter is mandatory β€” no skipping it, bestie. and it can be either the NVMe character device (ex: /dev/nvme0).

⚠️ Heads up: this will only work on WDC devices that actually support this feature. Results for any other device are undefined β€” like, we don't know, nobody knows, don't ask 😭

On success it returns 0, and an error code otherwise. slay when it works, sad when it doesn't 🫢


🌸 OUTPUT EXPLANATION 🌸

here's the vibe check on every field you'll see:

  • Percent Life Used. β€” The percentage of drive function used. basically how much of the drive's life is cooked πŸ”₯
  • EOL (End of Life) Status β€” The 3 possible states are: Normal, Read Only, or End of Life.
  • Assert Dump Status β€” The 2 possible states are: Present or Not Present.
  • Thermal Throttling Status β€” The 3 possible states are: Off, On, or Unavailable.
  • Format Corrupt Reason β€” The 3 possible states are: Not Corrupted, Corrupt due to FW Assert, or Corrupt for Unknown Reason.

⭐ OPTIONS ⭐

πŸ’œ GLOBAL OPTIONS πŸ’œ

these are defined at the top-level nvme command and are available to this subcommand. icon behavior tbh πŸ‘‘

  • --dry-run β€” Print the command that would be executed, but do not actually execute it. all the vibes, none of the consequences ✨
  • --no-ioctl-probing β€” Disable probing for 64-bit IOCTL support.
  • --no-retries β€” Disable retry logic on transient errors. one shot, no take-backs πŸ’€
  • -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 a lane bestie πŸŽ€
  • --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 β€” don't try it πŸ™ˆ
  • --quiet β€” Suppress informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. shhhh 🀫
  • --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.
  • --timeout=<ms> β€” Set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). literally forever, no cap ⏳
  • -v, --verbose β€” Increase the level of detail in the output. May be specified multiple times to further increase verbosity. say it again, say it again πŸ—£οΈ

These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file. periodt πŸ’…


🌈 EXAMPLES 🌈

  • Has the program issue WDC get-drive-status command:
# nvme wdc get-drive-status /dev/nvme0

πŸ‘‘ NVME πŸ‘‘

Part of the nvme-user suite. we're fam 🫢


okayyy that's the whole page bestie, go forth and get those drive statuses πŸ’–

mwah πŸ’‹ β€” this was the NVMe manual, dated 10/30/2026, page NVME-WDC-GET-DRIV(1). catch you in the next one πŸ¦‹βœ¨

πŸ“¦ where this page comes from