Red Hat Bugzilla – Bug 435258
F9 Alpha - anaconda generated wrong grub.conf
Last modified: 2008-05-25 23:31:03 EDT
Description of problem:
In a multiple operating systems installed disk (eg. /dev/sda) which does not
have a /boot partition and does use chain-load from GRUB (the /dev/sda1 system
provided GRUB) to load each one, install F9 alpha to one of the partitions, such
as /dev/sda3. After the installation try starting F9 alpha, it loaded the
/dev/sda1 system. It looked that the kernel of F9 alpha WRONGLY used
'root=LABEL=/' rather than 'root=LABEL=/dev/sda3' to load its own file system.
And then loading /dev/sda1 from GRUB directly failed.
Version-Release number of selected component (if applicable):
Fedora 9 Alpha
Can you reproduce this with later rawhide trees?
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Thank you for the bug report. Though the release version is changed to fedora 9
from Fedora 9 Alpha, I would really appreciate if you could give us details on
whether you are able to reproduce this bug in Fedora 9 too ? . Please give us
the details on that and so currently i would mark this bug's status as NEEDINFO.
Thanks for your kindly reminder. I retested it with anaconda-18.104.22.168-1 in F9
GA and found the problem has been fixed already. So I am closing the bug.