I have a problem, and I dont know what makes the server hang.

I got this syslog BEFORE it hanged.

 

The computer locks up completely.

 

It could be a failing drive, but which one?

 

If someone could check the syslog and see if they can figure something out.

 

Thanks in advance.

syslog-2010-11-02.zip

I am getting the same thing... nothing has changed in months yet I have had 2 total lock up in the same day!  i cant even telnet into the box?

A failing drive generally shouldn't cause the web server to hang. Have you guys run memtest?

I ran one a while ago.. but I will run one overnight.

skyfox, you seem to have RAM issues. I see a series of memory related error codes at the end of your syslog:

Nov  2 16:56:21 skyfoxserver kernel: BUG: unable to handle kernel paging request at 942abe7c

Nov  2 16:56:21 skyfoxserver kernel: IP: [<c106f316>] vfs_getattr+0x15/0x34

Nov  2 16:56:21 skyfoxserver kernel: *pdpt = 0000000035523001 *pde = 0000000000000000

Nov  2 16:56:21 skyfoxserver kernel: Oops: 0000 [#12] SMP

Nov  2 16:56:21 skyfoxserver kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:09.0/host5/target5:0:0/5:0:0:0/block/sdf/stat

Nov  2 16:56:21 skyfoxserver kernel: Modules linked in: md_mod xor ide_gd_mod via82cxxx 8139too e1000 sata_sil sata_promise

Nov  2 16:56:21 skyfoxserver kernel:

Nov  2 16:56:21 skyfoxserver kernel: Pid: 5307, comm: ls Tainted: G      D W  (2.6.32.9-unRAID #5)  

Nov  2 16:56:21 skyfoxserver kernel: EIP: 0060:[<c106f316>] EFLAGS: 00010246 CPU: 0

Nov  2 16:56:21 skyfoxserver kernel: EIP is at vfs_getattr+0x15/0x34

Nov  2 16:56:21 skyfoxserver kernel: EAX: 942abe3c EBX: 00000000 ECX: c456aab0 EDX: f54e3f5c

Nov  2 16:56:21 skyfoxserver kernel: ESI: f71f1cc0 EDI: c4477300 EBP: f54e3f2c ESP: f54e3f20

Nov  2 16:56:21 skyfoxserver kernel:  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068

Nov  2 16:56:21 skyfoxserver kernel: Process ls (pid: 5307, ti=f54e2000 task=f74f9130 task.ti=f54e2000)

Nov  2 16:56:21 skyfoxserver kernel: Stack:

Nov  2 16:56:21 skyfoxserver kernel:  00000000 f54e3f5c f54e3f34 f54e3f48 c106f376 c4477300 f71f1cc0 f54e3f5c

Nov  2 16:56:21 skyfoxserver kernel: <0> 0805d518 0805d510 f54e3f54 c106f3cd 00000100 f54e3fac c106f3e3 f54e3f6c

Nov  2 16:56:21 skyfoxserver kernel: <0> c107dcc3 f54e3f80 c457a218 f54e3f78 c1072c5a 0000000a f54e3f94 c106f11c

Nov  2 16:56:21 skyfoxserver kernel: Call Trace:

Nov  2 16:56:21 skyfoxserver kernel:  [<c106f376>] ? vfs_fstatat+0x41/0x54

Nov  2 16:56:21 skyfoxserver kernel:  [<c106f3cd>] ? vfs_lstat+0x16/0x18

Nov  2 16:56:21 skyfoxserver kernel:  [<c106f3e3>] ? sys_lstat64+0x14/0x28

Nov  2 16:56:21 skyfoxserver kernel:  [<c107dcc3>] ? mntput_no_expire+0x16/0x74

Nov  2 16:56:21 skyfoxserver kernel:  [<c1072c5a>] ? path_put+0x20/0x23

Nov  2 16:56:21 skyfoxserver kernel:  [<c106f11c>] ? sys_readlinkat+0x67/0x71

Nov  2 16:56:21 skyfoxserver kernel:  [<c106f139>] ? sys_readlink+0x13/0x15

Nov  2 16:56:21 skyfoxserver kernel:  [<c1002935>] ? syscall_call+0x7/0xb

Nov  2 16:56:21 skyfoxserver kernel: Code: 43 44 b8 01 00 00 00 89 53 48 8b 49 6c d3 e0 89 43 40 5b 5e 5d c3 55 89 e5 57 89 c7 56 89 d6 89 ca 8b 4e 10 53 8b 81 9c 00 00 00 <8b> 58 40 85 db 74 0a 89 d1 89 f8 89 f2 ff d3 eb 09 89 c8 e8 31

Nov  2 16:56:21 skyfoxserver kernel: EIP: [<c106f316>] vfs_getattr+0x15/0x34 SS:ESP 0068:f54e3f20

Nov  2 16:56:21 skyfoxserver kernel: CR2: 00000000942abe7c

Nov  2 16:56:21 skyfoxserver kernel: ---[ end trace ed8d4b1d5d409a4c ]---

 

I would suggest you go ahead and run memtest on your system as is. If you have multiple sticks of RAM, you can then run them one at a time to see which is faulty.

Hmm. memory problems.... could be, but I have never been able to run a memtest on that computer, whatever the RAM I use, memory test hangs all the time as soon I start it. And I have tried many ram sticks.

 

But unraid has been almost completely stable until recently when it have hunged many times a day.

 

Since you are telling the error code are memoy related then it apparently has to be the memory anyway.

 

Thx, now I atleast have something to start with, check other ram (again)

Hmm, that doesn't seem like a good sign. If you can't run memtest, and you've tried multiple sticks of RAM, then you might have a bad memory controller on the motherboard.