NVME-FW-LOG(1)

πŸ’… NVME-FW-LOG πŸ’…

okay bestie, real talk β€” this one's a legacy page from the NVMe Manual, so let's get into it ✨


🌸 NAME 🌸

nvme-fw-log β€” sends a request for the NVMe Firmware log page, hands you back the result and the log. also: it's deprecated, so like… heads up 🫢


πŸŽ€ SYNOPSIS πŸŽ€

nvme [<global-options>] fw-log <device> [--raw-binary | -b]

that's the whole vibe. <device> goes in, firmware log comes out πŸ’–


πŸ¦‹ DESCRIPTION πŸ¦‹

so this is a deprecated alias for nvme-log-fw(1), and it's literally just hanging around for the scripts that were written against nvme-cli versions older than 3.0. the options and behavior are completely identical, ngl β€” the only thing kept alive here is the top-level command name. periodt.

new scripts? bestie, please use nvme log fw instead πŸ™ˆ this alias prints a deprecation warning on stderr and β€” lowkey important β€” may be removed in a future release. so don't get attached πŸ’€

for the full option reference, go see nvme-log-fw(1). iykyk.


✨ GLOBAL OPTIONS ✨

these are defined at the top-level nvme command and they're all available to this subcommand too. slay πŸ‘‘

  • --dry-run β€” prints the command that would be executed, but does not actually execute it. it's giving window shopping πŸ›οΈ
  • --no-ioctl-probing β€” turns off probing for 64-bit IOCTL support. no probing, no problem πŸ’…
  • --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, bestie β€” pick your fighter πŸŽ€
  • --output-format-version=<version> β€” picks 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. any other version gets rejected 🚫
  • --quiet β€” suppresses informational messages. errors still get reported, and --quiet cancels any --verbose for the library log level. it's the "shhh" of flags 🀫
  • --set-options=<key=value>[,<key=value>...] β€” sets libnvme library options for this invocation. the 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). patience is a virtue fr fr ⭐
  • -v, --verbose β€” increases the level of detail in the output. you can specify it multiple times to crank the verbosity even higher. more is more πŸ”₯

also important: these options can be set as machine-wide defaults in nvme-cli.conf(5) β€” but a command-line flag always overrides the file. file says one thing, flag says another, flag wins πŸ‘‘


πŸ“ EXAMPLES πŸ“

No Examples

(i know 😭 iconic of them honestly)


πŸ’œ NVME πŸ’œ

part of the nvme-user suite 🫢


🌟 SEE ALSO 🌟


alright that's the page, bestie β€” go read the real one and stay off the deprecated stuff πŸ’…βœ¨

this cutie came from the NVMe folks, dated 10/30/2026, and it lives at reference NVME-FW-LOG(1) β€” mwah, bye πŸŽ€

πŸ“¦ where this page comes from