Bug 126953
Summary: | Upgrading from RH9 to FC2 on with SATA root renders system unbootable: initrd doesn't include ata_piix | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | C.Laurence Gonsalves <clgonsal> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED DUPLICATE | QA Contact: | Mike McLean <mikem> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | barryn |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 19:04:17 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
C.Laurence Gonsalves
2004-06-29 18:36:57 UTC
It looks like the problem was due to the initrd being incomplete. In particular, I think it was missing the ata_piix module. To fix this, I ran the following: mkinitrd --preload=scsi_mod --preload=sd_mod --with=ata_piix \ /boot/initrd.img-2.6.5-sata 2.6.5-1.358 and then I modified my grub parameters in two ways: - I changed the initrd line to refer to the output of the above command - I changed the root= option to use /dev/sda3 My system is now able to boot again. So there appears to be a problem in the way the FC2 installer constructs the initrd that it installs on some systems. *** This bug has been marked as a duplicate of 121848 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |