NVME-OCP-EOL-PLP-FAILURE-MODE(1)

🎀 NVME-OCP-EOL-PLP-FAILURE-MODE 💅

okay bestie so this is the nvme-ocp-eol-plp-failure-mode page from the NVME-OCP-EOL-PLP manual — yes that's a mouthful, iykyk — and it's literally all about setting (or peeking at) your EOL or PLP circuitry failure mode. no cap, that's the whole vibe.

---

✨ SYNOPSIS ✨

nvme [<global-options>] ocp eol-plp-failure-mode <device>
                        [--mode=<mode> | -m <mode>]
                        [--no-uuid | -n]
                        [--save | -s]
                        [--sel=<select> | -S <select>]

---

🦋 DESCRIPTION 🦋

So what does it do? It defines the EOL or PLP circuitry failure mode. and if you give it no argument? it just prints the current mode. iconic behavior honestly. 🌸

The <device> parameter is mandatory — like, you cannot skip it — and it can be either the NVMe character device (ex: /dev/nvme0) or a block device (ex: /dev/nvme0n1). either works, pick your fighter. 🫶

real talk though: this will only work on OCP compliant devices supporting this feature. Results for any other device are undefined — so like, don't come for me if you run it on random hardware. 💀

On success it returns 0, error code otherwise. that's it, that's the deal. ✨

---

💖 OPTIONS 💖

• -m <mode>, --mode=<mode> — sets the EOL or PLP circuitry failure mode to [0-3] (0: default, 1: rom, 2: wtm or 3: normal). only one mode at a time bestie, don't be greedy. the default is rom.
• -n, --no-uuid — don't try to automatically detect the UUID index for this command. (required for old OCP 1.0 support, so like… legacy besties, this one's for you 🎀)
• -s, --save — saves the attribute so it persists through all power states and resets. permanent main character energy. 👑
• -s <select>, --sel=<select> — the Select (SEL) field, which specifies which value of the attributes gets returned in the provided data:
  • 0 — current — Current
  • 1 — default — Default
  • 2 — saved — Saved
  • 3 — supported — Supported capabilities

🙈 okay yes, <hotpink>both -s flags exist in the original and i am NOT touching that</hotpink> — that's exactly how it's written, no notes, we preserve the lore.

---

🌈 GLOBAL OPTIONS 🌈

these are defined at the top-level nvme command and they're available to this subcommand too, so you're not missing out:

• --dry-run — prints the command that would be executed, but does not actually execute it. manifesting without the commitment. ✨
• --no-ioctl-probing — disables probing for 64-bit IOCTL support.
• --no-retries — disables the retry logic on transient errors. one shot, no second chances. 💀
• -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, 'json, or binary`. only one output format at a time please and thank you.
• --output-format-version=<version> — selects 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 — sorry babes. 🚫
• --quiet — suppresses informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. (they cannot coexist, it's giving exes at the same party.)
• --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). patient queen behavior. 🧚
• -v, --verbose — increases the level of detail in the output. may be specified multiple times to further increase verbosity. stack it, bestie. 🔥

These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file. 💅

---

⭐ EXAMPLES ⭐

• Has the program issue a eol-plp-failure-mode to retrieve the 0xC2 get features:

# nvme ocp eol-plp-failure-mode /dev/nvme0

see? easy. slay. 🍓

---

👑 NVME 👑

Part of the nvme-user suite. literally part of the family. 🫶

---

k bye bestie 💜 — this has been the NVME-OCP-EOL-PLP manual page, brought to you by the NVME-OCP-EOL-PLP() source/version and whatever day you're reading this. go forth and configure responsibly. 🦋✨🎀