NVME-SNDK-VS-TEMP(1)
π NVME-SNDK-VS-TEMP(1) π
okay bestie, so this page lives in the NVMe Manual and it's literally about printing out your drive's temperature tea β β like, all the thermal stats, laid out. let's get into it π«Ά
β¨ NAME β¨
nvme-sndk-vs-temperature-stats β display temperature-related statistics π‘οΈπ
β¨ SYNOPSIS β¨
nvme [<global-options>] sndk vs-temperature-stats <device>
β¨ DESCRIPTION β¨
so for the NVMe device you hand over, this prints the temperature statistics. that's the whole vibe. simple, iconic β¨
the <device> parameter is mandatory and it's the NVMe character device (ex: /dev/nvme0). no device, no stats, periodt π
heads up: this only works on Sandisk devices that support this feature. results for any other device are undefined β like, genuinely undefined, not "undefined bestie we'll figure it out". π
here's the expected status and description situation, no cap π:
- The current composite temperature β device temperature π‘οΈ
- Warning Composite TEMPerature threshold β temp of overheating π₯
- Critical Composite TEMPerature threshold β temp of critical overheating π¨
- Device Initiated Thermal Throttling support status β
0= unsupported,1= supported - Host Controlled Thermal Management support β
0= unsupported,1= supported - Thermal Management Temperature 1 (Light throttle) β temp to start light throttle πΈ
- Thermal Management Temperature 1 Transition Counter β # times switched into light throttle
- Thermal Management Temperature 1 Total Time β # seconds spent in light throttle β±οΈ
- Thermal Management Temperature 2 (Heavy throttle) β temp to start heavy throttle π₯΅
- Thermal Management Temperature 2 Transition Counter β # times switched into heavy throttle
- Thermal Management Temperature 2 Total Time β # seconds spent in heavy throttle β±οΈ
- Thermal Shutdown Threshold β temp of device shutdown π
on success it returns 0, error code otherwise. slay β
β¨ OPTIONS β¨
β¨ GLOBAL OPTIONS β¨
these bad boys are defined at the top-level nvme command, and they're available to this subcommand too. iykyk π
--dry-runβ print the command that would be executed, but don't actually execute it. it's giving "look but don't touch" π«Ά--no-ioctl-probingβ disable probing for 64-bit IOCTL support.--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, so pick your fighter π--output-format-version=<version>β select the output format version. version1uses the original field naming, while version2(default) provides more consistent and script-friendly field names. other versions are rejected π«--quietβ suppress informational messages. errors are still reported, and--quietcancels any--verbosefor the library log level. shhh π€«--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.--timeout=<ms>β set the timeout for the command in milliseconds.infiniteor-1waits without a time limit (0xffffffff). no clock-watching energy β°-v,--verboseβ increase the level of detail in the output. may be specified multiple times to further increase verbosity. the more the merrier β¨
these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. file found dead in a ditch, flag ate π
β¨ EXAMPLES β¨
- displays the temperature stats for the device:
# nvme sndk vs-temperature-stats /dev/nvme0
β¨ NVME β¨
part of the nvme-user suite. one of us, one of us π
okay that's the whole page bestie, go read your temps ππ¦
NVMe Β· 10/30/2026 Β· NVME-SNDK-VS-TEMP(1) β mwah, that's the version, the date, and the manual name all wrapped up in a little bow π love u, go touch grass (but check your drive's thermals first) π
π¦ 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