Just noticed the following:

all the drives show green balls, no errors

 

Should I shutdown/reboot?

 

Any advice?

 

Dec 22 14:25:33 Tower kernel: ------------[ cut here ]------------
Dec 22 14:25:33 Tower kernel: kernel BUG at kernel/cred.c:168!
Dec 22 14:25:33 Tower kernel: invalid opcode: 0000 [#1] SMP
Dec 22 14:25:33 Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:11.0/host6/target6:0:0/6:0:0:0/block/sde/stat
Dec 22 14:25:33 Tower kernel: Modules linked in: md_mod xor atiixp ahci r8169
Dec 22 14:25:33 Tower kernel:
Dec 22 14:25:33 Tower kernel: Pid: 19836, comm: smbd Not tainted (2.6.32.9-unRAID #5) A760G M2+
Dec 22 14:25:33 Tower kernel: EIP: 0060:[] EFLAGS: 00210202 CPU: 0
Dec 22 14:25:33 Tower kernel: EIP is at __put_cred+0xd/0x3e
Dec 22 14:25:33 Tower kernel: EAX: 00000001 EBX: dade9180 ECX: 00000003 EDX: dade9180
Dec 22 14:25:33 Tower kernel: ESI: dade9200 EDI: f4cc0dc0 EBP: dad33f6c ESP: dad33f6c
Dec 22 14:25:33 Tower kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Dec 22 14:25:33 Tower kernel: Process smbd (pid: 19836, ti=dad32000 task=f4cc0dc0 task.ti=dad32000)
Dec 22 14:25:33 Tower kernel: Stack:
Dec 22 14:25:33 Tower kernel: dad33f80 c103760d dade9200 00000000 c459d540 dad33f94 c1037e4d c459d540
Dec 22 14:25:33 Tower kernel: <0> 00000000 00000010 dad33fac c1038084 00000001 00000010 00000000 00000010
Dec 22 14:25:33 Tower kernel: <0> dad32000 c1002935 00000010 b78e4920 b6f6bff4 00000000 00000010 bfc44938
Dec 22 14:25:33 Tower kernel: Call Trace:
Dec 22 14:25:33 Tower kernel: [] ? commit_creds+0xcb/0xd2
Dec 22 14:25:33 Tower kernel: [] ? set_current_groups+0x35/0x3e
Dec 22 14:25:33 Tower kernel: [] ? sys_setgroups+0xbe/0xd6
Dec 22 14:25:33 Tower kernel: [] ? syscall_call+0x7/0xb
Dec 22 14:25:33 Tower kernel: Code: 9d 5b 5d c3 55 31 c0 89 e5 5d c3 55 8b 4a 2c 89 e5 89 48 1c 8b 52 30 89 50 20 31 c0 5d c3 89 c2 55 8b 00 8b 02 89 e5 85 c0 74 04 <0f> 0b eb fe 64 a1 54 e4 43 c1 3b 90 d4 01 00 00 75 04 0f 0b eb
Dec 22 14:25:33 Tower kernel: EIP: [] __put_cred+0xd/0x3e SS:ESP 0068:dad33f6c
Dec 22 14:25:33 Tower kernel: ---[ end trace 2b88122cb76fbb39 ]---

If everything is still working I would not reboot just yet.

 

Capture a syslog and post a full list of your hardware.

 

If you know what you were doing when this happened that would be great also.

 

Also, what version of unRAID are you running?

unRAID 4.5.6

 

I think around that time I had unMenu running Disk Usage, also was moving some files between disks.

Also may have had some media files being moved to unRAID server and/or comskip (running on another machine) processing against some of the files on unRAID.

 

Haven't seen any other issues since.

syslog-20101223.zip

unRAID 4.5.6

 

I think around that time I had unMenu running Disk Usage, also was moving some files between disks.

Also may have had some media files being moved to unRAID server and/or comskip (running on another machine) processing against some of the files on unRAID.

 

Haven't seen any other issues since.

 

Update to 4.6.  There was a kernel fix and you may have run into it, though I don't think so from what I saw.  Either way update to the latest version and see if the problem happens again.

unRAID 4.5.6

 

I think around that time I had unMenu running Disk Usage, also was moving some files between disks.

Also may have had some media files being moved to unRAID server and/or comskip (running on another machine) processing against some of the files on unRAID.

 

Haven't seen any other issues since.

 

I do not want to scare you and I just glanced for an instant but you have one Samsung F4 disk (the one with the possible data corruption).

 

The bad thing is that F4 is your disk "sde" and the error (third line from the attached syslog in your first post) references the same "sde" disk.

 

Hopefully not an issue. Need to see about doing the firmware update but do have write cache turned off on it

 

root@Tower:/root -> hdparm -W /dev/sde

 

/dev/sde:

write-caching =  0 (off)