defyance

got a proper crash this time, text still on console screen, if you still need captured diags, they are attached below, in the mean time i put the old cpu back in the machine for stability testing. Oct 5 02:30:02 Streamflix kernel: BUG: unable to handle kernel NULL pointer dereference at 00000000000000a2 Oct 5 02:30:02 Streamflix kernel: IP: [<ffffffff811766ad>] search_by_key+0x596/0xd34 Oct 5 02:30:02 Streamflix kernel: PGD 1bae3a067 PUD 15e251067 PMD 0 Oct 5 02:30:02 Streamflix kernel: Oops: 0002 [#1] PREEMPT SMP Oct 5 02:30:02 Streamflix kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod it87 hwmon_vid hid_logitech_hidpp hid_logitech_dj kvm r8169 k10temp mii ahci libahci i2c_piix4 pata_jmicron i2c_core pata_atiixp wmi acpi_cpufreq Oct 5 02:30:02 Streamflix kernel: CPU: 1 PID: 12023 Comm: Plex Media Scan Not tainted 4.4.23-unRAID #1 Oct 5 02:30:02 Streamflix kernel: Hardware name: Gigabyte Technology Co., Ltd. GA-MA78LM-S2H/GA-MA78LM-S2H, BIOS F11 05/20/2010 Oct 5 02:30:02 Streamflix kernel: task: ffff880226a24080 ti: ffff880209afc000 task.ti: ffff880209afc000 Oct 5 02:30:02 Streamflix kernel: RIP: 0010:[<ffffffff811766ad>] [<ffffffff811766ad>] search_by_key+0x596/0xd34 Oct 5 02:30:02 Streamflix kernel: RSP: 0018:ffff880209aff9d8 EFLAGS: 00010203 Oct 5 02:30:02 Streamflix kernel: RAX: 00000000000000a2 RBX: ffff8800aac69800 RCX: 0000000000000004 Oct 5 02:30:02 Streamflix kernel: RDX: 0000000000000016 RSI: ffff88003c5a8004 RDI: ffff880141cf0b60 Oct 5 02:30:02 Streamflix kernel: RBP: ffff880209affb00 R08: 0000000000001000 R09: 0000000000001000 Oct 5 02:30:02 Streamflix kernel: R10: 0000000000000003 R11: 0000000000001000 R12: 00000000ffffffff Oct 5 02:30:02 Streamflix kernel: R13: 0000000000001000 R14: ffff880209affb70 R15: ffff880209affb50 Oct 5 02:30:02 Streamflix kernel: FS: 00007f28afbff700(0000) GS:ffff88022fc40000(0000) knlGS:0000000000000000 Oct 5 02:30:02 Streamflix kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 5 02:30:02 Streamflix kernel: CR2: 00000000000000a2 CR3: 00000001b61e5000 CR4: 00000000000006e0 Oct 5 02:30:02 Streamflix kernel: Stack: Oct 5 02:30:02 Streamflix kernel: ffff880209b00000 0000000000000000 0000000000298808 ffff880100000010 Oct 5 02:30:02 Streamflix kernel: ffff880209affb78 ffff880209affbc8 0000000100000001 ffff880141cf0b60 Oct 5 02:30:02 Streamflix kernel: ffff880209affa28 ffffffff8112f2e7 ffff880209affa58 ffffffff811313c7 Oct 5 02:30:02 Streamflix kernel: Call Trace: Oct 5 02:30:02 Streamflix kernel: [<ffffffff8112f2e7>] ? unlock_buffer+0x12/0x14 Oct 5 02:30:02 Streamflix kernel: [<ffffffff811313c7>] ? ll_rw_block+0x55/0x7b Oct 5 02:30:02 Streamflix kernel: [<ffffffff811762d2>] ? search_by_key+0x1bb/0xd34 Oct 5 02:30:02 Streamflix kernel: [<ffffffff8110d93c>] ? inode_get_bytes+0x3b/0x45 Oct 5 02:30:02 Streamflix kernel: [<ffffffff81168250>] reiserfs_update_sd_size+0xa3/0x2c6 Oct 5 02:30:02 Streamflix kernel: [<ffffffff8106cb1d>] ? update_curr+0x7d/0xc6 Oct 5 02:30:02 Streamflix kernel: [<ffffffff8106d516>] ? dequeue_entity+0x69b/0x775 Oct 5 02:30:02 Streamflix kernel: [<ffffffff8110d93c>] ? inode_get_bytes+0x3b/0x45 Oct 5 02:30:02 Streamflix kernel: [<ffffffff8116ee2c>] reiserfs_dirty_inode+0x61/0x7a Oct 5 02:30:02 Streamflix kernel: [<ffffffff8116ee2c>] ? reiserfs_dirty_inode+0x61/0x7a Oct 5 02:30:02 Streamflix kernel: [<ffffffff81129e01>] __mark_inode_dirty+0x32/0x1e3 Oct 5 02:30:02 Streamflix kernel: [<ffffffff8116869e>] reiserfs_write_end+0x13a/0x220 Oct 5 02:30:02 Streamflix kernel: [<ffffffff810b8fa5>] generic_perform_write+0x10f/0x17e Oct 5 02:30:02 Streamflix kernel: [<ffffffff810ba2e3>] __generic_file_write_iter+0xc9/0x16f Oct 5 02:30:02 Streamflix kernel: [<ffffffff810ba499>] generic_file_write_iter+0x110/0x186 Oct 5 02:30:02 Streamflix kernel: [<ffffffff81109f34>] __vfs_write+0x90/0xb9 Oct 5 02:30:02 Streamflix kernel: [<ffffffff8110a4bf>] vfs_write+0xbc/0x160 Oct 5 02:30:02 Streamflix kernel: [<ffffffff8110ac0c>] SyS_write+0x49/0x84 Oct 5 02:30:02 Streamflix kernel: [<ffffffff8162132e>] entry_SYSCALL_64_fastpath+0x12/0x6d Oct 5 02:30:02 Streamflix kernel: Code: e8 49 f7 f0 49 39 c2 76 1a 49 89 f8 48 c7 c1 60 b6 77 81 48 c7 c2 18 b8 63 81 48 c7 c6 78 b6 77 81 eb 3f 48 ff c1 45 89 d8 48 6b <d1> 18 6b c9 18 0f b7 44 16 fc 41 29 c0 0f b7 46 04 44 01 c1 45 Oct 5 02:30:02 Streamflix kernel: RIP [<ffffffff811766ad>] search_by_key+0x596/0xd34 Oct 5 02:30:02 Streamflix kernel: RSP <ffff880209aff9d8> Oct 5 02:30:02 Streamflix kernel: CR2: 00000000000000a2 Oct 5 02:30:02 Streamflix kernel: ---[ end trace 6d429c39f119a00b ]--- streamflix-diagnostics-20161005-0213.zip

an ebay jobby, so i assume so

how about your console login screen, would it black out or just freeze text? I believe it would just freeze text.. but I am using the onboard video I still had all the old parts that have worked fine for years, so I just started swapping stuff around till it could only be the cpu.. New RAM + CPU = fail, Old RAM + CPU = fail, new RAM + old CPU = ok. Ordered a different CPU and it worked fine as well.. I'm not saying you have this issue, just something that happened to me.. thanks for your input, i think that might be the case here, just waiting for my logs to be reviewed and to do a half day memtest

how about your console login screen, would it black out or just freeze text?

i think you may have interpreted the post incorrectly, there are two slots, i have dual sticks of 4GB memory for a total of 8GB

another side note.. im just typing as i think.. but since i lose video on the console display, could the issue be video driver related? i ask because reading the forums, usually when unraid crashes theres still video on the console, wether it be kernal panic error codes or a lock up of text on the screen. now i am running from the integrated graphics, im just putting things out there for now

i just edited my post above, as for running memtext extended, i was waiting for my server to crash so i can post the logs and have them reviewed first, if theres nothing in the logs, next step was a half day run on memtext with 4 cores active, and i have dual 4gb ddr2 sticks kingston branded

it used to run a beefy video card back in my pc gaming days without issues. im doubting the psu is the issue as i ran the calc and even at low end running at 90% usage on the phenom id only need a 400 watt one, this one can peak 600w and has 80 cert, and APF , wasnt low end when bought lol. dont get me wrong im not trying to undermine you, i will take all the help/advice i can get right now, i just dont suspect the ram or PSU is the issue. if anything i wouls suspect the issue is with the CPU, as i did buy it from ebay. my setup ran flawlessly before upgrading it. im aware of the wattage difference between cpu's but 500watts for a micro atx board and 4 harddrives is totally underpulling on the psu imho

just adding to the thread that im currently updating to the unraid release released today. awaiting review of diags just some thoughts, could there be bios settings that had no issues with the x2 that the x4 does not like? i reset to optimized defaults but that didn't seem to matter.

http://outervision.com/b/TY9ePg

heres the PSU http://www.thermaltake.com/products-model.aspx?id=c_00001655 will run memtest next after troubleshooting mode diags get reviewed

attached is the diags and syslog generated by the fix common problems plugin in troubleshooting mode. crash leads to everything unresponsive, and console login screen on server is blank streamflix-diagnostics-20161003-2058.zip

yeah i hear you on the date code, but yes, i have checked the official datasheets, i will link you the board im using and everything checks out hardware compatibility wise, the power supply is not a cheapo-came-with-case psu, however im eating supper and not about to run down 2 flights of stairs to check the brand name, and yes, its a known brand, just cant remember which. http://www.gigabyte.com/products/product-page.aspx?pid=3193#ov

thanks for your input, my board supports the new processor and is a am2+/am3 motherboard, the date code on the 9950 is actually older than the x2 250 edit: i forgot to add, the heatsnk im using keeps the phenom at around 50 C under laod, my research shows the cpu is capable of hitting 60, so i think im ok on the hs/fan.

do i boot into safe mode for that? a little direction would be appreciated Since Fix Common Problems is a plugin, and SAFE mode will not load any plugins, then NO to booting in SAFE mode. yeah i figured out it was a plugin, i never heard of it until now, installed it and ran a scan, deleted some depreciated scripts, and activated troubleshooting mode. will keep you posted.