root@NAS:/home/user1# cryptsetup --debug luksFormat --type luks2 /dev/nvme3n1p1 --cipher aes-gcm-random --integrity aead
# cryptsetup 2.0.3 processing "cryptsetup --debug luksFormat --type luks2 /dev/nvme3n1p1 --cipher aes-gcm-random --integrity aead"
# Running command luksFormat.
# Locking memory.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.
WARNING!
========
Cette action écrasera définitivement les données sur /dev/nvme3n1p1.
Are you sure? (Type uppercase yes): YES
# Allocating context for crypt device /dev/nvme3n1p1.
# Trying to open and read device /dev/nvme3n1p1 with direct-io.
# Initialising device-mapper backend library.
# Interactive passphrase entry requested.
Saisissez la phrase secrète pour /dev/nvme3n1p1 :
Vérifiez la phrase secrète :
# PBKDF argon2i, hash sha256, time_ms 2000 (iterations 0), max_memory_kb 1048576, parallel_threads 4.
# Formatting device /dev/nvme3n1p1 as type LUKS2.
# Crypto backend (gcrypt 1.7.6-beta) initialized in cryptsetup library version 2.0.3.
# Detected kernel Linux 4.16.0-0.bpo.2-amd64 x86_64.
# Topology: IO (512/0), offset = 0; Required alignment is 1048576 bytes.
# Creating new digest 0 (pbkdf2).
# Setting PBKDF2 type key digest 0.
# Running pbkdf2(sha256) benchmark.
# PBKDF benchmark: memory cost = 0, iterations = 840205, threads = 0 (took 39 ms)
# PBKDF benchmark: memory cost = 0, iterations = 1344328, threads = 0 (took 390 ms)
# PBKDF benchmark: memory cost = 0, iterations = 1254277, threads = 0 (took 836 ms)
# Benchmark returns pbkdf2(sha256) 1254277 iterations, 0 memory, 0 threads (for 256-bits key).
# Digest JSON:
# {
"type":"pbkdf2",
"keyslots":[
],
"segments":[
],
"hash":"sha256",
"iterations":156784,
"salt":"NwIux87cV6KdbMFQf98BE9ZwRomr0+p0Ufc1qLP2BPY=",
"digest":"IBQIZt59E5VgP1Bf02MdtsmcQ4hmg0omp2DJF3Hg7rY="
}
# Segment 0 assigned to digest 0.
# Header JSON:
# {
"keyslots":{
},
"tokens":{
},
"segments":{
"0":{
"type":"crypt",
"offset":"4194304",
"iv_tweak":"0",
"size":"dynamic",
"encryption":"aes-gcm-random",
"sector_size":512,
"integrity":{
"type":"aead",
"journal_encryption":"none",
"journal_integrity":"none"
}
}
},
"digests":{
"0":{
"type":"pbkdf2",
"keyslots":[
],
"segments":[
"0"
],
"hash":"sha256",
"iterations":156784,
"salt":"NwIux87cV6KdbMFQf98BE9ZwRomr0+p0Ufc1qLP2BPY=",
"digest":"IBQIZt59E5VgP1Bf02MdtsmcQ4hmg0omp2DJF3Hg7rY="
}
},
"config":{
"json_size":"12288",
"keyslots_size":"4161536"
}
}
# Opening lock resource file /run/cryptsetup/L_259:9
# Acquiring write lock for device /dev/nvme3n1p1.
# Verifying write lock handle for device /dev/nvme3n1p1.
# Device /dev/nvme3n1p1 WRITE lock taken.
# Trying to format INTEGRITY device on top of /dev/nvme3n1p1, tmp name temporary-cryptsetup-954e81ee-a612-4cdb-b82a-5567abc01fc4, tag size 28.
# dm version [ opencount flush ] [16384] (*1)
# dm versions [ opencount flush ] [16384] (*1)
# Detected dm-ioctl version 4.37.0.
# Device-mapper backend running with UDEV support enabled.
# dm versions [ opencount flush ] [16384] (*1)
# DM-UUID is CRYPT-INTEGRITY-temporary-cryptsetup-954e81ee-a612-4cdb-b82a-5567abc01fc4
# Udev cookie 0xd4de5d4 (semid 131074) created
# Udev cookie 0xd4de5d4 (semid 131074) incremented to 1
# Udev cookie 0xd4de5d4 (semid 131074) incremented to 2
# Udev cookie 0xd4de5d4 (semid 131074) assigned to CREATE task(0) with flags DISABLE_SUBSYSTEM_RULES DISABLE_DISK_RULES DISABLE_OTHER_RULES DISABLE_LIBRARY_FALLBACK (0x2e)
# dm create temporary-cryptsetup-954e81ee-a612-4cdb-b82a-5567abc01fc4 CRYPT-INTEGRITY-temporary-cryptsetup-954e81ee-a612-4cdb-b82a-5567abc01fc4 [ opencount flush ] [16384] (*1)
# dm reload temporary-cryptsetup-954e81ee-a612-4cdb-b82a-5567abc01fc4 [ opencount flush securedata ] [16384] (*1)
device-mapper: reload ioctl on failed: Argument invalide
# Udev cookie 0xd4de5d4 (semid 131074) decremented to 1
# Udev cookie 0xd4de5d4 (semid 131074) incremented to 2
# Udev cookie 0xd4de5d4 (semid 131074) assigned to REMOVE task(2) with flags DISABLE_SUBSYSTEM_RULES DISABLE_DISK_RULES DISABLE_OTHER_RULES DISABLE_LIBRARY_FALLBACK (0x2e)
# dm remove temporary-cryptsetup-954e81ee-a612-4cdb-b82a-5567abc01fc4 [ opencount flush securedata ] [16384] (*1)
# Udev cookie 0xd4de5d4 (semid 131074) decremented to 1
# Udev cookie 0xd4de5d4 (semid 131074) waiting for zero
# Udev cookie 0xd4de5d4 (semid 131074) destroyed
# dm versions [ opencount flush ] [16384] (*1)
# dm versions [ opencount flush ] [16384] (*1)
Cannot format integrity for device /dev/nvme3n1p1.
# Device /dev/nvme3n1p1 WRITE lock released.
# Releasing crypt device /dev/nvme3n1p1 context.
# Releasing device-mapper backend.
# Unlocking memory.
La commande a échoué avec le code -1 (paramètres erronés ou manquants).
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx https://www.saout.de/mailman/listinfo/dm-crypt
