NVME-INTEL-INTERNA(1)

💖 NAME 💖

nvme-intel-internal-log — Retrieve Intel device's internal log and save to file. 💾✨

This is the NVME-INTEL-INTERNA(1) page from the NVMe Manual, and yes bestie, we're getting that Intel internal log and writing it to a file. 🎀

---

🌸 SYNOPSIS 🌸

       nvme [<global-options>] intel internal-log <device> [--log=<NUM>, -l <NUM>]
                       [--region=<NUM>, r <NUM>]
                       [--nlognum=<NUM>, m <NUM>]
                       [--namespace-id=<NUM>, -n <NUM>]
                       [--output-file=<FILE>, -O <FILE>]

---

💅 DESCRIPTION 💅

For the NVMe device given, it sends the Intel vendor unique device log request and saves the result to a file. 🫶

The <device> parameter is mandatory — no skipping it — and may be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1). If you're using the character device, the namespace id parameter is mandatory too. 💡

This will only work on Intel devices supporting this feature, which includes (but is not limited to) all the Intel DC P3xxx family of controllers. Results for any other device are undefined. 😭 Like, do not expect cute behavior from a random non-supporting device, okay?

---

✨ OPTIONS ✨

• -l <NUM>, --log=<NUM> — Log type: 0, 1, or 2 for nlog, event log, and assert log, respectively. 📝
• -n <NUM>, --namespace-id=<NUM> — Namespace to use. The broadcast value 0xffffffff can also be given as all or -1. 🦋
• -O <FILE>, --output-file=<FILE> — Output file; defaults to device name provided. 🎀
• -r <NUM>, --region=<NUM> — Select which core region to retrieve the log from. -1 for all available, if supported by the device. 🌈
• -m <NUM>, --nlognum=<NUM> — When used with nlog, this specifies which nlog to read. -1 for all, if supported by the device. 🔥

---

🌈 GLOBAL OPTIONS 🌈

The following options are defined at the top-level nvme command and are available to this subcommand:

• --dry-run — Print the command that would be executed, but do not actually execute it. 👀
• --no-ioctl-probing — Disable probing for 64-bit IOCTL support. 🛠️
• --no-retries — Disable retry logic on transient errors. 💀
• -o <fmt>, --output-format=<fmt> — Set the reporting format to normal, tabular, 'json, or binary. Only one output format may be used at a time. 📊
• --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. 🚫
• --quiet — Suppress informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. 🤫
• --set-options=<key=value>[,<key=value>...] — Set libnvme library options for this invocation. Supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. 🔧
• --timeout=<ms> — Set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). ⏳
• -v, --verbose — Increase the level of detail in the output. May be specified multiple times to further increase verbosity. 🗣️

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

---

🎀 EXAMPLES 🎀

• Gets the nlog from the device and saves to default file:

# nvme intel internal-log /dev/nvme0 --namespace-id=1 --log=0

• Gets the event log from the device and saves to defined file:

# nvme intel internal-log /dev/nvme0 --namespace-id=1 --log=1 --output-file=MyAwesomeEventLog

---

👑 NVME 👑

Part of the nvme-user suite. 🧚

Catch you later, bestie — source/version NVMe, date 10/30/2026, page NVME-INTEL-INTERNA(1) 🫶💜