Provided by: cryptsetup-bin_2.6.1-1ubuntu1_amd64 bug

NAME
       cryptsetup-erase, cryptsetup-luksErase - erase all keyslots


SYNOPSIS
       cryptsetup  erase [<options>] <device>
       cryptsetup luksErase [<options>] <device>


DESCRIPTION
       Erase all keyslots and make the LUKS container permanently inaccessible. You do not need
       to provide any password for this operation.

       WARNING: This operation is irreversible.

       <options> can be [--header, --disable-locks].


OPTIONS
       --header <device or file storing the LUKS header>
           Use a detached (separated) metadata device or file where the LUKS header is stored.
           This option allows one to store ciphertext and LUKS header on different devices.

           For commands that change the LUKS header (e.g. luksAddKey), specify the device or file
           with the LUKS header directly as the LUKS device.

       --disable-locks
           Disable lock protection for metadata on disk. This option is valid only for LUKS2 and
           ignored for other formats.

           WARNING: 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).

       --batch-mode, -q
           Suppresses all confirmation questions. Use with care!

           If the --verify-passphrase option is not specified, this option also switches off the
           passphrase verification.

       --debug or --debug-json
           Run in debug mode with full diagnostic logs. Debug output lines are always prefixed by
           #.

           If --debug-json is used, additional LUKS2 JSON data structures are printed.

       --version, -V
           Show the program version.

       --usage
           Show short option help.

       --help, -?
           Show help text and default parameters.


REPORTING BUGS
       Report bugs at cryptsetup mailing list <cryptsetup@lists.linux.dev> or in Issues project
       section <https://gitlab.com/cryptsetup/cryptsetup/-/issues/new>.

       Please attach output of the failed command with --debug option added.


SEE ALSO
       Cryptsetup FAQ <https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions>

       cryptsetup(8), integritysetup(8) and veritysetup(8)


CRYPTSETUP
       Part of cryptsetup project <https://gitlab.com/cryptsetup/cryptsetup/>.