Went to access my shares when suddenly I was not able to access the one folder.  I quickly logged in to the web console while I still could and I was greeted with a Kernel Error.

 

I ran error free for a month and a half, so I am not sure what suddenly went wrong causing this failure.  Attached is the copied syslog.

 

Thanks for the help.

 

syslog.txt

Went to access my shares when suddenly I was not able to access the one folder.  I quickly logged in to the web console while I still could and I was greeted with a Kernel Error.

 

I ran error free for a month and a half, so I am not sure what suddenly went wrong causing this failure.  Attached is the copied syslog.

 

Thanks for the help.

 

 

 

 

Looks like you had couple power failure but UPS pick it up and eventually had kernel panic. run memtest first and if result is positive, welcome to "the Oops club".  

Refer to following link for more information.

 

http://lime-technology.com/forum/index.php?topic=7877.msg76158#msg76158

 

---------------------------------- from your syslog -------------------------------------------------------------

Sep 16 16:02:45 Tower kernel: BUG: unable to handle kernel paging request at f82c3000

Sep 16 16:02:45 Tower kernel: IP: [] md_cmd_proc_read+0x41/0x54 [md_mod]

Sep 16 16:02:45 Tower kernel: *pdpt = 0000000001447001 *pde = 0000000037411067 *pte = 0000000000000000

Sep 16 16:02:45 Tower kernel: Oops: 0000 [#1] SMP

Sep 16 16:02:45 Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:11.0/host6/target6:0:0/6:0:0:0/block/sdf/stat

Sep 16 16:02:45 Tower kernel: Modules linked in: md_mod xor atiixp ahci r8169

Sep 16 16:02:45 Tower kernel:

Sep 16 16:02:45 Tower kernel: Pid: 1565, comm: emhttp Not tainted (2.6.32.9-unRAID #2) GA-MA74GM-S2

Sep 16 16:02:45 Tower kernel: EIP: 0060:[] EFLAGS: 00210212 CPU: 0

Sep 16 16:02:45 Tower kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod]

Sep 16 16:02:45 Tower kernel: EAX: f6fbdf38 EBX: fffff859 ECX: 3ffff035 EDX: fffff859

Sep 16 16:02:45 Tower kernel: ESI: f82c2fff EDI: c6a30784 EBP: f6fbdf04 ESP: f6fbdef4

Sep 16 16:02:45 Tower kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068

Sep 16 16:02:45 Tower kernel: Process emhttp (pid: 1565, ti=f6fbc000 task=f75b3a70 task.ti=f6fbc000)

Sep 16 16:02:45 Tower kernel: Stack:

Sep 16 16:02:45 Tower kernel: f6fbdf38 f82b9883 00000000 c6a2d000 f6fbdf4c c109d5f5 00000400 f6fbdf3c

Sep 16 16:02:45 Tower kernel: <0> 00000000 00000400 00000000 00000400 b7868000 f76f7600 00000000 f76f7600

Sep 16 16:02:45 Tower kernel: <0> 00000400 c6a2d000 00000001 f76f7600 c109d4ea fffffffb f6fbdf70 c1099f72

Sep 16 16:02:45 Tower kernel: Call Trace:

Sep 16 16:02:45 Tower kernel: [] ? md_cmd_proc_read+0x0/0x54 [md_mod]

Sep 16 16:02:45 Tower kernel: [] ? proc_file_read+0x10b/0x22d

Sep 16 16:02:45 Tower kernel: [] ? proc_file_read+0x0/0x22d

Sep 16 16:02:45 Tower kernel: [] ? proc_reg_read+0x56/0x6a

Sep 16 16:02:45 Tower kernel: [] ? proc_reg_read+0x0/0x6a

Sep 16 16:02:45 Tower kernel: [] ? vfs_read+0x8a/0x114

Sep 16 16:02:45 Tower kernel: [] ? sys_read+0x3b/0x60

Sep 16 16:02:45 Tower kernel: [] ? syscall_call+0x7/0xb

Sep 16 16:02:45 Tower kernel: Code: 55 f0 e8 8a d2 e7 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 a0 ed 2b f8 c1 e9 02 89 38 a5 89 d9 83 e1 03 74 02 f3 a4 5a 89 d8 5b 5e 5f 5d c3 55 89

Sep 16 16:02:45 Tower kernel: EIP: [] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:f6fbdef4

Sep 16 16:02:45 Tower kernel: CR2: 00000000f82c3000

Sep 16 16:02:45 Tower kernel: ---[ end trace 1b3b254d00891f57 ]---

 

Well, now that is funny.

 

I guess I will accept the OOPs error.  Not really certain if this is real common or not.  While I hate the fact that it is really not explained, I work with computers all day, so sometimes I understand that that feel like messing up.  Also, because this error appears different than my previous that I had with the old PSU, I will brush it off since things ran smooth for 1.5 months.  Now I just hope they dont rear their ugly head again for a while.  I hate having to do a hard reset.  I get nervous for my disks every time...

Well, now that is funny.

 

I guess I will accept the OOPs error.  Not really certain if this is real common or not.  While I hate the fact that it is really not explained, I work with computers all day, so sometimes I understand that that feel like messing up.  Also, because this error appears different than my previous that I had with the old PSU, I will brush it off since things ran smooth for 1.5 months.  Now I just hope they dont rear their ugly head again for a while.  I hate having to do a hard reset.  I get nervous for my disks every time...

 

The good news : It doesn't happen often.

The bad news : In my opinion, this is not easy to fix.

The solution : If you haven't drop limetech an email to notify them about this problem, please do so and point them to this thread.

                    such that it might push up the severity of this bug in to do list.

 

Is this a bug in the code one their end or is this something that only crops up in certain builds and configurations such as mine?  Good to know it isnt common and also that I have hopefully solved my PSU woes I had been having before.  The symptoms were the exact same so i was worried.