NVME-SMART-LOG(1)
π NVME-SMART-LOG β the deprecated-but-still-iconic smart log request β¨
okay bestie, so this is a page from the NVMe Manual (like, the nvme command family, iykyk) β and it's all about nvme-smart-log, which sends an NVMe SMART log page request and returns the result and log. Huge, right? Except... it's deprecated π. Read on, I got you.
πΈ NAME πΈ
nvme-smart-log β sends the NVMe SMART log page request, gives you back the result and the log. Yep. That's the whole vibe. But also: it's deprecated, so, like, noted π.
π SYNOPSIS π
nvme [<global-options>] smart-log <device>
[--namespace-id=<nsid> | -n <nsid>]
[--raw-binary | -b]
That's the shape of it β top-level nvme, then smart-log, then your <device>, plus optional namespace id and raw-binary flags. Slay.
π¦ DESCRIPTION π¦
So here's the tea: this command is a deprecated alias for nvme-log-smart(1). It's literally just kept around for scripts that were written against nvme-cli versions older than 3.0. The options and behavior are identical, fr fr β the only thing being retained is the top-level command name. Nothing else changed, periodt.
New scripts should be using nvme log smart instead. This alias prints a deprecation warning on stderr and may be removed in a future release β so don't get too attached, bestie π.
For the full option reference, go see nvme-log-smart(1). That's where the real detail lives.
β¨ GLOBAL OPTIONS β¨
These are defined up at the top-level nvme command, and they're available to this subcommand too. Global queen behavior π:
--dry-runβ prints the command that would be executed, but doesn't actually execute it. All the looks, none of the commitment π--no-ioctl-probingβ disables probing for 64-bit IOCTL support.--no-retriesβ disables retry logic on transient errors. No second chances, sorry π-o <fmt>,--output-format=<fmt>β sets the reporting format tonormal,tabular,'json, orbinary. Only one output format may be used at a time β pick a lane π«Ά--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 β don't even try it π--quietβ suppresses informational messages. Errors are still reported, and--quietcancels any--verbosefor the library log level. Shhh π€«--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). Patience is a virtue β-v,--verboseβ increases the level of detail in the output. May be specified multiple times to further increase verbosity. More is more, 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 main character, always π
π EXAMPLES π
No Examples
Yeah. That's the whole section. No examples. Iconic of them to say it like that, honestly π
π NVME π
Part of the nvme-user suite π«Ά
β SEE ALSO β
nvme-log-smart(1)β the non-deprecated one, go there for the full option reference, bestie π
and that's the page!! this came from the NVMe manual, dated 10/30/2026 β mwah, love that for us πβ¨
π¦ 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