NVME-SNDK-CLOUD-B(1)

📦
version 3.2 · 9 versions
, in arch rolling

💅 nvme-sndk-cloud-boot-SSD-version — like, the whole manual, but make it make sense

okay bestie, gather round 🫶 this is a page straight out of the NVMe Manual, and it's all about one lil subcommand that tells you your drive's Cloud Hyperscale Boot Version. yes, that's a real thing. no cap.

✨ NAME ✨

nvme-sndk-cloud-boot-SSD-version — the sndk plugin command that displays the Cloud Boot SSD Version. that's the whole gig. iconic, honestly 🎀

🌸 SYNOPSIS 🌸

nvme [<global-options>] sndk cloud-boot-SSD-version <device>

that's it. that's the shape of it. global options up front, then sndk, then cloud-boot-SSD-version, then the device. slay 💅

🦋 DESCRIPTION 🦋

so for the NVMe device you hand it, this command displays the current Cloud Hyperscale Boot Version — but only if the device supports it, bestie. if it doesn't? it's giving "not my problem." 💀

the <device> parameter is mandatory and it's an NVMe character device (ex: /dev/nvme0). mandatory mandatory. like, don't skip it. 🙈

and the receipts: on success it returns 0, and an error code otherwise. periodt.

✨ OPTIONS ✨

🌈 GLOBAL OPTIONS 🌈

okay so these ones live at the top-level nvme command — but guess what, they're available to this subcommand too. sharing is caring 💖

  • --dry-run — prints out the command it would run, but doesn't actually run it. a little look-but-don't-touch moment 👀
  • --no-ioctl-probing — turns off probing for 64-bit IOCTL support. no probing, no vibes check.
  • --no-retries — kills the retry logic for transient errors. one shot, one opportunity 😭
  • -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, 'json, or binary. one output format at a time only, bestie — don't be greedy 🍓
  • --output-format-version=<version> — picks the output format version. version 1 is the original field naming, and version 2 (the default) is more consistent and script-friendly with the field names. any other version gets rejected. be normal or be v2, no in-betweens.
  • --quiet — suppresses the informational messages. errors still get reported, and heads up: --quiet cancels any --verbose for the library log level. they literally cannot coexist, it's giving enemies to lovers 💀
  • --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. very much the "advanced settings" screen energy 🔥
  • --timeout=<ms> — sets the timeout for the command, in milliseconds. infinite or -1 waits with no time limit (0xffffffff). patient queen behavior ⭐
  • -v, --verbose — cranks up the level of detail in the output. you can pass it multiple times to get even more verbose. more. MORE. 📈
💡 also: these options can be set as machine-wide defaults in nvme-cli.conf(5). but a command-line flag always overrides the file — the flag wins, every time, main character energy 👑

🎀 EXAMPLES 🎀

  • displays the cloud boot ssd version for the device:
# nvme sndk cloud-boot-SSD-version /dev/nvme0

look at that. clean. flawless. one line and you're done. ate and left no crumbs 🍽️✨

👑 NVME 👑

this bad boy is part of the nvme-user suite. iykyk 🫶

aaaaand that's the page!! 🧚 ngl it's a short one but she's cute. this masterpiece came from the NVMe source, dated 10/30/2026, and lives at NVME-SNDK-CLOUD-B(1) in the manual. mwah, go check your boot versions bestie 💜

📦 where this page comes from