Anyone ever have cryptsetup just start hanging after entering password on boot? This seems like it’s going to be a fun issue to try to resolve…

    • The Doctor@beehaw.orgEnglish
      4·
      7 months ago

      That’s more than a reasonable period of time to wait.

      Can you run a SMART check on the drive from a liveCD? memtest86?

    • krolden
      2·
      7 months ago

      Paste the output of cryptsetup benchmark

      • Dr. Wesker@lemmy.sdf.orgOPEnglish
        2·
        7 months ago
        # Tests are approximate using memory only (no storage IO).
PBKDF2-sha1      2957901 iterations per second for 256-bit key
PBKDF2-sha256    4946113 iterations per second for 256-bit key
PBKDF2-sha512    1945410 iterations per second for 256-bit key
PBKDF2-ripemd160 1123875 iterations per second for 256-bit key
PBKDF2-whirlpool  773286 iterations per second for 256-bit key
argon2i       8 iterations, 1048576 memory, 4 parallel threads (CPUs) for 256-bit key (requested 2000 ms time)
argon2id      8 iterations, 1048576 memory, 4 parallel threads (CPUs) for 256-bit key (requested 2000 ms time)
#     Algorithm |       Key |      Encryption |      Decryption
        aes-cbc        128b      1794.0 MiB/s      6427.8 MiB/s
    serpent-cbc        128b       107.4 MiB/s       765.7 MiB/s
    twofish-cbc        128b       275.7 MiB/s       498.2 MiB/s
        aes-cbc        256b      1392.5 MiB/s      5266.3 MiB/s
    serpent-cbc        256b       114.8 MiB/s       798.4 MiB/s
    twofish-cbc        256b       284.6 MiB/s       498.7 MiB/s
        aes-xts        256b      5290.1 MiB/s      5322.6 MiB/s
    serpent-xts        256b       697.6 MiB/s       635.9 MiB/s
    twofish-xts        256b       403.4 MiB/s       413.4 MiB/s
        aes-xts        512b      4070.4 MiB/s      4048.9 MiB/s
    serpent-xts        512b       664.6 MiB/s       642.0 MiB/s
    twofish-xts        512b       417.6 MiB/s       421.7 MiB/s
        • krolden
          1·
          7 months ago

          how about systemd-analyze and cryptsetup luksDump <lukspart> | grep Slot

          • Dr. Wesker@lemmy.sdf.orgOPEnglish
            1·
            7 months ago

            I’m not using systemd. Grepping on Slot doesn’t return any results.

            LUKS header information
Version:       	2
Epoch:         	3
Metadata area: 	16384 [bytes]
Keyslots area: 	16744448 [bytes]
UUID:          	<redacted>
Label:         	(no label)
Subsystem:     	(no subsystem)
Flags:       	(no flags)

Data segments:
  0: crypt
	offset: 16777216 [bytes]
	length: (whole device)
	cipher: aes-xts-plain64
	sector: 512 [bytes]

Keyslots:
  0: luks2
	Key:        512 bits
	Priority:   normal
	Cipher:     aes-xts-plain64
	Cipher key: 512 bits
	PBKDF:      argon2id
	Time cost:  8
	Memory:     1048576
	Threads:    4
	Salt:       <redacted>
	AF stripes: 4000
	AF hash:    sha512
	Area offset:32768 [bytes]
	Area length:258048 [bytes]
	Digest ID:  0