NVME-MANGOBOOST-ID(1)

🖥️ nvme-mangoboost-id-ctrl — NVMe Manual 🖥️

okay bestie, welcome to the page where we send an Identify Controller command and get the result plus the returned structure. It's literally the drive handing over its whole little ID card. 💅

---

✨ NAME ✨

nvme-mangoboost-id-ctrl — Send NVMe Identify Controller, return result and structure.

---

📜 SYNOPSIS 📜

nvme [<global-options>] mangoboost id-ctrl <device>
                        [--vendor-specific | -V]
                        [--raw-binary | -b]
                        [--human-readable | -H]

---

📝 DESCRIPTION 📝

For the NVMe device you give it, this sends an identify controller command and provides the result and returned structure. very "tell me about yourself" energy. ✨

The <device> parameter is mandatory and may be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1).

On success, the structure may be returned in one of several ways depending on the option flags; the structure may be parsed by the program or the raw buffer may be printed to stdout.

If having the program decode the output for readability, this version will decode MangoBoost vendor unique portions of the structure. MangoBoost-specific decoding, slay.

---

🎀 OPTIONS 🎀

• -b, --raw-binary — Print the raw buffer to stdout. Structure is not parsed by program. This overrides the vendor specific and human readable options. raw mode takes over, periodt.
• -V, --vendor-specific — In addition to parsing known fields, this option will dump the vendor specific region of the structure in hex with ascii interpretation. hex plus ascii, very "look at all this lore."
• -H, --human-readable — Display values in a human-readable format where possible. (deprecated, use --verbose) deprecated alert, bestie: use --verbose instead.

---

🌐 GLOBAL OPTIONS 🌐

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

• --dry-run — Print the command that would be executed, but do not actually execute it. all the plan, none of the action.
• --no-ioctl-probing — Disable probing for 64-bit IOCTL support.
• --no-retries — Disable retry logic on transient errors.
• -o <fmt>, --output-format=<fmt> — Set the reporting format to normal, tabular, 'json, or binary. Only one output format may be used at a time. one format at a time, no mixing and matching.
• --output-format-version=<version> — Select 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.
• --quiet — Suppress informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level.
• --set-options=<key=value>[,<key=value>...] — Set libnvme library options for this invocation. Supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir.
• --timeout=<ms> — Set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff).
• -v, --verbose — Increase the level of detail in the output. May be specified multiple times to further increase verbosity.

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

---

🌸 EXAMPLES 🌸

• Has the program interpret the returned buffer and display the known fields in a human readable format:

# nvme mangoboost id-ctrl /dev/nvme0

• In addition to showing the known fields, has the program to display the vendor unique field:

# nvme mangoboost id-ctrl /dev/nvme0 --vendor-specific
# nvme mangoboost id-ctrl /dev/nvme0 -V

The above will dump the vs buffer in hex since it doesn't know how to interpret it. it's giving "mystery bytes, but make it hexadecimal."

• Have the program return the raw structure in binary:

# nvme mangoboost id-ctrl /dev/nvme0 --raw-binary > id_ctrl.raw
# nvme mangoboost id-ctrl /dev/nvme0 -b > id_ctrl.raw

It is probably a bad idea to not redirect stdout when using this mode. redirect that stdout, bestie.

• Alternatively you may want to send the data to another program that can parse the raw buffer.

# nvme mangoboost id-ctrl /dev/nvme0 --raw-binary | nvme_parse_id_ctrl

The parse program in the above example can be a program that shows the structure in a way you like. The following program is such an example that will parse it and can accept the output through a pipe, '|', as shown in the above example, or you can 'cat' a saved output buffer to it.

/* File: nvme_parse_id_ctrl.c */

#include <linux/nvme.h>
#include <stdio.h>
#include <unistd.h>

int main(int argc, char **argv)
{
        unsigned char buf[sizeof(struct nvme_id_ctrl)];
        struct nvme_id_ctrl *ctrl = (struct nvme_id_ctrl *)buf;

        if (read(STDIN_FILENO, buf, sizeof(buf)))
                return 1;

        printf("vid   : %#x\n", ctrl->vid);
        printf("ssvid : %#x\n", ctrl->ssvid);
        return 0;
}

---

🌈 NVME 🌈

Part of the nvme-user suite.

---

okay that's the whole page, bestie! 🫶 source/version: NVMe · date: 10/30/2026 · page id: NVME-MANGOBOOST-ID(1) — byeee 💖