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

  • Nibodhika@lemmy.world
    1·
    11 months ago

    His fstab says rw, and the example I sent for refind config also has rw on the first option. You can definitely boot systemd on ro, I’ve done that in the past when I had some issue (can’t remember what exactly). The error he’s having happens because when you generate the refind config inside the arch live image it adds the UUID of the root of the live iso to the boot parameters, so when it tries to boot from there it can’t find the drive with that UUID, ergo the message with an empty string where it should have the drive. The solution is to simply change that to the name of the drive where you have your root. I do that almost every time I install arch because I always forget about this quirk from refind.