Bug 592184

Summary:	Boot loader configuration incorrect after installing to /dev/sdb
Product:	Red Hat Enterprise Linux 6	Reporter:	Amit Shah <amit.shah>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED NOTABUG	QA Contact:	Release Test Team <release-test-team>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	hdegoede
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-05-14 07:46:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.