cciss Drivers and RedHat AS 4

[Jason Jones_10]

Hi all,

I have just downloaded RedHat AS 4 in a bid to solve my disk errors with the cciss drivers. On the RedHat site I found AS4 Update 1 and so downloaded those ISOs.

However, when trying to install the cpq_cciss RPM I discover that only the original AS 4 kernel is supported and not the 'Update 1' kernel. :-(

Does anyone know when the Update 1 kernel will be supported? Or does anyone know how to install the RPM and build the kernel?

Many thanks,

Jason

[Gopi Sekar]

I believe cciss driver is a binary only driver (no source included). it will install only on the kernels for which it has binary object (.o) file.

What version of Proliant support pack you are trying to use? If i am correct PSP 7.40 (which has support for RHEL 4 update 1) is due for release very soon, you should be able to download it from hp.com website by end of this month.

Hope this helps,
Gopi

[Vitaly Karasik_1]

Jason,

Which problems do you have with cciss/disks?

I have many RHEL 2.1/3/4 on DL360/380, which work without problems.
BTW, cciss driver itself is GPL.

[Gopi Sekar]

the other post just made me to do google and got this website. it has source code for cciss.

http://sourceforge.net/projects/cciss

[Jason Jones_10]

Hi Vitaly,

My first email might have been a bit misleading. I was having problems with my machine when using Fedora Core 2 and as that was not supported I upgraded to AS 4 to try to solve my problems.

The original submission is at:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=948535

I am not worried about having to upgrade to AS 4 - that is fine with me. I just want to make sure that this will solve my problems. Was there a problem with Fedora Core 2 drivers?

[Vitaly Karasik_1]

I see.
I haven't worked with Promise RM8000, I'm using "standart" cciss driver from RHEL 2.1/3 with DL 360/380 G3/G4

[Jason Jones_10]

I don't think it is the Promise drive though. As I said in that other posting, I took the drive off and thrashed it with an SGI Onyx and there were no errors.

And, during an up2date session, I noticed the same errors were happening on the internal system disk. I am guessing it was probably the first time the system disk was thrashed with writes since installation.

Basically, the DL380 is the I/O node for our cluster comprising loads of DL145's. We chose it because it had the SCSI interface and then individual research groups could purchase their own RAID drives if they wanted to. These errors only started happening when this first RAID drive was attached - probably because the node was idle before.

I will be putting the Promise drive back on later today and I will leave the machine thrashing it again to see if any more errors get reported.

Jason

[Gopi Sekar]

if you feel you are having problems with FC2 then why don't you try with FC4 which is virtually equivalent to RHEL 4 ?

I am sorry if i am dragging you too much in to other way...

Regards,
Gopi

[Vitaly Karasik_1]

AFAIK, RHEL4 is *similar* to FC3, not FC4.

But anyway - I suggest to leave with RHEL and open support ticket in RH.

[Jason Jones_10]

The reason I chose AS4 over Fedora Core 4 was that HP would support it with their RPMs if I ran into any troubles.

I guess I was hoping that someone would come along and give a good reason for Fedora Core 2 having problems and that AS 4 works fine.

My only worry is that I move to AS 4 (as it is installed now) and whilst the machine is out of the production cluster it seems to solve my problems, but in 3 weeks time, when I put it back in the cluster, the same errors happen.