NVME-SNDK-CU-SMAR(1)

💅 nvme-sndk-cu-smart-log(1) — the NVMe Manual, bestie edition 🎀

okay so real talk: this one lives in the NVMe Manual, and honestly? it's giving "niche but iconic." it's a vendor-unique situation, so buckle up 🦋

✨ NAME ✨

nvme-sndk-cu-smart-log — the one where you send an NVMe Sandisk cu-smart-log Vendor Unique Command and it hands you back the result. that's the whole vibe 🫶

🌸 SYNOPSIS 🌸

nvme [<global-options>] sndk cu-smart-log <device>
                        [--uuid-index=<uuid-index> | -u <uuid-index>]

💖 DESCRIPTION 💖

so for the NVMe device you hand it, it retrieves and formats the Vendor Unique Sandisk 0xCA log page. that's it. that's the job. and it does it slayfully ✨

the <device> parameter is mandatory — like, non-negotiable, main character requirement — and it can be either the NVMe character device (ex: /dev/nvme0) or the block device (ex: /dev/nvme0n1). either one, we're not picky 💅

⚠️ big heads up: this will only work on Sandisk devices that support this feature. results for any other device are undefined — so like, don't come for me if you poke a non-Sandisk drive with this. undefined is undefined, no cap 😭

on success it returns 0, and an error code otherwise. simple. clean. periodt 💜

🔥 OPTIONS 🔥

• -u <uuid-index>, --uuid-index=<uuid-index> — sets the uuid-index of the log page you want retrieved. defaults to 0 if you don't give it anything, because it's generous like that 🎁

👑 GLOBAL OPTIONS 👑

these bad boys are defined at the top-level nvme command, which means they're available to this subcommand too. they're the group chat everyone's in 💬

• --dry-run — prints the command that would be executed but doesn't actually execute it. it's the "window shopping" of flags, iconic honestly 🛍️
• --no-ioctl-probing — disables probing for 64-bit IOCTL support. no probing. we respect the boundary 🚫
• --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 at a time, bestie — we don't do "why not both" here 🙅‍♀️
• --output-format-version=<version> — picks the output format version. version 1 uses the original field naming, while version 2 (the default, the moment) provides more consistent and script-friendly field names. any other version gets rejected — not on the list, not getting in 💀
• --quiet — suppresses informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. so it's like, the anti-yapper flag 🤫
• --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. customisation queen behavior 🎀
• --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). no clock-watching, we're patient 💤
• -v, --verbose — increases the level of detail in the output. may be specified multiple times to further increase verbosity — stack it, we love a repeat offender 📈

and psst: 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, no debate 👑

🌈 EXAMPLES 🌈

• has the program issue the Sandisk cu-smart-log plugin Command, like the icon it is:

# nvme sndk cu-smart-log /dev/nvme0

⭐ NVME ⭐

part of the nvme-user suite. one of us, one of us 🧚

---

and that's the whole page, bestie 🫶 this lil guy is from the NVMe fam, version/date situation is 10/30/2026 — go forth and retrieve those vendor-unique log pages responsibly 💜✨