You are not logged in.
That sounds strange to me. There's not key configuration in my /boot/loader/entries/arch.conf nor in my /etc/crypttab. I tried to open the crypted partition from a live USB media and it prompted for the password once:
Also, I don't have an history for when I created the encrypted partition because I was doing it from the live media. If there was a key setup should I see that in /etc/crypttab file, right? But there's nothing there.
Offline
The keyfile to be used with the encrypt hook would be specified in the bootloader config. As you stated it is not specified so the encrypt hook prompts for a password which fails then works on the second attempt.
At a guess perhaps something is caught in the keyboard buffer on the first attempt.
Offline
Well, to get a clearer view lets take '/mnt/external750' out of the equation, disable it and reboot.
It seems strange for 2 key slots seem to be used!?
Offline
At a guess perhaps something is caught in the keyboard buffer on the first attempt.
That would be really bad( I hope you're not right , my guess is a dual slot or that second partition
He could check by doing a 'luksDump'
Offline
I disabled external750 both in /etc/fstab and /etc/crypttab, rebooted and it still asks for the password twice
Offline
I'm still not sure why it's happening, is your locale.conf okay?
Have no idea if it will help, but, regenerate your initramfs and try again..
If have read some topics about this issue on the net but there seem to be various answers.
Offline
locale.conf seems OK
~ % cat /etc/locale.conf
LANG=en_US.UTF-8
~ % mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.9.10-arch1-1
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [encrypt]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 5.9.10-arch1-1
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
-> Running build hook: [encrypt]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
Still asking twice
Offline
I am not sure I fully follow what is going on, but according to the wiki (which is what I used to setup my system), you need to add a keyfile to the initramfs via the FILE array in mkinitcpio.conf.
I'm sorry. I just realized I posted it from another Arch machine, not the one having the problem. This is the one with the problem:
~ % cat /etc/mkinitcpio.conf # FILES # This setting is similar to BINARIES above, however, files are added # as-is and are not parsed in any way. This is useful for config files. FILES=()
Offline
But I'm OK with entering the password at every boot.
Offline
What do the password prompts look like?
Your previous picture showed two prompts but the first one was "no key available with this passphrase" which suggests you mistyped it the first time...
Offline
It asks for the password twice every single time. Also I'm sure I'm putting the right password in. Look, I've found this on Reddit. I'm gonna try it this weekend.
Offline