modprobe kernel module loading issue [SOLVED]

[anonybosh]

Hi-
So I recently decided to move my server onto a couple of larger drives (2x 500gb). Using software RAID1, opted for moving away from the 0.9x metadata to the v1.2, for which I opted to go for Grub2 and assemble the array in an initramfs.
Long story short, now that I have a bootable system, I can no longer seem to use modprobe to load kernel modules. (This issue did not exist prior to this larger drive migration).

Code: Select all

#modprobe -v loop
#lsmod
Module            Size    Used by
#modprobe --show-depends loop
insmod /lib/modules/3.5.4-hardened-r1/kernel/drivers/block/loop.ko
#insmod /lib/modules/3.5.4-hardened-r1/kernel/drivers/block/loop.ko
#lsmod
Module            Size    Used by
loop            15432      0

There are no errors reported {dmesg; /var/log/messages}. The init.d modules scripts states that it loads 5 modules, however nothing actually loads.
I've tried recompiling module-init-tools, make clean && make && make modules_install && update-modules on my kernel source. I've even actually now just finished up recompiling the entire system (using this script).
I seem to be able to load everything via insmod, and I have, but it is a damned pita.
Anyone have any ideas?

Thanks!

[cbx550f]

Just a thought, and likely not a good one, but is your /proc mounted correctly?

My output from "mount":

Code: Select all

proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)

[anonybosh]

Great thought! /proc ended up being double mounted:

Code: Select all

#mount|grep -i proc
proc on /proc type proc (rw)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)

And looking into that a bit further, found that in my initramfs init script, I wasn't unmounting {proc,sys,dev} prior to switch_root.

Now I'm back up and running! Thank you!

[cbx550f]

Good stuff - and thanks for adding the extra info - sounds like something I'm bound to do sooner or later too.