Bug 592184 - Boot loader configuration incorrect after installing to /dev/sdb
Boot loader configuration incorrect after installing to /dev/sdb
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Anaconda Maintenance Team
Release Test Team
Depends On:
  Show dependency treegraph
Reported: 2010-05-14 03:39 EDT by Amit Shah
Modified: 2010-05-14 03:46 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-14 03:46:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Amit Shah 2010-05-14 03:39:50 EDT
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 03:46:55 EDT
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.