Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 592184 - Boot loader configuration incorrect after installing to /dev/sdb
Summary: Boot loader configuration incorrect after installing to /dev/sdb
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-14 07:39 UTC by Amit Shah
Modified: 2010-05-14 07:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-14 07:46:55 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Amit Shah 2010-05-14 07:39:50 UTC
Description of problem:
On a desktop with two hard disks, I installed RHEL6 in a partition on /dev/sdb. I 'activated' only /dev/sdb for install and kept /dev/sda for the data mounts.

I selected /dev/sdb for installation of the boot loader.

After the install was done, booting into /dev/sdb wasn't possible. Peeking into the grub.conf file generated, it used hd(0,0) as the root instead of (hd1,0). It also used (hd0,0) for the splashimage location.

After manually correcting this, boot works.

This is from a nightly install of RHEL6, anaconda version anaconda-13.21.38-1.el6.x86_64.rpm

Comment 1 Hans de Goede 2010-05-14 07:46:55 UTC
This is expected behaviour, the disks to install unto selection screen where you can move disks from the left to the right, has a radiobutton column in the right display named boot, here you indicate which disk your system will boot from, you indicated it will boot from sdb, so anaconda assumes that sdb is the first disk in the bios order (iow bios disk 80) and thus hd0.

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