CaptainCopSuey

Replacing my CPU seems to have alleviated this particular call trace, but I've since seen a new kind of error arise. I've created a new topic for it here:

A month or so ago, my server started having issues where it would completely crash, and would require a reboot to fix. I posted here, with my syslog attached, and in a bid to fix those errors, I've replaced my CPU. That seemed to fix my errors. I have; however, started experiencing several new errors. One error seemed to related to the version of libtorrent being used by qbittorrent, and changing the repo to use libtorrent1 seems to have resolved that. Now onto my new problem. Upon logging into my server this morning to review the syslog, and saw a new error, and I've no idea what to do about this. Any help would be greatly appreciated. I've attached my syslog here, and have posted the section of my log below to make it visible for other people searching for this: Apr 16 04:25:24 kernel: kernel BUG at arch/x86/kernel/traps.c:934! Apr 16 04:25:24 kernel: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI Apr 16 04:25:24 kernel: CPU: 9 PID: 30504 Comm: shfs Tainted: P O 6.1.79-Unraid #1 Apr 16 04:25:24 kernel: Hardware name: ASUS System Product Name/TUF GAMING Z790-PRO WIFI, BIOS 1401 09/08/2023 Apr 16 04:25:24 kernel: RIP: 0010:fixup_bad_iret+0x7c/0xa7 Apr 16 04:25:24 kernel: Code: 00 ba 80 00 00 00 48 89 ee 48 89 e7 e8 9e 31 00 00 ba a8 00 00 00 48 89 df 48 89 e6 e8 8e 31 00 00 f6 83 88 00 00 00 03 75 02 <0f> 0b 48 8b 84 24 a8 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 Apr 16 04:25:24 kernel: RSP: 0018:fffffe0000215e58 EFLAGS: 00010046 Apr 16 04:25:24 kernel: RAX: fffffe0000215f58 RBX: fffffe0000215f58 RCX: 0000000000000000 Apr 16 04:25:24 kernel: RDX: 00000000000000a8 RSI: fffffe0000215f00 RDI: fffffe0000216000 Apr 16 04:25:24 kernel: RBP: fffffe0000215f28 R08: 0000000000000000 R09: 0000000000000000 Apr 16 04:25:24 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 Apr 16 04:25:24 kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Apr 16 04:25:24 kernel: FS: 0000154e3b8f76c0(0000) GS:ffff889fff240000(0000) knlGS:0000000000000000 Apr 16 04:25:24 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 16 04:25:24 kernel: CR2: 0000150a1dc4b000 CR3: 0000000167f04000 CR4: 0000000000750ee0 Apr 16 04:25:24 kernel: PKRU: 55555554 Apr 16 04:25:24 kernel: Call Trace: Apr 16 04:25:24 kernel: <ENTRY_TRAMPOLINE> Apr 16 04:25:24 kernel: ? __die_body+0x1a/0x5c Apr 16 04:25:24 kernel: ? die+0x30/0x49 Apr 16 04:25:24 kernel: ? do_trap+0x7b/0xfe Apr 16 04:25:24 kernel: ? fixup_bad_iret+0x7c/0xa7 Apr 16 04:25:24 kernel: ? fixup_bad_iret+0x7c/0xa7 Apr 16 04:25:24 kernel: ? do_error_trap+0x6e/0x98 Apr 16 04:25:24 kernel: ? fixup_bad_iret+0x7c/0xa7 Apr 16 04:25:24 kernel: ? exc_invalid_op+0x4c/0x60 Apr 16 04:25:24 kernel: ? fixup_bad_iret+0x7c/0xa7 Apr 16 04:25:24 kernel: ? asm_exc_invalid_op+0x16/0x20 Apr 16 04:25:24 kernel: ? fixup_bad_iret+0x7c/0xa7 Apr 16 04:25:24 kernel: ? fixup_bad_iret+0x73/0xa7 Apr 16 04:25:24 kernel: ? entry_SYSCALL_64_after_hwframe+0x64/0xce Apr 16 04:25:24 kernel: error_entry+0x118/0x120 Apr 16 04:25:24 kernel: RIP: 0000:0x0 Apr 16 04:25:24 kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Apr 16 04:25:24 kernel: RSP: 594f274b:fffffffffffffff5 EFLAGS: 00000000 ORIG_RAX: 0000000000000282 Apr 16 04:25:24 kernel: RAX: 0000154e3b8f6c38 RBX: 0000000000000000 RCX: 0000000000000000 Apr 16 04:25:24 kernel: RDX: 0000154e3b5f5038 RSI: 00000000000008a8 RDI: 0000000000416a10 Apr 16 04:25:24 kernel: RBP: 0000154e3b8f6c38 R08: 0000000000416a78 R09: ffffffff81a000dc Apr 16 04:25:24 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000416a78 Apr 16 04:25:24 kernel: R13: ffffffff81a000dc R14: 0000000000000000 R15: 0000000000000000 Apr 16 04:25:24 kernel: ? asm_exc_general_protection+0x9/0x30 Apr 16 04:25:24 kernel: ? entry_SYSCALL_64_after_hwframe+0x64/0xce Apr 16 04:25:24 kernel: ? entry_SYSCALL_64_after_hwframe+0x64/0xce Apr 16 04:25:24 kernel: </ENTRY_TRAMPOLINE> Apr 16 04:25:24 kernel: Modules linked in: tcp_diag udp_diag inet_diag xt_nat xt_tcpudp ipvlan 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 md_mod nct6775 nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge 8021q garp mrp stp llc bonding tls igc r8125(O) zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) nvme nvme_core ahci libahci x86_pkg_temp_thermal intel_powerclamp coretemp i915 kvm_intel kvm drm_buddy crct10dif_pclmul i2c_algo_bit crc32_pclmul crc32c_intel ttm ghash_clmulni_intel sha512_ssse3 sha256_ssse3 btusb sha1_ssse3 drm_display_helper btrtl btbcm aesni_intel btintel drm_kms_helper crypto_simd cryptd bluetooth drm rapl mei_hdcp mei_pxp intel_rapl_msr wmi_bmof intel_gtt input_leds intel_cstate processor_thermal_device_pci ecdh_generic joydev led_class ecc processor_thermal_device agpgart Apr 16 04:25:24 kernel: i2c_i801 mpt3sas intel_uncore processor_thermal_rfim i2c_smbus processor_thermal_mbox mei_me processor_thermal_rapl raid_class i2c_core intel_rapl_common mei scsi_transport_sas int340x_thermal_zone syscopyarea sysfillrect vmd iosf_mbi sysimgblt thermal fb_sys_fops fan video wmi int3400_thermal acpi_thermal_rel backlight acpi_pad intel_pmc_core acpi_tad button unix [last unloaded: igc] Apr 16 04:25:24 kernel: ---[ end trace 0000000000000000 ]--- Apr 16 04:25:24 kernel: RIP: 0010:fixup_bad_iret+0x7c/0xa7 Apr 16 04:25:24 kernel: Code: 00 ba 80 00 00 00 48 89 ee 48 89 e7 e8 9e 31 00 00 ba a8 00 00 00 48 89 df 48 89 e6 e8 8e 31 00 00 f6 83 88 00 00 00 03 75 02 <0f> 0b 48 8b 84 24 a8 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 Apr 16 04:25:24 kernel: RSP: 0018:fffffe0000215e58 EFLAGS: 00010046 Apr 16 04:25:24 kernel: RAX: fffffe0000215f58 RBX: fffffe0000215f58 RCX: 0000000000000000 Apr 16 04:25:24 kernel: RDX: 00000000000000a8 RSI: fffffe0000215f00 RDI: fffffe0000216000 Apr 16 04:25:24 kernel: RBP: fffffe0000215f28 R08: 0000000000000000 R09: 0000000000000000 Apr 16 04:25:24 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 Apr 16 04:25:24 kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Apr 16 04:25:24 kernel: FS: 0000154e3b8f76c0(0000) GS:ffff889fff240000(0000) knlGS:0000000000000000 Apr 16 04:25:24 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 16 04:25:24 kernel: CR2: ffffffffffffffd6 CR3: 0000000167f04000 CR4: 0000000000750ee0 Apr 16 04:25:24 kernel: PKRU: 55555554 Apr 16 04:25:24 kernel: note: shfs[30504] exited with irqs disabled syslog.log

If it helps, I have my docker containers appdata stored on a cache, in a RAID 1 configuration. I have run the extended SMART testing on both, with both returning 0 errors. I can upload their reports if needed.

Ok. I let it run for two days without docker enabled. Enabling docker, I've started slowly re-enabling containers, and it crashed on my immich. I restarted the process of enabling containers, got to jellyfin, which worked fine before, and now it crashed there. Immich still won't start without bringing my server to it's knees. Frustratingly, my syslog file, which is being saved to a separate location, shows call traces, but seems to offer no hint as to what is actually happening. I have no clue what is going, so have attached my newer syslog file here. syslog-10.216.18.3.log

I'm having a similar problem, and I'm running on an i9-14900k with an Asus TUF Gaming Z790-PRO. I've tried narrowing down the scope of the problem, and for me it seems to be happening when I have docker running. Mine seems to have problems whenever I start my Immich container, but I thought the same about a MusicBrainz container and its persisted anyway, so I'm entirely unsure if that's the real culprit.

Digging a little bit more into this issue, I seem to be having an error similar to the one here: https://forums.unraid.net/topic/157879-unraid-crashes-randomly-takes-a-few-restarts-to-come-back-up/

Memtest completed with a Pass.

Hello all. I've got a problem with my server that is utterly bewildering me. A couple weeks ago, and without making any changes to my server, it keeps crashing all of the time, and without any reproducible source. Genuinely, I have no idea what is going on here, and would appreciate any help anyone can offer. I've tried the following troubleshooting to no avail: Separated the main server IP from all docker vlan's to separate NIC's. Removed several docker containers that constantly seemed to be crashing the server. Disassembled and reassembled server to ensure no components have apparent physical damage. I'm sure I'm missing a lot here, so I've also attached my syslog here. Thanks. syslog-10.216.18.3.log

As the title says, I'm needing help understanding a SMART report for one of the disks in my array. It looks to me like it didn't pass the extended SMART test, but at the top of the report it says that it passed. I'm more than a little confused WDC_WD60EFRX-68MYMN1_WD-WX71D65JEXD2-20221209-1237.txt

After many long hours of troubleshooting and learning, I have put together a configuration that gets NPM, Nextcloud, and iOS all playing nicely. Create a proxy host Input domain name (nextcloud.example.com) Scheme: https Forward Hostname / IP*: whatever your endpoint is Forward Port: 443 or whatever https port you are using Check "Block Common Exploits" and "Websockets Support" Click SSL Obtain new SSL cert, and check boxes for "Force SSL", "HTTP/2 Support", "HSTS Enabled", and "HSTS Subdomains" Click Advanced Input the following into entry box: proxy_hide_header Upgrade; proxy_max_temp_file_size 1024000m; proxy_next_upstream error timeout invalid_header http_500 http_502 http_503; proxy_buffers 32 4k; proxy_connect_timeout 240; proxy_headers_hash_bucket_size 128; proxy_headers_hash_max_size 1024; proxy_read_timeout 240; proxy_redirect http:// $scheme://; proxy_send_timeout 240; proxy_cache_bypass $cookie_session; proxy_no_cache $cookie_session; proxy_set_header Early-Data $ssl_early_data; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Proto https; proxy_set_header X-Forwarded-Ssl on; proxy_set_header X-Real-IP $remote_addr; Save! Hope this helps. FYI, I put this together referencing the nextcloud.subdomain.conf.sample and proxy.conf in SWAG's configuration files.

Ok. So, this is probably super noob question, but, after changing the gamemode to creative in server.properties file in /mnt/user/appdata/binhex-minecraftbedrockserver, and then rebooting the docker container, when connecting to the game, it seems to still be in survival mode on the game clients. If someone here could help me with this, then I'd be most appreciative as I have no clue where to go from here. Also, if it helps, I can change other values and see those reflected in the client. For example, changing the number of allowed users to any value will show the updated value after rebooting the server and connecting to it with a client.