[SOLVED] Strange errors in the logs one time

Hello,

I try my unraid server since last week with the basic option and i test it before buying the pro option. Since saturday, I make copy of my files from the old WHS server to the unraid server without any problem (2TB of data for the moment), but sunday on the afternoon, I had some errors. This is a part of the syslog, at the end of this message.

My server runs on a MSI Z87 motherboard with a pentium G2020 cpu and 4GB of DDR3.

3 drives are WD green 2TB WD20EZRX.

Flashdrive is a 4GB MediaRange

I don't know what is the reason of these errors, do you know if it is specific error (hardware ?). I see several times "cpuidle_xxx" so is it a problem with the CPU idle ? Something to deactivate in the BIOS or else ? But only one time error...

Thanks to help me to understand. I discovered unraid because I want to change WHS (runs well but need to much drive to have security and to have a system on a flashdrive is  priceless in case of hardware failure, death motherboard for example).

zigzig

(forgive me for my english, I'm better in french :-)    )

Mar 29 05:16:28 Tower kernel: NTFS driver 2.1.30 [Flags: R/W MODULE]. (System)
Mar 29 12:30:10 Tower kernel: md: sync done. time=26735sec (unRAID engine)
Mar 29 12:30:10 Tower kernel: md: recovery thread sync completion status: 0 (unRAID engine)
Mar 30 08:58:04 Tower unmenu[1164]: which: no bwm-ng in (/bin:/sbin:/usr/bin:/usr/sbin)
Mar 30 08:58:53 Tower last message repeated 3 times
Mar 30 12:47:26 Tower kernel: mce: [Hardware Error]: Machine check events logged (Errors)
Mar 30 13:48:20 Tower kernel: irq 16: nobody cared (try booting with the "irqpoll" option) (Errors)
Mar 30 13:48:20 Tower kernel: Pid: 0, comm: swapper/0 Tainted: G           O 3.9.11p-unRAID #5 (Errors)
Mar 30 13:48:20 Tower kernel: Call Trace: (Errors)
Mar 30 13:48:20 Tower kernel:  [<c105f922>] __report_bad_irq+0x29/0xb4 (Errors)
Mar 30 13:48:20 Tower kernel:  [<c105fae4>] note_interrupt+0x137/0x1ac (Errors)
Mar 30 13:48:20 Tower kernel:  [<c135b37d>] ? cpuidle_wrap_enter+0x2f/0x82 (Errors)
Mar 30 13:48:20 Tower kernel:  [<c105e058>] handle_irq_event_percpu+0x109/0x11a (Errors)
Mar 30 13:48:20 Tower kernel:  [<c105ffa8>] ? handle_percpu_irq+0x3b/0x3b (Errors)
Mar 30 13:48:20 Tower kernel:  [<c105e08e>] handle_irq_event+0x25/0x3c (Errors)
Mar 30 13:48:20 Tower kernel:  [<c105ffa8>] ? handle_percpu_irq+0x3b/0x3b (Errors)
Mar 30 13:48:20 Tower kernel:  [<c1060015>] handle_fasteoi_irq+0x6d/0xab (Errors)
Mar 30 13:48:20 Tower kernel:  <IRQ>  [<c100362e>] ? do_IRQ+0x37/0x9b
Mar 30 13:48:20 Tower kernel:  [<c1401d2c>] ? common_interrupt+0x2c/0x31 (Errors)
Mar 30 13:48:20 Tower kernel:  [<c135b37d>] ? cpuidle_wrap_enter+0x2f/0x82 (Errors)
Mar 30 13:48:20 Tower kernel:  [<c135b3e2>] ? cpuidle_enter_tk+0x12/0x14 (Errors)
Mar 30 13:48:20 Tower kernel:  [<c135ae6d>] ? disable_cpuidle+0xf/0xf (Errors)
Mar 30 13:48:20 Tower kernel:  [<c135ae8b>] ? cpuidle_enter_state+0xc/0x38 (Errors)
Mar 30 13:48:20 Tower kernel:  [<c135b2a1>] ? cpuidle_idle_call+0x73/0x9b (Errors)
Mar 30 13:48:20 Tower kernel:  [<c1008802>] ? cpu_idle+0x46/0x6f (Errors)
Mar 30 13:48:20 Tower kernel:  [<c13f5038>] ? rest_init+0x58/0x5a (Errors)
Mar 30 13:48:20 Tower kernel:  [<c156fa0d>] ? start_kernel+0x2ad/0x2b3 (Errors)
Mar 30 13:48:20 Tower kernel:  [<c156f5db>] ? repair_env_string+0x53/0x53 (Errors)
Mar 30 13:48:20 Tower kernel:  [<c156f2a3>] ? i386_start_kernel+0x79/0x7d (Errors)
Mar 30 13:48:20 Tower kernel: handlers:
Mar 30 13:48:20 Tower kernel: [<c1321df0>] usb_hcd_irq (Drive related)
Mar 30 13:48:20 Tower kernel: Disabling IRQ #16
Mar 30 14:01:24 Tower in.telnetd[22890]: connect from 192.168.0.1 (192.168.0.1) (Routine)
Mar 30 14:01:25 Tower login[22891]: ROOT LOGIN  on '/dev/pts/0' from '192.168.0.1' (Logins)
Apr  1 11:05:35 Tower unmenu[1164]: which: no bwm-ng in (/bin:/sbin:/usr/bin:/usr/sbin)

Can you post a complete SYSLOG?

http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog

Yes I can ;-)

File is too big for this post, this is the link : syslog

Curious thing : this morning, i can't access server in telnet. Only change one thing, yesterday, I installed the bwm-ng package. I'll try to restart the server later.

EDIT : in windows 8, I can't log with "telnet IP" in command window (worked yesterday) but I can type telnet and after "open IP" works. It's windows, it's strange :-)

Oh I think I have found the origin of the error.

The problem seems to appear when I plug/unplug the DVI cable in the monitor. I have tested that 2 times and had instantly 2 times the error.

Lets say : Problem solved