[SOLVED] 2 SSDs each with EFI boot - 4 OS installs - why internal doesn't boot first?
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Mint Cinnamon, Debian sid KDE, PCLOS Cinnamon, Manjaro XFCE
Posts: 280
Original Poster
Rep:
Well, I tired appending it to 40 and nano was all sorts of no, wouldn't take ctrlx and just save it, things about buffer and the name? But I tried a grub update after and it gave a lot of errors. I will try and go back and fix.
Code:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.5.0-15-generic
Found initrd image: /boot/initrd.img-6.5.0-15-generic
Found linux image: /boot/vmlinuz-6.5.0-14-generic
Found initrd image: /boot/initrd.img-6.5.0-14-generic
Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Found KDE neon 5.27 (22.04) on /dev/sda4
/usr/sbin/grub-probe: error: unknown filesystem.
Found Manjaro Linux (23.1.3) on /dev/sdb1
/usr/sbin/grub-probe: error: unknown filesystem.
Adding boot menu entry for UEFI Firmware Settings ...
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 431
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.
Distribution: Mint Cinnamon, Debian sid KDE, PCLOS Cinnamon, Manjaro XFCE
Posts: 280
Original Poster
Rep:
Quote:
Originally Posted by colorpurple21859
Post the contents on /etc/grub.d/40_custom
I fixed it with kate. It should be like it was but I am still getting an error on update-grub. Hope I didn't damage it with my crummy nano skills where's vim when I need it
Code:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Windows Boot Manager (on /dev/sda1)" --class windows --class os $menuentry_id_option 'osprober-efi-89E2-26CF' {
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 89E2-26CF
else
search --no-floppy --fs-uuid --set=root 89E2-26CF
fi
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
Distribution: Mint Cinnamon, Debian sid KDE, PCLOS Cinnamon, Manjaro XFCE
Posts: 280
Original Poster
Rep:
No joy. Added. I still get the errors on update-grub below and I have an extra file in there 40_custom.save (from the nano fun - kate saved with correct name. Behavior has not changed - I can only boot manjaro if I move it up in boot sequence with f12. Doesn't boot from ubuntu's or neon's grub menu. Get error - typed from notes
error: file 'boot/vmlinuz-6.5x86_64' not found
error: you need to load the kernel first.
Code:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.5.0-15-generic
Found initrd image: /boot/initrd.img-6.5.0-15-generic
Found linux image: /boot/vmlinuz-6.5.0-14-generic
Found initrd image: /boot/initrd.img-6.5.0-14-generic
Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Found KDE neon 5.27 (22.04) on /dev/sda4
/usr/sbin/grub-probe: error: unknown filesystem.
Found Manjaro Linux (23.1.3) on /dev/sdb1
/usr/sbin/grub-probe: error: unknown filesystem.
Adding boot menu entry for UEFI Firmware Settings ...
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 459
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.
I copied and pasted your 40_custom to one of my systems and there was no errors with the windows entry. Add the manjaro entry from post 52 to /etc/grub.d/40_custom after windows and run the following to re-enable 40_custom:
The grub error message maybe from one of the other files in grub.d between os-prober and 40_custom file, suggest to disable each one with the chmod -x command to find which one is causing grub-update to error.
Last edited by colorpurple21859; 02-05-2024 at 09:58 PM.
Distribution: Mint Cinnamon, Debian sid KDE, PCLOS Cinnamon, Manjaro XFCE
Posts: 280
Original Poster
Rep:
I already copied manjaro into 40_custom. Disabled no difference - manjaro won't boot from grub. I disabled 31 no difference. what should I do about 40_custom.save?
Quote:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Windows Boot Manager (on /dev/sda1)" --class windows --class os $menuentry_id_option 'osprober-efi-89E2-26CF' {
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 89E2-26CF
else
search --no-floppy --fs-uuid --set=root 89E2-26CF
fi
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
menuentry "Manjaro bootloader (on /dev/sda1)" {
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 89E2-26CF
else
search --no-floppy --fs-uuid --set=root 89E2-26CF
fi
chainloader /EFI/Manjaro/grubx64.efi
}
Code:
$ sudo update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.5.0-15-generic
Found initrd image: /boot/initrd.img-6.5.0-15-generic
Found linux image: /boot/vmlinuz-6.5.0-14-generic
Found initrd image: /boot/initrd.img-6.5.0-14-generic
Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Found KDE neon 5.27 (22.04) on /dev/sda4
/usr/sbin/grub-probe: error: unknown filesystem.
Found Manjaro Linux (23.1.3) on /dev/sdb1
/usr/sbin/grub-probe: error: unknown filesystem.
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 453
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.
I need to disable all these? yikes.
Code:
ls /etc/grub.d/
00_header 20_linux_xen 31_uefi-firmware 41_custom README
05_debian_theme 21_memtest86+ 35_fwupd backup
10_linux 29_os-prober_proxy 40_custom bin
11_linux_zfs 30_os-prober_proxy 40_custom.save proxifiedScripts
stephanie@stephanie-Inspiron-5566:~$
I have to go to hospital this morning, laptop not coming with me. It will have to wait for whenever I get back and can function. But I only say that error after I messed with 40_custom with nano
Last edited by Nishtya; 02-06-2024 at 05:49 AM.
Reason: added 40_custom content
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
