Bug 70844 - install generated invalid grub.conf
Summary: install generated invalid grub.conf
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda (Show other bugs)
(Show other bugs)
Version: limbo
Hardware: i386 Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2002-08-06 01:17 UTC by Jay Berkenbilt
Modified: 2007-04-18 16:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-08-06 01:17:48 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jay Berkenbilt 2002-08-06 01:17:44 UTC
Note: I did a search for this and was astonished not to find any bugs reported
on anaconda in limbo.  I hope I did the correct search.

Description of Problem:

I did a from-scratch install with root /dev/hda7.  I have regular RedHat 7.3
also installed on this machine with root on /dev/hda2, and /dev/hda2 already has
the label /.  /dev/hda7 was labelled /1 (which is fine).  I told the installer
to install grub on /dev/hda7 (rather than /dev/hda) which it did correctly.  The
/boot/grub/grub.conf that it generated contains this line:

	kernel /boot/vmlinuz-2.4.18-7.80 ro hdd=ide-scsi root=LABEL=/1

which is wrong.  The kernel doesn't like root=LABEL=/1.  root=/dev/hda7 would
correct.  Presumably this string came from the same source that was used for
generating /etc/fstab, but I should refrain from idle speculation in this bug

I am otherwise able to boot fine by editing this line to change root=LABEL=/1 to

Version-Release number of selected component (if applicable):

limbo 7.3.93

How Reproducible:


Steps to Reproduce:

I don't really know, but I described my configuration above: from scratch
install onto an unused partition with another partition on the system already
labelled as /, instruct grub (using advanced options in the installer) to
install grub on the root device instead of the master boot record.

Actual Results:

grub.conf generated the invalid root=LABEL=/1 kernel parameter.

Expected Results:

grub.conf should have had root=/dev/hda7 as an argument rather than root=LABEL=/1.

Comment 1 Jay Berkenbilt 2002-08-06 01:21:52 UTC
Oops -- sorry about this.  The booting problem I had was not related to this. 
This bug report is wrong.  Just ignore it.

Note You need to log in before you can comment on or make changes to this bug.