trwolff04

Hoping someone can help me out, I bought a Plus key in 2022 and my flash drive failed. Yes, I now have my flash backed up ... 😅 ... but my trial has ran out and my original activiation code isn't working anymore. Can a moderator email me and sort this out so I can get my server up and running again?

Crashes were due to qbittorrent libtorrent v2 and the filled log was because I had a ton of log in attempts from someone poking around in India. Turned off external access. Resolved.

7 days still no issues. Thank you. Marked resolved unless anything else comes up.

I downgraded to the last version of hexbin-qbittorrent (4.3.9-2-01) that used libtorrentv1 today dpecifically because I was having docker crashes, and sometimes full gui crashes, anywhere between 24 hours and 8 days after starting my server. This version seems to fix it but I won't know for sure until another week passes.

qbittorrent has always run better for me and binhex has a version available for that. You need to pull version 4.3.9-2-01 as that is the last one to use libtorrent v1. Mine is running fine again though I'll know for sure in a week if it doesn't crash. Through ssh: docker pull binhex/arch-qbittorrentvpn:4.3.9-2-01 in unraid apps, search install binhex qbittorrentvpn, under container options specify "binhex/arch-qbittorrentvpn:4.3.9-2-01" next to repository and it should work fine. I know you don't want to switch but I'm confirmed operational.

Thank you! I will look into this in the morning. Happy Easter.

I'm having the same issue, except with haugene qbittorrent w/ vpn, though normally my gui crashes or at last partially crashes when it happens. No issues on earlier 6.10.x builds.

I have a very similar issue, same message in my log, although mine says CPU 26 is tainted, mentions qbittorrent. Almost same server (I am running a Poweredge R720) and I have an open thread about it as well. Thoughts?

Okay, 7 days running on the newest unraid version in safe mode and I've had a partial crash. The docker page won't even load, some of my containers have stopped running including, once again, qbittorrent. I had enabled the syslog server in anticipation of this. Do I have to shutdown before I download and upload the syslog or will it be functional for you if I upload it now while the server is still running? File attached. Please let me know if this is enough info for you to resolve this issue. I see the one auth problem filling up the log but I think that is a separate issue. See this part: Apr 8 01:32:12 BEAST kernel: BUG: kernel NULL pointer dereference, address: 0000000000000036 Apr 8 01:32:12 BEAST kernel: #PF: supervisor read access in kernel mode Apr 8 01:32:12 BEAST kernel: #PF: error_code(0x0000) - not-present page Apr 8 01:32:12 BEAST kernel: PGD 0 P4D 0 Apr 8 01:32:12 BEAST kernel: Oops: 0000 [#1] PREEMPT SMP PTI Apr 8 01:32:12 BEAST kernel: CPU: 26 PID: 21942 Comm: qbittorrent-nox Not tainted 5.19.17-Unraid #2 Apr 8 01:32:12 BEAST kernel: Hardware name: Dell Inc. PowerEdge R720/0H5J4J, BIOS 2.9.0 12/06/2019 Apr 8 01:32:12 BEAST kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21 Apr 8 01:32:12 BEAST kernel: Code: e8 9d fd 67 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 c1 35 69 00 48 81 c4 88 00 00 00 5b c3 cc cc cc cc <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb Apr 8 01:32:12 BEAST kernel: RSP: 0000:ffffc9000a433cc0 EFLAGS: 00010246 Apr 8 01:32:12 BEAST kernel: RAX: 0000000000000002 RBX: 0000000000000002 RCX: 0000000000000002 Apr 8 01:32:12 BEAST kernel: RDX: 0000000000000001 RSI: ffff8885700cdda8 RDI: 0000000000000002 Apr 8 01:32:12 BEAST kernel: RBP: 0000000000000000 R08: 0000000000000004 R09: ffffc9000a433cd0 Apr 8 01:32:12 BEAST kernel: R10: ffffc9000a433cd0 R11: ffffc9000a433d48 R12: 0000000000000000 Apr 8 01:32:12 BEAST kernel: R13: ffff888648b9e3f8 R14: 000000000000f3c6 R15: ffff888648b9e400 Apr 8 01:32:12 BEAST kernel: FS: 000015448e8ed6c0(0000) GS:ffff88880fb40000(0000) knlGS:0000000000000000 Apr 8 01:32:12 BEAST kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 8 01:32:12 BEAST kernel: CR2: 0000000000000036 CR3: 00000008e34f0003 CR4: 00000000000606e0 Apr 8 01:32:12 BEAST kernel: Call Trace: Apr 8 01:32:12 BEAST kernel: <TASK> Apr 8 01:32:12 BEAST kernel: __filemap_get_folio+0x98/0x1ff Apr 8 01:32:12 BEAST kernel: ? _raw_spin_unlock+0x14/0x29 Apr 8 01:32:12 BEAST kernel: filemap_fault+0x6e/0x524 Apr 8 01:32:12 BEAST kernel: __do_fault+0x30/0x6e Apr 8 01:32:12 BEAST kernel: __handle_mm_fault+0x9a5/0xc7d Apr 8 01:32:12 BEAST kernel: handle_mm_fault+0x113/0x1d7 Apr 8 01:32:12 BEAST kernel: do_user_addr_fault+0x36a/0x514 Apr 8 01:32:12 BEAST kernel: exc_page_fault+0xfc/0x11e Apr 8 01:32:12 BEAST kernel: asm_exc_page_fault+0x22/0x30 Apr 8 01:32:12 BEAST kernel: RIP: 0033:0x1544a7ab90c1 Apr 8 01:32:12 BEAST kernel: Code: 48 01 d0 eb 1b 0f 1f 40 00 f3 0f 1e fa 48 39 d1 0f 82 83 63 07 00 0f 1f 00 f3 0f 1e fa 48 89 f8 48 83 fa 10 0f 82 af 00 00 00 <0f> 10 06 48 83 fa 20 0f 87 0f 01 00 00 0f 10 4c 16 f0 0f 11 07 0f Apr 8 01:32:12 BEAST kernel: RSP: 002b:000015448e8eb2c8 EFLAGS: 00010206 Apr 8 01:32:12 BEAST kernel: RAX: 0000154340028d70 RBX: 000015448e8ec308 RCX: 000015448e8eb500 Apr 8 01:32:12 BEAST kernel: RDX: 0000000000004000 RSI: 0000153bebfc6000 RDI: 0000154340028d70 Apr 8 01:32:12 BEAST kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 Apr 8 01:32:12 BEAST kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000 Apr 8 01:32:12 BEAST kernel: R13: 0000154344045bb0 R14: 0000000000000000 R15: 0000564d584635f0 Apr 8 01:32:12 BEAST kernel: </TASK> Apr 8 01:32:12 BEAST kernel: Modules linked in: af_packet tcp_diag udp_diag inet_diag macvlan tun xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc tg3 mgag200 drm_shmem_helper i2c_algo_bit drm_kms_helper drm ipmi_ssif backlight x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd mpt3sas rapl intel_cstate i2c_core nvme ahci raid_class syscopyarea input_leds sysfillrect sysimgblt intel_uncore nvme_core libahci joydev led_class cdc_acm fb_sys_fops scsi_transport_sas wmi ipmi_si acpi_power_meter button unix [last unloaded: tg3] Apr 8 01:32:12 BEAST kernel: CR2: 0000000000000036 Apr 8 01:32:12 BEAST kernel: ---[ end trace 0000000000000000 ]--- Apr 8 01:32:12 BEAST kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21 Apr 8 01:32:12 BEAST kernel: Code: e8 9d fd 67 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 c1 35 69 00 48 81 c4 88 00 00 00 5b c3 cc cc cc cc <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb Apr 8 01:32:12 BEAST kernel: RSP: 0000:ffffc9000a433cc0 EFLAGS: 00010246 Apr 8 01:32:12 BEAST kernel: RAX: 0000000000000002 RBX: 0000000000000002 RCX: 0000000000000002 Apr 8 01:32:12 BEAST kernel: RDX: 0000000000000001 RSI: ffff8885700cdda8 RDI: 0000000000000002 Apr 8 01:32:12 BEAST kernel: RBP: 0000000000000000 R08: 0000000000000004 R09: ffffc9000a433cd0 Apr 8 01:32:12 BEAST kernel: R10: ffffc9000a433cd0 R11: ffffc9000a433d48 R12: 0000000000000000 Apr 8 01:32:12 BEAST kernel: R13: ffff888648b9e3f8 R14: 000000000000f3c6 R15: ffff888648b9e400 Apr 8 01:32:12 BEAST kernel: FS: 000015448e8ed6c0(0000) GS:ffff88880fb40000(0000) knlGS:0000000000000000 Apr 8 01:32:12 BEAST kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 8 01:32:12 BEAST kernel: CR2: 0000000000000036 CR3: 00000008e34f0003 CR4: 00000000000606e0 Thoughts? Looks like another user with a similar system (R710 vs my R720) is having a similar issue here: syslog-192.168.1.60.log

This is after server has been running ~2 days in safe mode on newest Unraid version. I have been having an issue with GUI crashes that I posted about in another thread still unresolved and I'm testing for issues. Diagnostics attached. beast-diagnostics-20230404-1302.zip

I don't know yet. It normally takes days or weeks to fill the log. Do my diagnostics also indicate I have a mem leak?

Thanks. Didn't ask for -L. Should I try it anyway?

Phase 1 - find and verify superblock... - block cache size set to 3078920 entries Phase 2 - using internal log - zero log... zero_log: head block 48373 tail block 48373 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 bad CRC for inode 1079657638 bad CRC for inode 1079657638, would rewrite would have cleared inode 1079657638 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 bad CRC for inode 1079657638, would rewrite would have cleared inode 1079657638 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 Metadata corruption detected at 0x46b5b8, inode 0x405a44a6 dinode couldn't map inode 1079657638, err = 117 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected dir inode 1610846306, would move to lost+found Phase 7 - verify link counts... Metadata corruption detected at 0x46b5b8, inode 0x405a44a6 dinode couldn't map inode 1079657638, err = 117, can't compare link counts No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Sun Apr 2 10:12:51 2023 Phase Start End Duration Phase 1: 04/02 10:12:50 04/02 10:12:50 Phase 2: 04/02 10:12:50 04/02 10:12:50 Phase 3: 04/02 10:12:50 04/02 10:12:51 1 second Phase 4: 04/02 10:12:51 04/02 10:12:51 Phase 5: Skipped Phase 6: 04/02 10:12:51 04/02 10:12:51 Phase 7: 04/02 10:12:51 04/02 10:12:51 Total run time: 1 second

This is at least the 10th time this has happened now. Any ideas what's going on? Server starts becoming intermittently unresponsive with some of my docker apps once I reach this point. beast-diagnostics-20230331-1256.zip

Ran for 8 days in safe mode then crashed again. All docker containers were still working except haugene transmission. Downgraded back to 10.6.3 ... booted without safe mode, no issues yet. Seems there is definitely some type of bug present.