Hello,

 

I've just updates my Slackware 13.0 / unRAID 4.5 installation to Slackware 13.1 / unRAID 4.5.6 and now have some problems with modprobe on 13.1.

Unloading of modules does not work with using modprobe -rw which should be fixed using 5.0-beta2. By now I don't want to use 5.0-beta2 so I'm searching for a workaround for Version 4.5.6

When I try to use modprobe shipped with unRAID 4.5.6 unraid will unload the mod_md module but other modules like my eth0 driver will not load.

 

Newer versions of the module-init-tools from version 3.10 onward no longer provide for the modprobe '-w' or '--wait' options, but still offer it on rmmod. This includes Slackware 13.1 and 13.2 (Current). You can not replace just the modprobe executable with the one from unRAID.

 

The easiest way to work-around the issue is to edit emHttp with a binary editor, changing "modprobe -rw md-mod 2>&1 | logger" string to "rmmod    -w md-mod 2>&1 | logger" -- this replaces the 8 characters of modprobe with "rmmod    " (rmmod AND 4 SPACES).

 

Limetech was willing to adjust this for unRAID 5.0 beta 2.

Works great, thank you!

 

I've changed modprobe -rw to rmmod -w

Just to clarify, BRiT's instructions are extremely helpful, but ever so slightly incorrect/unclear.

 

You should replace "modprobe -rw" with "rmmod  -w " (that's "rmmod<space><space><space><space>-w<space>", such that there are now two spaces between "-w" and "md-mod" and four spaces total between "rmmod" and "-w"). 

 

Editing the binary in 'vim' worked fine for me.

 

Just for reference, this post consolidates all the additional steps compared to the wiki that I had to take when installing unRAID 4.6 onto a full Slackware 13.1 distribution.

Woops, must not have had my cola for the day. I've since corrected the slight issue in my previous post.