Bug 1127385
Summary: | RHS 3.0 ISO (pre-release) does not recognize HP B120i RAID controller used for boot disk mirroring | ||||||
---|---|---|---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Veda Shankar <veshanka> | ||||
Component: | distribution | Assignee: | Sreenath G <sgirijan> | ||||
Status: | CLOSED DEFERRED | QA Contact: | storage-qa-internal <storage-qa-internal> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | rhgs-3.0 | CC: | bcompton, bturner, dsulliva, nlevinki, rcyriac, rhs-bugs, rick.beldin, smohan | ||||
Target Milestone: | --- | Keywords: | ZStream | ||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2018-04-16 07:25:22 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Veda Shankar
2014-08-06 19:26:13 UTC
RHS 3.0 is based on RHEL 6 mainline (6.5 now) and RHS 2.1u2 is based on RHEL 6.3.z. Is the driver available for RHEL 6 mainline and 6.3.z? I see RHEL 6.5 and RHEL 6.3.z drivers in the link. Please try with appropriate driver. (In reply to Bala.FA from comment #2) > RHS 3.0 is based on RHEL 6 mainline (6.5 now) and RHS 2.1u2 is based on RHEL > 6.3.z. > > Is the driver available for RHEL 6 mainline and 6.3.z? I think you meant RHEL 6 mainline and 6.4.z , as RHS 3.0 is based on RHEL 6 mainline and RHSS 2.1 is based on RHEL 6.4.z. Please see comments from Gary Case below. If you have questions on how this is supposed to work, please consult "Gary Case" gcase and "John Shortt" jshortt. Bottom line - I am NOT able to insert an external driver (using USB) during the OS install boot process. This works on stock RHEL6 and RHS ISO should behave the same way. John, I think this is what we in the past referred to as "fakeraid", where the BIOS is doing the work and there's no hardware dedicated to doing the RAID operations. From looking at the hpvsa.ko module that HP provides, the PCI IDs listed there match up with the following: alias: pci:v00001590d00000047sv00001590sd00000047bc*sc*i* alias: pci:v00001590d00000045sv00001590sd00000045bc*sc*i* alias: pci:v00008086d00001D04sv00001590sd00000048bc*sc*i* C600/X79 series chipset SATA RAID Controller alias: pci:v00008086d00008C04sv00001590sd00000084bc*sc*i* 8 Series/C220 Series Chipset Family SATA Controller 1 [RAID mode] alias: pci:v00008086d00008C06sv00001590sd00000084bc*sc*i* 8 Series/C220 Series Chipset Family SATA Controller 1 [RAID mode] alias: pci:v00008086d00001C04sv00001590sd0000006Cbc*sc*i* 6 Series/C200 Series Chipset Family SATA RAID Controller Sayan, I don't see an hpvsa.ko module in RHEL 6.5 or even in Fedora 20, which leads me to believe we don't ship one. I'll let John provide the definitive answer. -Gary Hi all. Just to further clarify things here: -The hpvsa driver is not provided with RHEL, to get the b120i's RAID functionality you need to: install with: # linux dd blacklist=ahci If you don't blacklist the ahci driver these disks show up as 2 devices sda and sdb. When you blacklist ahci and use the driver disk these show up as a single block device as expected. -This works fine on vanilla 6.5: [root@g60ds-2 ~]# lsmod | grep hpvsa hpvsa 2548743 2 [root@g60ds-2 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.5 (Santiago) -The driver disk just contains and RPM for the hpvsa kmod. When I unpack the RPM I see: $ rpm2cpio kmod-hpvsa-1.2.8-160.rhel6u5.x86_64.rpm | cpio -idmv ./etc/depmod.d/hpvsa.conf ./lib/modules/2.6.32-431.el6.x86_64 ./lib/modules/2.6.32-431.el6.x86_64/extra ./lib/modules/2.6.32-431.el6.x86_64/extra/hpvsa ./lib/modules/2.6.32-431.el6.x86_64/extra/hpvsa/hpvsa.ko -If I hit ctrl+alt+f2 during the installer and it looks like RHS 3.0 is running the 2.6.32-431.el6 kernel. I wonder if the kernel version being off is the reason this is failing? I'm sorry, in my last update RHS 3.0 is running the: 2.6.32-431.32.3.el6 kernel There is a typo in my last update. (In reply to Ben Turner from comment #8) > I'm sorry, in my last update RHS 3.0 is running the: > > 2.6.32-431.32.3.el6 kernel > > There is a typo in my last update. I see that the latest RHSS ISO compose for RHS 3.0 - RHSS-3.0-20140805.0-RHS-x86_64-DVD1 - has the 2.6.32-431.23.3.el6 kernel, which is also the highest available kernel version for RHEL 6 in production. I'm not 100% positive but I believe our rescue disk/iso has the same problem. So rescue disk has same problem. To work around you'd blacklist=ahci and then follow here https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/rescuemode_drivers.html I really don't like this because an operational support person may not know the bios array controller was set to dynamic b120i controller and would most likely not know about hpvsa. So very possible to boot into resuce mode see two devices and start working on them independently with something like e2fsck. Can someone tell me why we wouldn't just want to set the bios to ahci controller and use native md raid support? Then there would be no problems here for RHS 3 ISO or linux rescue iso. There seems to be quite a few negatives relative to using hpvsa, notes above plus maintenance burden. Thoughts? hpvsa seen as a possible migration path for customers to hpsa devices. Out of the factory, raid mode (hpvsa) is default. Extra steps needed by customer (going to RBSU) to disable. This is similar to: 1207831 |