Description of problem: I have on my laptop (Lenovo L430) two Fedora systems. One F19 with /boot on /dev/sda1 and one F20 on /dev/sda8. After installation of F20 only F20 was bootable. Ran os-prober in order to create F19 entry in grub2 of F20 but no output from os-prober. Version-Release number of selected component (if applicable): os-prober 1.58-4 How reproducible: every time Steps to Reproduce: 1.boot F20 2.run os-prober 3. Actual results: No output Expected results: /dev/sda1:Fedora (3.11.10-200.fc19.x86_64) 19 (Scrödinger's Cat):Fedora:linux Additional info:
Please give the os-prober output in /var/log/messages, this is certainly not a general problem since it works fine on my system. Also, make sure that your Fedora 19 is rebooted/shut down cleanly.
(In reply to Hedayat Vatankhah from comment #1) > Please give the os-prober output in /var/log/messages, this is certainly not > a general problem since it works fine on my system. Also, make sure that > your Fedora 19 is rebooted/shut down cleanly. I've reinstalled grub2 on F19 so I could boot it. Going back to F20 using same method didn't succeed so I can't boot F20 at the moment. Using the rescue feature I can chroot F20 and running os-prober in this way does not produce any output neither on the terminal nor /var/log/messages. I will reinstall F20 and see what it brings. Will come back when it's done.
Created attachment 839259 [details] os-prober output to file messages.
And where is the / partition of F19?
(In reply to Hedayat Vatankhah from comment #4) > And where is the / partition of F19? I have following layouts: F19: /dev/sda1: /boot /dev/sda2: /usr /dev/sda3: /var /dev/sda5: /tmp /dev/sda6: / /dev/sda7: /home F20: /dev/sda8: /boot /dev/sda9: /home /dev/sda10: /usr /dev/sda11: /tmp /dev/sda12: /var /dev/sda13: /
I think I found the problem. This is probably because your /usr is separate. I'll try to fix the issue. Thanks for your report. Unfortunately, I'll probably be absent for a while but I'll fix it ASAP.
(In reply to Hedayat Vatankhah from comment #6) > I think I found the problem. This is probably because your /usr is separate. > I'll try to fix the issue. > Thanks for your report. > Unfortunately, I'll probably be absent for a while but I'll fix it ASAP. Merry Christmas
Any progress with fixing this bug?
I'm back. Please wait a little, I'll try to fix it soon. However, I think it needs some thought since the 'usermove' concept of Fedora and using a separate /usr breaks a fundamental assumption in os-prober in detecting "Linux" OS.
Hi Erik, os-prober does not see Fedora 20 on /dev/sdd (gpt partition btrfs format) I have a day to day Fedora 20 on my /dev/sda. After reinstalling Fedora 20 on the /dev/sdd partitioned gpt, and with using anaconda's choice to use btrfs, this system installed correctly, and shows all the operating systems on this computer. However, the Fedora 20 on /dev/sda (msdos org, formatted ext4 as non btrfs and non lvm), does not see the other F20. Is it a problem with gpt, or a problem with having chosen btrfs via anaconda? There is also a fedora19 on this system at /dev/sdc (MSDOS partitions and using ext4 (non lvm and not btrfs). My work around for now is to boot from the newer installation, but by default, start the version on /dev/sda
(In reply to Hedayat Vatankhah from comment #9) > I'm back. Please wait a little, I'll try to fix it soon. However, I think it > needs some thought since the 'usermove' concept of Fedora and using a > separate /usr breaks a fundamental assumption in os-prober in detecting > "Linux" OS. I have never seen this problem before. I have always used this partition scheme latest with F18 which would see all other linux systems, so I assume this is a problem with F20.
Well, a new Fedora can see other distributions including older Fedora's without usermove feature, but the problem is 'see'ing newer Fedora's. Would you please check if this will fix the problem on your system: run os-prober and give the output. Then: In /usr/libexec/os-probes/mounted/90linux-distro find the following line if (ls "$dir"/lib*/ld*.so* && [ -d "$dir/boot" ] || ls "$dir"/usr/lib*/ld*.so*) >/dev/null 2>/dev/null; then And change it to: if [ -L "$dir"/lib ] || (ls "$dir"/lib*/ld*.so* && [ -d "$dir/boot" ] || ls "$dir"/usr/lib*/ld*.so*) >/dev/null 2>/dev/null; then run os-prober again and see if the output shows recognition of F19.
(In reply to Hedayat Vatankhah from comment #12) > Well, a new Fedora can see other distributions including older Fedora's > without usermove feature, but the problem is 'see'ing newer Fedora's. > > Would you please check if this will fix the problem on your system: > run os-prober and give the output. Then: > > In /usr/libexec/os-probes/mounted/90linux-distro find the following line > if (ls "$dir"/lib*/ld*.so* && [ -d "$dir/boot" ] || ls > "$dir"/usr/lib*/ld*.so*) >/dev/null 2>/dev/null; then > > And change it to: > if [ -L "$dir"/lib ] || (ls "$dir"/lib*/ld*.so* && [ -d "$dir/boot" ] || ls > "$dir"/usr/lib*/ld*.so*) >/dev/null 2>/dev/null; then > > run os-prober again and see if the output shows recognition of F19. Right on. It certainly does fix the problem. Thanks a lot.
Thank you :) So my guess about the problem was correct. However, this is still not the solution. I'll check further to see how it can be properly solved.
(In reply to Hedayat Vatankhah from comment #14) > Thank you :) > So my guess about the problem was correct. However, this is still not the > solution. I'll check further to see how it can be properly solved. An added comment which may be a little pessimistic. It is true that os-prober finds the other OSes (F19 and F16) when it is executed from the command line. But when I boot F20 only F16 is found. Isn't it os-prober that finds the other OSes when F20 is booted?
No, when Fedora is booted no OS is being 'found'. Boot menu comes from grub config file. To generate a new config using the fixed os-prober you should do the following: grub2-mkconfig -o /boot/grub2/grub.cfg grub2-mkconfig uses os-prober to found other OSes, and generates the config for them.
(In reply to Hedayat Vatankhah from comment #16) > No, when Fedora is booted no OS is being 'found'. Boot menu comes from grub > config file. To generate a new config using the fixed os-prober you should > do the following: > grub2-mkconfig -o /boot/grub2/grub.cfg > > grub2-mkconfig uses os-prober to found other OSes, and generates the config > for them. OK. Ran grub2-mkconfig and F19 showed up at boot. Very nice.
os-prober-1.58-6.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/os-prober-1.58-6.fc20
os-prober-1.58-6.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/os-prober-1.58-6.fc19
(In reply to Fedora Update System from comment #18) > os-prober-1.58-6.fc20 has been submitted as an update for Fedora 20. > https://admin.fedoraproject.org/updates/os-prober-1.58-6.fc20 I am sorry but I can't see that you have made any change to os-prober. The bug is back after installing the update.
That's weird. Would you please run: grep "\-L" /usr/libexec/os-probes/mounted/90linux-distro and give the output?
(In reply to Hedayat Vatankhah from comment #21) > That's weird. Would you please run: > grep "\-L" /usr/libexec/os-probes/mounted/90linux-distro > > and give the output? [root@epohost ~]# grep "\-L" /usr/libexec/os-probes/mounted/90linux-distro [root@epohost ~]#
Package os-prober-1.58-6.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing os-prober-1.58-6.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-6117/os-prober-1.58-6.fc19 then log in and leave karma (feedback).
(In reply to Fedora Update System from comment #23) > Package os-prober-1.58-6.fc19: > * should fix your issue, > * was pushed to the Fedora 19 testing repository, > * should be available at your local mirror within two days. > Update it with: > # su -c 'yum update --enablerepo=updates-testing os-prober-1.58-6.fc19' > as soon as you are able to. > Please go to the following url: > https://admin.fedoraproject.org/updates/FEDORA-2014-6117/os-prober-1.58-6. > fc19 > then log in and leave karma (feedback). Vil that also work for fc20?
well, changed fc19 with fc20 and ran the update and now the bug was gone (again :-)
So the update works fine. I wonder what did you do initially as the update was NOT installed. Anyway, it would be nice if you leave a karma in the update page.
In comment 18 you announced that os-prober was submitted for update so I ran yum update os-prober but apparently I got the old buggy os-prober. I would be happy to leave a karma but in my vocabulary karma is something you cannot leave. If you mean feedback isn't that what I've done so far?
:) Looks like that you are not much familiar with Fedora update system. Comment 18(19 and 23) are not from mine, but fedora update system. It says the package is 'submitted' as an update, but it takes some time for it to actually enter updates repo. Comment 23 says that it has entered 'testing' repo. And, it is not yet in Fedora updates repository. And about karma, well I'm talking about karma in bodhi vocabulary: > Please go to the following url: > https://admin.fedoraproject.org/updates/FEDORA-2014-6117/os-prober-1.58-6. > fc19 > then log in and leave karma (feedback) In that URL, you can leave feedback and also mark if the update works fine for you. That mark is called karma (if negative, it is -1 karma and +1 if positive). If the package reaches +3 karma, it'll be pushed to updates repository automatically. If not, I can push the update to updates repository after at least 1 week if I believe that that the update is OK.
Yes, you are right. I am not familiar with the update system. I went to the link for leaving the karma, logged in and found no place to leave it. Maybe there is a place but my intuition isn't good enough to find it. I surely would leave the karma if I could.
:) Sorry for not being more clear. After logging in, you should see "Add a comment >>" at the bottom of the page. When clicked, you can add a comment and select one of these: Untested (no karma), Works for me (+1 karme), Does not work (-1 karma). Even if there is no comment, you should press 'Add Comment" to add the karma.
os-prober-1.58-6.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
os-prober-1.58-6.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.