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…

      • Dr. Wesker@lemmy.sdf.orgOPEnglish
        0·
        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
    • The Doctor@beehaw.orgEnglish
      0·
      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?