unable to boot from rEFInd: "invalid loaderfile"

Googites · 2018-05-25 04:17:59

warning: I'm pretty novice.
I have been attempting to boot into my Arch system from the rEFInd bootmenu and have been having great difficulty in doing so.

I specificallly get the following error:

Starting vmlinuz-linux
Using load options 'root=7f572996-0864-466d-830d-8251ea227d92 rw add_efi_memmap
initrd=\initranfs-linux.img
Invalid Loader file!
Error: Not found while loading vmlinuz-linux

My refind.conf manual entry looks like this:

menuentry "Arch Linux" {
	icon     /EFI/refind/icons/os_arch.png
	volume   "7f572996-0864-466d-830d-8251ea227d92"
	loader   /vmlinuz-linux
	initrd   /initramfs-linux.img
	options  "root=UUID=7f572996-0864-466d-830d-8251ea227d92 rw add_efi_memmap"
}

I've attempted everything I could find online.
Help greately appricated

Last edited by Googites (2018-05-25 04:20:51)

V1del · 2018-05-25 07:22:10

Assuming both refind and the linux images are properly on the ESP, you should remove the volume line (or at least move the volume line and the icon line after the loader and initrd lines) or adjust the path so that it points to /boot/vmlinux-linux and /boot/initramfs-linux.img

Also if that error message really is as you posted it, you either have a typo in the entry config or the errormessage (i.e. initranfs, should be initramfs)

If this isn't sufficient post an lsblk -f and your fstab

Last edited by V1del (2018-05-25 07:23:31)

nl6720 · 2018-05-25 08:13:43

The error message is quite explicit, it can't find vmlinuz-linux . The volume and possibly also paths are wrong.

If the ESP is mounted to /boot remove the volume line, or if /boot is a part of the root filesystem fix the the loader & initrd paths and the volume. Volume only supports LABEL, PARTUUID or PARTLABEL, not UUID. rEFInd article on the Wiki explains most of these things.

d_fajardo · 2018-05-25 08:57:37

I had the same issue when I first installed rEFInd. Like nl6720 said, it seems like it's not finding the vmlinuz-linux. You have to find the correct UUID of where the root file is located. Just an example mine looks like:
"root=PARTUUID=87281890-4cfd-4f16-828e-d18354591710"

nl6720 · 2018-05-25 09:01:41

It's the volume line that is wrong not the options line. If "7f572996-0864-466d-830d-8251ea227d92" really is the UUID of the root filesystem, there's no need to change the "root=..." parameter.

Trilby · 2018-05-25 11:09:07

d_fajardo wrote:

I had the same issue when I first installed rEFInd. Like nl6720 said, it seems like it's not finding the vmlinuz-linux. You have to find the correct UUID of where the root file is located. Just an example mine looks like:
"root=PARTUUID=87281890-4cfd-4f16-828e-d18354591710"

If that option solved your problem, it was neither the same issue nor was it due to the kernel not being found. That "root=PARTUUID=..." options line is passed to the kernel: if the kernel itself can't be found, the parameters passed to it are irrelevant.

Last edited by Trilby (2018-05-25 11:09:41)

Arch Linux

#1 2018-05-25 04:17:59

unable to boot from rEFInd: "invalid loaderfile"

#2 2018-05-25 07:22:10

Re: unable to boot from rEFInd: "invalid loaderfile"

#3 2018-05-25 08:13:43

Re: unable to boot from rEFInd: "invalid loaderfile"

#4 2018-05-25 08:57:37

Re: unable to boot from rEFInd: "invalid loaderfile"

#5 2018-05-25 09:01:41

Re: unable to boot from rEFInd: "invalid loaderfile"

#6 2018-05-25 11:09:07

Re: unable to boot from rEFInd: "invalid loaderfile"

Board footer