June 28, 201016 yr Hello! I have been running Unraid 4.4.2 for over a year, without a single hiccup on the box. My setup is as follows: Abit AN9 32X 2 2GB ECC Kingston Memory 6 1TB Seagate LP 5900 RPM HD's (using onboard Nvidia 590 chipset SATA controllers) Onboard Nvidia Gigabit NIC (it has 2 - I disabled one) Corsair 550 Watt Power Supply I recently upgraded to 4.5.3 and began experiencing random freezes/lock-ups (server just drops off the network) of the server when playing back movies from my Windows 7 HTPC (either Blu-Ray or standard DVD vob files). I could however copy (from Win7 x64) large files (Blu-Ray ISO's 35GB+, etc.) with no problems. I finally had some time to troubleshoot the problems and decided to upgrade to 4.5.4 to see if this would help, but unfortunately, this provided no resolution to the problems above. Using 4.5.4, whenever I attempt to copy a file over to the server (i.e. DVD vob file structure, blu-ray ISO), the server just drops off the network and I have to manually power the box off and back on again. Upon reboot, the server will start a parity check, run for hours, but will always come up clean. I have manually ran SMART checks on all 6 drives (includes parity drive), which come up clean (zero errors) as well. The server will run for maybe an hour or two, and lock-up again and I have to restart the reboot process all over again. I originally thought this could be a hardware issue, so I disabled the onboard NIC that I was using, and enabled the 2nd onboard nic and rebooted. I tried the copy process once again, same result. Below is the final part detailing what happens when I start the copy process. ------------------------ Jun 27 22:21:18 MEDIATOWER emhttp: shcmd (29): killall -HUP smbd Jun 27 22:21:18 MEDIATOWER emhttp: shcmd (30): /etc/rc.d/rc.nfsd restart | logger Jun 27 22:21:25 MEDIATOWER ntpd[1448]: synchronized to 207.171.7.152, stratum 2 Jun 27 22:24:04 MEDIATOWER kernel: kernel tried to execute NX-protected page - exploit attempt? (uid: 0) Jun 27 22:24:04 MEDIATOWER kernel: BUG: unable to handle kernel paging request at c709f3b8 Jun 27 22:24:04 MEDIATOWER kernel: IP: [<c709f3b8>] 0xc709f3b8 Jun 27 22:24:04 MEDIATOWER kernel: *pdpt = 0000000001447001 *pde = 80000000070001e3 Jun 27 22:24:04 MEDIATOWER kernel: Oops: 0011 [#1] SMP Jun 27 22:24:04 MEDIATOWER kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:0d.2/host8/target8:0:0/8:0:0:0/block/sdg/stat Jun 27 22:24:04 MEDIATOWER kernel: Modules linked in: md_mod xor forcedeth sata_nv sata_sil24 Jun 27 22:24:04 MEDIATOWER kernel: Jun 27 22:24:04 MEDIATOWER kernel: Pid: 1620, comm: shfs Not tainted (2.6.32.9-unRAID #2) Jun 27 22:24:04 MEDIATOWER kernel: EIP: 0060:[<c709f3b8>] EFLAGS: 00010002 CPU: 0 Jun 27 22:24:04 MEDIATOWER kernel: EIP is at 0xc709f3b8 Jun 27 22:24:04 MEDIATOWER kernel: EAX: c709f3b0 EBX: c709f3b0 ECX: 00000000 EDX: 00000003 Jun 27 22:24:04 MEDIATOWER kernel: ESI: c709f3ac EDI: 00000001 EBP: c2175d18 ESP: c2175cf8 Jun 27 22:24:04 MEDIATOWER kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Jun 27 22:24:04 MEDIATOWER kernel: Process shfs (pid: 1620, ti=c2174000 task=f75e8a50 task.ti=c2174000) Jun 27 22:24:04 MEDIATOWER kernel: Stack: Jun 27 22:24:05 MEDIATOWER kernel: c101bd06 c2175d44 c709f3ac 00000003 c709f3ac c709f3a8 00000001 00000286 Jun 27 22:24:05 MEDIATOWER kernel: <0> c2175d38 c101c3e2 00000000 c2175d44 00000003 c709f3a8 f732986c 00000000 Jun 27 22:24:05 MEDIATOWER kernel: <0> c2175d50 c10338fc c2175d44 c6efa900 00000000 c6efa900 c2175d5c c1048c43 Jun 27 22:24:05 MEDIATOWER kernel: Call Trace: Jun 27 22:24:05 MEDIATOWER kernel: [<c101bd06>] ? __wake_up_common+0x35/0x5b Jun 27 22:24:05 MEDIATOWER kernel: [<c101c3e2>] ? __wake_up+0x28/0x3b Jun 27 22:24:05 MEDIATOWER kernel: [<c10338fc>] ? __wake_up_bit+0x2c/0x32 Jun 27 22:24:05 MEDIATOWER kernel: [<c1048c43>] ? unlock_page+0x18/0x1b Jun 27 22:24:05 MEDIATOWER kernel: [<c10b02eb>] ? reiserfs_write_end+0x1c6/0x223 Jun 27 22:24:05 MEDIATOWER kernel: [<c101b028>] ? kmap_atomic+0x14/0x16 Jun 27 22:24:05 MEDIATOWER kernel: [<c104937d>] ? generic_file_buffered_write+0x10b/0x1de Jun 27 22:24:05 MEDIATOWER kernel: [<c1049983>] ? __generic_file_aio_write+0x3ca/0x404 Jun 27 22:24:05 MEDIATOWER kernel: [<c1049a11>] ? generic_file_aio_write+0x54/0x95 Jun 27 22:24:05 MEDIATOWER kernel: [<c106c46d>] ? do_sync_write+0xbb/0xf9 Jun 27 22:24:05 MEDIATOWER kernel: [<c106c566>] ? do_sync_read+0xbb/0xf9 Jun 27 22:24:05 MEDIATOWER kernel: [<c103391d>] ? autoremove_wake_function+0x0/0x30 Jun 27 22:24:05 MEDIATOWER kernel: [<c103391d>] ? autoremove_wake_function+0x0/0x30 Jun 27 22:24:05 MEDIATOWER kernel: [<c10b03c2>] ? reiserfs_file_write+0x6b/0x74 Jun 27 22:24:05 MEDIATOWER kernel: [<c10b0357>] ? reiserfs_file_write+0x0/0x74 Jun 27 22:24:05 MEDIATOWER kernel: [<c106cac4>] ? vfs_write+0x8c/0x116 Jun 27 22:24:05 MEDIATOWER kernel: [<c106d095>] ? sys_pwrite64+0x44/0x5d Jun 27 22:24:05 MEDIATOWER kernel: [<c1002935>] ? syscall_call+0x7/0xb Jun 27 22:24:05 MEDIATOWER kernel: Code: f3 09 c7 00 00 00 00 94 f3 09 c7 94 f3 09 c7 00 00 00 00 a0 f3 09 c7 a0 f3 09 c7 00 01 00 00 bc f3 09 c7 ac f3 09 c7 00 00 00 00 <b8> f3 09 c7 b8 f3 09 c7 00 00 00 00 c4 f3 09 c7 c4 f3 09 c7 00 Jun 27 22:24:05 MEDIATOWER kernel: EIP: [<c709f3b8>] 0xc709f3b8 SS:ESP 0068:c2175cf8 Jun 27 22:24:05 MEDIATOWER kernel: CR2: 00000000c709f3b8 Jun 27 22:24:05 MEDIATOWER kernel: ---[ end trace a96262d976ad6624 ]--- ------------------------------ I have attached a copy of the entire SYSLOG to this message for review. Does anyone have any ideas on what this Kernel Paging Request error could be? I was tempted to roll-back to 4.4.2, but realized I no longer have this version. Is there somewhere I can download this old-reliable version? Thanks again for any assistance... Pancho >>>>>> SOLVED>>>>>>> I ran through every disk test known to man suggested on these forums, numerous memory tests, rolling back to 4.4.2, etc, everything checked out fine. I was literally pulling my hair out and finally ran across this blog on ECC memory: http://mindofjim.blogspot.com/2010_01_01_archive.html I adjusted the ECC settings in the BIOS based on his recommendations: Memory Hole Remapping - Enabled DRAM ECC Enable - Enabled DRAM MCE ENABLE - Enabled CHIP-KILL Mode Enable - Enabled DRM ECC REDIRECTION - Enabled DRAM Scrub Rate - 10.2 L2 Cache Scrub Rate - Disabled L1 DCache Scrub Rate - Disabled Auto Optimize Bottom IO - Enabled After these adjustments, I booted back in 4.4.2 and had no issues. I ran this configuration as-is on 4.4.2 for about 3 days, worked perfectly. I upgraded to 4.5.6 and tested again for 3 more days. I have been running rock solid ever since (almost 30 days now)! Bottom line, this ended up being incorrect memory settings. Several months ago, I had a power drop in my house that reset the CMOS on my unraid server. From that time forward, I believe these issues began. I only used the ECC memory in this server because I had it sitting here in a box available. In either case, I appear to be up and running. Lesson learned. Pancho syslog.txt
Archived
This topic is now archived and is closed to further replies.