EOS didn't boot properly after install; took me to GRUB version 2.06

blindfolded_7 · January 10, 2023, 11:24am

DISCLAIMER: if you have a similar issue and are looking for solution here, please make sure to read everything before doing anything, because people have provided me a solution and only later on it became clear that it’s probably not the right solution; moreover, it involved risks of making the situation even worse. So… be careful and, if you feel unsure, please make your own post / topic, that will probably be much safer for your computer.

This is what happened after I installed EOS and restarted my laptop… what do I do? o:

(I already found some potential solutions on the forum, but I feel unsure whether these are meant for specifically my problem, so I decided to just post it, to avoid causing even more errors…)

Prior to installing this EOS, I had Fedora and EOS already installed, but I wanted a clean reinstall, so I deleted their partitions through GParted (including their uEfi boot loader partitions). I have Windows 10 on my laptop as well, so I deleted every partition that is not related to Windows. Experienced people told me it’s safe, so…

pebcak · January 10, 2023, 11:50am

Could you boot up you live enos usb and post the output of the following commands:

sudo parted -l

efibootmgr -v

Copy the terminal output as text, paste it into your reply box, highlight it and press Ctrl-E to format.

dalto · January 10, 2023, 11:53am

What partitioning option did you use when you installed?

blindfolded_7 · January 10, 2023, 11:56am

“Replace partition” (I selected a lot of unallocated free space)

dalto · January 10, 2023, 11:57am

My best guess would be that you are booting the grub for one of the distros you erased instead of your new install.

blindfolded_7 · January 10, 2023, 11:58am

I see…
I hope that solution that the user above has provided will fix this, gonna try that in a few minutes

dalto · January 10, 2023, 12:01pm

That isn’t a solution. That is information gathering to be able to provide better help.

blindfolded_7 · January 10, 2023, 1:09pm

sorry for the delay, I was a bit busy

output of the first command (sudo parted -l):

Model: ATA ST1000LM035-1RK1 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      1049kB  556MB   555MB   ntfs         Basic data partition          hidden, diag
 2      556MB   661MB   105MB   fat32        EFI System Partition          boot, esp
 3      661MB   677MB   16.8MB               Microsoft reserved partition  msftres
 4      677MB   228GB   227GB   ntfs         Basic data partition          msftdata
 5      228GB   1000GB  772GB   ext4         endeavouros


Model: UFD 2.0 Silicon-Power32G (scsi)
Disk /dev/sdb: 32.7GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size   Type     File system  Flags
 2      1931MB  2041MB  110MB  primary  fat16        esp

output of the second command (efibootmgr -v):

BootCurrent: 0008
Timeout: 1 seconds
BootOrder: 0003,0000,0004,0008,0009
Boot0000* Windows Boot Manager	HD(2,GPT,20ebbb4f-b1a3-4a12-a5e0-c1f27c8b819f,0x109000,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000061000100000010000000040000007fff0400
      dp: 04 01 2a 00 02 00 00 00 00 90 10 00 00 00 00 00 00 20 03 00 00 00 00 00 4f bb eb 20 a3 b1 12 4a a5 e0 c1 f2 7c 8b 81 9f 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 49 00 43 00 52 00 4f 00 53 00 4f 00 46 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 4d 00 47 00 46 00 57 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 61 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0003* Fedora	HD(2,GPT,20ebbb4f-b1a3-4a12-a5e0-c1f27c8b819f,0x109000,0x32000)/File(\EFI\FEDORA\SHIMX64.EFI)
      dp: 04 01 2a 00 02 00 00 00 00 90 10 00 00 00 00 00 00 20 03 00 00 00 00 00 4f bb eb 20 a3 b1 12 4a a5 e0 c1 f2 7c 8b 81 9f 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 46 00 45 00 44 00 4f 00 52 00 41 00 5c 00 53 00 48 00 49 00 4d 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
Boot0004* Fedora	HD(2,GPT,20ebbb4f-b1a3-4a12-a5e0-c1f27c8b819f,0x109000,0x32000)/File(\EFI\FEDORA\SHIM.EFI)0000424f
      dp: 04 01 2a 00 02 00 00 00 00 90 10 00 00 00 00 00 00 20 03 00 00 00 00 00 4f bb eb 20 a3 b1 12 4a a5 e0 c1 f2 7c 8b 81 9f 02 02 / 04 04 2e 00 5c 00 45 00 46 00 49 00 5c 00 46 00 45 00 44 00 4f 00 52 00 41 00 5c 00 53 00 48 00 49 00 4d 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
    data: 00 00 42 4f
Boot0008* UEFI: UFD 2.0 Silicon-Power32G1100	PciRoot(0x0)/Pci(0x12,0x0)/USB(0,0)/USB(0,0)/CDROM(1,0x398c00,0xd2a6)0000424f
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 12 / 03 05 06 00 00 00 / 03 05 06 00 00 00 / 04 02 18 00 01 00 00 00 00 8c 39 00 00 00 00 00 a6 d2 00 00 00 00 00 00 / 7f ff 04 00
    data: 00 00 42 4f
Boot0009* UEFI: UFD 2.0 Silicon-Power32G1100, Partition 1	PciRoot(0x0)/Pci(0x12,0x0)/USB(0,0)/USB(0,0)/HD(1,MBR,0x5ab6cd03,0x398c00,0x34800)0000424f
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 12 / 03 05 06 00 00 00 / 03 05 06 00 00 00 / 04 01 2a 00 01 00 00 00 00 8c 39 00 00 00 00 00 00 48 03 00 00 00 00 00 03 cd b6 5a 00 00 00 00 00 00 00 00 00 00 00 00 01 01 / 7f ff 04 00
    data: 00 00 42 4f

bonus: a photo of my BIOS boot menu, which still has Fedora options, even though I did erase Fedora’s partition through GParted:

pebcak · January 10, 2023, 1:20pm

Judging by the output of efibootmgr, you don’t seem to have an EFI boot entry for EnOS.
You would need to reinstall your Grub bootloader.

In order to do so, boot up your live usb (make sure you boot up your usb in UEFI mode).

Open a terminal and perform the following:

1. sudo mount /dev/sda5 /mnt 
2. sudo mount /dev/sda2 /mnt/boot/efi
3. sudo arch-chroot /mnt
4. grub-install
5. grub-mkconfig -o /boot/grub/grub.cfg
6. exit

Now check with efibootmgr -v to see if a boot entry has actually been created. If so reboot and test.
If you get any error messages at any of the steps above, post them back here.

blindfolded_7 · January 10, 2023, 1:27pm

I’m sorry, how exactly do I make sure of that?.. (I’m not sure what UEFI mode even is)

pebcak · January 10, 2023, 1:28pm

In the Bios boot menu (one-time boot menu), next to the name of your USB flash drive there should be an indication of UEFI. Choose that option.

blindfolded_7 · January 10, 2023, 1:30pm

in the photo I posted a bit above, both the USB options say “UEFI” at the start. Is that what you mean?

pebcak · January 10, 2023, 1:31pm

Exactly, that’s it! Sorry I missed that.

blindfolded_7 · January 10, 2023, 1:33pm

when doing this one, it said:

mount: /mnt/boot/efi: mount point does not exist.
       dmesg(1) may have more information after failed mount system call.

do I proceed with the rest of the commands, or…?

pebcak · January 10, 2023, 1:39pm

No. Not sure why the directory isn’t there.

Try

sudo mkdir /mnt/boot/efi

and again:

sudo mount /dev/sda2 /mnt/boot/efi

blindfolded_7 · January 10, 2023, 1:40pm

there’s no output anymore. I guess I’ll proceed

blindfolded_7 · January 10, 2023, 1:42pm

this is me doing these two:

[liveuser@eos-2022.12.17 ~]$ sudo arch-chroot /mnt
[root@EndeavourOS /]# grub-install
bash: grub-install: command not found

pebcak · January 10, 2023, 1:47pm

Make sure you have internet connection in your live session.

Then, install the package Grub (in chroot):

pacman -Sy grub

and proceed with grub-install.

Also after you exit chroot and before you reboot, post the output of:

lsblk -f

and

cat /mnt/etc/fstab

There might be some minor adjustment to do before reboot.

blindfolded_7 · January 10, 2023, 1:52pm

this is me doing this command. Does everything look alright? Because it gave a warning

[root@EndeavourOS /]# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done

pebcak · January 10, 2023, 1:54pm

You can ignore the warning for the moment.

Now type exit to quit chroot and post the output of the following commands:

efibootmgr -v

cat /mnt/etc/fstab

lsblk -fs