NVME-TOSHIBA-CLEAR(1)

πŸŽ€ nvme-toshiba-clear-pcie-correctable-errors πŸŽ€

okay so this is a page from the NVMe Manual, and bestie, it's a whole vibe: we're clearing PCIe correctable errors on your Toshiba drive. let's go πŸ’…


✨ NAME ✨

nvme-toshiba-clear-pcie-correctable-errors β€” resets the PCIe correctable errors count all the way back to zero. clean slate energy, no cap 🧹✨


🌸 SYNOPSIS 🌸

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

πŸ¦‹ DESCRIPTION πŸ¦‹

so for whatever NVMe device you hand it, this literally sends the Toshiba clear PCIe correctable errors request. that's the whole job. iconic, honestly πŸ’œ

and listen β€” the <device> parameter is mandatory, like it's not optional, it's not a suggestion, it is required fr fr πŸ™ˆ. you can give it either:

  • the NVMe character device (ex: /dev/nvme0), or
  • a namespace block device (ex: /dev/nvme0n1)

either one works, pick your fighter 🫢


πŸ’– OPTIONS πŸ’–

⭐ GLOBAL OPTIONS ⭐

these ones live at the top-level nvme command, so they're defined up there and they're available to this subcommand too. iykyk πŸ’«

  • --dry-run β€” prints the command it would have run, but doesn't actually run it. all the clout, none of the consequences πŸ’€
  • --no-ioctl-probing β€” turns off probing for 64-bit IOCTL support. bye probing πŸ‘‹
  • --no-retries β€” disables the retry logic on transient errors. one shot, no do-overs 😭
  • -o <fmt>, --output-format=<fmt> β€” sets the reporting format to normal, tabular, 'json, or binary. and heads up: only one output format at a time, you can't collect them all πŸŽ€
  • --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 and script-friendly field names. any other versions get rejected, periodt 🚫
  • --quiet β€” suppresses informational messages. errors still get reported, and --quiet also cancels any --verbose for the library log level. it's giving "i'm ignoring you but i still see everything" πŸ™ˆ
  • --set-options=<key=value>[,<key=value>...] β€” sets libnvme library options for this one 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 with no time limit at all (0xffffffff). commitment issues? not anymore πŸ’€
  • -v, --verbose β€” increases the level of detail in the output. you can specify it multiple times to get even more verbose. more is more, bestie πŸ”₯
ok so real talk: these options can also be set as machine-wide defaults in nvme-cli.conf(5). but a command-line flag always overrides the file. always. the flag wins, that's the law πŸ‘‘

πŸ“ EXAMPLES πŸ“

  • clear the PCIe correctable errors count:
# nvme toshiba clear-pcie-correctable-errors /dev/nvme0

🌈 NVME 🌈

part of the nvme-user suite. you're in good company 🫢


and that's the whole page, bestie! πŸ’– this one came from the NVMe source (that's the suite name, cute right?) and it's dated 10/30/2026 β€” so go forth and clear those correctable errors, you absolute main character πŸŒŸπŸ’…πŸŽ€

πŸ“¦ where this page comes from