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 to0if 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 tonormal,tabular,'json, orbinary. 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. version1uses the original field naming, while version2(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--quietcancels any--verbosefor 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 areforce-4k,mi-probe-enabled,test-base-dirandtest-sysfs-dir.--timeout=<ms>β sets the timeout for the command in milliseconds.infiniteor-1waits 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
- arch rolling: nvme-cli 3.2-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms