NVME-WDC-CU-SMART(1)

πŸ’– nvme-wdc-cu-smart-log πŸ’–

okay bestie, so this is a page from the nvme manual β€” like, the NVMe Manual, the whole nvme-user suite vibe β€” and today's main character is nvme-wdc-cu-smart-log, aka the tool that hits up your WDC drive for its very own vendor-unique log page and then formats it all pretty for you. ✨


🌸 NAME 🌸

nvme-wdc-cu-smart-log β€” sends the NVMe WDC cu-smart-log Vendor Unique Command, and returns the result. that's it, that's the whole job, and she does it gorgeously πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

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

πŸ¦‹ DESCRIPTION πŸ¦‹

so for the NVMe device you hand her, she retrieves and formats the Vendor Unique WDC 0xCA log page. iconic behavior, honestly.

the <device> parameter is mandatory β€” no device, no vibes. and it can be either the NVMe character device (ex: /dev/nvme0) or the block device (ex: /dev/nvme0n1). either one works, she's not picky 🫢

⚠️ quick reality check, bestie: this will only work on WDC devices that actually support this feature. results for any other device are undefined β€” like, genuinely undefined, not the cute kind of undefined. don't come crying to me 😭

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


✨ OPTIONS ✨

  • -u <uuid-index>, --uuid-index=<uuid-index> β€” sets the uuid-index of the log page to be retrieved. defaults to 0 if you don't say anything, which is very chill of her πŸ’œ

🌈 GLOBAL OPTIONS 🌈

these ones live at the top-level nvme command, but they're available to this subcommand too, so she's got the full group chat behind her:

  • --dry-run β€” prints the command that would be executed, but doesn't actually execute it. all the fantasy, zero commitment πŸ™ˆ
  • --no-ioctl-probing β€” disables probing for 64-bit IOCTL support.
  • --no-retries β€” disables retry logic on transient errors.
  • -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 chaos 🌸 β€” ngl that stray apostrophe in there is literally in the original, i'm just the messenger.
  • --output-format-version=<version> β€” selects 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, no exceptions, the door is closed πŸ’€
  • --quiet β€” suppresses informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. she goes whisper mode but she will still tell you when things are broken 🀫
  • --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.
  • --timeout=<ms> β€” sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). she has all the time in the world, apparently ⭐
  • -v, --verbose β€” increases the level of detail in the output. may be specified multiple times to further increase verbosity. stack it, queen πŸ‘‘
πŸ’‘ these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file β€” flag stays winning, no cap.

πŸ“ EXAMPLES πŸ“

  • has the program issue WDC cu-smart-log plugin Command:
# nvme wdc cu-smart-log /dev/nvme0

look at her go. flawless. πŸ”₯


πŸ‘‘ NVME πŸ‘‘

part of the nvme-user suite. one big happy family πŸ’–


okay and finally, the cute sign-off you asked for: this adorable little page comes from the NVMe manual, dated 10/30/2026, and it documents NVME-WDC-CU-SMART(1) πŸŽ€ go forth and read your WDC logs, bestie, you're gonna slay πŸ¦‹βœ¨

πŸ“¦ where this page comes from