FoxxMD Posted November 23, 2018 Share Posted November 23, 2018 On 6.6.3 I did a normal reboot to do some cable cleanup under my desk, then: upgrade my letsencrypt container Saw a few crc count errors try to start an Ubuntu VM At which point my machine restarted and I've received panic traces everytime I've tried to start up since Original panic Panic in safe mode Different panic in safe mode Another, different panic in safe mode Anyone have any idea what is going on? Link to comment
John_M Posted November 23, 2018 Share Posted November 23, 2018 What happens if you select MemTest from the boot menu? Link to comment
FoxxMD Posted November 23, 2018 Author Share Posted November 23, 2018 Will try memtest in a second. I managed to actually boot normally somehow. Opened Logs and had it up when another panic occured, this time I have more info: Nov 23 18:51:28 foxxnas avahi-daemon[9469]: Joining mDNS multicast group on interface vethed9bfcf.IPv6 with address fe80::8404:77ff:fe97:5267. Nov 23 18:51:28 foxxnas avahi-daemon[9469]: New relevant interface vethed9bfcf.IPv6 for mDNS. Nov 23 18:51:28 foxxnas avahi-daemon[9469]: Registering new address record for fe80::8404:77ff:fe97:5267 on vethed9bfcf.*. Nov 23 18:51:29 foxxnas avahi-daemon[9469]: Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:eff:fead:bfb0. Nov 23 18:51:29 foxxnas avahi-daemon[9469]: New relevant interface docker0.IPv6 for mDNS. Nov 23 18:51:29 foxxnas avahi-daemon[9469]: Registering new address record for fe80::42:eff:fead:bfb0 on docker0.*. Nov 23 18:51:29 foxxnas kernel: eth0: renamed from vethf9174ef Nov 23 18:51:29 foxxnas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5a135dd: link becomes ready Nov 23 18:51:29 foxxnas kernel: docker0: port 2(veth5a135dd) entered blocking state Nov 23 18:51:29 foxxnas kernel: docker0: port 2(veth5a135dd) entered forwarding state Nov 23 18:51:30 foxxnas rc.docker: DDclient: started succesfully! Nov 23 18:51:30 foxxnas kernel: docker0: port 3(vethade5761) entered blocking state Nov 23 18:51:30 foxxnas kernel: docker0: port 3(vethade5761) entered disabled state Nov 23 18:51:30 foxxnas kernel: device vethade5761 entered promiscuous mode Nov 23 18:51:30 foxxnas kernel: IPv6: ADDRCONF(NETDEV_UP): vethade5761: link is not ready Nov 23 18:51:30 foxxnas kernel: docker0: port 3(vethade5761) entered blocking state Nov 23 18:51:30 foxxnas kernel: docker0: port 3(vethade5761) entered forwarding state Nov 23 18:51:30 foxxnas kernel: docker0: port 3(vethade5761) entered disabled state Nov 23 18:51:30 foxxnas avahi-daemon[9469]: Joining mDNS multicast group on interface veth5a135dd.IPv6 with address fe80::949b:86ff:fe6a:28ab. Nov 23 18:51:30 foxxnas avahi-daemon[9469]: New relevant interface veth5a135dd.IPv6 for mDNS. Nov 23 18:51:30 foxxnas avahi-daemon[9469]: Registering new address record for fe80::949b:86ff:fe6a:28ab on veth5a135dd.*. Nov 23 18:51:32 foxxnas kernel: eth0: renamed from veth2c14f1d Nov 23 18:51:32 foxxnas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethade5761: link becomes ready Nov 23 18:51:32 foxxnas kernel: docker0: port 3(vethade5761) entered blocking state Nov 23 18:51:32 foxxnas kernel: docker0: port 3(vethade5761) entered forwarding state Nov 23 18:51:33 foxxnas rc.docker: letsencrypt: started succesfully! Nov 23 18:51:34 foxxnas avahi-daemon[9469]: Joining mDNS multicast group on interface vethade5761.IPv6 with address fe80::d01d:35ff:fe35:e565. Nov 23 18:51:34 foxxnas avahi-daemon[9469]: New relevant interface vethade5761.IPv6 for mDNS. Nov 23 18:51:34 foxxnas avahi-daemon[9469]: Registering new address record for fe80::d01d:35ff:fe35:e565 on vethade5761.*. Nov 23 18:51:37 foxxnas kernel: md: recovery thread: P incorrect, sector=3400712 Nov 23 18:52:43 foxxnas kernel: plugin[17195]: segfault at 71697673d2e8 ip 000014697ee75304 sp 00007ffefabb8d20 error 6 in ld-2.28.so[14697ee69000+20000] Nov 23 18:52:43 foxxnas kernel: Code: 1f 80 00 00 00 00 48 8b 08 8b 50 08 4c 01 f9 48 83 fa 26 74 0a 48 83 fa 08 0f 85 9f 10 00 00 48 8b 50 10 48 83 c0 18 4c 01 fa <48> 89 11 48 39 c3 77 d4 49 8b 82 d0 01 00 00 48 85 c0 0f 85 82 fa Nov 23 18:54:05 foxxnas kernel: md: recovery thread: P incorrect, sector=45222712 Nov 23 18:54:08 foxxnas kernel: md: recovery thread: P incorrect, sector=45855952 Nov 23 18:54:08 foxxnas kernel: md: recovery thread: P incorrect, sector=45920416 Nov 23 18:54:23 foxxnas kernel: md: recovery thread: P incorrect, sector=50183320 Nov 23 18:54:56 foxxnas kernel: general protection fault: 0000 [#1] SMP NOPTI Nov 23 18:54:56 foxxnas kernel: CPU: 3 PID: 9268 Comm: mdrecoveryd Not tainted 4.18.15-unRAID #1 Nov 23 18:54:56 foxxnas kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./990FXA-UD3, BIOS F3 05/28/2015 Nov 23 18:54:56 foxxnas kernel: RIP: 0010:get_active_stripe+0x8e/0x374 [md_mod] Nov 23 18:54:56 foxxnas kernel: Code: 85 c0 75 02 0f 0b 83 3d 0d 6e 00 00 04 7e 0f 4c 89 e6 48 c7 c7 8d 71 0f a0 e8 e4 6c f9 e0 49 8b 07 4a 8b 1c 28 48 85 db 74 0b <4c> 3b 63 28 74 1f 48 8b 1b eb f0 83 3d de 6d 00 00 04 7e 25 4c 89 Nov 23 18:54:56 foxxnas kernel: RSP: 0018:ffffc90003373ca8 EFLAGS: 00010086 Nov 23 18:54:56 foxxnas kernel: RAX: ffff8805224eb000 RBX: ffff3704f75291a0 RCX: 0000000000000300 Nov 23 18:54:56 foxxnas kernel: RDX: 0000000000000001 RSI: 00000000038e8ac8 RDI: ffff880523685a68 Nov 23 18:54:56 foxxnas kernel: RBP: ffff880523685a68 R08: 00000000038e8ac8 R09: 00000000fffffffd Nov 23 18:54:56 foxxnas kernel: R10: 0000000000000000 R11: 0000000000001000 R12: 00000000038e8ac8 Nov 23 18:54:56 foxxnas kernel: R13: 0000000000000ac8 R14: ffffffff8106aff3 R15: ffff880523685800 Nov 23 18:54:56 foxxnas kernel: FS: 0000000000000000(0000) GS:ffff88053ecc0000(0000) knlGS:0000000000000000 Nov 23 18:54:56 foxxnas kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 23 18:54:56 foxxnas kernel: CR2: 0000148f0d5da000 CR3: 00000004ac15c000 CR4: 00000000000406e0 Nov 23 18:54:56 foxxnas kernel: Call Trace: Nov 23 18:54:56 foxxnas kernel: unraid_sync+0x16/0x98 [md_mod] Nov 23 18:54:56 foxxnas kernel: md_do_sync+0x11d/0x2f4 [md_mod] Nov 23 18:54:56 foxxnas kernel: ? wait_woken+0x68/0x68 Nov 23 18:54:56 foxxnas kernel: ? mod_timer+0x213/0x23a Nov 23 18:54:56 foxxnas kernel: ? md_open+0x2c/0x2c [md_mod] Nov 23 18:54:56 foxxnas kernel: md_do_recovery+0xa8/0x14a [md_mod] Nov 23 18:54:56 foxxnas kernel: md_thread+0xcc/0xf1 [md_mod] Nov 23 18:54:56 foxxnas kernel: ? wait_woken+0x68/0x68 Nov 23 18:54:56 foxxnas kernel: kthread+0x10b/0x113 Nov 23 18:54:56 foxxnas kernel: ? kthread_flush_work_fn+0x9/0x9 Nov 23 18:54:56 foxxnas kernel: ret_from_fork+0x22/0x40 Nov 23 18:54:56 foxxnas kernel: Modules linked in: veth macvlan xt_nat ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod it87 hwmon_vid bonding edac_mce_amd kvm_amd ccp kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc k10temp aesni_intel aes_x86_64 crypto_simd cryptd i2c_piix4 i2c_core ahci r8169 fam15h_power glue_helper libahci mii mxm_wmi wmi button pcc_cpufreq acpi_cpufreq Nov 23 18:54:56 foxxnas kernel: ---[ end trace c7dc0e1781baa0ad ]--- Nov 23 18:54:56 foxxnas kernel: RIP: 0010:get_active_stripe+0x8e/0x374 [md_mod] Nov 23 18:54:56 foxxnas kernel: Code: 85 c0 75 02 0f 0b 83 3d 0d 6e 00 00 04 7e 0f 4c 89 e6 48 c7 c7 8d 71 0f a0 e8 e4 6c f9 e0 49 8b 07 4a 8b 1c 28 48 85 db 74 0b <4c> 3b 63 28 74 1f 48 8b 1b eb f0 83 3d de 6d 00 00 04 7e 25 4c 89 Nov 23 18:54:56 foxxnas kernel: RSP: 0018:ffffc90003373ca8 EFLAGS: 00010086 Nov 23 18:54:56 foxxnas kernel: RAX: ffff8805224eb000 RBX: ffff3704f75291a0 RCX: 0000000000000300 Nov 23 18:54:56 foxxnas kernel: RDX: 0000000000000001 RSI: 00000000038e8ac8 RDI: ffff880523685a68 Nov 23 18:54:56 foxxnas kernel: RBP: ffff880523685a68 R08: 00000000038e8ac8 R09: 00000000fffffffd Nov 23 18:54:56 foxxnas kernel: R10: 0000000000000000 R11: 0000000000001000 R12: 00000000038e8ac8 Nov 23 18:54:56 foxxnas kernel: R13: 0000000000000ac8 R14: ffffffff8106aff3 R15: ffff880523685800 Nov 23 18:54:56 foxxnas kernel: FS: 0000000000000000(0000) GS:ffff88053ecc0000(0000) knlGS:0000000000000000 Nov 23 18:54:56 foxxnas kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 23 18:54:56 foxxnas kernel: CR2: 0000148f0d5da000 CR3: 00000004ac15c000 CR4: 00000000000406e0 Nov 23 18:54:56 foxxnas kernel: WARNING: CPU: 3 PID: 9268 at kernel/exit.c:771 do_exit+0x58/0x8a4 Nov 23 18:54:56 foxxnas kernel: Modules linked in: veth macvlan xt_nat ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod it87 hwmon_vid bonding edac_mce_amd kvm_amd ccp kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc k10temp aesni_intel aes_x86_64 crypto_simd cryptd i2c_piix4 i2c_core ahci r8169 fam15h_power glue_helper libahci mii mxm_wmi wmi button pcc_cpufreq acpi_cpufreq Nov 23 18:54:56 foxxnas kernel: CPU: 3 PID: 9268 Comm: mdrecoveryd Tainted: G D 4.18.15-unRAID #1 Nov 23 18:54:56 foxxnas kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./990FXA-UD3, BIOS F3 05/28/2015 Nov 23 18:54:56 foxxnas kernel: RIP: 0010:do_exit+0x58/0x8a4 Nov 23 18:54:56 foxxnas kernel: Code: 06 00 00 48 85 c0 74 24 48 8b 10 48 39 d0 75 1a 48 8b 48 10 48 8d 50 10 48 39 d1 75 0d 48 8b 50 20 48 83 c0 20 48 39 c2 74 02 <0f> 0b 65 8b 05 39 5d fc 7e 25 00 ff 1f 00 48 c7 c7 63 5c d3 81 89 Nov 23 18:54:56 foxxnas kernel: RSP: 0018:ffffc90003373ee8 EFLAGS: 00010006 Nov 23 18:54:56 foxxnas kernel: RAX: ffffc90003373d90 RBX: ffff880505235e80 RCX: 0000000000000007 Nov 23 18:54:56 foxxnas kernel: RDX: ffff8800ac711840 RSI: ffff88053ecd6470 RDI: 000000000000000b Nov 23 18:54:56 foxxnas kernel: RBP: 000000000000000b R08: 000000000000000f R09: ffff8800000bf000 Nov 23 18:54:56 foxxnas kernel: R10: 0000000000000410 R11: 0000000000014bf4 R12: 0000000000000000 Nov 23 18:54:56 foxxnas kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Nov 23 18:54:56 foxxnas kernel: FS: 0000000000000000(0000) GS:ffff88053ecc0000(0000) knlGS:0000000000000000 Nov 23 18:54:56 foxxnas kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 23 18:54:56 foxxnas kernel: CR2: 0000148f0d5da000 CR3: 00000004ac15c000 CR4: 00000000000406e0 Nov 23 18:54:56 foxxnas kernel: Call Trace: Nov 23 18:54:56 foxxnas kernel: ? kthread+0x10b/0x113 Nov 23 18:54:56 foxxnas kernel: rewind_stack_do_exit+0x17/0x20 Nov 23 18:54:56 foxxnas kernel: ---[ end trace c7dc0e1781baa0ae ]--- Nov 23 18:54:59 foxxnas kernel: BUG: unable to handle kernel paging request at ffffb3052379c1f8 Nov 23 18:54:59 foxxnas kernel: PGD 0 P4D 0 Nov 23 18:54:59 foxxnas kernel: Oops: 0000 [#2] SMP NOPTI Nov 23 18:54:59 foxxnas kernel: CPU: 6 PID: 1738 Comm: smbd Tainted: G D W 4.18.15-unRAID #1 Nov 23 18:54:59 foxxnas kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./990FXA-UD3, BIOS F3 05/28/2015 Nov 23 18:54:59 foxxnas kernel: RIP: 0010:anon_vma_interval_tree_insert+0x30/0x87 Nov 23 18:54:59 foxxnas kernel: Code: 49 89 f0 45 31 c9 48 8b 42 08 48 2b 02 4c 8b 92 98 00 00 00 ba 01 00 00 00 48 c1 e8 0c 49 8d 7c 02 ff 49 8b 00 48 85 c0 74 28 <48> 3b 78 18 76 04 48 89 78 18 4c 8b 40 e0 4d 3b 90 98 00 00 00 73 Nov 23 18:54:59 foxxnas kernel: RSP: 0018:ffffc900036d3d68 EFLAGS: 00010282 Nov 23 18:54:59 foxxnas kernel: RAX: ffffb3052379c1e0 RBX: 0000000000000000 RCX: ffff8804f5597340 Nov 23 18:54:59 foxxnas kernel: RDX: 0000000000000001 RSI: ffff88052255e930 RDI: 000000000000000a Nov 23 18:54:59 foxxnas kernel: RBP: ffff8804f5551d80 R08: ffff88052255e930 R09: 0000000000000000 Nov 23 18:54:59 foxxnas kernel: R10: 000000000000000a R11: ffff8804f5551c20 R12: ffff88052379c140 Nov 23 18:54:59 foxxnas kernel: R13: ffff880523f5e600 R14: ffff88052255e8f0 R15: ffff88052255e8f0 Nov 23 18:54:59 foxxnas kernel: FS: 00001506f0abb940(0000) GS:ffff88053ed80000(0000) knlGS:0000000000000000 Nov 23 18:54:59 foxxnas kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 23 18:54:59 foxxnas kernel: CR2: ffffb3052379c1f8 CR3: 00000005237a6000 CR4: 00000000000406e0 Nov 23 18:54:59 foxxnas kernel: Call Trace: Nov 23 18:54:59 foxxnas kernel: anon_vma_clone+0xfa/0x15c Nov 23 18:54:59 foxxnas kernel: anon_vma_fork+0x30/0x12b Nov 23 18:54:59 foxxnas kernel: copy_process.part.5+0xc60/0x1766 Nov 23 18:54:59 foxxnas kernel: _do_fork+0xc5/0x2ae Nov 23 18:54:59 foxxnas kernel: do_syscall_64+0x57/0xe6 Nov 23 18:54:59 foxxnas kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Nov 23 18:54:59 foxxnas kernel: RIP: 0033:0x1506ef743852 Nov 23 18:54:59 foxxnas kernel: Code: db 0f 85 21 01 00 00 64 4c 8b 0c 25 10 00 00 00 45 31 c0 4d 8d 91 d0 02 00 00 31 d2 31 f6 bf 11 00 20 01 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 ba 00 00 00 89 c5 85 c0 0f 85 c8 00 00 00 Nov 23 18:54:59 foxxnas kernel: RSP: 002b:00007ffed5324340 EFLAGS: 00000246 ORIG_RAX: 0000000000000038 Nov 23 18:54:59 foxxnas kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00001506ef743852 Nov 23 18:54:59 foxxnas kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011 Nov 23 18:54:59 foxxnas kernel: RBP: 0000000000000023 R08: 0000000000000000 R09: 00001506f0abb940 Nov 23 18:54:59 foxxnas kernel: R10: 00001506f0abbc10 R11: 0000000000000246 R12: 000055fd7dd822a0 Nov 23 18:54:59 foxxnas kernel: R13: 000055fd7dd92c80 R14: 000055fd7dd81390 R15: 000055fd7dd92c80 Nov 23 18:54:59 foxxnas kernel: Modules linked in: veth macvlan xt_nat ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod it87 hwmon_vid bonding edac_mce_amd kvm_amd ccp kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc k10temp aesni_intel aes_x86_64 crypto_simd cryptd i2c_piix4 i2c_core ahci r8169 fam15h_power glue_helper libahci mii mxm_wmi wmi button pcc_cpufreq acpi_cpufreq Nov 23 18:54:59 foxxnas kernel: CR2: ffffb3052379c1f8 Nov 23 18:54:59 foxxnas kernel: ---[ end trace c7dc0e1781baa0af ]--- Nov 23 18:54:59 foxxnas kernel: RIP: 0010:get_active_stripe+0x8e/0x374 [md_mod] Nov 23 18:54:59 foxxnas kernel: Code: 85 c0 75 02 0f 0b 83 3d 0d 6e 00 00 04 7e 0f 4c 89 e6 48 c7 c7 8d 71 0f a0 e8 e4 6c f9 e0 49 8b 07 4a 8b 1c 28 48 85 db 74 0b <4c> 3b 63 28 74 1f 48 8b 1b eb f0 83 3d de 6d 00 00 04 7e 25 4c 89 Nov 23 18:54:59 foxxnas kernel: RSP: 0018:ffffc90003373ca8 EFLAGS: 00010086 Nov 23 18:54:59 foxxnas kernel: RAX: ffff8805224eb000 RBX: ffff3704f75291a0 RCX: 0000000000000300 Nov 23 18:54:59 foxxnas kernel: RDX: 0000000000000001 RSI: 00000000038e8ac8 RDI: ffff880523685a68 Nov 23 18:54:59 foxxnas kernel: RBP: ffff880523685a68 R08: 00000000038e8ac8 R09: 00000000fffffffd Nov 23 18:54:59 foxxnas kernel: R10: 0000000000000000 R11: 0000000000001000 R12: 00000000038e8ac8 Nov 23 18:54:59 foxxnas kernel: R13: 0000000000000ac8 R14: ffffffff8106aff3 R15: ffff880523685800 Nov 23 18:54:59 foxxnas kernel: FS: 00001506f0abb940(0000) GS:ffff88053ed80000(0000) knlGS:0000000000000000 Nov 23 18:54:59 foxxnas kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 23 18:54:59 foxxnas kernel: CR2: ffffb3052379c1f8 CR3: 00000005237a6000 CR4: 00000000000406e0 Nov 23 18:55:56 foxxnas kernel: INFO: rcu_sched detected stalls on CPUs/tasks: Nov 23 18:55:56 foxxnas kernel: 3-...0: (0 ticks this GP) idle=5e2/1/4611686018427387904 softirq=32127/32127 fqs=13615 Nov 23 18:55:56 foxxnas kernel: (detected by 4, t=60002 jiffies, g=17221, c=17220, q=130630) Nov 23 18:55:56 foxxnas kernel: Sending NMI from CPU 4 to CPUs 3: Nov 23 18:55:56 foxxnas kernel: NMI backtrace for cpu 3 Nov 23 18:55:56 foxxnas kernel: CPU: 3 PID: 26 Comm: ksoftirqd/3 Tainted: G D W 4.18.15-unRAID #1 Nov 23 18:55:56 foxxnas kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./990FXA-UD3, BIOS F3 05/28/2015 Nov 23 18:55:56 foxxnas kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x165/0x16d Nov 23 18:55:56 foxxnas kernel: Code: eb eb 13 48 8b 0a 48 85 c9 75 04 f3 90 eb f4 c7 41 08 01 00 00 00 65 ff 0d 4a dd f9 7e c3 85 d2 74 0a 8b 07 84 c0 74 04 f3 90 <eb> f6 66 c7 07 01 00 c3 49 b8 eb 83 b5 80 46 86 c8 61 b9 40 00 00 Nov 23 18:55:56 foxxnas kernel: RSP: 0018:ffffc9000323bd50 EFLAGS: 00000002 Nov 23 18:55:56 foxxnas kernel: RAX: 0000000000180101 RBX: 0000000000000246 RCX: 0000000000000101 Nov 23 18:55:56 foxxnas kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff880523685a68 Nov 23 18:55:56 foxxnas kernel: RBP: ffff8804f7cc8968 R08: ffff8804f7cc8a18 R09: 0000000000000200 Nov 23 18:55:56 foxxnas kernel: R10: 8080808080800010 R11: ffff880526ed4400 R12: ffff880523685800 Nov 23 18:55:56 foxxnas kernel: R13: ffff880523685a68 R14: 0000000000001000 R15: 0000000000000000 Nov 23 18:55:56 foxxnas kernel: FS: 0000000000000000(0000) GS:ffff88053ecc0000(0000) knlGS:0000000000000000 Nov 23 18:55:56 foxxnas kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 23 18:55:56 foxxnas kernel: CR2: 0000148f0d5da000 CR3: 00000004ac15c000 CR4: 00000000000406e0 Nov 23 18:55:56 foxxnas kernel: Call Trace: Nov 23 18:55:56 foxxnas kernel: _raw_spin_lock_irqsave+0x28/0x2f Nov 23 18:55:56 foxxnas kernel: end_request+0x4f/0x7a [md_mod] Nov 23 18:55:56 foxxnas kernel: blk_update_request+0x109/0x206 Nov 23 18:55:56 foxxnas kernel: scsi_end_request+0x27/0x196 Nov 23 18:55:56 foxxnas kernel: scsi_io_completion+0x1f5/0x49b Nov 23 18:55:56 foxxnas kernel: blk_done_softirq+0x89/0xa6 Nov 23 18:55:56 foxxnas kernel: __do_softirq+0xce/0x1c8 Nov 23 18:55:56 foxxnas kernel: ? smpboot_park_thread+0x25/0x25 Nov 23 18:55:56 foxxnas kernel: run_ksoftirqd+0x19/0x2d Nov 23 18:55:56 foxxnas kernel: smpboot_thread_fn+0x134/0x149 Nov 23 18:55:56 foxxnas kernel: kthread+0x10b/0x113 Nov 23 18:55:56 foxxnas kernel: ? kthread_flush_work_fn+0x9/0x9 Nov 23 18:55:56 foxxnas kernel: ret_from_fork+0x22/0x40 unraid was attempting to do a parity check when this occurred. Link to comment
FoxxMD Posted November 24, 2018 Author Share Posted November 24, 2018 Ran memtest and was seeing massive amounts of errors. I have 2x 2GB sticks that must be at least 7 years old now. Took them out and re-ran memtest for ~5 minutes with 0 errors so I think one of these two sticks was the problem. Server started normally after removing and everything seems okay so far. Thanks for the tip on checking memtest...hopefully it was these old sticks and not my newer, larger 8GB sticks... Link to comment
Squid Posted November 24, 2018 Share Posted November 24, 2018 1 hour ago, FoxxMD said: re-ran memtest for ~5 minutes Bare minimum of memtest would be a single pass. Anything less and the memory is still questionable Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.