Created attachment 699678 [details] umount: /var/lib/os-prober/mount: filesystem umounted, but mount(8) failed: Connection timed out Description of problem: After updating, via Apper, the new linux kernel around early february 2013 the Windows 7 second bootloader entry does not appear in the grub2 start menu anymore (formerly there were 2 Windows 7 entries). It is not really problem for me because Windows 7 still boots correctly on that sole entry. F18 is installed along with Windows 7 dual boot mode on the same harddrive. It is a Fujitsu Esprimo P700 E90+ with a 500GB SATA 7.2k 3.5" harddrive. I just wondered if there is a connection with the mounting problem that was reported by grub2-mkconfig ,see attachment. Because of the dual boot mode I have to set the default menu entry after every kernel update. Version-Release number of selected component (if applicable): How reproducible: See attachment. This is a record of the 3 attempt. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
1. Do you have any NFS entries in your /etc/fstab? 2. Please attach os-prober's log in syslog ("tailf /var/log/messages" output after running os-prober).
Created attachment 706787 [details] After updating at 7 march there are 5 menuitems in Grub instead of 3 I updated F18 at 7 march 2013 and i now have 5 GRUB menu items instead of 3. There is 1 that i have never seen before " tboot 1.7.0" . Sorry that i reacted so late , i was on holiday in Sri Lanka and one of the first things i did was updating F18.
(sorry for my late answer too!) OK, seems that the mount error doesn't appear anymore, and the second entry is back! Now, some questions: 1. do you have two windows installations or one? 2. Is there any "Windows" directory in /dev/sda5? 3. Please run the mentioned 'tailf' command in a separate terminal and then run grub2-mkconfig. I want the tailf command to be running when you run grub2-mkconfig command so that I can see os-prober logs generated in this process. Or, you can run grub2-mkconfig and then post the end of /var/log/messages which contains all of the logs generated by os-prober (not other logs). Thanks
ad 1 . I have only 1 Windows 7 installation. When I select in the Grub menu the /dev/sda1 item starts Windows 7 correctly. When i select in the same Grub menu the /dev/sda5 item then Windows 7 also starts correctly. ad. 2 I don't quit understand the question. Maybe the above answers it or take a look at the attached terminal log. ad 3. I added the requested os_prober log also in the attachment. Good luck
Created attachment 712213 [details] Log of Terminal session and requested os_prober_log The requested os_prober log
Looks like that /dev/sda5 is your real windows partition and /dev/sda1 is probably something like a recovery partition or maybe a boot loader partition for Win 7. (maybe it is created to be able to boot windows from a logical partition). About the tboot option, it seems that it is not generated by os-prober. Anyway, would you please report the output of the following commands: mount /dev/sda1 /mnt ls /mnt umount /mnt mount /dev/sda5 /mnt ls /mnt umount /mnt grep tboot /etc/grub.d/*
Created attachment 713213 [details] logs from mount and umount commands from /dev/sda1 and /dev/sda5 There are 2 very different test results. I have added some information that maybe help to explain the differences.
OK, tboot entry has nothing to do with os-prober. It is generated by grub2 itself, and it seems that it is generated because you have installed tboot since it is not part of grub2 itself and apparently added by tboot. And the double Windows 7 entries is probably what I said: /dev/sda1 is apparently there to boot windows from /dev/sda5. I wonder if two entries should be reduced to one (if it is possible to discover if the two entries are actually booting a single Windows installation). The time when the second entry probably disappeared due to some problems mounting /dev/sda5 in that time. I cannot tell why until it happens again and I can have the logs. Thanks anyway. Please reopen the bug if the problem appeared again.