joshsalvi Posted June 25 Share Posted June 25 This is what appeared in the console. Happy to share more information, but this led to a crash just now. Quote Link to comment
joshsalvi Posted June 25 Author Share Posted June 25 Diagnostics here. tower-diagnostics-20240625-1106.zip Quote Link to comment
JorgeB Posted June 25 Share Posted June 25 Diags are after rebooting so not much to see, enable the syslog server and post that after a crash, or if you think Plex is the problem, confirm if it only crashes with Plex enabled. Quote Link to comment
joshsalvi Posted June 26 Author Share Posted June 26 Here's the syslog file from a crash earlier this morning. The same messages as I included in the screenshot above appeared in the frozen console. Some notes: Note that I had this issue previously in another thread and isolated it to Plex, so I thought. When I turned off Plex but kept all else constant, there were not previously crashes before. The problem was fixed for a few days when I switched to a different Plex container (from linuxserver to the official Docker). I'm using the "latest" version in my settings. I also replaced the RAM and had tried with each stick of RAM individually. Memtest86+ passed. I do sometimes get USB errors, and I've replaced the USB drive twice out of fear that that was the issue, but it didn't fix the problem. Ran in maintenance mode, I ran tests on each disk, and all passed. Could this be another hardware issue? The hardware is very new, all purchased within the last year, except for the drives. I have no idea how to isolate the problem... I also wonder if turning off maintenance tasks in Plex could help? syslog-192.168.1.224.log Quote Link to comment
JorgeB Posted June 26 Share Posted June 26 There are multiple call traces logged, but difficult for me to say if they are hardware or software related, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one. P.S. disable mover logging, unless you are troubleshooting the mover it should always be disable, or it will create a lot of noise in the log. Quote Link to comment
joshsalvi Posted June 26 Author Share Posted June 26 Hi, I did this previously and seem to have isolated it to Plex.. Quote Link to comment
JorgeB Posted June 26 Share Posted June 26 If the problem is Plex I can't help, never used it. Quote Link to comment
joshsalvi Posted July 1 Author Share Posted July 1 Here's the latest call trace: Jul 1 13:50:03 Tower kernel: docker0: port 16(vethcb32f18) entered disabled state Jul 1 13:50:03 Tower kernel: device vethcb32f18 left promiscuous mode Jul 1 13:50:03 Tower kernel: docker0: port 16(vethcb32f18) entered disabled state Jul 1 14:34:12 Tower kernel: BUG: kernel NULL pointer dereference, address: 0000000000000350 Jul 1 14:34:12 Tower kernel: #PF: supervisor instruction fetch in kernel mode Jul 1 14:34:12 Tower kernel: #PF: error_code(0x0010) - not-present page Jul 1 14:34:12 Tower kernel: PGD 0 P4D 0 Jul 1 14:34:12 Tower kernel: Oops: 0010 [#1] PREEMPT SMP NOPTI Jul 1 14:34:12 Tower kernel: CPU: 12 PID: 4466 Comm: Plex Media Scan Tainted: P U O 6.1.79-Unraid #1 Jul 1 14:34:12 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. Z690 AORUS ELITE DDR4/Z690 AORUS ELITE DDR4, BIOS F7 08/09/2022 Jul 1 14:34:12 Tower kernel: RIP: 0010:0x350 Jul 1 14:34:12 Tower kernel: Code: Unable to access opcode bytes at 0x326. Jul 1 14:34:12 Tower kernel: RSP: 0018:ffffc9002c3a7ec8 EFLAGS: 00010282 Jul 1 14:34:12 Tower kernel: RAX: 0000000080000001 RBX: ffff888137d17000 RCX: ffff88a03f72eab8 Jul 1 14:34:12 Tower kernel: RDX: 0000000000000002 RSI: ffff88a03f72e040 RDI: 00000000ffffffff Jul 1 14:34:12 Tower kernel: RBP: ffffc9002c3a7f10 R08: 0000000000000000 R09: 0000000000000384 Jul 1 14:34:12 Tower kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff88a03f72e040 Jul 1 14:34:12 Tower kernel: R13: ffff888137d17000 R14: 0000000000000000 R15: ffff888137d175b0 Jul 1 14:34:12 Tower kernel: FS: 0000147bc2993b00(0000) GS:ffff88a03f700000(0000) knlGS:0000000000000000 Jul 1 14:34:12 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 1 14:34:12 Tower kernel: CR2: 0000000000000350 CR3: 00000004c4e64000 CR4: 0000000000750ee0 Jul 1 14:34:12 Tower kernel: PKRU: 55555554 Jul 1 14:34:12 Tower kernel: Call Trace: Jul 1 14:34:12 Tower kernel: <TASK> Jul 1 14:34:12 Tower kernel: ? __die_body+0x1a/0x5c Jul 1 14:34:12 Tower kernel: ? page_fault_oops+0x329/0x376 Jul 1 14:34:12 Tower kernel: ? exc_page_fault+0xfb/0x11d Jul 1 14:34:12 Tower kernel: ? asm_exc_page_fault+0x22/0x30 Jul 1 14:34:12 Tower kernel: ? _raw_spin_lock+0x13/0x1c Jul 1 14:34:12 Tower kernel: schedule+0x8e/0xcc Jul 1 14:34:12 Tower kernel: __do_sys_sched_yield+0xa/0x11 Jul 1 14:34:12 Tower kernel: do_syscall_64+0x68/0x81 Jul 1 14:34:12 Tower kernel: entry_SYSCALL_64_after_hwframe+0x64/0xce Jul 1 14:34:12 Tower kernel: RIP: 0033:0x147bcacfc57a Jul 1 14:34:12 Tower kernel: Code: 0f 05 9b 48 89 c7 e9 45 38 fd ff 48 c7 c7 da ff ff ff e9 39 38 fd ff 48 c7 c7 da ff ff ff e9 2d 38 fd ff b8 18 00 00 00 0f 05 <9b> 48 89 c7 e9 1d 38 fd ff 48 8d 35 f6 eb 01 00 e9 00 00 00 00 41 Jul 1 14:34:12 Tower kernel: RSP: 002b:0000147bc2992b38 EFLAGS: 00000202 ORIG_RAX: 0000000000000018 Jul 1 14:34:12 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000000012 RCX: 0000147bcacfc57a Jul 1 14:34:12 Tower kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000 Jul 1 14:34:12 Tower kernel: RBP: 0000147bc2992bb0 R08: 0000147bcacbd640 R09: 0000000000000350 Jul 1 14:34:12 Tower kernel: R10: 0000000000000002 R11: 0000000000000202 R12: 0000147bc5071bb0 Jul 1 14:34:12 Tower kernel: R13: 0000147bc3b645f0 R14: 0000147bc5071b80 R15: 0000147bc5071b50 Jul 1 14:34:12 Tower kernel: </TASK> Jul 1 14:34:12 Tower kernel: Modules linked in: xt_mark nft_compat nft_chain_nat nf_tables xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag i915 drm_buddy i2c_algo_bit ttm drm_display_helper drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs af_packet 8021q garp mrp bridge stp llc bonding tls intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel mei_pxp mei_hdcp crypto_simd cryptd Jul 1 14:34:12 Tower kernel: rapl gigabyte_wmi wmi_bmof intel_cstate mpt3sas intel_uncore i2c_i801 nvme mei_me i2c_smbus r8169 raid_class sr_mod i2c_core mei ahci input_leds scsi_transport_sas joydev nvme_core cdrom led_class realtek libahci thermal fan video tpm_crb tpm_tis tpm_tis_core wmi tpm intel_pmc_core backlight acpi_pad acpi_tad button unix Jul 1 14:34:12 Tower kernel: CR2: 0000000000000350 Jul 1 14:34:12 Tower kernel: ---[ end trace 0000000000000000 ]--- Jul 1 14:34:12 Tower kernel: RIP: 0010:0x350 Jul 1 14:34:12 Tower kernel: Code: Unable to access opcode bytes at 0x326. Jul 1 14:34:12 Tower kernel: RSP: 0018:ffffc9002c3a7ec8 EFLAGS: 00010282 Jul 1 14:34:12 Tower kernel: RAX: 0000000080000001 RBX: ffff888137d17000 RCX: ffff88a03f72eab8 Jul 1 14:34:12 Tower kernel: RDX: 0000000000000002 RSI: ffff88a03f72e040 RDI: 00000000ffffffff Jul 1 14:34:12 Tower kernel: RBP: ffffc9002c3a7f10 R08: 0000000000000000 R09: 0000000000000384 Jul 1 14:34:12 Tower kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff88a03f72e040 Jul 1 14:34:12 Tower kernel: R13: ffff888137d17000 R14: 0000000000000000 R15: ffff888137d175b0 Jul 1 14:34:12 Tower kernel: FS: 0000147bc2993b00(0000) GS:ffff88a03f700000(0000) knlGS:0000000000000000 Jul 1 14:34:12 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 1 14:34:12 Tower kernel: CR2: 0000000000000350 CR3: 00000004c4e64000 CR4: 0000000000750ee0 Jul 1 14:34:12 Tower kernel: PKRU: 55555554 Jul 1 14:34:12 Tower kernel: note: Plex Media Scan[4466] exited with irqs disabled Jul 1 14:34:12 Tower kernel: note: Plex Media Scan[4466] exited with preempt_count 1 Jul 1 14:51:31 Tower root: ACPI action down is not defined It looks like by disabling many of the Plex maintenance tasks, the call trace occurs but the system doesn't immediately crash (this just happened, and the server is still running right now). Is there by any chance a guide to reading these call traces? Perhaps I can debug it myself if so. Quote Link to comment
JorgeB Posted July 2 Share Posted July 2 I would suggest asking for help in the support thread for the Plex container you are using. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.