[SOLVED] Unable to boot from rEFInd

g0r0 · 2017-09-30 13:00:06

Hello guys i installed new arch system as the main os. Now when i try to boot with refind
I drop into the efi shell.
So i guess i needed to tell refind to load the microcode first in options tough i dont really know how to do it.
Thanks for any help.

Last edited by g0r0 (2017-09-30 23:49:16)

Mr.Elendig · 2017-09-30 13:49:16

Sounds more like you never added an actual entry for arch to the refind config.
https://wiki.archlinux.org/index.php/RE … figuration.

But do post the efibootmgr -v output and so on.

g0r0 · 2017-09-30 14:23:31

Mr.Elendig wrote:

Sounds more like you never added an actual entry for arch to the refind config.
https://wiki.archlinux.org/index.php/RE … figuration.
But do post the efibootmgr -v output and so on.

Ok i edited in /boot/efi/EFI/refind/refind.conf
The options under arch linux entry :
Options "rw root=/boot initrd=/intel-ucode.img"
yet still i see this error :

Starting vmlinuz-linux
Using load options 'rw root=/boot initrd=/intel-ucode.img initrd=\boot\initramfs-linux.img'
Invalid loader file!
Error: not found while loading vmlinuz-linux

* hit any key to continue *

Scimmia · 2017-09-30 14:26:19

So it's saying invalid loader file, but you aren't giving us the loader entry. Think this through.

g0r0 · 2017-09-30 17:08:58

Scimmia wrote:

So it's saying invalid loader file, but you aren't giving us the loader entry. Think this through.

Thank you for the help so far
This is my layout :
Icon /EFI/refind/icons/os_arch.png
Volume "fs_boot" #this is /boot
Loader /boot/vmlinuz-linux
Initrd /boot/initramfs-linux.img
Options "root=PARTUUID=... rw
add_efi_memmap initrd=/intel-ucode.img"

The same error as before.
This is my first expirience in UEFI any guidance will be much appreciated

Scimmia · 2017-09-30 17:29:38

So your issue is related to the warnings on the wiki page Mr.Elendig linked to.

mrunion · 2017-09-30 17:41:37

g0r0 wrote:

Using load options 'rw root=/boot initrd=/intel-ucode.img initrd=\boot\initramfs-linux.img'

You have some backwards slashes in the second initrd=.... I think.

loqs · 2017-09-30 17:59:52

If /boot is the ESP why are you using

Volume   "fs_boot" #this is /boot
Loader    /boot/vmlinuz-linux

meaning the full path refind will look for would be /boot/boot/vmlinuz-linux

g0r0 · 2017-09-30 18:40:50

loqs wrote:

If /boot is the ESP why are you using
Volume   "fs_boot" #this is /boot
Loader    /boot/vmlinuz-linux
meaning the full path refind will look for would be /boot/boot/vmlinuz-linux

/boot is not ESP my ESP is /boot/efi.
Nevertheless i able to locate the loader by removing the /boot/ prefix from initrd and loader now new error occured :

: : running early hook [udev]
Starting version 234
: : running hook [udev]
: : Triggering uevents . . .
: : performing fsck on ' /dev/sda2'
: : fs_boot : clean, 18/128016 files, 63857/512000 blocks
: : mounting ' /dev/sda2' on real root
: : running cleanup hook [udev]
ERROR: root device mounted succesfully, but /sbin/init does not exist.
Bailing out, you are on your own. Good luck.
Sh: cant access tty; job control turned off
[rootfs ]#

loqs · 2017-09-30 18:50:05

Options    "root=PARTUUID=... rw

mounting ' /dev/sda2' on real root

Why would a root referenced by PARTUUID mount as /dev/sda2? Did you change the root option in refind.conf or edit the systems output replacing the PARTUUID with /dev/sda2?
What is the options line from the relevant refind.conf stanza and the output of

# blkid

jasonwryan · 2017-09-30 19:00:29

Please edit your first post and choose a title that describes your issue: https://wiki.archlinux.org/index.php/Co … ow_to_post

g0r0 · 2017-09-30 19:07:02

This is blkid.. and yes i might have change the root directory in refind.conf to the PARTUUID of the boot partition ( fs_boot )
https://imgur.com/a/hQxbL

Last edited by g0r0 (2017-09-30 19:11:45)

loqs · 2017-09-30 19:40:29

g0r0 wrote:

This is blkid.. and yes i might have change the root directory in refind.conf to the PARTUUID of the boot partition ( fs_boot )

Please do not post pictures of text. You also did not include the refind.conf stanza requested. The root option needs to specify the root filesystem not the boot filesystem.

g0r0 · 2017-09-30 19:52:28

loqs wrote:

g0r0 wrote:
This is blkid.. and yes i might have change the root directory in refind.conf to the PARTUUID of the boot partition ( fs_boot )
Please do not post pictures of text. You also did not include the refind.conf stanza requested. The root option needs to specify the root filesystem not the boot filesystem.

Thank you for your help so far heres
My entry :

Icon /EFI/refind/icons/os_arch.png
volume "fs_boot"
loader vmlinuz-linux
Initrd initramfs-linux.img
options "root=PARTUUID=#root_fs# rw add_efi_memmap initrd=/intel-ucode.img"

EDIT : now i was successfully booted to my system Thank you very much all of you and special thanks to loqs.

Last edited by g0r0 (2017-09-30 19:56:03)

circleface · 2017-09-30 23:24:29

Please make sure you remember to mark your thread as solved by editing the first post and prepending [SOLVED] to it.

Arch Linux

#1 2017-09-30 13:00:06

[SOLVED] Unable to boot from rEFInd

#2 2017-09-30 13:49:16

Re: [SOLVED] Unable to boot from rEFInd

#3 2017-09-30 14:23:31

Re: [SOLVED] Unable to boot from rEFInd

#4 2017-09-30 14:26:19

Re: [SOLVED] Unable to boot from rEFInd

#5 2017-09-30 17:08:58

Re: [SOLVED] Unable to boot from rEFInd

#6 2017-09-30 17:29:38

Re: [SOLVED] Unable to boot from rEFInd

#7 2017-09-30 17:41:37

Re: [SOLVED] Unable to boot from rEFInd

#8 2017-09-30 17:59:52

Re: [SOLVED] Unable to boot from rEFInd

#9 2017-09-30 18:40:50

Re: [SOLVED] Unable to boot from rEFInd

#10 2017-09-30 18:50:05

Re: [SOLVED] Unable to boot from rEFInd

#11 2017-09-30 19:00:29

Re: [SOLVED] Unable to boot from rEFInd

#12 2017-09-30 19:07:02

Re: [SOLVED] Unable to boot from rEFInd

#13 2017-09-30 19:40:29

Re: [SOLVED] Unable to boot from rEFInd

#14 2017-09-30 19:52:28

Re: [SOLVED] Unable to boot from rEFInd

#15 2017-09-30 23:24:29

Re: [SOLVED] Unable to boot from rEFInd

Board footer