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

blindfolded_7 · January 10, 2023, 1:59pm

output of efibootmgr -v:

BootCurrent: 0008
Timeout: 1 seconds
BootOrder: 0001,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
Boot0001* arch	HD(2,GPT,20ebbb4f-b1a3-4a12-a5e0-c1f27c8b819f,0x109000,0x32000)/File(\EFI\arch\grubx64.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 30 00 5c 00 45 00 46 00 49 00 5c 00 61 00 72 00 63 00 68 00 5c 00 67 00 72 00 75 00 62 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 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

output of cat /mnt/etc/fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=9e7e6637-9374-40b8-a378-41f49b04bc46 /              ext4    defaults,noatime 0 1

output of lsblk -fs:

NAME  FSTYPE   FSVER         LABEL        UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0                                                                   0   100% /run/archiso/airootfs
sda1  ntfs                   Восстановить 8688A53A88A52A1F                                    
└─sda                                                                                         
sda2  vfat     FAT32                      4CA7-F7C8                              53.7M    44% /mnt/boot/efi
└─sda                                                                                         
sda3                                                                                          
└─sda                                                                                         
sda4  ntfs                   Windows 10   6E46AF2946AEF14F                                    
└─sda                                                                                         
sda5  ext4     1.0           endeavouros  9e7e6637-9374-40b8-a378-41f49b04bc46  663.7G     1% /mnt
└─sda                                                                                         
sdb1  iso9660  Joliet Extens EOS_202212   2022-12-17-15-01-34-00                     0   100% /run/archiso/bootmnt
└─sdb iso9660  Joliet Extens EOS_202212   2022-12-17-15-01-34-00                              
sdb2  vfat     FAT16         ARCHISO_EFI  A59C-8529                                           
└─sdb iso9660  Joliet Extens EOS_202212   2022-12-17-15-01-34-00

(“Восстановить” means “Restore”)

pebcak · January 10, 2023, 2:03pm

Edit your /etc/fstab.

sudo nano /mnt/etc/fstab

Add the following line:

UUID=4CA7-F7C8 /boot/efi vfat defaults 0 0

Press Ctrl-O, Enter and Ctrl-X.

Now reboot.

blindfolded_7 · January 10, 2023, 2:05pm

“edit” just means I run the commands you just posted… right?

dalto · January 10, 2023, 2:05pm

Most likely this means that either systemd-boot was chosen or more likely in this case, a legacy install was done instead of UEFI.

Personally, I think reinstalling in UEFI mode would be the better approach.

blindfolded_7 · January 10, 2023, 2:06pm

I don’t remember choosing anything that said “Legacy” during the install process though…

I did choose systemd-boot though, since it’s the default for EOS, I decided not to touch it

pebcak · January 10, 2023, 2:08pm

Right. I was thinking also to suggest that. Not sure why I chose the rabbit hole.

That’s what I suspected as well but not seeing an entry for “Linux Boot Manager” made me wonder.

Also the partitioning seems to be out of order for systemd-boot install? Since the only ESP is only 100 MB.

Also no entry in fstab either.

dalto · January 10, 2023, 2:09pm

It is determined by how you boot the ISO. If you boot it in legacy mode, you get a legacy install.

If you chose systemd-boot then it definitely wasn’t a legacy install. That only shows up in a UEFI install.

However, if you chose systemd-boot, you shouldn’t be following instructions to reinstall grub. You probably are just making your system more broken at this point.

blindfolded_7 · January 10, 2023, 2:11pm

well… a photo of my BIOS boot loader a bit above says “UEFI” in both of the USB options that are there. I’m pretty sure I could only have chosen UEFI mode then

cri
… but I already went through with all of it…
what should I do now, then?..

dalto · January 10, 2023, 2:13pm

Yeah, it looks like a legacy install to me too.

dalto · January 10, 2023, 2:14pm

Since it is a new install anyway, I would reinstall. Be careful to boot the ISO in UEFI mode.

pebcak · January 10, 2023, 2:14pm

If it was a systemd-boot install, it looks to be a broken one at the outset.

It should have created a second ESP the size of 1 GB if I am not mistaken since the existing ESP (100 MB) is too small.

Also, there was no entry for “Linux Boot Manager” in the output of efibootmgr.

dalto · January 10, 2023, 2:17pm

Although, it looks like you had to install grub.

I wonder if no bootloader was selected.

blindfolded_7 · January 10, 2023, 2:17pm

… I’m just gonna ask this to make sure
the “UEFI” that it says at the start of my USB options - is this what you mean by saying “UEFI mode”? Because if so, then my install was in that same mode and… should I really reinstall it all then?

pebcak · January 10, 2023, 2:18pm

That is the most probable scenario.

pebcak · January 10, 2023, 2:20pm

@dalto
I think if OP has edited their fstab already, it should work now, don’t you think?
They have done the most part already.

dalto · January 10, 2023, 2:20pm

Yes.

It seems likely based on all the information we have at this point is that “no bootloader” was inadvertently selected.

You have two choices. Finish the work to install and configure grub on your system or reinstall. Since this is a brand-new install anyway, reinstallation is certainly the easiest option.

dalto · January 10, 2023, 2:21pm

Maybe? Did we install the other packages needed for a grub install such as eos-dracut and os-prober?

blindfolded_7 · January 10, 2023, 2:23pm

there MIGHT be more useful information in my previous forum post… but be aware that ALL the scheenshots and data from there are out of date, since it shows my previous distros, which I have erased through GParted - I erased everything except /sda1-2-3-4. Maybe not everything from these was erased after all?..

pebcak · January 10, 2023, 2:24pm

No, no more packages apart from Grub.

Won’t the other packages get installed as part of the “eos-base-package”? Perhaps not if “no bootloader” option was selected

At any rates, I guess you are right about a re-install.

blindfolded_7 · January 10, 2023, 2:31pm

I don’t need to do any of this if I reinstall, right?..

(btw, I address the message from my last reply to dalto to you as well)