Bug 115803 - no drives detected with HP Smart Array 642 controller
Summary: no drives detected with HP Smart Array 642 controller
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
(Show other bugs)
Version: rawhide
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-16 09:41 UTC by Lorenzo Musizza
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-02-16 16:32:10 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Lorenzo Musizza 2004-02-16 09:41:12 UTC 
Description of problem:
trying to install FC2 test1 on a HP ProLiant ML350 with an HP Smart
Array 642 contoller results in the correct kernel driver for the array
being loaded but no available disks found to install.
With Fedora Core 1 there are no problems and the install goes fine.
I think the problem may reside in the creation of the appropriate
device (e.g. /dev/cciss/c0d0).



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


How reproducible: always


Steps to Reproduce:
1. install Fedora Core 2 test 1 on a Smart Array 642 controller
2. anaconda loads the correct kernel module but...
3. ...no disk can be found
  
Actual results:

installation is not possible

Expected results:

I should be able to install

Additional info:

all works fine with Fedora Core 1
Comment 1 Jeremy Katz 2004-02-16 16:32:10 UTC 
cciss, cpqarray, and dac960 probing were busted in test1... I fixed
them the day after we froze, so the development tree should be good to
go for them.
Note You need to log in before you can comment on or make changes to this bug.