I installed Arch yesterday, and sometimes it boots without issue, and sometimes it fails.
When it fails, I get the following:
:: running early hook [udev]
Starting systemd-udevd version 255.7-1-arch
:: running hook [udev]
:: Triggering uevents...
:: running hook [keymap]
:: Loading keymap...done.
Waiting 10 seconds for device /dev/nvme0n1p3 ...
Waiting 10 seconds for device /dev/nvme0n1p3 ...
ERROR: device '/dev/nvme0n1p3' not found. Skipping fsck.
:: mounting '/dev/nvme0n1p3' on real root
mount: /new_root: fsconfig system call failed: /dev/nvme0n1p3: Can't lookup blockdev
dmesg(1) may have more information after failed mount system call.
ERROR: Failed to mount '/dev/nvme0n1p3' on real root
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ~]#
I have two NVME drives; nvme0n1 has three partitions: p1 is EFI boot, p2 is a swap, and p3 is root ext4. Nvme1n1 is a single ext4 partition for /home.
My /etc/fstab file looks correct now, but I did have to manually fix it after initial installation using the arch ISO because the device identifiers seemed to switch (nvme0n1 was originally the drive with the single partition, and nvme1n1 was the drive with three partitions on the first boot, but the block device identifiers switched on subsequent boots).
When I get the error on boot now I can launch into the Framework UEFI Boot Manager and select the Arch Linux boot, and it works fine. Rebooting the machine or starting from powered off works sometimes, and sometimes generates the error above.
Any suggestions for what might be going wrong here?