Bug 27058 - Installer fails to set active partition properly (boot order wrong).
Summary: Installer fails to set active partition properly (boot order wrong).
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-02-11 17:53 UTC by Ed McKenzie
Modified: 2007-04-18 16:31 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2001-09-27 19:30:25 UTC


Attachments (Terms of Use)

Description Ed McKenzie 2001-02-11 17:53:08 UTC
This box has two off-board disk controllers (Initio SCSI and Promise ATA,
both with a combination of disks and CD-ROMs), and anaconda fails to create
a lilo.conf that can successfully boot the system. The Promise card is the
boot device, as it's first in PCI order and gets assigned BIOS drives C and
D. However, anaconda sets boot=/dev/sda (E:) in lilo.conf. Incidentally,
the kernel too lists sda first in /proc/partitions, which is wrong.
Changing the boot order in the BIOS doesn't seem to affect this ordering.

After installation, the system can't be booted, as there aren't any active
partitions and anaconda has installed LILO on the wrong MBR.

Comment 1 Michael Fulbright 2001-02-12 03:59:54 UTC
What is the device name(s) for the drives on the Promise card?

Comment 2 Ed McKenzie 2001-02-12 04:12:04 UTC
full setup:

/dev/hdb - CD-ROM on primary slave (on-board controller, VIA MVP3)
/dev/hde - IBM Deskstar on primary master (Promise)
/dev/hdg - IBM Deskstar on secondary master (Promise)
/dev/sda - Seagate on ID0 (boot) of Initio 9100UW
/dev/scd0 - CD-RW on Initio

Comment 3 Michael Fulbright 2001-02-14 05:33:22 UTC
What are the partitions/mount points you specified?

Comment 4 Ed McKenzie 2001-02-14 07:02:41 UTC
/
	/dev/sda1
/boot
	/dev/hde1
/usr
	/dev/hde3
/home
	/dev/hde4


Comment 5 Michael Fulbright 2001-02-14 18:02:47 UTC
Thanks I will look at this.

Comment 6 Michael Fulbright 2001-02-14 21:29:12 UTC
This is something we will have to address in the future.  There is not currently
a mechanism to determine which drive is 0x80 as far as the BIOS is concerned.
Adding a UI interface to allow the user is not an option at this time because we
have frozen the UI.

Comment 7 Jeremy Katz 2002-01-22 00:59:32 UTC
For future releases, you will be able to change the order of the drives if our
guess is not correct


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