NVME-MICRON-CLEAR-PCIE-ERRORS(1)

πŸ’… NVME-MICRON-CLEAR β€” the nvme-micron-clear page, bestie

okay so welcome to the <rainbow>NVME-MICRON-CLEAR()</rainbow> manual page πŸŽ€ that's the whole header, the title and the manual name are literally the same string twice, iconic of them tbh. anyway. sit down, grab a strawberry drink πŸ“, we're clearing some PCIe errors.


✨ NAME ✨

nvme-micron-clear-pcie-errors β€” clears correctable PCIe correctable errors of a given Micron device 🧚

(yes the NAME line says "correctable PCIe correctable errors", she's a little caffeinated, we love her πŸ’€)


🌸 SYNOPSIS 🌸

nvme [<global-options>] micron clear-pcie-correctable-errors <device>

that's the whole shape of it, no cap πŸ’–


πŸ¦‹ DESCRIPTION πŸ¦‹

so this command clears correctable pcie errors for the Micron device you point at. that's the vibe. that's the job.

the <device> parameter is mandatory, bestie, no skipping it πŸ™ˆ β€” and it can be either:

  • the NVMe character device, like /dev/nvme0, or
  • a namespace block device, like /dev/nvme0n1
⭐ real talk: this will only work on Micron devices devices of model numbers 54XX. support for new devices may be added subsequently. (yes. "devices devices". she said it twice. no I will not be fixing it, it's part of the lore 😭)

πŸŽ€ OPTIONS πŸŽ€

None. literally none. this subcommand has zero options of its own. slay, minimal queen πŸ‘‘


πŸ‘‘ GLOBAL OPTIONS πŸ‘‘

these bad boys are defined up at the top-level nvme command and they're available to this subcommand too. so like, you do have options, just inherited ones 🫢

  • --dry-run β€” prints the command that would be executed but does not actually execute it. a little vision board, no follow-through πŸ™ˆ
  • --no-ioctl-probing β€” disables probing for 64-bit IOCTL support.
  • --no-retries β€” disables retry logic on transient errors. one shot, one opportunity πŸ’€
  • -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, pick a lane ✨
  • --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. other versions are rejected, don't even try it πŸ”₯
  • --quiet β€” suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. it's giving "shhh, but I'm still watching" 🌈
  • --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. very build-your-own-adventure of her πŸŽ€
  • --timeout=<ms> β€” set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). time is fake, the wait is real πŸ’€
  • -v, --verbose β€” increase the level of detail in the output. may be specified multiple times to further increase verbosity. stack it like accessories, bestie πŸ’…
πŸ“Œ these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. file says one thing, your flag says "not today" 😌

πŸ’œ EXAMPLES πŸ’œ

  • retrieve NAND statistics information
# nvme micron clear-pcie-correctable-errors /dev/nvme0

(yes that bullet really does say "Retrieve NAND statistics information" for a clear-errors command. she contains multitudes. we don't question it πŸ“)


🌟 NVME 🌟

part of the nvme-user suite. one of us, one of us πŸ‘‘


and that's the page!! 🫢 the footer is just <cyan>NVME-MICRON-CLEAR()</cyan> all over again β€” no date, no version string, nothing else, she keeps it mysterious like that πŸ’€πŸ’– (source: the nvme-user suite, as announced up in NVME. bye bestie, go clear some correctable PCIe errors responsibly βœ¨πŸŽ€)

πŸ“¦ where this page comes from