Daishan Posted February 21, 2020 Share Posted February 21, 2020 My Uraid server will randomly become unresponsive. It happens randomly, some time i can last a month or two, other time a couple days. The webui, ssh, ping the server has no response. I can usually get to the cli with a monitor connected and when i try a shut down, it fails the clean shut down, and freezes on the diagnostic creating. It happened again today around 12 I was able to use the cli to copy the syslog, before having to do a hard reboot. I tried looking through the log and the below cut seem to keep repeating it self. It seems to mentions Plex Media Serv Tainted, and i am running binhex-plexpass but unsure what it all means. Is any one able to understand why it fails? Feb 20 11:44:11 Tower kernel: ------------[ cut here ]------------ Feb 20 11:44:11 Tower kernel: WARNING: CPU: 1 PID: 93378 at mm/truncate.c:707 invalidate_inode_pages2_range+0x163/0x369 Feb 20 11:44:11 Tower kernel: Modules linked in: veth macvlan xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap xt_nat ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod igb i2c_algo_bit sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper mpt3sas isci intel_cstate libsas i2c_i801 intel_uncore i2c_core intel_rapl_perf ahci raid_class libahci scsi_transport_sas pcc_cpufreq wmi ipmi_si button [last unloaded: i2c_algo_bit] Feb 20 11:44:11 Tower kernel: CPU: 1 PID: 93378 Comm: Plex Media Serv Tainted: G W 4.19.88-Unraid #1 Feb 20 11:44:11 Tower kernel: Hardware name: Intel Corporation S2600CP ........../S2600CP, BIOS SE5C600.86B.01.08.0003.022620131521 02/26/2013 Feb 20 11:44:11 Tower kernel: RIP: 0010:invalidate_inode_pages2_range+0x163/0x369 Feb 20 11:44:11 Tower kernel: Code: 8b 70 20 f6 c1 01 74 04 48 8d 51 ff 48 89 e8 48 29 d0 48 c1 f8 06 48 01 f0 48 39 c3 74 0e 48 c7 c7 69 f6 d2 81 e8 7d 1d fa ff <0f> 0b 4c 39 65 18 0f 85 70 01 00 00 48 8b 55 08 48 89 e8 f6 c2 01 Feb 20 11:44:11 Tower kernel: RSP: 0018:ffffc90007d13b28 EFLAGS: 00010246 Feb 20 11:44:11 Tower kernel: RAX: 0000000000000024 RBX: 0000000000049382 RCX: 0000000000000000 Feb 20 11:44:11 Tower kernel: RDX: 0000000000000000 RSI: ffff88881da564f8 RDI: ffff88881da564f8 Feb 20 11:44:11 Tower kernel: RBP: ffff88879a78b398 R08: 0000000000000003 R09: 000000000005a400 Feb 20 11:44:11 Tower kernel: R10: 0000000000000000 R11: 0000000000000044 R12: ffff888170c02e68 Feb 20 11:44:11 Tower kernel: R13: 0000000000000000 R14: 000000000000000b R15: ffff888170c02e70 Feb 20 11:44:11 Tower kernel: FS: 000014c17f5fa700(0000) GS:ffff88881da40000(0000) knlGS:0000000000000000 Feb 20 11:44:11 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 20 11:44:11 Tower kernel: CR2: 00001514ac663eb8 CR3: 00000001de29a001 CR4: 00000000000606e0 Feb 20 11:44:11 Tower kernel: Call Trace: Feb 20 11:44:11 Tower kernel: ? wait_woken+0x6a/0x6a Feb 20 11:44:11 Tower kernel: ? fuse_prepare_release+0x6/0xbe Feb 20 11:44:11 Tower kernel: fuse_finish_open+0x3c/0xe2 Feb 20 11:44:11 Tower kernel: fuse_open_common+0x8d/0xb4 Feb 20 11:44:11 Tower kernel: ? fuse_open_common+0xb4/0xb4 Feb 20 11:44:11 Tower kernel: do_dentry_open+0x20c/0x2d3 Feb 20 11:44:11 Tower kernel: path_openat+0xa91/0xc83 Feb 20 11:44:11 Tower kernel: ? __bpf_prog_run32+0x34/0x54 Feb 20 11:44:11 Tower kernel: do_filp_open+0x4c/0xa9 Feb 20 11:44:11 Tower kernel: ? _copy_to_user+0x27/0x2a Feb 20 11:44:11 Tower kernel: do_sys_open+0x135/0x1d9 Feb 20 11:44:11 Tower kernel: do_syscall_64+0x57/0xf2 Feb 20 11:44:11 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Feb 20 11:44:11 Tower kernel: RIP: 0033:0x14c218e9ee84 Feb 20 11:44:11 Tower kernel: Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 86 f4 ff ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 b8 f4 ff ff 8b 44 Feb 20 11:44:11 Tower kernel: RSP: 002b:000014c17f5f97f0 EFLAGS: 00000293 ORIG_RAX: 0000000000000101 Feb 20 11:44:11 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000000072 RCX: 000014c218e9ee84 Feb 20 11:44:11 Tower kernel: RDX: 0000000000080000 RSI: 000014c1a40b94a0 RDI: 00000000ffffff9c Feb 20 11:44:11 Tower kernel: RBP: 000014c1a40b94a0 R08: 0000000000000000 R09: 0000000000000000 Feb 20 11:44:11 Tower kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000080000 Feb 20 11:44:11 Tower kernel: R13: 000014c1a4172701 R14: 000014c1a4194bc0 R15: 000014c17f5f9880 Feb 20 11:44:11 Tower kernel: ---[ end trace ec0b24b216f45fbd ]--- I have attached my diagnostics that i generated after the reboot. Not sure it that helps. syslog.txt tower-diagnostics-20200220-1951.zip Quote Link to comment
trurl Posted February 21, 2020 Share Posted February 21, 2020 On mobile so not looked at Diagnostics yet. Have you done memtest? Quote Link to comment
Payyn Posted February 8 Share Posted February 8 (edited) Did you ever find a fix for this? I have the same issue with that docker. The server was becoming unresponsive almost every night until I checked "Run scanner tasks at a lower priority" under the Library section. Since the change the server been running now for over 3 days without any issues. However, I still see the errors in my log. Edited February 8 by Payyn Quote Link to comment
trurl Posted February 8 Share Posted February 8 This is a very old thread, and OP has not visited the forum in nearly a year. Not clear what errors you mean in your log since you haven't given us anything. The screenshot posted above suggest macvlan is the problem and not really plex. If you want us to take a look at your situation, attach Diagnostics to your NEXT post in this thread. 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.