NVME-SNDK-VS-DRIV(1)

📦
version 3.2 · 9 versions
, in arch rolling

💖 NAME 💖

okay so bestie, this is the nvme-sndk-vs-drive-info page from the nvme manual set — it's the one that sends the NVMe sndk vs-drive-info command and hands you back the result. 🫶

✨ SYNOPSIS ✨

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

🌸 DESCRIPTION 🌸

So for the NVMe device you point at, this sends that one very specific sndk vs-drive-info command and gives you the extra drive information on top. It's giving "behind the scenes lore drop" energy, honestly.

The <device> parameter is mandatory — like, non-negotiable, main character requirement — and it has to be the NVMe character device (for example /dev/nvme0).

⚠️ Heads up: this only works on Sandisk devices that actually support this feature. Results for any other device are undefined — so yeah, don't come crying to me if you try it on something else, iykyk 😭

On success it returns 0, and an error code otherwise. Periodt. 💅

🎀 OUTPUT EXPLANATION 🎀

Depending on the drive, there are several different fields that come back from this command:

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

🦋 EXAMPLE 🦋

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

👑 OPTIONS 👑

🌈 GLOBAL OPTIONS 🌈

These ones live at the top-level nvme command and are available to this subcommand too — so you get them for free, slay:

  • --dry-run — prints the command that would be executed, but doesn't actually execute it. Just a little dress rehearsal, no cap. 🙈
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support.
  • --no-retries — disables the retry logic on transient errors. One shot, no takebacks. 💀
  • -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. (Yes, the quote mark in 'json is literally there in the original — don't @ me.) ⭐
  • --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. Other versions are rejected. 🚫
  • --quiet — suppresses informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. 🤫
  • --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.
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). Literally forever, bestie. ⏳
  • -v, --verbose — increases the level of detail in the output. May be specified multiple times to further increase verbosity. Spam it, honestly. 🔥

These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file — CLI stays winning. 👑

💜 NVME 💜

Part of the nvme-user suite. 🧚

That's the whole vibe check — this page is from the NVMe manual, dated 10/30/2026, and it's NVME-SNDK-VS-DRIV(1) in case you need to cite your sources. Stay hydrated, go read your drive info, ily! 🍓💖✨

📦 where this page comes from