NVME-SOLIDIGM-VS-(1)

📦
version 3.2 · 10 versions
, in arch rolling

💅 nvme-solidigm-vs-internal-log — girl help, we're pulling debug logs 🎀

okay so this is a page from the NVMe Manual, and it's about nvme-solidigm-vs-internal-log, which is genuinely just the world's most extra way of saying "grab the debug log binaries off your Solidigm drive." she's niche, she's specific, she slays 💖

✨ NAME ✨

nvme-solidigm-vs-internal-log — retrieve Debug log binaries 🫶

🌸 SYNOPSIS 🌸

nvme [<global-options>] solidigm vs-internal-log <device>
                        [--log-type=<type> | -t <type>]
                        [--output-dir=<dir> | -d <dir>]

🦋 DESCRIPTION 🦋

So for the NVMe device you hand her, this command retrieves the Solidigm vendor-specific internal debug log binaries and saves them into the output directory you picked. literally just "gimme the logs, put 'em there" no cap 💅

The <device> parameter is mandatory — like, not optional, bestie, she will not guess — and it can be either the NVMe character device (ex: /dev/nvme0) or a namespace block device (ex: /dev/nvme0n1). both are valid. pick your fighter 🌈

🎀 OPTIONS 🎀

  • -t <type>, --log-type=<type> — tells her which type of log to retrieve. valid options are ALL, CIT, HIT, NLOG, ASSERT, EVENT, and EXTENDED. defaults to ALL. and listen — the EXTENDED option generates logs that may take longer time or affect drive performance, but it gives you way more comprehensive debugging information. so like, more tea ☕ but she's gonna take a minute and might be a lil heavy on the drive ngl.
  • -d <dir>, --output-dir=<dir> — where the log files go. defaults to the current working directory. if you don't say anything she just drops 'em right where you're standing 🙈

👑 GLOBAL OPTIONS 👑

these ones are defined at the top-level nvme command and are available to this subcommand. so they're not hers, they're inherited, but she absolutely uses them:

  • --dry-run — print the command that would be executed, but do not actually execute it. a little "what if" moment, no commitment 🫶
  • --no-ioctl-probing — disable probing for 64-bit IOCTL support.
  • --no-retries — disable retry logic on transient errors. one shot, no second chances 💀
  • -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. pick ONE, she's not doing combos.
  • --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. so 1 or 2, that's the whole menu, don't come at her with version 3 🧚
  • --quiet — suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. she goes silent but she still tells you when something breaks 💜
  • --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. yes you can pass multiple, comma-separated, go off ⭐
  • --timeout=<ms> — set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). for the patient girlies 🕰️
  • -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity. -v, -vv, -vvv, she keeps going 🔥
real talk: these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. no exceptions, that's the rule 💅

💖 EXAMPLES 💖

  • retrieve all internal logs and save them to the current directory:
# nvme solidigm vs-internal-log /dev/nvme0
  • retrieve a specific log type and save it to a custom directory:
# nvme solidigm vs-internal-log /dev/nvme0 -t NLOG -d /tmp/logs
  • retrieve logs with verbose output:
# nvme solidigm vs-internal-log /dev/nvme0 -v
  • retrieve extended logs:
# nvme solidigm vs-internal-log /dev/nvme0 -t EXTENDED

🧚 NVME 🧚

part of the nvme-user suite. she's in the family, she belongs there 🎀

and that's the whole page, bestie — no notes, she ate. this iconic little number is from the NVMe manual set, dated 10/30/2026, filed under NVME-SOLIDIGM-VS-(1). go get those logs 💅✨

📦 where this page comes from