Red Hat Bugzilla – Bug 431642
anaconda is not adding installed fedora to grub
Last modified: 2009-01-21 11:17:34 EST
Description of problem: f9 alpha x86_64 live cd : during install to hard disk, anaconda does not add installed fedora (8) to grub Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.install f9 alpha x86_64 live cd to hard disk 2. 3. Actual results: anaconda does not add installed fedora to grub Expected results: anaconda sees and adds all installed operating systems to grub menu Additional info:
still true for f9beta x86_64 live
Please attach /var/log/anaconda.log to this bug report, as well as your grub.conf file. Thanks.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Created attachment 308653 [details] grub.conf
Created attachment 308654 [details] anaconda dump (it crashed)
Created attachment 313524 [details] anaconda log f 10 alpha i686 live cd
Created attachment 313525 [details] grub conf f10 alpha i686 live cd as you can see, the installer assumes the added boot entry belongs to an windows-like os.
Did you get a dialog with the following message in it during installation? Error: Error informing the kernel about modifications to partition /dev/sdb5 -- Device or resource busy. This means Linux won't know about any changes you made to /dev/sdb5 until you reboot -- so you shouldn't mount it or use it in any way before rebooting.
yes, as reported here: https://bugzilla.redhat.com/show_bug.cgi?id=431641
Yeah, the error message you are getting is what's then causing this problem with your grub.conf. The best thing to do here is to (unfortunately) reboot after partitioning and do the exact same partitioning steps again. I don't really have a better answer for you as far as anaconda goes, but perhaps there is something we could do in parted.
This message usually occurs when you attempt to partition on a mounted device. Was the device you tried to install to mounted? If so Im guessing that this could be addressed in anaconda by doing some sort of mount-check before comiting any parted changes (if this is the case, this bug is a clone of 450203)
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I'm dupping these two bugs based on the fact that the error messages are identical. *** This bug has been marked as a duplicate of bug 450203 ***