Fixed by using grub.
Error when trying to boot into new install.
ERROR: device ' ' not found. Skipping fsck. :: mounting ' ' on real root mount : /new_root: no valid filesystem type specified. ERROR: Failed to mount ' ' on real root
And I’m getting dropped in emergency shell. I used official wiki, used refind as bootloader. Second time I tried installing and got same error.
Edit1: fstab
`#/dev/nvme0n1p2
UUID=4dae009f-c08f-4636-b1b5-85a4713a6f40 / ext4 rw,relatime 0 1
#/dev/nvme0n1p1
UUID=0019-78B6 /boot vfat rw,relatime, fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2 `
p2 is root partition
p1 is efi partition.
Edit2: running timedatectl in chroot returns
System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down
You’ll need to post more info about your bootloader/fstab config. The error
ERROR: device ' ' not found
implies there’s something set to an empty string.Also come on guys, let’s prove that the Arch community isn’t all full of assholes, let’s help this dickhead sort their stupid ass issue.
(/s)
Both lines are commented out, # means that it is ignored
1 Did you boot the live medium with bios or efi?
2 Do you have libnvme and nvme-cli installed? If no, try them, if yes look up things on the manuals. It may be that your bootloader can’t read/mount from the nvme
3 Ever since systemd-boot appeared things have been not working so well, now, have they?
Efi I think
It makes a difference, especially when trying to setup via chroot, it is possible but much harder to setup efi from a bios booted system.
@Hiro8811Solved it by installing grub. I then installed refind