Starting iscsid - generates unknown symbol in module

Latest response

Attempting to upgrade a server installation to 5.9 (previously 5.3). Following base installation, starting the iscsid service generates a number of warning/fatal messages listed below. Could anyone enlighten me about the messages? Are they a problem or not? Why is the symbol not in the module? Is there a work around?

dmesg lists registered transports for cxgb3i, tcp, and be2iscsi (not bnx2i, or ib_iser)

Thanks for any replies.

WARNING: Error inserting libiscsi2 (/lib/modules/2.6.18-348.3.1.el5PAE/kernel/drivers/scsi/libscsi2.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting bnx2i (/lib/modules/2.6.18-348.3.1.el5PAE/kernel/drivers/scsi/bnx2i.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting ib_core (/lib/modules/2.6.18-348.3.1.el5PAE/kernel/drivers/infiniband/core/ib_core.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting ib_mad (/lib/modules/2.6.18-348.3.1.el5PAE/kernel/drivers/infiniband/core/ib_mad.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting ib_sa (/lib/modules/2.6.18-348.3.1.el5PAE/kernel/drivers/infiniband/core/ib_sa.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting iw_cm (/lib/modules/2.6.18-348.3.1.el5PAE/kernel/drivers/infiniband/core/iw_cm.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting ib_cm (/lib/modules/2.6.18-348.3.1.el5PAE/kernel/drivers/infiniband/core/ib_cm.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting rdma_cm (/lib/modules/2.6.18-348.3.1.el5PAE/kernel/drivers/infiniband/core/rdma_cm.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting libiscsi2 (/lib/modules/2.6.18-348.3.1.el5PAE/kernel/drivers/scsi/libiscsi2.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting ib_iser (/lib/modules/2.6.18-348.3.1.el5PAE/kernel/drivers/infiniband/ulp/iser/ib_iser.ko): Unknown symbol in module, or unknown parameter (see dmesg)

Responses

Have you verified that the modules aren't getting double-loaded for some reason; perhaps a bad cleanup after the update? I've seen something similar (not this exact thing) with CentOS box that did an upgrade.

I've seen weirdness similar to this when people have removed IPv6 support the wrong way (typically as part of a poorly-written hardening guide).