NVME-LOG-BOOT-PAR(1)

💅 nvme-log-boot-part(1) — the NVMe Manual, but make it cute 🎀

okay so bestie, this is a page from the NVMe Manual, and it's all about nvme-log-boot-part — the little command that goes and grabs a Boot Partition log page off your NVMe device and hands you the struct back. it's giving "grab the receipt, bring it here" energy. 🧚✨

---

🌸 SYNOPSIS 🌸

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

---

💖 DESCRIPTION 💖

So what it does: it retrieves a Boot Partition log page from an NVMe device, and then it provides you the returned structure. simple! iconic! no cap. 👑

Now, the <device> parameter is mandatory — you literally cannot skip it, bestie — and it can be either:

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

On success, the returned log structure will be in raw binary format only with the --output-file option, which is mandatory. so yeah, if you were hoping for pretty-printed vibes, this is not that. it's raw bytes or nothing, fr fr. 😭

heads up: --output-file isn't optional here. it's mandatory. mandatory mandatory. main character mandatory. 🫶

---

✨ OPTIONS ✨

• -s <field>, --lsp=<field> — the log specified field of LID. that's the field you're picking, yep, that one. 🦋
• -f <file>, --output-file=<file> — the file name that the raw binary data gets saved to. this is where your bytes go live. 💾

---

🌈 GLOBAL OPTIONS 🌈

These ones are defined up at the top-level nvme command, and they're available to this subcommand too. so you get to use them here, lucky you! 💜

• --dry-run — prints the command that would be executed, but does not actually execute it. it's the "manifesting it" option. 🙈
• --no-ioctl-probing — disables probing for 64-bit IOCTL support. bye bye probing. 👋
• --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 may be used at a time, so don't get greedy. ✨
• --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. any other versions? rejected. not invited to the party. 🚫
• --quiet — suppresses informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. it's the "shhh, i'm thriving" flag. 🤫
• --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 without a time limit (0xffffffff). patience is a virtue, lowkey. ⏳
• -v, --verbose — increases the level of detail in the output. you may specify it multiple times to further increase verbosity. more -v = more lore. 🔥

oh and also, these options can be set as machine-wide defaults in nvme-cli.conf(5). but a command-line flag always overrides the file. always. periodt. 💅

---

🍓 EXAMPLES 🍓

• Retrieve Boot Partition data to boot_part_log.bin:

# nvme log boot-part /dev/nvme0 --output-file=boot_part_log.bin

look at that. one command. flawless execution. ate and left no crumbs. ⭐

---

👑 NVME 👑

part of the nvme-user suite — you're in good company, bestie. 🌸

---

okay that's the whole page!! 🎀 it's from the NVMe Manual, it's all part of the nvme-user suite, and it's dated 10/30/2026 — so go forth, grab those boot partition logs, and slay. mwah. 💖🦋✨