NVME-SOLIDIGM-SMAR(1)

💖 nvme-solidigm-smart-log-add(1) — the Solidigm SMART log girly 💖

okay so bestie, welcome to the nvme-solidigm-smart-log-add page from the NVMe Manual — this is the one that goes and grabs the Solidigm vendor-specific SMART log for you. it's giving "let me just check on my drive's whole vibe" and honestly? iconic. ✨

---

🌸 NAME 🌸

nvme-solidigm-smart-log-add — Retrieve Solidigm SMART Log. that's it, that's the whole job, and she does it well 💅

---

🎀 SYNOPSIS 🎀

nvme [<global-options>] solidigm smart-log-add <device>
                        [--namespace-id=<nsid> | -n <nsid>]

---

🦋 DESCRIPTION 🦋

So what this does: it retrieves the Solidigm vendor-specific SMART log for the NVMe device you point at — and optionally for the specific namespace you name — then it displays that log for you. literally just "give me the tea about this drive" energy 🌈

The <device> parameter is mandatory (no, you can't skip it, she needs to know which drive you're talking about 🙈) and it can be either:

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

either one works, pick your fighter 💖

---

✨ OPTIONS ✨

• -n <nsid>, --namespace-id=<nsid> — retrieve the log for the given nsid. if you don't specify it, the log gets retrieved for all namespaces (very "everyone's invited to the party" of it 🎉). also, the broadcast value 0xffffffff can be given as all or -1 — iykyk 🫶

---

👑 GLOBAL OPTIONS 👑

these ones live at the top-level nvme command (main character energy, they're above all the subcommands), but they're still available to this subcommand. so you can absolutely use them here:

• --dry-run — print the command that would be executed, but don't actually execute it. it's the "screenshot the outfit before you commit to going out" of options 📸
• --no-ioctl-probing — disable probing for 64-bit IOCTL support.
• --no-retries — disable retry logic on transient errors. no second chances, we're moving on 💀
• -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, so pick one and commit, bestie (yes, the 'json is literally written like that in the manual — I don't make the rules, I just relay them 🍓).
• --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 — not even a maybe, just no 🚫
• --quiet — suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. so she's quiet, not silent — she'll still tell you if something's wrong 😭
• --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. very "customize your experience" of her ✨
• --timeout=<ms> — set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). she can wait forever if you need her to, and honestly? relatable 🕰️
• -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity — stack her like a Starbucks order, the more the merrier 💅

also important bestie: these options can also be set as machine-wide defaults in nvme-cli.conf(5), and a command-line flag always overrides the file. command line stays winning 👑

---

🔥 EXAMPLES 🔥

here's where it gets fun, the actual hands-on stuff:

1. Retrieve the Solidigm SMART log for all namespaces:

# nvme solidigm smart-log-add /dev/nvme0

1. Retrieve the Solidigm SMART log for namespace 1:

# nvme solidigm smart-log-add /dev/nvme0 -n 1

1. Retrieve the Solidigm SMART log in JSON format:

# nvme solidigm smart-log-add /dev/nvme0 -o json

three little commands, three little vibes, all slaying 🌸

---

🧚 NVME 🧚

Part of the nvme-user suite. she's part of a whole friend group, and you love to see it 🫶

---

aaaand that's the whole page, bestie! 🌟 this one's from the NVMe manual, dated 10/30/2026 — so like, future girlboss energy fr fr. go forth and read those SMART logs, you've got this 💜🎀🦋