I've been using the beginners guide Gummiboot now called systemd-boot since the start without problems. I now want a more customizeable and more robust bootloader, so I chose rEFInd. I've been following the wiki, trying both the automated and manual methods but always get:
ERROR: Unable to find root device ''.
You are being dropped into the recovery shell
Most who have this problem will be presented with a UUID or label like so:
ERROR: Unable to find root device 'UUID=.....'.
But I don't get that. Have I missed a step??
Replacing the boot loader isn't something I'd recommend doing... May I ask why rEFInd over Grub? I'm using Grub perfectly on my system and it uses UEFI in place of Legacy.
It appears as if rEFInd wasn't installed in the /boot partition or it didn't create a configuration file.
While it may be possible to get it working I would chroot into the install and set up grub.
That's partially because is was developed by Kay Sievers who is also a Systemd developer.
1 Like
Ah I see, thanks for that
So after much hastle, reinstalling Windows, re-flashing a fresh bios, and maually installing refind again, it seems to work well.. I've just added the Regular theme and a manual entry for Arch, instead of pointing to systemd-boot.
Still a few things to work out, but at least I can boot propperly now
2 Likes
I actually made a error in the installation..
https://wiki.archlinux.org/index.php/REFInd#Passing_kernel_parameters shows that you should have a refind_linux.conf file. I ran the command refind-mkrlconf as root and now can boot from the vmlinuz... entry in rEFInd. Hope this helps anyone who makes the same mistake I made