[Solved]New Installation fails to boot, drops to rootfs

DevilishTruthStare · 2019-06-12 22:03:23

I recently installed arch linux on my computer, but after following the installation instructions when I try to boot in to arch it drops to the rootfs shell.

I can get into the normal install and operate normally if I type

it boots

mount /dev/sda2 /new_root
exit

/boot/EFI/refind/refind.conf

timeout 20

menuentry Linux {
    icon EFI/refind/icons/os_linux.png
    volume 904404F8-B481-440C-A1E3-11A5A954E601
    loader bzImage-3.3.0-rc7
    initrd initrd-3.3.0.img
    options "ro root=UUID=4efb9796-dae7-42f6-bb98-79d8f72a16e7 rw add_efi_memmap"
    #options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
    disabled
}

menuentry "Arch Linux" {
    icon     /EFI/refind/icons/os_arch.png
    volume   "Arch Linux"
    loader   /boot/vmlinuz-linux
    initrd   /boot/initramfs-linux.img
    #options  "root=PARTUUID=5028fa50-0079-4c40-b240-abfaf28693ea rw add_efi_memmap"
    options  "root=UUID=43fb9796-dae7-42f6-bb98-79d8f72a16e7 rw add_efi_memmap"
    submenuentry "Boot using fallback initramfs" {
        initrd /boot/initramfs-linux-fallback.img
    }
    submenuentry "Boot to terminal" {
        add_options "systemd.unit=multi-user.target"
    }
    disabled
}

menuentry Ubuntu {
    loader /EFI/ubuntu/grubx64.efi
    icon /EFI/refind/icons/os_linux.png
    disabled
}

menuentry "ELILO" {
    loader \EFI\elilo\elilo.efi
    disabled
}

menuentry "Windows 7" {
    loader \EFI\Microsoft\Boot\bootmgfw.efi
    disabled
}

menuentry "Windows via shell script" {
    icon \EFI\refind\icons\os_win.png
    loader \EFI\tools\shell.efi
    options "fs0:\EFI\tools\launch_windows.nsh"
    disabled
}

menuentry "My macOS" {
    icon \EFI\refind\icons\os_mac.png
    volume "macOS boot"
    loader \System\Library\CoreServices\boot.efi
    disabled
}

/etc/fstab

# /dev/sda2
UUID=4efb9796-dae7-42f6-bb98-79d8f72a16e7    /             ext4          rw,relatime    0 1

# /dev/sda1
UUID=464D-12A2          /boot         vfat          rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro    0 2

# /dev/sda4
UUID=ee0df3d7-eead-4e04-bb9d-2d5d45367291    /home         ext4          rw,relatime    0 2

# /dev/sda3
UUID=45138276-d3cd-426b-a38c-9a6cafeea81b    none          swap          defaults      0 0

Not sure how to permanently fix this, and advice is appreciated.

Last edited by DevilishTruthStare (2019-06-13 00:31:38)

jasonwryan · 2019-06-12 22:16:20

Please use code tags for all the paste output, not quote tags.

Also, paste the output of blkid: your UUID in fstab and grub conf do not match.

DevilishTruthStare · 2019-06-12 22:21:37

jasonwryan wrote:

Please use code tags for all the paste output, not quote tags.

Edited

jsonwryan wrote:

Also, paste the output of blkid: your UUID in fstab and grub conf do not match.

/dev/sda1: UUID="464D-12A2" TYPE="vfat" PARTLABEL="/boot" PARTUUID="d6c17b95-f07e-479c-9957-4e9598a859e1"
/dev/sda2: UUID="4efb9796-dae7-42f6-bb98-79d8f72a16e7" TYPE="ext4" PARTLABEL="/" PARTUUID="217ffe90-463c-403b-80ee-a1f7b8a5b515"
/dev/sda3: UUID="45138276-d3cd-426b-a38c-9a6cafeea81b" TYPE="swap" PARTLABEL="/swap" PARTUUID="66161925-5043-4cf7-91c1-922535207b56"
/dev/sda4: UUID="ee0df3d7-eead-4e04-bb9d-2d5d45367291" TYPE="ext4" PARTLABEL="/home" PARTUUID="eb4eca5d-8894-42b3-a57e-956cb24b8f66"
/dev/sdc1: LABEL="ARCH_201906" UUID="E2E9-6C2A" TYPE="vfat" PARTUUID="00023500-01"

loqs · 2019-06-12 22:29:13

The root specified in the refind entry

root=UUID=43fb9796-dae7-42f6-bb98-79d8f72a16e7

does not match any of the entries from blkid.
Edit:
Although every entry in refind.conf appears to marked as disabled.

Last edited by loqs (2019-06-12 22:31:37)

DevilishTruthStare · 2019-06-12 22:31:32

I don't think that matters, as everything in the refind.conf is marked as disabled by default, when I remove that line I get another option, but it doesn't boot from it.

I think what I'm booting from is refind autodetecting something, then for somereason it isn't mounting /dev/sda2

loqs · 2019-06-12 22:33:54

When you are dropped to the rescue shell what is the output of

cat /proc/cmdline

DevilishTruthStare · 2019-06-12 22:35:41

\\vmlinuz-linux archisobasedir=arch archisolabel=ARCH_201906 initrd=\initramfs-linux.img

loqs · 2019-06-12 22:40:46

Given that REFInd#Without_configuration is producing that broken entry I would suggest using REFInd#refind_linux.conf or REFInd#Manual_boot_stanzas.

DevilishTruthStare · 2019-06-13 00:23:46

I fixed it!

I set the options in refind.conf to be the same as in /boot/refind_linux.conf for minimal options, put that in the /boot/EFI/refind/refind.conf

I don't know why the first entry wasn't working, or why the autodetect wasn't working properly, but I changed the 'Arch Linux" label to have minimal options, and removed the path to the loader and initrd, since they were in the working directory when that is being referenced

I still don't know why the autodetect isn't working and if anyone has any ideas, or needs more output let me know.

jasonwryan · 2019-06-13 00:30:39

Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.

crimist · 2022-07-30 21:01:18

I managed to fix autodetect on my system.
Turns out that refind was somehow detecting the arch installation USB and using it's arguments in the my refind_linux.conf.

Solution:

Unplug your installation USB
Run refind-install

Last edited by crimist (2022-07-30 21:03:37)

2ManyDogs · 2022-07-30 22:08:41

crimist, this thread is three years old and marked [SOLVED]. Please do not necrobump.

Closing.

Arch Linux

#1 2019-06-12 22:03:23

[Solved]New Installation fails to boot, drops to rootfs

#2 2019-06-12 22:16:20

Re: [Solved]New Installation fails to boot, drops to rootfs

#3 2019-06-12 22:21:37

Re: [Solved]New Installation fails to boot, drops to rootfs

#4 2019-06-12 22:29:13

Re: [Solved]New Installation fails to boot, drops to rootfs

#5 2019-06-12 22:31:32

Re: [Solved]New Installation fails to boot, drops to rootfs

#6 2019-06-12 22:33:54

Re: [Solved]New Installation fails to boot, drops to rootfs

#7 2019-06-12 22:35:41

Re: [Solved]New Installation fails to boot, drops to rootfs

#8 2019-06-12 22:40:46

Re: [Solved]New Installation fails to boot, drops to rootfs

#9 2019-06-13 00:23:46

Re: [Solved]New Installation fails to boot, drops to rootfs

#10 2019-06-13 00:30:39

Re: [Solved]New Installation fails to boot, drops to rootfs

#11 2022-07-30 21:01:18

Re: [Solved]New Installation fails to boot, drops to rootfs

#12 2022-07-30 22:08:41

Re: [Solved]New Installation fails to boot, drops to rootfs

Board footer