Bug 142622 - Fedora core 3 can not boot from system disk after installation
Summary: Fedora core 3 can not boot from system disk after installation
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda   
(Show other bugs)
Version: 3
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2004-12-10 23:26 UTC by Robinson Tiemuqinke
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-14 01:48:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Robinson Tiemuqinke 2004-12-10 23:26:21 UTC
Description of problem:

The problem is related to kernel module load sequence by anaconda.

I have 4 SATA hard drives on my PC, two connected to motherboard 
directly and 2 others are conncted through Promise SATA raid card. 
while only the primary SATA hard drive directly connected to 
motherboard is bootable.

 When FC3 anaconda begins installation, it first load sata_promise, 
and then load ata_piix(wrong sequence!!). So /dev/sda and /dev/sdb 
are wrongly assigned to two hard drives connected through peripheral 
Promise SATA card, FC3 operation system is then installed to /dev/sda 
which is not bootable. /dev/sdc and /dev/sdd are then assgined to two 
hard drives directly connected to motherboard(ata_piix module).

 After machhine installed successfully, it just can not boot. 

 If anaconda can change the sata drive load sequence, like:

 the driver module for SATA interfaces motherboard loads first.
 the driver module for peripheral local SATA interface load second,
 Then the problems will go away at once.

 If there is a place|section, like in ks.cfg or anaconda.conf, that 
we can specify the above "kernel module loading sequence" for initial 
installation? does anaconda respect /etc/modules.conf 
or /etc/modprobe.conf(FC3) during installation?  

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1. find a machine, like HP workstation xw4100 or xw4200, with 4 sata 
hard drives, two connected to motherboard, and two others through 
promise SATA card.

2. begin normal installation  in text mode and it will be 
successfully installed, check the /tmp/anaconda.log to have a look of 
the module load sequence.

3. reboot and now the machine just can not boot.

Actual results: 

    can not find FC3 operation system installed.

Expected results:

    machine should boot.

Additional info:


Comment 1 Jeremy Katz 2004-12-14 01:48:56 UTC
The driver load order is determined by PCI ordering which ends up
being machine and even BIOS dependent.  You can change the ordering of
the drives for boot loader purposes by going into the advanced boot
loader screen and changing the drive order.

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