minor issuses unraid 4.7 whats this mean?

[Ryan00]

Hello everyone just got my unraid server up and running about 2 weeks ago everything looks really good i have all green balls , however when i look in the syslog  i see 3 minor issues , I have nothing in red so that is good. Is this something to worry about and does anyone know what this means?

 

syslog reports (unmenu)

 

 

Feb  6 23:32:50 Media kernel: ACPI Warning for \_SB_._OSC: Return type mismatch - found Integer, expected Buffer (20090903/nspredef-1006) (Minor Issues)

 

Feb  6 23:32:50 Media kernel: ACPI Warning: Incorrect checksum in table [OEMB] - A0, should be 9D (20090903/tbutils-314) (Minor Issues)

 

 

Feb  6 23:32:52 Media emhttp: shcmd (13): killall -HUP smbd (Minor Issues)

 

 

Thanks for the help Ryan...

 

[Ryan00]

Okay if I was to post my whole syslog would that help? Know one has any idea on this?

[Joe L.]

Okay if I was to post my whole syslog would that help? Know one has any idea on this?

The first two indicate your Motherboard BIOS is in need of an update.

 

The third indicated that SAMBA file sharing was stopped while you made a configuration change of some kind.

 

Google is your friend.  Every Linux server has a system log.  Every system log has tones of lines of messages, the "minor" vs. Major issues in unMENU was based on syslog produced about 4 or 5 years ago.  You can look at the patterns it is using to color code output in /boot/unmenu/syslog_match.conf

 

Even major errors may not be errors at all.  a line is colored "red' if it has the word "error" anywhere in it.  It might say

No Error Found

and still be marked in red.

 

The color coding is crude, not all inclusive, and is there only to help point out the non-obvious. 

 

Enjoy your server.

 

[mbryanr]

As noted, those are minor issues (ACPI <Advanced Configuration and Power Interface> -likely bios/memory mapping errors) I have the 2nd one in my Asus M4A785-M board.

 

https://access.redhat.com/kb/docs/DOC-65400.pdf

 

killall -HUP smbd is just a clean stop for Samba process after a change (not a Linux expert, just from a quick search)

Example:

Jan  1 04:06:00 Tower emhttp: shcmd (32): cp /etc/exports- /etc/exports

Jan  1 04:06:00 Tower emhttp: shcmd (33): echo \"/mnt/disk1\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=11' '*(rw)' >>/etc/exports

Jan  1 04:06:00 Tower emhttp: shcmd (34): echo \"/mnt/disk2\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=12' '*(rw)' >>/etc/exports

Jan  1 04:06:00 Tower emhttp: shcmd (35): echo \"/mnt/disk3\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=13' '*(rw)' >>/etc/exports

Jan  1 04:06:00 Tower emhttp: shcmd (36): echo \"/mnt/disk4\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=14' '*(rw)' >>/etc/exports

Jan  1 04:06:00 Tower emhttp: shcmd (37): echo \"/mnt/disk5\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=15' '*(rw)' >>/etc/exports

Jan  1 04:06:00 Tower emhttp: shcmd (38): echo \"/mnt/disk6\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=16' '*(rw)' >>/etc/exports

Jan  1 04:06:00 Tower emhttp: shcmd (39): echo \"/mnt/disk7\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=17' '*(rw)' >>/etc/exports

Jan  1 04:06:00 Tower emhttp: shcmd (40): mkdir /mnt/user

Jan  1 04:06:00 Tower emhttp: shcmd (41): /usr/local/sbin/shfs /mnt/user  -o noatime,big_writes,allow_other,default_permissions

Jan  1 04:06:01 Tower emhttp: shcmd (42): echo \"/mnt/user/Autumn\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=101' '*(rw)' >>/etc/exports

Jan  1 04:06:01 Tower emhttp: shcmd (43): echo \"/mnt/user/movies\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=100' '*(rw)' >>/etc/exports

Jan  1 04:06:01 Tower emhttp: shcmd (44): echo \"/mnt/user/music\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=102' '*(rw)' >>/etc/exports

Jan  1 04:06:01 Tower emhttp: shcmd (45): killall -HUP smbd

 

[Ryan00]

Thanks for the reply, I have a super micro x8sil-f board and i went to super micro's website to found the current bios update and my board already has it . Says the current bios is 1.1 and when i went into the bios on my system says im at V 1.1 so i'm good their. I think it was a addon or script i installed. Because i remember looking at the syslog when i first setup the server and didn't see the minor issuse then. However my server is running fine so i prob shouldnt worry about it to much .  I just don't want a crash any time soon so that's why i thought i would ask. I understand how the syslog works and what the colors mean. However when it shows numbers and letters it gets confusing to what its trying to say. 

 

 

Thanks for the help Ryan.