NVME-INTEL-SMART-(1)
π NVME-INTEL-SMART-(1) β the nvme intel smart-log-add glow-up π
okay bestie, so this is a page from the NVMe Manual (yes, the NVME-INTEL-SMART-(1) one, we're fancy) and it's all about pulling the Intel Additional SMART log page off your drive. let's get into it β¨
β¨ NAME β¨
nvme-intel-smart-log-add β sends the NVMe Intel Additional SMART log page request, then hands you back the result and the log. it's giving "ask and you shall receive" π«Ά
π¦ SYNOPSIS π¦
nvme [<global-options>] intel smart-log-add <device>
[--namespace-id=<nsid> | -n <nsid>]
[--raw-binary | -b]
[--json | -j]
look at that little command, so iconic, so compact π
πΈ DESCRIPTION πΈ
so what does it do. it retrieves the NVMe Intel Additional SMART log page from your device and gives you the returned structure. that's the whole vibe. π₯
the <device> parameter is mandatory β like, non-negotiable, you literally cannot skip it. and it can be either:
- the NVMe character device (example:
/dev/nvme0), or - a namespace block device (example:
/dev/nvme0n1)
on success, the returned smart log structure may come back in one of several ways depending on which option flags you picked: the structure may be parsed by the program and printed in a readable format, or the raw buffer may be printed to stdout for another program to parse. your call, main character π
π OPTIONS π
-n <nsid>,--namespace-id=<nsid>β retrieve the Additional SMART log for the given nsid. this is optional, and ngl its success may depend on the device's capabilities to provide this log on a per-namespace basis (peep the NVMe Identify Controller for this capability, iykyk). the default nsid to use is0xfffffffffor the device global SMART log. the broadcast value0xffffffffcan also be given asallor-1. π«-b,--raw-binaryβ print the raw Intel Additional SMART log buffer tostdout. no parsing, no edit, just vibes and bytes π-j,--jsonβ dump output in json format. for the script girlies β
π GLOBAL OPTIONS π
the following options are defined at the top-level nvme command and are available to this subcommand. so like, they're not this command's options, they're the parent's, but they still show up to the party π
--dry-runβ print the command that would be executed, but do not actually execute it. manifesting the command without committing π--no-ioctl-probingβ disable probing for 64-bit IOCTL support. periodt, no probing.--no-retriesβ disable retry logic on transient errors. one shot, one opportunity π«‘-o <fmt>,--output-format=<fmt>β set the reporting format tonormal,tabular,'json, orbinary. only one output format may be used at a time β pick a lane, bestie π--output-format-version=<version>β select 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. we don't do off-brand versions here π--quietβ suppress informational messages. errors are still reported, and--quietcancels any--verbosefor the library log level. shhhh π€«--set-options=<key=value>[,<key=value>...]β set libnvme library options for this invocation. supported keys areforce-4k,mi-probe-enabled,test-base-dirandtest-sysfs-dir. custom settings, custom girl π--timeout=<ms>β set the timeout for the command in milliseconds.infiniteor-1waits without a time limit (0xffffffff). no cap, it'll wait forever β³-v,--verboseβ increase the level of detail in the output. may be specified multiple times to further increase verbosity. the more the merrier, stack it up π₯
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, always π
π EXAMPLES π
- print the Intel Additional SMART log page in a human readable format:
# nvme intel smart-log-add /dev/nvme0
- print the raw Intel Additional SMART log to a file:
# nvme intel smart-log-add /dev/nvme0 --raw-binary > smart_log.raw
β οΈ it is probably a bad idea to not redirect stdout when using this mode. like, don't do it. the raw buffer will just spill everywhere and you'll be sad π
π NVME π
part of the nvme-user suite. one of us, one of us π§
okay that's the whole page, and yes the manual is NVMe, dated 10/30/2026, page NVME-INTEL-SMART-(1) β mwah, thanks for reading bestie, go check your SMART log πβ¨π
π¦ 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