Red Hat Bugzilla – Bug 620523
anaconda not correctly detecting HP Smart Array P410i RAID controller
Last modified: 2010-09-14 10:07:01 EDT
Description of problem: anaconda (and I suppose RHEL6 in general) is not correctly detecting the HP Smart Array P410i RAID controller. the P410i controller is pretty much standard on all DL/BL 300 G6 series hosts. Version-Release number of selected component (if applicable): RHEL6.0-20100715.2-Server-x86_64 How reproducible: if you have the hardware, very. Steps to Reproduce: 1. Grab a G6 DL360 or BL460 (the two models of hosts I tried this on with P410i controllers) 2. try to install RHEL via DVD or kickstart Actual results: /dev/sda shows up as the logical disk Expected results: /dev/cciss/c0d0 shows up as the logical disk Additional info: I would attach the logs, but they don't appear to be all that helpful. Anaconda doesn't pick up the controller and the cciss driver never gets loaded. I have also opened a ticket with HP for this.
If the driver's not getting loaded, anaconda will never be able to detect the disks attached to it.
This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. **
I neglected to mention that loading the driver manually via kickstart's 'driver' option does not help either.
This really isn't a bug afterall - it looks like HP submitted the hpsa driver to the 2.6.34 kernel which white lists some controllers to use the hpsa kernel module. from: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.34.y.git;a=blob_plain;f=drivers/scsi/hpsa.c;hb=HEAD static struct board_type products[] = { {0x3241103C, "Smart Array P212", &SA5_access}, {0x3243103C, "Smart Array P410", &SA5_access}, {0x3245103C, "Smart Array P410i", &SA5_access}, {0x3247103C, "Smart Array P411", &SA5_access}, {0x3249103C, "Smart Array P812", &SA5_access}, {0x324a103C, "Smart Array P712m", &SA5_access}, {0x324b103C, "Smart Array P711m", &SA5_access}, {0x3233103C, "StorageWorks P1210m", &SA5_access}, {0x333F103C, "StorageWorks P1210m", &SA5_access}, {0xFFFF103C, "Unknown Smart Array", &SA5_access}, }; I suppose it's time to write some more logic into our kickstart scripts :)
Yup. :)
Thank you for your bug report. This issue was evaluated for inclusion in the current release of Red Hat Enterprise Linux. Unfortunately, we are unable to address this request in the current release. Because we are in the final stage of Red Hat Enterprise Linux 6 development, only significant, release-blocking issues involving serious regressions and data corruption can be considered. If you believe this issue meets the release blocking criteria as defined and communicated to you by your Red Hat Support representative, please ask your representative to file this issue as a blocker for the current release. Otherwise, ask that it be evaluated for inclusion in the next minor release of Red Hat Enterprise Linux.