unRaid crashes (sort of)

I'm new to unRaid and have just built a new box - specs below.

 

I have a problem with unRaid becoming unreachable from my browser with //tower after certain operations.  Specifically, parity check and moving files from cache to the array.  The move is achieved with the auto-script.

 

In both cases after the operation finishes I can no longer get to the web gui //tower although unmenu still works.  In this state i can not do a tidy power down and therefore have to reboot the machine via the power switch which means a new parity check and a new crash on completion.  After the error I can still access the  shares from my windows machine.

 

Syslog shows an error occurring as follows . . .

 

Oct 20 05:31:47 Tower kernel: mdcmd (2314): check CORRECT

Oct 20 05:31:47 Tower kernel: md: recovery thread woken up ...

Oct 20 05:31:47 Tower kernel: md: recovery thread checking parity...

Oct 20 05:31:47 Tower kernel: md: using 2304k window, over a total of 1953514552 blocks.

Oct 20 10:15:12 Tower emhttp: shcmd (51): /usr/sbin/hdparm -y /dev/sdb >/dev/null

Oct 20 12:37:53 Tower kernel: md: sync done. time=25565sec rate=76413K/sec

Oct 20 12:37:53 Tower kernel: md: recovery thread sync completion status: 0

Oct 20 12:53:01 Tower kernel: mdcmd (4976): spindown 0

Oct 20 12:53:01 Tower kernel: mdcmd (4977): spindown 1

Oct 20 12:53:02 Tower kernel: mdcmd (4979): spindown 2

Oct 20 12:53:02 Tower kernel: BUG: unable to handle kernel paging request at f8579000

Oct 20 12:53:02 Tower kernel: IP: [<f856f8e4>] md_cmd_proc_read+0x41/0x54 [md_mod]

Oct 20 12:53:02 Tower kernel: *pdpt = 0000000001447001 *pde = 000000003753f067 *pte = 0000000000000000

Oct 20 12:53:02 Tower kernel: Oops: 0000 [#1] SMP

Oct 20 12:53:02 Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.2/host10/target10:0:0/10:0:0:0/block/sdd/stat

Oct 20 12:53:02 Tower kernel: Modules linked in: md_mod xor i2c_i801 i2c_core ahci e1000e sata_mv

Oct 20 12:53:02 Tower kernel:

Oct 20 12:53:02 Tower kernel: Pid: 1647, comm: emhttp Not tainted (2.6.32.9-unRAID #5) empty

Oct 20 12:53:02 Tower kernel: EIP: 0060:[<f856f8e4>] EFLAGS: 00210202 CPU: 1

Oct 20 12:53:02 Tower kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod]

Oct 20 12:53:02 Tower kernel: EAX: f7539f38 EBX: fffff81c ECX: 3fffef72 EDX: fffff81c

Oct 20 12:53:02 Tower kernel: ESI: f8579000 EDI: f4362a54 EBP: f7539f04 ESP: f7539ef4

Oct 20 12:53:02 Tower kernel:  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068

Oct 20 12:53:02 Tower kernel: Process emhttp (pid: 1647, ti=f7538000 task=f772f390 task.ti=f7538000)

Oct 20 12:53:02 Tower kernel: Stack:

Oct 20 12:53:02 Tower kernel:  f7539f38 f856f8a3 00000000 f435f000 f7539f4c c109d5f5 00000400 f7539f3c

Oct 20 12:53:02 Tower kernel: <0> 00000000 00000400 00000000 00000400 b776c000 f6d5fde0 00000000 f6d5fde0

Oct 20 12:53:02 Tower kernel: <0> 00000400 f435f000 00000001 f6d5fde0 c109d4ea fffffffb f7539f70 c1099f72

Oct 20 12:53:02 Tower kernel: Call Trace:

Oct 20 12:53:02 Tower kernel:  [<f856f8a3>] ? md_cmd_proc_read+0x0/0x54 [md_mod]

Oct 20 12:53:02 Tower kernel:  [<c109d5f5>] ? proc_file_read+0x10b/0x22d

Oct 20 12:53:02 Tower kernel:  [<c109d4ea>] ? proc_file_read+0x0/0x22d

Oct 20 12:53:02 Tower kernel:  [<c1099f72>] ? proc_reg_read+0x56/0x6a

Oct 20 12:53:02 Tower kernel:  [<c1099f1c>] ? proc_reg_read+0x0/0x6a

Oct 20 12:53:02 Tower kernel:  [<c106cbd8>] ? vfs_read+0x8a/0x114

Oct 20 12:53:02 Tower kernel:  [<c106cf6f>] ? sys_read+0x3b/0x60

Oct 20 12:53:02 Tower kernel:  [<c1002935>] ? syscall_call+0x7/0xb

Oct 20 12:53:02 Tower kernel: Code: 55 f0 e8 6a 72 bc c8 8d 50 01 29 f2 39 d3 7c 0b 8b 45 0c 89 d3 c7 00 01 00 00 00 8b 45 f0 89 d9 81 c6 ac 4d 57 f8 c1 e9 02 89 38 <f3> a5 89 d9 83 e1 03 74 02 f3 a4 5a 89 d8 5b 5e 5f 5d c3 55 89

Oct 20 12:53:02 Tower kernel: EIP: [<f856f8e4>] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:f7539ef4

Oct 20 12:53:02 Tower kernel: CR2: 00000000f8579000

Oct 20 12:53:02 Tower kernel: ---[ end trace fb0be77f6cc34ac0 ]---

 

Anyone know what this all means?  thanks for any help.  Full syslog is attached.

syslog-2010-10-20.txt