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…

  • krolden
    link
    fedilink
    arrow-up
    1
    ·
    7 months ago

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

    • Dr. Wesker@lemmy.sdf.orgOP
      link
      fedilink
      English
      arrow-up
      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