> Oct 31 16:28:50 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/discs/disc0/part2 ... > Oct 31 16:28:50 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro > Oct 31 16:28:50 90linux-distro: result: /dev/discs/disc0/part2:Fedora Core release 3 (Heidelberg):Fedora:linux > Oct 31 16:28:50 50mounted-tests: debug: os found by subtest /usr/lib/os-probes/mounted/90linux-distro > Oct 31 16:28:50 os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests > Oct 31 16:28:50 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/discs/disc0/part3 > Oct 31 16:28:50 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/discs/disc0/part4 > Oct 31 16:28:50 linux-boot-prober: debug: running /usr/lib/linux-boot-probes/50mounted-tests > Oct 31 16:28:50 50mounted-tests: debug: mounting boot partition by label for linux system on /dev/discs/disc0/part2: LABEL=/boot Well I was wrong about the label, os-prober is smarter than I remembered.. > Oct 31 16:28:50 50mounted-tests: debug: running /usr/lib/linux-boot-probes/mounted/40grub /dev/discs/disc0/part2 /dev/discs/disc0/part1 /var/lib/os-prober/mount ext2 > Oct 31 16:28:50 40grub: debug: parsing menu.lst > Oct 31 16:28:50 40grub: debug: parsing: # grub.conf generated by anaconda > Oct 31 16:28:50 40grub: debug: parsing: # > Oct 31 16:28:50 40grub: debug: parsing: # Note that you do not have to rerun grub after making changes to this file > Oct 31 16:28:50 40grub: debug: parsing: # NOTICE: You have a /boot partition. This means that > Oct 31 16:28:50 40grub: debug: parsing: # all kernel and initrd paths are relative to /boot/, eg. > Oct 31 16:28:50 40grub: debug: parsing: # root (hd0,0) > Oct 31 16:28:50 40grub: debug: parsing: # kernel /vmlinuz-version ro root=/dev/hda2 > Oct 31 16:28:50 40grub: debug: parsing: # initrd /initrd-version.img > Oct 31 16:28:50 40grub: debug: parsing: #boot=/dev/hda > Oct 31 16:28:50 40grub: debug: parsing: default=0 > Oct 31 16:28:50 40grub: debug: parsing: timeout=5 > Oct 31 16:28:50 40grub: debug: parsing: splashimage=(hd0,0)/grub/splash.xpm.gz > Oct 31 16:28:50 40grub: debug: parsing: hiddenmenu > Oct 31 16:28:50 40grub: debug: parsing: title Fedora Core (2.6.9-1.667) > Oct 31 16:28:50 40grub: debug: parsing: root (hd0,0) > Oct 31 16:28:50 40grub: debug: parsing: kernel /vmlinuz-2.6.9-1.667 ro root=LABEL=/1 rhgb quiet > Oct 31 16:28:50 40grub: debug: parsing: initrd /initrd-2.6.9-1.667.img > Oct 31 16:28:50 50mounted-tests: debug: running /usr/lib/linux-boot-probes/mounted/50lilo /dev/discs/disc0/part2 /dev/discs/disc0/part1 /var/lib/os-prober/mount ext2 > Oct 31 16:28:50 50mounted-tests: debug: running /usr/lib/linux-boot-probes/mounted/90fallback /dev/discs/disc0/part2 /dev/discs/disc0/part1 /var/lib/os-prober/mount ext2 > Oct 31 16:28:50 90fallback: result: /dev/discs/disc0/part2:/dev/discs/disc0/part1::/boot/vmlinuz-2.6.9-1.667::root=/dev/hda2 > Oct 31 16:28:50 50mounted-tests: debug: /usr/lib/linux-boot-probes/mounted/90fallback succeeded So the bug is in the grub probe, it failed to provide a result and the fallback probe (that doesn't always find initrds since there is no naming consistency) was the only one to succeed. Hmm, I tried running the menu.lst through 40grub by hand, and it successfully determined that the kernel was at /boot/vmlinuz-2.6.9-1.667 an the initrd at /boot/initrd-2.6.9-1.667.img. Seems that for it to get that far and not provide a result, its final tests to see if the detected kernel and initrd files exist must have failed somehow. That's all I can tell from the log. Debugging this further would require an os-prober with more debugging information. If you'd like to do a non-destructive test involving booting the installer again, here's what would probably help me figure it out: 1. Boot the installer in expert mode "expert" at boot prompt. 2. Go through the steps as usual, but do NOT go into the disk partitioner. Instead, stop after it has detected your hard drive. 3. Use the menu item to open a shell. 4. In the shell: nano /usr/lib/linux-boot-probes/mounted/40grub Change the "set -e" to "set -ex". 5. Run: linux-boot-prober /dev/discs/disc0/part2 > log 2>&1 6. Mount a disk and copy the log file created in step 5 to it, that contains the debugging info I need. 7. Reboot without finishing the installation or doing any partitioning and you'll lose no data. -- see shy jo
Attachment:
signature.asc
Description: Digital signature