NVME-WDC-VS-DRIVE(1)

📦
version 3.2 · 14 versions
, in arch rolling

💅 NVME-WDC-VS-DRIVE(1) — the nvme-wdc-vs-drive-info girlies' edition

okay so this is a page from the NVMe Manual, bestie, and it's about nvme-wdc-vs-drive-info. yes the command name on the page is longer than the filename, that's just how she is. lowkey iconic of her.

✨ NAME ✨

nvme-wdc-vs-drive-info — sends the NVMe WDC vs-drive-info command and gives you the result back. that's it, that's the whole job. 🎀

🌸 SYNOPSIS 🌸

nvme [<global-options>] wdc vs-drive-info <device>

🦋 DESCRIPTION 🦋

so for the NVMe device you hand her, she sends the unique WDC vs-drive-info command and provides the additional drive information. it's giving ✨extra✨ info, and honestly? slay.

the <device> parameter is mandatory — non-negotiable, bestie, she will not work without it — and it must be the NVMe character device (ex: /dev/nvme0).

real talk: this will only work on WDC devices that support this feature. results for any other device are undefined — like, nobody knows what happens, so don't come crying to me. 💀

on success it returns 0. error code otherwise. periodt.

🔥 OUTPUT EXPLANATION 🔥

there are several different fields returned from this command, and which ones you get depends on the drive. main character energy: every drive gets a different lineup. 💅

  • Drive HW Revision
  • FTL Unit Size
  • Customer Serial Number
  • HyperScale Boot Version
  • TCG Device Ownership

🎀 EXAMPLE 🎀

# nvme wdc vs-drive-info /dev/nvme0

literally just that. gorgeous. no notes. 🫶

⭐ OPTIONS ⭐

💜 GLOBAL OPTIONS

the following options are defined at the top-level nvme command and are available to this subcommand (so yes, you can use them here too, bestie — they're not gatekept):

  • --dry-run — prints the command that would be executed but does not actually execute it. it's the "window shopping" option, fr fr. 🛍️
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support. no probing, no poking, we're done here.
  • --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 may be used at a time — pick a lane, queen. ✨
  • --output-format-version=<version> — selects the output format version. version 1 uses the original field naming, while version 2 (the default) provides more consistent and script-friendly field names. other versions are rejected — no exceptions. 🙈
  • --quiet — suppresses informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. she's quiet, not silent, iykyk.
  • --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. yes that's the whole list, don't invent more. 🍓
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). forever girlie behavior. ⏳
  • -v, --verbose — increases the level of detail in the output. may be specified multiple times to further increase verbosity. stack 'em like bracelets. 🌈
💖 these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file — flags stay winning, no cap.

👑 NVME 👑

part of the nvme-user suite. obviously. she runs with a whole crew. 🧚

okay that's the whole page, bestie — go forth and interrogate your WDC drive 💜

— from the NVMe fam, dated 10/30/2026, page NVME-WDC-VS-DRIVE(1). mwah 💋

📦 where this page comes from