completion of grub2-mkconfig takes >five minutes

English Install/Boot/Login
1

Yes, well, I’ve never known a grub2-mkconfig take so long - greater than 5 (five) minutes)

linux:~ # grub2-mkconfig -o /boot/grub2/grub.cfg 
Generating grub configuration file ...
Found background: /home/hugh/Pictures/gandharva.png
Found linux image: /boot/vmlinuz-3.17.2-1-desktop
Found initrd image: /boot/initrd-3.17.2-1-desktop
Found memtest image: /boot/memtest.bin
  WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
  connect() failed on local socket: No such file or directory
  Internal cluster locking initialisation failed.
  WARNING: Falling back to local file-based locking.
  Volume Groups with the clustered attribute will be inaccessible.
  No volume groups found
Found Windows 8 (loader) on /dev/sda1
Found PCLinuxOS on /dev/sdb5
Found Arch on /dev/sdb6
Found openSUSE 20141112 (x86_64) on /dev/sdb7
done

I have never known grub2-mkconfig to take so long to complete.

The wait period begins after ‘No volume groups found’

I am wondering if that is the point where os-prober kicks in.

I don’t actually boot to the other OS’es listed from openSUSE so don’t really need them probed or listed.

Would it be OK to disable os-prober in /etc/default.d/grub or remove it entirely from the system?

Have other people done this and survived?

Thanks,

Hugh

KDE x86_64 Bit Tumbleweed installed directly from the repo and not upgraded from a 13.2 install

2

suggest try first in -Yast --Boot Loader —Boot Loader Settings
the Probe Foreign OS is only selected for the preferred booting OS
in the other make sure its de-selected

does this change improve anything?

3

Yes! grub2-mkconfig completed in seconds after I was done with Yast.

I edited /etc/default/grub made a change saved the change
then I ran

grub2-mkconfig -o /boot/grub2/grub.cfg

The command completed in seconds.

Thanks,

Hugh