On Fri, 2004-12-31 at 11:30 +0200, Toni wrote:

I've found a problem with CentOS 3 latest kernel (2.4.21-27.0.1.ELsmp) and megaraid2 driver.

Hardware: Dell PE1600SC with CERC ATA100 RAID controller

The problem is somewhat similar, but not identical as:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=123289

After updating new glibc and kernel packages the new kernel don't boot. Boot fails to mount root fs with "Cannot open root device" message.

I doublechecked that /etc/modules.conf is refering to megaraid2 as it should and then recreated initrd manually, no help. Older kernel version (2.4.21-20.0.1.ELsmp) boots just fine.

As RHEL3 U4 release notes states:

http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/release-notes/as...

The megaraid2 driver has been updated from v2.10.6 to 2.10.8.2-RH1 The new driver is scsi/megaraid2.o The older driver has been preserved as addon/megaraid_2106/megaraid_2106.o

So I decided to try megaraid_2106, changed modules.conf, recreated initrd and... server booted with the new kernel!

Could there be a problem with the latest megaraid2 driver (2.10.8.2-RH1)? Since I'm using CentOS and not RHEL, how/where I could report this problem?

I would report this at bugzilla.redhat.com for RHEL 3. I report bugs with the RedHat SRPMS there all the time. (It's down for maintenance right now). In your verbose description, you can include that this is on CentOS-3 but seems to be an upstream 2.10.8.2-RH1 driver problem on the 2.4.21-27.0.1.ELsmp kernel.

You might also want to post it to the taroon-list (RHEL 3) mailing list: http://www.redhat.com/mailman/listinfo/taroon-list

RedHat is happy for legitimate problems to be posted so they can take corrective action. That is one of the benefits to the rest of the Linux community that CentOS provides.