cryptsetup output from installcd

cryptsetup-broken.txt (text/plain), 5.91 KB, created by Ben Kohler on 2018-07-19 17:26:36 UTC

# cryptsetup 1.7.5 processing "cryptsetup luksFormat /dev/sda2 --debug"
# Running command luksFormat.
# Locking memory.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.

WARNING!
========
This will overwrite data on /dev/sda2 irrevocably.

Are you sure? (Type uppercase yes): # Allocating crypt device /dev/sda2 context.
# Trying to open and read device /dev/sda2 with direct-io.
# Initialising device-mapper backend library.
# Timeout set to 0 miliseconds.
# Iteration time set to 2000 milliseconds.
# Interactive passphrase entry requested.
# Formatting device /dev/sda2 as type LUKS1.
# Crypto backend (gcrypt 1.8.3) initialized in cryptsetup library version 1.7.5.
# Detected kernel Linux 4.14.52-gentoo x86_64.
# Topology: IO (512/0), offset = 0; Required alignment is 1048576 bytes.
# Checking if cipher aes-xts-plain64 is usable.
# Userspace crypto wrapper cannot use aes-xts-plain64 (-95).
# Using dmcrypt to access keyslot area.
# Calculated device size is 1 sectors (RW), offset 0.
# dm version   OF   [16384] (*1)
# dm versions   OF   [16384] (*1)
# Detected dm-crypt version 1.18.1, dm-ioctl version 4.37.0.
# Device-mapper backend running with UDEV support disabled.
# DM-UUID is CRYPT-TEMP-temporary-cryptsetup-9767
# dm create temporary-cryptsetup-9767 CRYPT-TEMP-temporary-cryptsetup-9767 OF   [16384] (*1)
# dm reload temporary-cryptsetup-9767  OFRW    [16384] (*1)
# Cookie value is not set while trying to call DM_DEVICE_RESUME ioctl. Please, consider using libdevmapper's udev synchronisation interface or disable it explicitly by calling dm_udev_set_sync_support(0).
# Switching off device-mapper and all subsystem related udev rules. Falling back to libdevmapper node creation.
# dm resume temporary-cryptsetup-9767  OFRW    [16384] (*1)
# temporary-cryptsetup-9767: Stacking NODE_ADD (252,0) 0:0 0600
# temporary-cryptsetup-9767: Stacking NODE_READ_AHEAD 256 (flags=1)
# temporary-cryptsetup-9767: Processing NODE_ADD (252,0) 0:0 0600
# Created /dev/mapper/temporary-cryptsetup-9767
# temporary-cryptsetup-9767: Processing NODE_READ_AHEAD 256 (flags=1)
# temporary-cryptsetup-9767 (252:0): read ahead is 256
# temporary-cryptsetup-9767: retaining kernel read ahead of 256 (requested 256)
# Cookie value is not set while trying to call DM_DEVICE_REMOVE ioctl. Please, consider using libdevmapper's udev synchronisation interface or disable it explicitly by calling dm_udev_set_sync_support(0).
# Switching off device-mapper and all subsystem related udev rules. Falling back to libdevmapper node creation.
# dm remove temporary-cryptsetup-9767  OFT    [16384] (*1)
# temporary-cryptsetup-9767: Stacking NODE_DEL
# temporary-cryptsetup-9767: Processing NODE_DEL
# Removed /dev/mapper/temporary-cryptsetup-9767
# Generating LUKS header version 1 using hash sha256, aes, xts-plain64, MK 32 bytes
# KDF pbkdf2, hash sha256: 1137284 iterations per second (256-bits key).
# Data offset 4096, UUID 053a7181-b3b0-4113-bfd3-62eb5d254092, digest iterations 277500
# Updating LUKS header of size 1024 on device /dev/sda2
# Key length 32, device size 40892383 sectors, header size 2050 sectors.
# Reading LUKS header of size 1024 from device /dev/sda2
# Key length 32, device size 40892383 sectors, header size 2050 sectors.
# Adding new keyslot -1 using volume key.
# Calculating data for key slot 0
# KDF pbkdf2, hash sha256: 1117884 iterations per second (256-bits key).
# Key slot 0 use 2183367 password iterations.
# Using hash sha256 for AF in key slot 0, 4000 stripes
# Updating key slot 0 [0x1000] area.
# Userspace crypto wrapper cannot use aes-xts-plain64 (-95).
# Using dmcrypt to access keyslot area.
# Calculated device size is 250 sectors (RW), offset 8.
# DM-UUID is CRYPT-TEMP-temporary-cryptsetup-9767
# dm create temporary-cryptsetup-9767 CRYPT-TEMP-temporary-cryptsetup-9767 OF   [16384] (*1)
# dm reload temporary-cryptsetup-9767  OFW    [16384] (*1)
# Cookie value is not set while trying to call DM_DEVICE_RESUME ioctl. Please, consider using libdevmapper's udev synchronisation interface or disable it explicitly by calling dm_udev_set_sync_support(0).
# Switching off device-mapper and all subsystem related udev rules. Falling back to libdevmapper node creation.
# dm resume temporary-cryptsetup-9767  OFW    [16384] (*1)
# temporary-cryptsetup-9767: Stacking NODE_ADD (252,0) 0:0 0600
# temporary-cryptsetup-9767: Stacking NODE_READ_AHEAD 256 (flags=1)
# temporary-cryptsetup-9767: Processing NODE_ADD (252,0) 0:0 0600
# Created /dev/mapper/temporary-cryptsetup-9767
# temporary-cryptsetup-9767: Processing NODE_READ_AHEAD 256 (flags=1)
# temporary-cryptsetup-9767 (252:0): read ahead is 256
# temporary-cryptsetup-9767: retaining kernel read ahead of 256 (requested 256)
# Cookie value is not set while trying to call DM_DEVICE_REMOVE ioctl. Please, consider using libdevmapper's udev synchronisation interface or disable it explicitly by calling dm_udev_set_sync_support(0).
# Switching off device-mapper and all subsystem related udev rules. Falling back to libdevmapper node creation.
# dm remove temporary-cryptsetup-9767  OFT    [16384] (*1)
# Cookie value is not set while trying to call DM_DEVICE_REMOVE ioctl. Please, consider using libdevmapper's udev synchronisation interface or disable it explicitly by calling dm_udev_set_sync_support(0).
# Switching off device-mapper and all subsystem related udev rules. Falling back to libdevmapper node creation.
# dm remove temporary-cryptsetup-9767  OFT    [16384] (*2)
# temporary-cryptsetup-9767: Stacking NODE_DEL
# temporary-cryptsetup-9767: Processing NODE_DEL
# Removed /dev/mapper/temporary-cryptsetup-9767
# Key slot 0 was enabled in LUKS header.
# Updating LUKS header of size 1024 on device /dev/sda2
# Key length 32, device size 40892383 sectors, header size 2050 sectors.
# Reading LUKS header of size 1024 from device /dev/sda2
# Key length 32, device size 40892383 sectors, header size 2050 sectors.
# Releasing crypt device /dev/sda2 context.
# Releasing device-mapper backend.
# Unlocking memory.
Command successful.