NVME-SOLIDIGM-VS-(1)

🌸 NVME-SOLIDIGM-VS-(1): NAME 🌸

Okay bestie, welcome to the NVMe Manual page for nvme-solidigm-vs-fw-activate-history β€” the command that gets the firmware activation history log. That's literally the whole name and the whole job. πŸ’…

πŸ¦‹ SYNOPSIS πŸ¦‹

Run it like this, no cap:

nvme [<global-options>] solidigm vs-fw-activate-history <device> [OPTIONS]

✨ DESCRIPTION ✨

This command retrieves the firmware activation history log for Solidigm NVMe devices, and it redirects to the OCP plug-in for compatibility. So you ask for the history, and it hands things over to the OCP plug-in. That's the vibe. 🫢

πŸŽ€ OPTIONS πŸŽ€

πŸ’œ GLOBAL OPTIONS πŸ’œ

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

  • --dry-run β€” prints the command that would be executed, but does not actually execute it. It's giving "look but don't touch." πŸ‘€
  • --no-ioctl-probing β€” disables probing for 64-bit IOCTL support.
  • --no-retries β€” disables retry logic on transient errors.
  • -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 fave. ✨
  • --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. Periodt.
  • --quiet β€” suppresses informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. So it's quiet, but not "ignore actual problems" quiet. 😭
  • --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 without a time limit (0xffffffff). No rush, bestie. ⏳
  • -v, --verbose β€” increases the level of detail in the output. May be specified multiple times to further increase verbosity. Say it with me: more -v, more lore. πŸ”₯

These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file, every single time. πŸ‘‘

πŸ”₯ EXAMPLES πŸ”₯

  • Print the firmware activation history log in normal format:
# nvme solidigm vs-fw-activate-history /dev/nvme0
  • Print the firmware activation history log in JSON format:
# nvme solidigm vs-fw-activate-history /dev/nvme0 -o json

πŸ‘‘ NVME πŸ‘‘

Part of the nvme-cli suite. Iconic. 🌈


That's the whole page, bestie! πŸ’– Source/version: NVMe. Date: 10/30/2026. Mwah! 🫢

πŸ“¦ where this page comes from