You are not logged in.
I am trying to install Arch on a new computer. If I run the following, I get a "No key available with this passphrase" error every time, with any password. Using "archinstall" breaks with the same error.
sgdisk --clear \
--new=1:0:+550MiB --typecode=1:ef00 --change-name=1:EFI \
--new=2:0:0 --typecode=2:8e00 --change-name=2:system \
/dev/nvme0n1
mkfs.vfat -F32 -n EFI /dev/disk/by-partlabel/EFI
cryptsetup -c aes-xts-plain -s 256 luksFormat /dev/disk/by-partlabel/system
cryptsetup luksOpen /dev/disk/by-partlabel/system luksroot
How can I determine if this is a bug or an issue with the NVME drive?
Offline
Does it work if you use /dev/nvme0n1p2 instead of /dev/disk/by-partlabel/system?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
use 'aes-xts-plain64' instead of the deprecated aes-xts-plain. this is also the default so you can simply not specify it at all.
you can also create an empty file (truncate -s 100M foobar.img) then run cryptsetup luksFormat, cryptsetup open on that file. if that works, then it maybe the fault of your ssd, but otherwise ... consider running a memtest.
also cryptsetup requires kernel and modules to work, so it may fail in a chroot where those modules don't yet exist or can't be loaded. but you rarely run into this problem as cryptsetup is usually done first before chrooting, not inside chroot when it hadn't been used before.
Last edited by frostschutz (2022-11-16 11:30:37)
Online