Bug 6118 - RedHat 6.1 installer fails w/SCSI boot drive and IDE data drives
Summary: RedHat 6.1 installer fails w/SCSI boot drive and IDE data drives
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jay Turner
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-10-20 04:35 UTC by jered
Modified: 2015-01-07 23:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-10-20 15:06:33 UTC

Attachments (Terms of Use)

Description jered 1999-10-20 04:35:29 UTC
I found that the RedHat 6.1 installer fails in a multitude
of ways when I try to install on a machine with both IDE and
SCSI hard drives, where the SCSI drive is the boot drive.

First, Disk Druid.  In the graphical installer, even when
/dev/sda is given as the only disk I want to allow / on, it
still gets put onto /dev/hda. this is wrong.

Second, when installing LILO, the installer only gives me
the options of installing on the MBR of /dev/hda, or on the
first partition of another drive. There is no way for me to
install to the MBR of /dev/sda from the GUI installer. This
is wrong.

LILO also loses whn Linux knows about hard drives that the
BIOS was told to ignore (because it wants the BIOS ID
number), but LILO is a festering pile of dog droppings and I
don't really expect you to fix that. I do suggest possibly
replacing LILO with GRUB, a friendlier (and more
maintainable) boot loader, however.

I've submitted this with severity normal as most people with
this sort of setup know enough about linux to bash the
installer into submission.


Comment 1 Jay Turner 1999-10-20 15:06:59 UTC
The best way around these issues is to perform an expert install,
using fdisk to partition the drive, which will allow you to put the
root partition and /boot partition anywhere that you wish.  Once this
is done, lilo will allow you to install to the MBR os sda.

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