NVME-BOOT-PART-LO(1)

📦
version 3.2 · 14 versions
, in arch rolling

🌸 NVME-BOOT-PART-LO(1) — the nvme manual, bestie edition 🌸

okay so real talk, this is a page straight outta the NVMe Manual and it's about the nvme-boot-part-log command. it's short, it's deprecated, and it's literally just a vibe-preserving alias. let's get into it 💅

✨ NAME ✨

nvme-boot-part-log — retrieves a Boot Partition log page from an NVMe device. and yes, it's deprecated (we'll get there, don't panic) 🫶

✨ SYNOPSIS ✨

nvme [<global-options>] boot-part-log <device> [--lsp=<field> | -s <field>]
                        [--output-file=<file> | -f <file>]

that's the whole shape of it — parent nvme command, global options, the subcommand, your <device>, and then optionally --lsp=<field> (or -s <field>) and/or --output-file=<file> (or -f <file>) 😌

✨ DESCRIPTION ✨

bestie. listen. this command is a deprecated alias for nvme-log-boot-part(1). it only still exists for the scripts that were written against nvme-cli versions older than 3.0. the options and the behavior are identical — the only thing being kept alive here is the top-level command name 🎀

if you're writing something new, please please please use nvme log boot-part instead. this alias prints a deprecation warning on stderr every time you run it, and ngl it may be removed in a future release. it's giving "still in the group chat but hasn't said anything since 2022" 😭

heads up: for the full option reference, the manpage points you at nvme-log-boot-part(1). go read that one, it's the main character 👑

✨ GLOBAL OPTIONS ✨

these are defined up at the top-level nvme command, and they're available to this subcommand too. so you get all the inherited lore ✨

  • --dry-run — prints the command it would have executed, but doesn't actually execute it. all the outfit, none of the commitment 💅
  • --no-ioctl-probing — turns off probing for 64-bit IOCTL support 🔍
  • --no-retries — disables the retry logic on transient errors. one shot, no second chances, no cap 💀
  • -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, json, or binary. only one output format at a time, bestie — pick a lane 🌈
  • --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, script-friendly field names. any other version gets rejected, periodt 🙅‍♀️
  • --quiet — suppresses informational messages. errors still get reported, and just so you know: --quiet cancels any --verbose for the library log level. they do not coexist, it's not that kind of party 🤫
  • --set-options=<key=value>[,<key=value>...] — sets libnvme library options just for this invocation. the supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir 🔧
  • --timeout=<ms> — sets the command timeout in milliseconds. infinite or -1 waits with no time limit at all (0xffffffff). patient queen energy ⏳
  • -v, --verbose — increases the detail in the output. you can stack it multiple times to keep cranking the verbosity up, iykyk 🗣️
also! these options can be set as machine-wide defaults in nvme-cli.conf(5). but a command-line flag always overrides the file — the flag wins, always, no discussion 🫡

✨ EXAMPLES ✨

No Examples

yep. that's it. that's the section. the manpage literally just says no examples and honestly? iconic minimalism 🎀

✨ NVME ✨

part of the nvme-user suite 💜

✨ SEE ALSO ✨

and that's the whole page!! mwah 💖 this little beauty comes from the NVMe manual, dated 10/30/2026 — go forth and use the new command name, bestie, your future self will thank you 🌸✨

📦 where this page comes from