[SOLVED] Grub os-prober runs twice on update

Nishtya · 02-01-2024, 10:08 PM

Here is one I haven't seen yet in my many adventures of grub2/EFI boot fun while playing the distro field. Latest when I run update-grub (to add a new try-out to the menu) os-prober runs twice. See below when update is run:

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
Found Mageia 9 (9) on /dev/sdb2
Adding boot menu entry for UEFI Firmware Settings ...
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
Found Mageia 9 (9) on /dev/sdb2
done

I thought it was just I might have added the enable probe line twice (kubuntu ships disabled by default) but I looked at the file and it is only there once:

Quote:

If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'

GRUB_DEFAULT="Ubuntu"
GRUB_TIMEOUT_STYLE="hidden"
GRUB_TIMEOUT="10"
GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
GRUB_DISABLE_OS_PROBER="false"

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL="console"

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE="640x480"

Hope I formatted the above properly. Anyone have any ideas why it is probing twice? Everything booting fine <knock on wood> but oh yeah, haven't tried windows yet. I test each other install when I have added a new shiny plaything, I do windows last -sigh- because I don't care. Will update if there is an issue.

colorpurple21859 · 02-01-2024, 10:19 PM

Os-prober to find other installed systems is what is running twice. What is the contents of /etc/grub.d?

Nishtya · 02-01-2024, 10:33 PM

I see two of os-prober but not sure why and which to keep?

Code:

$ dir /etc/grub.d
00_header        20_linux_xen        35_fwupd            backup
05_debian_theme  21_memtest86+       40_custom           bin
10_linux         30_os-prober_proxy  41_custom           proxifiedScripts
11_linux_zfs     31_uefi-firmware    42_os-prober_proxy  README

yancek · 02-02-2024, 06:57 AM

The os_prober files you have are from Grub Customizer which renames some Grub files hence the proxy ending. Why you have 2 files I don't know as I've never seen the need to use the software. Did you look at and compare the contents?

Nishtya · 02-02-2024, 07:54 AM

30 probe

Quote:

#THIS IS A GRUB PROXY SCRIPT
'/etc/grub.d/proxifiedScripts/os-prober' | /etc/grub.d/bin/grubcfg_proxy "+*
-'PCLinuxOS (on /dev/sdb2)'~3549fb5aef084635c9099c059dc74777~
-'SUBMENU' as 'Advanced options for PCLinuxOS (on /dev/sdb2)'{-'Advanced options for PCLinuxOS (on /dev/sdb2)'/*, -'Advanced options for PCLinuxOS (on /dev/sdb2)'/'PCLinuxOS (6.4.14-pclos1) 2023 (on /dev/sdb2)'~8834c42ad296eb2cae62592b9f3ff3bb~, -'Advanced options for PCLinuxOS (on /dev/sdb2)'/'PCLinuxOS (6.4.14-pclos1) 2023 (recovery mode) (on /dev/sdb2)'~9bdf23140c5c04be5fd0bf5697eff379~}
+'KDE neon 5.27 (22.04) (on /dev/sda4)'~5ca317eb6ac2e96054f3bd4cb3aa6550~
+'SUBMENU' as 'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'{+'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/*, +'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/'Neon GNU/Linux (on /dev/sda4)'~79f5731637374354b3c3c8d5effdca5f~, +'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/'Neon GNU/Linux, with Linux 6.5.0-15-generic (on /dev/sda4)'~79f5731637374354b3c3c8d5effdca5f~, +'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/'Neon GNU/Linux, with Linux 6.5.0-15-generic (recovery mode) (on /dev/sda4)'~6f074c5e183df4ff35f99ceaad0bf80e~, +'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/'Neon GNU/Linux, with Linux 6.5.0-14-generic (on /dev/sda4)'~8359ca5a2394833c8a90e0a5de162f59~, +'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/'Neon GNU/Linux, with Linux 6.5.0-14-generic (recovery mode) (on /dev/sda4)'~7ddb981e79ac5212e8e2fde79095a513~, +'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/'Neon GNU/Linux, with Linux 5.15.0-92-generic (on /dev/sda4)'~7ceebfcea47e66c53740c259709b3e08~, +'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/'Neon GNU/Linux, with Linux 5.15.0-92-generic (recovery mode) (on /dev/sda4)'~02182e79237ed1cc6a4f06576733d927~}
+#text
-'Windows Boot Manager (on /dev/sda1)'~e16ac4e4291bd2a95696965a2ab6a04c~
"

42:

Quote:

/etc/grub.d/proxifiedScripts/os-prober' | /etc/grub.d/bin/grubcfg_proxy "-*
-'PCLinuxOS (on /dev/sdb2)'~3549fb5aef084635c9099c059dc74777~
-'SUBMENU' as 'Advanced options for PCLinuxOS (on /dev/sdb2)'{-'Advanced options for PCLinuxOS (on /dev/sdb2)'/*, -'Advanced options for PCLinuxOS (on /dev/sdb2)'/'PCLinuxOS (6.4.14-pclos1) 2023 (on /dev/sdb2)'~8834c42ad296eb2cae62592b9f3ff3bb~, -'Advanced options for PCLinuxOS (on /dev/sdb2)'/'PCLinuxOS (6.4.14-pclos1) 2023 (recovery mode) (on /dev/sdb2)'~9bdf23140c5c04be5fd0bf5697eff379~}
-'KDE neon 5.27 (22.04) (on /dev/sda4)'~5ca317eb6ac2e96054f3bd4cb3aa6550~
-'SUBMENU' as 'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'{-'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/*, -'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/'Neon GNU/Linux (on /dev/sda4)'~79f5731637374354b3c3c8d5effdca5f~, -'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/'Neon GNU/Linux, with Linux 6.5.0-15-generic (on /dev/sda4)'~79f5731637374354b3c3c8d5effdca5f~, -'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/'Neon GNU/Linux, with Linux 6.5.0-15-generic (recovery mode) (on /dev/sda4)'~6f074c5e183df4ff35f99ceaad0bf80e~, -'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/'Neon GNU/Linux, with Linux 6.5.0-14-generic (on /dev/sda4)'~8359ca5a2394833c8a90e0a5de162f59~, -'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/'Neon GNU/Linux, with Linux 6.5.0-14-generic (recovery mode) (on /dev/sda4)'~7ddb981e79ac5212e8e2fde79095a513~, -'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/'Neon GNU/Linux, with Linux 5.15.0-92-generic (on /dev/sda4)'~7ceebfcea47e66c53740c259709b3e08~, -'Advanced options for KDE neon 5.27 (22.04) (on /dev/sda4)'/'Neon GNU/Linux, with Linux 5.15.0-92-generic (recovery mode) (on /dev/sda4)'~02182e79237ed1cc6a4f06576733d927~}
-#text
+'Windows Boot Manager (on /dev/sda1)'~e16ac4e4291bd2a95696965a2ab6a04c~
"

I reinstalled PCLOS last night after sacrificing it on previous boot issue. I was getting a panic for it after install. I could not find the issue with the PCLOS install so formatted partition and put Mageia on it which caused no issues. No idea why probe is running twice in ubuntu. It runs just once when I updated neon for mageia. But I didn't run customizer in neon, not sure if I even have it installed there. I use customizer to clean up and write to MBR only in ubuntu since it is my main. I went on to ubuntu to update and used customizer to remove the pclos entries that were showing in customizer (I think only one instance with options) and then had it write to MBR. Something else is causing that double probe. Way over my head.

If circumstances were different I would have a play box for new shiny toys but have to be content with just the laptop. Trying new distros didn't used to be this hard, really it wasn't <pops werthers>

colorpurple21859 · 02-02-2024, 07:56 AM

Instead of deleting, disable 42_os-prober_proxy:

Code:

sudo chmod -x /etc/grub/42_os-prober_proxy
sudo update-grub

If there is a problem with 30_os-prober_proxy disable it and re-enable 42_os-prober_proxy

Nishtya · 02-02-2024, 08:30 AM

Quote:

Originally Posted by colorpurple21859

Instead of deleting, disable 42_os-prober_proxy:

Code:

sudo chmod -x /etc/grub/42_os-prober_proxy
sudo update-grub

If there is a problem with 30_os-prober_proxy disable it and re-enable 42_os-prober_proxy

results in

Quote:

chmod: cannot access '/etc/grub/42_os-prober_proxy': No such file or directory

providing I get past this, how do I reenable if I manage to disable?

colorpurple21859 · 02-02-2024, 08:40 AM

should have been:

Code:

sudo chmod -x /etc/grub.d/42_os-prober_proxy

use: chmod +x

sorry about that.

Nishtya · 02-02-2024, 09:24 AM

Quote:

Originally Posted by colorpurple21859

should have been:

Code:

sudo chmod -x /etc/grub.d/42_os-prober_proxy

use: chmod +x

sorry about that.

I should have noticed it, too early in morning here. It returned no errors and prober only ran once. Going to boot through everything and then will mark this solved if if no issues.

How did you know which was the one probably to disable?

Update: windows is missing from the grub menu now though probe picks it up, it is in the BIOS setup EFI list and presumably I can still boot it that way though inconvenient. I only use windows once or twice a day for a game site that absolutely won't with any linux/browser I have tried. Will restore that disabled file and report back. Windows can always be sacrificed but takes the better part of a day to reinstall. ubuntu data is recently backed up but I have it just the way I want it settings-wise and would cry since I am in a nursing home and can't drink and curse (well can't drink)

colorpurple21859 · 02-02-2024, 09:34 AM

They both seem to be working correctly, update-grub/grub-mkconfig runs the files in order of the numbering, 30 puts the os-prober menus before the uefi menu.

Nishtya · 02-02-2024, 09:58 AM

Quote:

Originally Posted by colorpurple21859

They both seem to be working correctly, update-grub/grub-mkconfig runs the files in order of the numbering, 30 puts the os-prober menus before the uefi menu.

Not quite following but I next reenabled 42, disabled 30. Update grub then reboot and it took a long time and never stopped on a grub menu-went straight to ubuntu. I reenabled 30. Update. Double probe, all is back as it was.

I am quite confused. The difference between the two scripts in OP, first probe updates UEFI firmware setting after Mageia and second probe doesn't. The start is a bit different but I don't know enough about what it is. I haven't tried what happens with the external connected and one of those proxy scripts disabled and not sure I want to. Troubleshooting this with just the internal with windows, ubuntu and neon. External with mageia not connected at this time. ubuntu is default in EFI

Quote:

BootCurrent: 0001
Timeout: 2 seconds
BootOrder: 0001,0000,0002,0004
Boot0000* Windows Boot Manager
Boot0001* ubuntu
Boot0002* neon
Boot0004* mageia

looking at 30 and 42 doesn't to makes sense as in 30 removes the windows boot mgr and 42 adds it looking at those scripts. But when I disabled 42, I lost windows in grub menu and when I disable 30 I lose menu completely and it just boots straight up ubuntu. The help is appreciated thanks

yancek · 02-02-2024, 02:04 PM

You've mentioned 4 Linux systems but which are you booting and updating Grub from? If you have an EFI install of windows on the same drive as the booting Linux with Grub and your Linux on that drive is a Legacy/MBR install, Grub won't detect windows. Do you have a directory in /boot/efi for whichever Linux you are running Grub from, that is, an EFI install. If you have a Legacy Linux on one drive and an EFI install of windows on a separate physical drive, it should detect and boot windows. That is my experience with it.

Basically, if all installs on both drives are UEFI, Grub should detect and boot them. Lots of people have problems from using Grub Customizer. Never used it myself so have no opinion.

Nishtya · 02-02-2024, 02:35 PM

All are EFI - both internal and external drive installs. Windows, ubuntu (main driver for years) and a runner-up are on the internal SSD and a plaything or two get kept on the external SSD with some partitions for storage/backups

The answer lies somewhere between those two prober scripts. Neither has all the pieces it seems so I have to keep them both enabled for now.

I wonder about the customizer too, saw it recommended so often in buntu forums when googling and seemed to be pretty handy to use it to install to the MBR rather than how I was doing it CLI with cheat sheets. But creates all these files/dupes add the ubuntus that are too closely related and it gets out of control. I have used linux for 20 yrs because I wanted control. But if there was anyone else around who could be root I would be happy to offer them the job. I am retired.

FWIW, Solus broke my heart and I thought it would be my new number one. It broke my booting so bad what with it using CLR I just couldn't learn to daisy chainload or whatever. That is why I am in re-install *ell and looking for things that will play nice with each other (well except for windows of course you have to pick which hill to die on).

colorpurple21859 · 02-02-2024, 02:51 PM

what happens if you do this:

Code:

sudo mv /etc/grub.d/42_os-prober_proxy /etc/grub.d/29_os-prober_proxy 
sudo chmod -x /etc/grub.d/30_os-prober_proxy
sudo chmod +x /etc/grub.d/29_os-prober_proxy
sudo update-grub

If it isn't to your liking revert back

Nishtya · 02-02-2024, 03:02 PM

Quote:

Originally Posted by colorpurple21859

what happens if you do this:

Code:

sudo mv /etc/grub.d/42_os-prober_proxy /etc/grub.d/29_os-prober_proxy 
sudo chmod -x /etc/grub.d/30_os-prober_proxy
sudo chmod +x /etc/grub.d/29_os-prober_proxy
sudo update-grub

If it isn't to your liking revert back

I could try it if you could explain mv 42, 29. The enable/disable thing I know how to revert. But I need to know more if you can elaborate. Thank you. I am trying to learn this (although not averse to cheat sheets)