Bug 446549 - Cannot see Smart Array 431 even after loading Module
Summary: Cannot see Smart Array 431 even after loading Module
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 9
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-15 01:43 UTC by Martin Rheumer
Modified: 2008-08-05 13:25 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-08-05 00:20:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Compaq ML350 lshal Output (54.68 KB, text/plain)
2008-05-15 23:46 UTC, Martin Rheumer
no flags Details

Description Martin Rheumer 2008-05-15 01:43:31 UTC
Description of problem:

When trying to upgrade from Fedora Core 8 to Fedora Core 9 or installing Fedora 
Core 9 The anaconda installer cannot see the hard drives connected to the Smart 
Array 431 in a Compaq Proliant ML350. I chose kernel option noprobe and can add 
the Smart Array in the installation process, which then finds the existing 
partitions no problem ( ALT-F2 ) fdisk etc all works ok. Installer then says 
there is no drives to install to ( and cannot see existing installation to 
upgrade to ).


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


How reproducible:

Install Fedora Core 9 on ML350 via netinst cd.

Steps to Reproduce:
1.
2.
3.
  
Actual results:

Cannot See Hard Drives

Expected results:

Given the choice to upgrade the existing install.

Additional info:

Comment 1 Chris Lumens 2008-05-15 17:02:14 UTC
Once you're up in the graphical installer, can you pretty ctrl-alt-f2 and attach
the output of lshal to this bug report?  Thanks.

Comment 2 Martin Rheumer 2008-05-15 23:46:44 UTC
Created attachment 305560 [details]
Compaq ML350 lshal Output

Comment 3 Chris Lumens 2008-08-04 15:29:13 UTC
Looks to me like HAL isn't recognizing CCISS devices.  Do you have the proper modules loaded?  You can tell by running lsmod on the command line.

Comment 4 Martin Rheumer 2008-08-05 00:20:42 UTC
This machine was redployed with Debian 4.0 due to non working fedora 9.


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