Yes, I am running a beta, and yes it is on my production system, and no I do not suggest this to "normal" unRAID users.  With that all being said I have attached a syslog from the last couple of days of that is showing some weird things.

 

System is:

Gigabyte EP43-UD3L motherboard (HPA off by default)

2GB of RAM (for now, have 8 more to add when I get a chance)

mixture of drives

some addons install but have mostly been turned off to figure out what is going on for now

 

 

The errors seem to be realted to sdi which is my cache drive.  There should not be anything wrong with that drive, it has been in use for a very long time and not shown any problems to this point. I have run memtest on the system for 24 hours without issue, I can copy to the drive without issue, but it seems mover is having issues moving the data off of the drive.

 

Take a look at the syslog and let me know what you all think.

syslog-2011-03-12.txt

This is the Kernel OOPS bug related to how unRAID would read commands. It was the big bug fixed in unRAID 4.6 and later. It was also fixed in later 5.0 beta series, perhaps even 5.0 beta 3.

 

Mar 11 12:25:54 Andromeda unmenu[3921]: /root/mdcmd: line 4: 18970 Killed                  cat /proc/mdcmd >/tmp/mdresp

Mar 11 12:25:54 Andromeda kernel: BUG: unable to handle kernel paging request at f82ee000

Mar 11 12:25:54 Andromeda kernel: IP: [<f82e48e4>] md_cmd_proc_read+0x41/0x54 [md_mod]

Mar 11 12:25:54 Andromeda kernel: *pdpt = 0000000001447001 *pde = 0000000037410067 *pte = 0000000000000000

Mar 11 12:25:54 Andromeda kernel: Oops: 0000 [#1] SMP

Mar 11 12:25:54 Andromeda kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.2/host9/target9:0:0/9:0:0:0/block/sdi/removable

Mar 11 12:25:54 Andromeda kernel: Modules linked in: md_mod xor i2c_i801 i2c_core ahci r8169 sata_sil24

Mar 11 12:25:54 Andromeda kernel:

Mar 11 12:25:54 Andromeda kernel: Pid: 18970, comm: cat Not tainted (2.6.32.9-unRAID #5) EP43-UD3L

Mar 11 12:25:54 Andromeda kernel: EIP: 0060:[<f82e48e4>] EFLAGS: 00010213 CPU: 3

Mar 11 12:25:54 Andromeda kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod]

Mar 11 12:25:54 Andromeda kernel: EAX: e6d19f38 EBX: fffffbbe ECX: 3ffff432 EDX: fffffbbe

Mar 11 12:25:54 Andromeda kernel: ESI: f82edffd EDI: e8d20af4 EBP: e6d19f04 ESP: e6d19ef4

Mar 11 12:25:54 Andromeda kernel:  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068

Mar 11 12:25:54 Andromeda kernel: Process cat (pid: 18970, ti=e6d18000 task=f75aacb0 task.ti=e6d18000)

Mar 11 12:25:54 Andromeda kernel: Stack:

Mar 11 12:25:54 Andromeda kernel:  e6d19f38 f82e48a3 00001000 e8d1e000 e6d19f4c c109d5f5 00000400 e6d19f3c

Mar 11 12:25:54 Andromeda kernel: <0> 00000000 00001000 00000000 00000400 0804ec00 f75cce40 00000c00 f75cce40

Mar 11 12:25:54 Andromeda kernel: <0> 00000400 e8d1e000 00000001 f75cce40 c109d4ea fffffffb e6d19f70 c1099f72

Mar 11 12:25:54 Andromeda kernel: Call Trace:

Mar 11 12:25:54 Andromeda kernel:  [<f82e48a3>] ? md_cmd_proc_read+0x0/0x54 [md_mod]

This is the Kernel OOPS bug related to how unRAID would read commands. It was the big bug fixed in unRAID 4.6 and later. It was also fixed in later 5.0 beta series, perhaps even 5.0 beta 3.

 

Mar 11 12:25:54 Andromeda unmenu[3921]: /root/mdcmd: line 4: 18970 Killed                  cat /proc/mdcmd >/tmp/mdresp

Mar 11 12:25:54 Andromeda kernel: BUG: unable to handle kernel paging request at f82ee000

Mar 11 12:25:54 Andromeda kernel: IP: [<f82e48e4>] md_cmd_proc_read+0x41/0x54 [md_mod]

Mar 11 12:25:54 Andromeda kernel: *pdpt = 0000000001447001 *pde = 0000000037410067 *pte = 0000000000000000

Mar 11 12:25:54 Andromeda kernel: Oops: 0000 [#1] SMP

Mar 11 12:25:54 Andromeda kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.2/host9/target9:0:0/9:0:0:0/block/sdi/removable

Mar 11 12:25:54 Andromeda kernel: Modules linked in: md_mod xor i2c_i801 i2c_core ahci r8169 sata_sil24

Mar 11 12:25:54 Andromeda kernel:

Mar 11 12:25:54 Andromeda kernel: Pid: 18970, comm: cat Not tainted (2.6.32.9-unRAID #5) EP43-UD3L

Mar 11 12:25:54 Andromeda kernel: EIP: 0060:[<f82e48e4>] EFLAGS: 00010213 CPU: 3

Mar 11 12:25:54 Andromeda kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod]

Mar 11 12:25:54 Andromeda kernel: EAX: e6d19f38 EBX: fffffbbe ECX: 3ffff432 EDX: fffffbbe

Mar 11 12:25:54 Andromeda kernel: ESI: f82edffd EDI: e8d20af4 EBP: e6d19f04 ESP: e6d19ef4

Mar 11 12:25:54 Andromeda kernel:  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068

Mar 11 12:25:54 Andromeda kernel: Process cat (pid: 18970, ti=e6d18000 task=f75aacb0 task.ti=e6d18000)

Mar 11 12:25:54 Andromeda kernel: Stack:

Mar 11 12:25:54 Andromeda kernel:  e6d19f38 f82e48a3 00001000 e8d1e000 e6d19f4c c109d5f5 00000400 e6d19f3c

Mar 11 12:25:54 Andromeda kernel: <0> 00000000 00001000 00000000 00000400 0804ec00 f75cce40 00000c00 f75cce40

Mar 11 12:25:54 Andromeda kernel: <0> 00000400 e8d1e000 00000001 f75cce40 c109d4ea fffffffb e6d19f70 c1099f72

Mar 11 12:25:54 Andromeda kernel: Call Trace:

Mar 11 12:25:54 Andromeda kernel:  [<f82e48a3>] ? md_cmd_proc_read+0x0/0x54 [md_mod]

 

 

I figured as much from my initial searching, and I think I know what might be causing it.  The odd thing is is just started happening, possibly because of the fact that I have been doing some "extras" on my production array lately.

 

I will modify what I think is causing the problem and see if everything calms down.

 

Thanks for the input BRiT