NVME-UNCOR(1)
π nvme-uncor β like, the whole manual, bestie
okay so this is nvme-uncor(1) from the NVMe Manual π β yes that manual, the nvme-cli one. buckle up, we're doing this together and honestly it's not even that deep.
β¨ NAME β¨
nvme-write-uncor β send an NVMe write uncorrectable command, and yeah it returns results π
π¦ SYNOPSIS π¦
nvme [<global-options>] write-uncor <device>
[--start-block=<slba> | -s <slba>]
[--block-count=<nlb> | -c <nlb>]
[--namespace-id=<nsid> | -n <nsid>]
[--dir-type=<dtype> | -T <dtype>]
[--dir-spec=<dspec> | -S <dspec>]
like, you give it a <device>, then sprinkle on whichever flags you need. every one is optional, no pressure periodt π
πΈ DESCRIPTION πΈ
the Write Uncorrectable command does one thing and it's iconic: it invalidates a range of logical blocks. that's it. that's the whole vibe β¨
π OPTIONS π
-s <slba>,--start-block=<slba>β the start block, like where the whole thing kicks off π«Ά-c,--block-count=<nlb>β number of logical blocks to write uncorrectable. lowkey the important one ngl-n <nsid>,--namespace-id=<nsid>β the Namespace ID used in the command. and here's a fun one: the broadcast value0xffffffffcan also be given asallor-1π-T <dtype>,--dir-type=<dtype>β Directive type-S <dspec>,--dir-spec=<dspec>β Directive specific
π GLOBAL OPTIONS π
these ones live at the top-level nvme command and are available to this subcommand too. like they're not ours, they're everybody's, but they still show up for us π«Ά
--dry-runβ print the command that would be executed, but do not actually execute it. it's giving "look but don't touch" π--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 tonormal,tabular,'json, orbinary. only one output format may be used at a time, so pick your fighter π--output-format-version=<version>β select 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 π--quietβ suppress informational messages. errors are still reported, and--quietcancels any--verbosefor the library log level β¨--set-options=<key=value>[,<key=value>...]β set libnvme library options for this invocation. supported keys areforce-4k,mi-probe-enabled,test-base-dirandtest-sysfs-dirπ--timeout=<ms>β set the timeout for the command in milliseconds.infiniteor-1waits without a time limit (0xffffffff) β³-v,--verboseβ increase the level of detail in the output. may be specified multiple times to further increase verbosity, go off bestie π₯
heads up π«Ά these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file β flag wins, no cap.
π EXAMPLES π
No examples yet. (iconic of them honestly β when they drop, we'll be seated π)
π§ NVME π§
part of the nvme-user suite π
and that's the whole page, bestie π sign-off time: this is the NVMe manual page, NVME-UNCOR(1), dated 10/30/2026. screenshot it, cite it, love it πβ¨π
π¦ where this page comes from
- arch rolling: nvme-cli 3.2-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms