NVME-INTEL-TEMP-S(1)

💅 nvme-intel-temp-stats — the NVMe Manual, section 1, bestie ✨

Okay so real quick before we dive in: this page is NVME-INTEL-TEMP-S(1), from the NVMe Manual, and it's all about nvme-intel-temp-stats. Yes the name is a mouthful. No we're not changing it. Let's go 🎀

---

🦋 NAME 🦋

nvme-intel-temp-stats — sends an NVMe SMART log page request, and gives you back the result and the log. That's it. That's the whole vibe. 💖

---

✨ SYNOPSIS ✨

nvme [<global-options>] intel temp-stats <device> [--raw-binary | -b]

---

🌸 DESCRIPTION 🌸

So what this does is it retrieves the NVMe Intel Additional SMART log page from the device, and then hands you the returned structure. Simple, iconic, no cap. 👑

The <device> parameter is mandatory — like, you cannot skip it, it's giving main character energy and it needs to be there. It can be either:

• the NVMe character device, ex: /dev/nvme0, or
• a namespace block device, ex: /dev/nvme0n1.

On success, the returned smart log structure may come back in one of several ways depending on which option flags you used, bestie — because apparently one way wasn't enough 💀. Either:

• the structure gets parsed by the program and printed in a readable format, or
• the raw buffer gets printed to stdout so another program can parse it instead. iykyk.

---

🧚 OPTIONS 🧚

• -b, --raw-binary — prints the raw temperature stats log buffer straight to stdout. No parsing, no pretty printing, just raw vibes. 🫶

---

⭐ GLOBAL OPTIONS ⭐

The following options are defined at the top-level nvme command, and — good news — they're available to this subcommand too. Slay. 🌈

• --dry-run — prints the command that would be executed, but does not actually execute it. It's the "look but don't touch" of flags. 🙈
• --no-ioctl-probing — disables probing for 64-bit IOCTL support.
• --no-retries — disables the retry logic on transient errors. One shot, one opportunity. 😭
• -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, 'json, or binary. Only one output format may be used at a time, so pick your fighter. 💅
• --output-format-version=<version> — selects the output format version. Version 1 uses the original field naming, while version 2 (the default) provides more consistent and script-friendly field names. Other versions are rejected — not sorry, those are the rules. ⭐
• --quiet — suppresses informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. So it's not a full mute button, it's a selective mute. 👑
• --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this invocation. The 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). Basically "however long it takes, bestie." 💀
• -v, --verbose — increases the level of detail in the output. May be specified multiple times to further increase verbosity. Stack 'em like bracelets. 🎀

These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file — the flag is the main character, the file is the supporting cast. 💖

---

🔥 EXAMPLES 🔥

1. Print the temperature stats log page in a human readable format:

# nvme intel temp-stats /dev/nvme0

2. Print the raw SMART log to a file:

# nvme intel temp-stats /dev/nvme0 --raw-binary > temp_stats_log.raw

It is probably a bad idea to not redirect stdout when using this mode. Like, genuinely, redirect it. Don't raw-dump that buffer all over your terminal, please and thank you. 🙏

---

🌺 NVME 🌺

Part of the nvme-user suite. Family business. 🫶

---

Okay that's the whole page, bestie — you ate that 💅. This was NVME-INTEL-TEMP-S(1) from the NVMe Manual, dated 10/30/2026, version NVMe. Now go read your logs. Mwah. 💜✨