'\" t
.\"     Title: cryptsetup-erase
.\"    Author: [see the "AUTHOR(S)" section]
.\" Generator: Asciidoctor 2.0.20
.\"      Date: 2024-03-07
.\"    Manual: Maintenance Commands
.\"    Source: cryptsetup 2.7.1
.\"  Language: English
.\"
.TH "CRYPTSETUP\-ERASE" "8" "2024-03-07" "cryptsetup 2.7.1" "Maintenance Commands"
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.ss \n[.ss] 0
.nh
.ad l
.de URL
\fI\\$2\fP <\\$1>\\$3
..
.als MTO URL
.if \n[.g] \{\
.  mso www.tmac
.  am URL
.    ad l
.  .
.  am MTO
.    ad l
.  .
.  LINKSTYLE blue R < >
.\}
.SH "NAME"
cryptsetup-erase, cryptsetup-luksErase \- erase all keyslots
.SH "SYNOPSIS"
.sp
\fBcryptsetup  \fIerase\fP [<options>] <device>\fP
.br
\fBcryptsetup \fIluksErase\fP [<options>] <device>\fP
.SH "DESCRIPTION"
.sp
Erase all keyslots and make the LUKS container permanently inaccessible.
Unless the device is configured with HW OPAL support you do not need to
provide any password for this operation.
.sp
\fBWARNING:\fP This operation is irreversible.
.sp
\fBWARNING:\fP with \fB\-\-hw\-opal\-factory\-reset\fP ALL data is lost on the device,
regardless of the partition it is ran on, if any, and regardless of any LUKS2
header backup, and does not require a valid LUKS2 header to be present on the
device to run.
.sp
\fB<options>\fP can be [\-\-header, \-\-disable\-locks, \-\-hw\-opal\-factory\-reset, \-\-key\-file].
.SH "OPTIONS"
.sp
\fB\-\-batch\-mode, \-q\fP
.RS 4
Suppresses all confirmation questions. Use with care!
.sp
If the \-\-verify\-passphrase option is not specified, this option also
switches off the passphrase verification.
.RE
.sp
\fB\-\-debug or \-\-debug\-json\fP
.RS 4
Run in debug mode with full diagnostic logs. Debug output lines are
always prefixed by \fB#\fP.
.sp
If \-\-debug\-json is used, additional LUKS2 JSON data structures are printed.
.RE
.sp
\fB\-\-disable\-locks\fP
.RS 4
Disable lock protection for metadata on disk. This option is valid
only for LUKS2 and ignored for other formats.
.sp
\fBWARNING:\fP Do not use this option unless you run cryptsetup in a
restricted environment where locking is impossible to perform (where
/run directory cannot be used).
.RE
.sp
\fB\-\-header <device or file storing the LUKS header>\fP
.RS 4
Use to specify detached LUKS2 header when erasing HW OPAL enabled data device.
.RE
.sp
\fB\-\-help, \-?\fP
.RS 4
Show help text and default parameters.
.RE
.sp
\fB\-\-key\-file, \-d\fP \fIname\fP \fB(LUKS2 with HW OPAL only)\fP
.RS 4
Read the Admin PIN or PSID (with \-\-hw\-opal\-factory\-reset) from file
depending on options used.
.sp
If the name given is "\-", then the secret will be read from stdin.
In this case, reading will not stop at newline characters.
.RE
.sp
\fB\-\-usage\fP
.RS 4
Show short option help.
.RE
.sp
\fB\-\-version, \-V\fP
.RS 4
Show the program version.
.RE
.SH "REPORTING BUGS"
.sp
Report bugs at \c
.MTO "cryptsetup\(atlists.linux.dev" "\fBcryptsetup mailing list\fP"
or in \c
.URL "https://gitlab.com/cryptsetup/cryptsetup/\-/issues/new" "\fBIssues project section\fP" "."
.sp
Please attach output of the failed command with \-\-debug option added.
.SH "SEE ALSO"
.sp
.URL "https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions" "\fBCryptsetup FAQ\fP" ""
.sp
\fBcryptsetup\fP(8), \fBintegritysetup\fP(8) and \fBveritysetup\fP(8)
.SH "CRYPTSETUP"
.sp
Part of \c
.URL "https://gitlab.com/cryptsetup/cryptsetup/" "\fBcryptsetup project\fP" "."