Grub installation error 1

Exactly, without os-prober works fine, and grub load correctly, showing only the entry of the new installation. I’m writing from the new installation actually.

GRUB_DISABLE_OS_PROBER=true

Thanks for all your efforts.
Now the system boots fine, but I’m afraid to set multi boot to grub

1 Like

Nice, that’s good news!

You said before:

As can be seen from the output of sudo parted -l, there is no ESP (EFI System Partition) on that drive (/dev/sda). This is what is needed to be fixed. Creating an ESP, reinstalling the bootloader and generating a new grub.cfg with correct entries would most probably make your other install to boot again if there are no other issues with the install.

And then:

Is your Windows bootable? No ESP on that drive, so UEFI boot mode is out of question. If it is bootable, how do you go about booting it?

Also, If you think that you are satisfied with the resolution of this thread, please consider to check the solution box under the post which pointed to the solution for the topic to close automatically.

If you need help to fix the issue with the other EnOS install on /dev/sda, let us know.

Yes, i have a backup, but i would like to have all the entries on one grub, like before. Then i have to use os-prober, that appears to be bugged… would probably goes wrong this time too, or no?
To boot windows is valid the same written above, i can have three uefi entries but is more convenient to have one grub for all the three operating systems.

Have you some suggestions?

No esp partition on the other disk, all the boot part of the three operating systems shares the same esp.
Probably not the best solution. Right?

I have a backup of windows 10 bootloader too, it’s not the first time i made this mess and i have learned that the backup is a good practice

I think you should be fixing one thing at a time.

My suggestion would be to fix the Windows issue first. Restore it’s bootloader and make sure it is bootable.

Afterwards we can look at fixing your “old” EnOS install on /dev/sda3.

I have already fixed the Windows 10, copying the boot folder on the esp and adding a uefi entry using efibootmgr

efibootmgr -v

BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0001,0000,0003,0005,0006
Boot0000* EFI Hard Drive (SAMSUNG MZVLW128HEGR-000L2)	PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-BB-71-03-47-98)/HD(1,GPT,4830dd95-812f-3b43-9593-f47aaa9e1361,0x1000,0x96000)RC
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 1d / 01 01 06 00 00 00 / 03 17 10 00 01 00 00 00 00 25 38 bb 71 03 47 98 / 04 01 2a 00 01 00 00 00 00 10 00 00 00 00 00 00 00 60 09 00 00 00 00 00 95 dd 30 48 2f 81 43 3b 95 93 f4 7a aa 9e 13 61 02 02 / 7f ff 04 00
    data: 52 43
Boot0001* Windows 10	HD(1,GPT,4830dd95-812f-3b43-9593-f47aaa9e1361,0x1000,0x96000)/File(\EFI\Microsoft\Boot\bootmgr.efi)
      dp: 04 01 2a 00 01 00 00 00 00 10 00 00 00 00 00 00 00 60 09 00 00 00 00 00 95 dd 30 48 2f 81 43 3b 95 93 f4 7a aa 9e 13 61 02 02 / 04 04 44 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 72 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0002* EndeavourOS-new	HD(1,GPT,4830dd95-812f-3b43-9593-f47aaa9e1361,0x1000,0x96000)/File(\EFI\EndeavourOS-new\grubx64.efi)
      dp: 04 01 2a 00 01 00 00 00 00 10 00 00 00 00 00 00 00 60 09 00 00 00 00 00 95 dd 30 48 2f 81 43 3b 95 93 f4 7a aa 9e 13 61 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 45 00 6e 00 64 00 65 00 61 00 76 00 6f 00 75 00 72 00 4f 00 53 00 2d 00 6e 00 65 00 77 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  EFI Network 0 for IPv6 (54-E1-AD-F6-75-0F) 	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(54e1adf6750f,0)/IPv6([::]:<->[::]:,0,0)RC
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 03 1c / 01 01 06 00 00 00 / 03 0b 25 00 54 e1 ad f6 75 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 03 0d 3c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 7f ff 04 00
    data: 52 43
Boot0005* EFI USB Device (Generic Flash Disk)	PciRoot(0x0)/Pci(0x14,0x0)/USB(2,0)/HD(1,MBR,0xab3ab792,0x369fc0,0x33000)RC
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 14 / 03 05 06 00 02 00 / 04 01 2a 00 01 00 00 00 c0 9f 36 00 00 00 00 00 00 30 03 00 00 00 00 00 92 b7 3a ab 00 00 00 00 00 00 00 00 00 00 00 00 01 01 / 7f ff 04 00
    data: 52 43

There should be no issue installing dual boot with Windows. I have a number of current dual boot installs with Windows. Normally when installing Eos on another drive it creates it’s own efi partition and os-prober will pick up Windows and or other os installed and add it to grub.

Great!

Lets see if we can boot into your EnOS on /dev/sda3 via a custom.cfg in the /boot/grub directory of your current installation.

Make a file named custom.cfg in the mentioned folder with the following content:

menuentry 'EndeavourOS (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-linux--c59dd15a-40dd-47c1-b034-b21238b24941' {
		insmod part_gpt
		insmod ext2
		set root='hd0,gpt3'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  c59dd15a-40dd-47c1-b034-b21238b24941
		else
		  search --no-floppy --fs-uuid --set=root c59dd15a-40dd-47c1-b034-b21238b24941
		fi
		linux /boot/vmlinuz-linux root=UUID=c59dd15a-40dd-47c1-b034-b21238b24941 rw quiet splash vt.global_cursor_default=0 loglevel=2 rd.systemd.show_status=false rd.udev.log-priority=3 sysrq_always_enabled=1
		initrd /boot/intel-ucode.img /boot/initramfs-linux.img
	}

Reboot and see if you have a boot entry on Grub boot menu. Try it and see if it will boot up your old installation.

2 Likes

It works, thank you, after changing the new UUID of the esp on the fstab of the old installation, start normally from grub

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.