Bug 125886 - Install fails because disks cannot be found on mptscsih controller
Summary: Install fails because disks cannot be found on mptscsih controller
Status: CLOSED DUPLICATE of bug 123795
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2004-06-13 09:13 UTC by Joe Cooper
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2006-02-21 19:04:04 UTC

Attachments (Terms of Use)

Description Joe Cooper 2004-06-13 09:13:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040207 Firefox/0.8

Description of problem:
A system with the following controller:

01:04.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030
PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07)

Which uses the mptbase+mptscsih driver on Fedora Core 1 (though with
the bug mentioned in
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=125883 ), cannot
be installed or upgraded with Fedora Core 2, as anaconda or the kernel
do not correctly recognize the controller, so no disks are found.

I can manually insert the modules when offered the chance to do so,
but the disks are still not found and the system reboots at the
partitioning stage.

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

How reproducible:

Steps to Reproduce:
1. Try to install or upgrade Fedora Core 2.
2. Watch it fail to find the disks.

Actual Results:  Install fails.

Expected Results:  Install succeeds.

Additional info:

Comment 1 Bill Ralph 2004-06-14 19:17:46 UTC
This is the same bug as reported in 123795, which seems to have been
filed in /dev/null.

Comment 2 Joe Cooper 2004-06-14 19:31:48 UTC
Bill's right.  This is a dupe.  Apologies.  Though I would like to
know how to proceed to get it resolved.

*** This bug has been marked as a duplicate of 123795 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:04:04 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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