1CRYPTSETUP-ERASE(8)          Maintenance Commands          CRYPTSETUP-ERASE(8)
2
3
4

NAME

6       cryptsetup-erase, cryptsetup-luksErase - erase all keyslots
7

SYNOPSIS

9       cryptsetup  erase [<options>] <device>
10       cryptsetup luksErase [<options>] <device>
11

DESCRIPTION

13       Erase all keyslots and make the LUKS container permanently
14       inaccessible. You do not need to provide any password for this
15       operation.
16
17       WARNING: This operation is irreversible.
18
19       <options> can be [--header, --disable-locks].
20

OPTIONS

22       --header <device or file storing the LUKS header>
23           Use a detached (separated) metadata device or file where the LUKS
24           header is stored. This option allows one to store ciphertext and
25           LUKS header on different devices.
26
27           For commands that change the LUKS header (e.g. luksAddKey), specify
28           the device or file with the LUKS header directly as the LUKS
29           device.
30
31       --disable-locks
32           Disable lock protection for metadata on disk. This option is valid
33           only for LUKS2 and ignored for other formats.
34
35           WARNING: Do not use this option unless you run cryptsetup in a
36           restricted environment where locking is impossible to perform
37           (where /run directory cannot be used).
38
39       --batch-mode, -q
40           Suppresses all confirmation questions. Use with care!
41
42           If the --verify-passphrase option is not specified, this option
43           also switches off the passphrase verification.
44
45       --debug or --debug-json
46           Run in debug mode with full diagnostic logs. Debug output lines are
47           always prefixed by #.
48
49           If --debug-json is used, additional LUKS2 JSON data structures are
50           printed.
51
52       --version, -V
53           Show the program version.
54
55       --usage
56           Show short option help.
57
58       --help, -?
59           Show help text and default parameters.
60

REPORTING BUGS

62       Report bugs at cryptsetup mailing list <cryptsetup@lists.linux.dev> or
63       in Issues project section
64       <https://gitlab.com/cryptsetup/cryptsetup/-/issues/new>.
65
66       Please attach output of the failed command with --debug option added.
67

SEE ALSO

69       Cryptsetup FAQ
70       <https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions>
71
72       cryptsetup(8), integritysetup(8) and veritysetup(8)
73

CRYPTSETUP

75       Part of cryptsetup project <https://gitlab.com/cryptsetup/cryptsetup/>.
76
77
78
79cryptsetup 2.6.1                  2023-07-19               CRYPTSETUP-ERASE(8)
Impressum