sanitize-nvme · shipping

NVMe sanitize

NVMe Sanitize starts a controller-managed sanitization operation using a supported Block Erase, Overwrite or Crypto Erase action.

Related Observatory article: Read on hesela.com

The cited Base Specification 2.0e describes background processing: command completion is not operation completion. Inspect controller capabilities and the Sanitize Status log. Interpret the status field, not only progress: SPROG is FFFFh whenever the operation is not in progress, including states that do not establish success.

Unlike Format NVM, Sanitize is a separate background operation. Its user-data scope includes overprovisioned storage and it resumes after power interruption; this is not a claim that every device byte is user data.

Global Data Erased is separate from operation completion. A rejected Sanitize command can leave the previous result in the log; correlate the command outcome and log. The companion analysis supplies synthetic status examples and a tested, revision-scoped interpreter. Do not apply the 2.0e layout blindly to newer revisions.

Relations

related
NVMe, Secure erase, Data sanitization, Cryptographic erase, Sanitization verification, Sanitization validation, NVMe Format NVM, LUKS header backup

Advantages

  • Provides a dedicated status log for the sanitization operation. [1]

Limitations

  • Supported actions vary; verify capability and completion before accepting the result. [1]

Citations

  1. NVM Express Base Specification 2.0e, sections 5.24 and 5.16.1.25 (accessed 2026-10-21)

Further reading

  1. Hesela: SSD sanitization: why TRIM and a successful command are not enough (accessed 2026-10-10)
  2. NVM Express: NVMe Technology Solves Many Common Sanitize Operation Issues (accessed 2026-10-21)

JSON: /data/terms/sanitize-nvme.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. NVMe sanitize. Hesela. 2026-10-21. https://hesela.dev/terms/sanitize-nvme/