error report in /var/adm/go is this normal?

[rd_blair]

I am running 4.5.1 pro. I have replaced the file /config/go with the one from the  distro because I wanted to rule out any of my addons. This error happened with 4.5 pro also.

 

This is the error I get in the file /var/adm/go

 

ERROR: Module md_mod does not exist in /proc/modules.

 

When I telnet and use mc to quikview /proc/modules this is what I get:

 

md_mod 42668 2 - Live 0xf82c6000

xor 13852 1 md_mod, Live 0xf82b0000

pata_jmicron 2684 0 - Live 0xf82a3000

jmicron 2012 0 - Live 0xf8295000

ahci 31924 3 - Live 0xf828b000

sky2 40360 0 - Live 0xf8264000

 

Is this a problem ? What do I do next? Do I need to list my hardware or a log file?

 

I am very new to unraid and slackware and for that matter using a forum so I hope this is the right place to ask this question.

 

[purko]

I am running 4.5.1 pro. I have replaced the file /config/go with the one from the  distro because I wanted to rule out any of my addons. This error happened with 4.5 pro also.

 

This is the error I get in the file /var/adm/go

 

ERROR: Module md_mod does not exist in /proc/modules.

 

When I telnet and use mc to quikview /proc/modules this is what I get:

 

md_mod 42668 2 - Live 0xf82c6000

xor 13852 1 md_mod, Live 0xf82b0000

pata_jmicron 2684 0 - Live 0xf82a3000

jmicron 2012 0 - Live 0xf8295000

ahci 31924 3 - Live 0xf828b000

sky2 40360 0 - Live 0xf8264000

 

Is this a problem ? What do I do next? Do I need to list my hardware or a log file?

 

I am very new to unraid and slackware and for that matter using a forum so I hope this is the right place to ask this question.

 

 

I am trying really hard to imagine a reason why you -- being very new to unraid and slackware and all -- would dig yourself into looking inside that particular file? 

 

And to answer your question, that file is just there, on any unRAID I've seen, and you should pay no attention to it.

 

Purko

 

[Joe L.]

All I can guess is that the first thing emhttp does when invoked is to issue a command to un-install md_mod as a module prior to installing it as a module.

This is probably to allow it to clean up after itself if it (emhttp) is killed and re-started.

 

I have the exact same message in my /var/log/go file.  As already said, you can ignore it.

[rd_blair]

Thanks for the quick reply!!!