Red Hat Bugzilla – Bug 140647
megaraid -> megaraid_mbox name change not handled on upgrades
Last modified: 2015-01-04 17:12:56 EST
I just upgraded a Dell PowerEdge 1600SC running FC2 to FC3. The
upgrade crashed and burned with a kernel panic in the reboot after the
The problem is that this machine has a megaraid card. In FC2, that
used the megaraid driver. In FC3, that uses the megaraid_mbox driver.
Anaconda didn't fix /etc/modprobe.conf accordingly, so the initrd that
was generated lacked the required megaraid_mbox driver. Fixing
modprobe.conf from rescue mode and regenerating the initrd fixed the
This will likely bite anyone upgrading < FC3 to FC3 with megaraid devices
megaraid2 SCSI megaraid_mbox
megaraid SCSI megaraid_mbox
is in the upgrade list.
Is your card in the PCI listing for megaraid_mbox?
I think so. It's
01:02.0 Class 0104: 101e:1960 (rev 02)
Flags: bus master, medium devsel, latency 32, IRQ 185
Memory at fcd00000 (32-bit, prefetchable) [size=64K]
Expansion ROM at fce00000 [disabled] [size=64K]
Capabilities:  Power Management version 2
which should match
Hey, when did the kernel stop running the module upgrade program?
Chris, does running 'module_upgrade' by hand fix it?
Yep. I changed /etc/modprobe.conf back to the old entry
alias scsi_hostadapter2 megaraid
ran module_upgrade, and it corrected it to
alias scsi_hostadapter2 megaraid_mbox
There's no module_upgrade anywhere in the RPM %post scripts for the
kernel that's on that box (kernel-smp-2.6.9-1.681_FC3)
ok, its a bit late, but this has been fixed for FC4.