You are not logged in.
Yes, it takes several minutes between "No volume groups found" and "Found Gentoo Base System release 2.2 on /dev/sda2".
Which os-prober is responsible for. Are you certain you have the latest os-prober package? Check the binary it has 166* lines, pretty well formatted.
Edit:* plus 285 from /usr/share/os-prober/common.sh plus several others in /usr/lib/os-probe*.
Is there anything unique about your setup? Do you use lvm or raid?
Edit: The lvm question seems futile after 'no volume groups found' message.
Last edited by emeres (2014-08-07 10:50:18)
Offline
My sytem is up to date.
# pacman -Q| grep os-prober
os-prober 1.58-1
The lines of os-prober files:
# wc -l /usr/bin/os-prober
166 /usr/bin/os-prober
# wc -l /usr/share/os-prober/common.sh
285 /usr/share/os-prober/common.sh
# wc -l /usr/lib/os-prober/newns
18 /usr/lib/os-prober/newns
# wc -l /usr/lib/os-probes/50mounted-tests
93 /usr/lib/os-probes/50mounted-tests
# wc -l /usr/lib/os-probes/init/10filesystems
39 /usr/lib/os-probes/init/10filesystems
# wc -l /usr/lib/os-probes/mounted/*
70 /usr/lib/os-probes/mounted/05efi
23 /usr/lib/os-probes/mounted/10freedos
21 /usr/lib/os-probes/mounted/10qnx
30 /usr/lib/os-probes/mounted/20macosx
115 /usr/lib/os-probes/mounted/20microsoft
33 /usr/lib/os-probes/mounted/30utility
48 /usr/lib/os-probes/mounted/40lsb
16 /usr/lib/os-probes/mounted/70hurd
28 /usr/lib/os-probes/mounted/80minix
35 /usr/lib/os-probes/mounted/83haiku
138 /usr/lib/os-probes/mounted/90linux-distro
19 /usr/lib/os-probes/mounted/90solaris
# wc -l /usr/lib/os-probes/mounted/efi/*
24 /usr/lib/os-probes/mounted/efi/10elilo
28 /usr/lib/os-probes/mounted/efi/20microsoft
Offline
You do not have to count them, I just indicated it is not that much to read, but apparently it is, because of recursions. One of the commands/functions stalls the rest, the goal now should be to determine which one or at least which part of code. You could do that by setting break/information points, across the relevant files. Simply setting echo abstract-name between steps, will get you informed what part is being executed and how long it takes, echo could be used with date. Exit within functions could be also used. There might be internal logging features as well.
Edit: Just be careful, since you would need to run this as root.
Last edited by emeres (2014-08-06 23:43:35)
Offline
I am not able to do that...
Last edited by joseribeiro (2014-08-11 23:25:24)
Offline
You should have made a new post, there are too many threads to keep eye on every one of them. Any progress? I guess recent updates, should there have been any, did not improve the situation?
Offline
No improvements.
Offline
Try something like this. Run it directly, not through grub-mkconfig. Determine which part takes most time.
Offline