NVME-LOG-SELF-TES(1)

💅 NAME 💅

nvme-log-self-test — bestie, this one pulls the log info that the device-self-test kicked off and shows it to you. That's it, that's the vibe. 🎀

Oh and hey — real quick — this whole page lives in the NVMe Manual. So when you see shut-down-your-brain abbreviations floatin' around, just know the manual's got your back. 🫶

---

✨ SYNOPSIS ✨

nvme [<global-options>] log self-test <device>
                        [--log-entries=<entries> | -e <entries>]

---

🦋 DESCRIPTION 🦋

Okay so here's the tea ☕ — this grabs the log pages off your NVMe device that match the self-test you asked for, and hands you back the returned structure with the 20 most recent results. Iconic. No cap.

The <device> parameter is mandatory (like, you literally cannot skip it) and it can be either:

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

On success, that returned log structure can come back at you in a couple different ways depending on which option flags you vibe with 😌 — the structure can be parsed by the program and printed in a readable format, or you can get the raw buffer, or the json format. Choose your fighter.

By default? The log prints out in the normal readable format. Nice, clean, no chaos. 🌸

---

💅 OPTION 💅

• -e <entries>, --log-entries=<entries> — tells the program how many DST log entries it should request from the device. Rules, bestie: it must be at least one, and it shouldn't go over the 20 entries cap. Defaults to 20 DST log entries. Respect the limit fr fr. 💀

---

👑 GLOBAL OPTIONS 👑

These bad boys are defined at the top-level nvme command, and they're all available to this subcommand. So yes, you get to use them here too. Slay.

• --dry-run — prints the command that would be executed, but doesn't actually execute it. All the fantasy, none of the commitment. 🙈
• --no-ioctl-probing — disables probing for 64-bit IOCTL support.
• --no-retries — disables 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 at a time though — pick a lane. ✨
• --output-format-version=<version> — selects the output format version. Version 1 uses the original field naming, while version 2 (the default) gives you more consistent and script-friendly field names. Other versions get rejected — no negotiating. 😭
• --quiet — suppresses informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. 🤫
• --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this invocation. 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 with no time limit (0xffffffff). Patient queen energy. ⏳
• -v, --verbose — increases the level of detail in the output. Can be specified multiple times to keep cranking that verbosity up. 📈

Also! These options can be set as machine-wide defaults in nvme-cli.conf(5) — but a command-line flag always overrides the file. Command line stays the main character. 👑

---

🌈 EXAMPLES 🌈

• Get the self-test-log and print it in a human readable format:

# nvme log self-test /dev/nvme0

• Print the raw output to a file:

# nvme log self-test /dev/nvme0 -o "binary"

• Get the self-test-log and print it in a json format:

# nvme log self-test /dev/nvme0 -o "json"

---

🧚 NVME 🧚

Part of the nvme-user suite. One of the squad. 💜

---

And that's the whole page, bestie — go forth and self-test 🍓✨ This masterpiece was brought to you by the NVMe crew, dated 10/30/2026, filed under NVME-LOG-SELF-TES(1). See you in the group chat 💖