Bug 444183 - F9 preview boot failed on nash, system is AMD X2 PATA+SATA HW RAID
Summary: F9 preview boot failed on nash, system is AMD X2 PATA+SATA HW RAID
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd
Version: 9
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-04-25 17:51 UTC by Edmond
Modified: 2009-02-17 12:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-02-17 12:54:20 UTC

Attachments (Terms of Use)
screenshot of system hangs (367.45 KB, image/gif)
2008-04-25 17:51 UTC, Edmond
no flags Details

Description Edmond 2008-04-25 17:51:49 UTC
Description of problem:
F9 preview failed to boot after installed. It hangs w/ a init SIGSEGV (see
screenshot from F8 i686 install)

The system is:
AMD X2 3800+
Quamtum fireball AS 20GB PATA HDD
8x DVD drive
2 x WDC WC1600JS 160GB SATA HDD running on build in hw RAID1

Tried on F9 preview x86_64, F8 x86_64/i686 and seeing the same problem.

The system is currently running F6, but HDD is dying w/ lost interrupt.

Version-Release number of selected component (if applicable):
nash 6.0.19 from F9 preview

How reproducible:

Steps to Reproduce:
1. install via DVD
2. reboot
Actual results:
system hangs @ boot up

Expected results:
boot success and system start up continue

Additional info:

Comment 1 Edmond 2008-04-25 17:51:49 UTC
Created attachment 303806 [details]
screenshot of system hangs

Comment 2 Edmond 2008-04-28 13:10:31 UTC
As I continue to debug the problem, I removed the SATA HDDs and install F9
preview again. The system then successfully booted. I connect the SATA HDDs back
to the system and the system continue to function. It looks like something goes
wrong during installation.

Comment 3 Bug Zapper 2008-05-14 10:10:26 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:

Comment 4 Hans de Goede 2009-02-17 12:54:20 UTC
The backtrace seen in the attached image is a known problem with how mkinitrd handles dmraid sets, which is fixed in mkinitrd-6.0.78, which will show uop in rawhide soon. Due to invasive nature of the changes fixing this, an update fixing this for F-9 (nor F-10) is not very likely.

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