dabbler455

After a few days of running with the new microcode the system kernel panicked again. Time to replace the CPU for a second time.

After swapping memory everything was fine for a few days then the issues slowly crept back. In doing further investigation it looks like Intel has released new microcode for 13th and 14th gen CPUs as of 5/16/2025 CPU Microcode 0x12C Update Intel uCode to 0x12F I am updating the bios with new microcode and will report back in a few days if this fixes the 13th/14th gen issue. For anyone looking at this thread I recommend not going with newer generation Intel unless you are a glutton for punishment.

I pulled 2 ram sticks out. I'll let it sit for a couple of days and see if the issue persists

I downgraded from 7.2.4 to 6.12.15. I'll report tomorrow whether my issue still persists.

Ever since upgrading to 7.1.x I have been having issues with random server hangs where I cannot ssh to server to get to the GUI. Also the server is not responding to ping either. I noticed the following call-trace in the rsyslog this tainted error happens while Parity sync is running: Jun 27 06:31:43 Star-Command kernel: sd 12:0:3:0: Power-on or device reset occurred Jun 27 06:35:33 Star-Command kernel: kernel tried to execute NX-protected page - exploit attempt? (uid: 0) Jun 27 06:35:33 Star-Command kernel: BUG: unable to handle page fault for address: ffff88815cb58400 Jun 27 06:35:33 Star-Command kernel: #PF: supervisor instruction fetch in kernel mode Jun 27 06:35:33 Star-Command kernel: #PF: error_code(0x0011) - permissions violation Jun 27 06:35:33 Star-Command kernel: PGD 6001067 P4D 6001067 PUD 14ab26063 PMD 113fee063 PTE 800000015cb58163 Jun 27 06:35:33 Star-Command kernel: Oops: Oops: 0011 [#1] PREEMPT SMP NOPTI Jun 27 06:35:33 Star-Command kernel: CPU: 9 UID: 0 PID: 7969 Comm: unraidd0 Tainted: P O 6.12.24-Unraid #1 Jun 27 06:35:33 Star-Command kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE Jun 27 06:35:33 Star-Command kernel: Hardware name: Micro-Star International Co., Ltd. MS-7E25/MAG Z790 TOMAHAWK MAX WIFI (MS-7E25), BIOS A.80 09/27/2024 Jun 27 06:35:33 Star-Command kernel: RIP: 0010:0xffff88815cb58400 Jun 27 06:35:33 Star-Command kernel: Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 1e 2a 13 81 88 ff ff 00 67 84 ff ff e8 ff ff 00 d4 b7 56 81 88 Jun 27 06:35:33 Star-Command kernel: RSP: 0018:ffffc90004733c20 EFLAGS: 00010246 Jun 27 06:35:33 Star-Command kernel: RAX: 0000000000000001 RBX: ffff88815cb58400 RCX: ffff888114fc4200 Jun 27 06:35:33 Star-Command kernel: RDX: 0000000000000000 RSI: ffff88817ab8bf80 RDI: ffff88815cb58400 Jun 27 06:35:33 Star-Command kernel: RBP: ffff88817ab8bf80 R08: 0000000000000000 R09: ffff88817ab8bf80 Jun 27 06:35:33 Star-Command kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff8881132a1e00 Jun 27 06:35:33 Star-Command kernel: R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001 Jun 27 06:35:33 Star-Command kernel: FS: 0000000000000000(0000) GS:ffff889fff240000(0000) knlGS:0000000000000000 Jun 27 06:35:33 Star-Command kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 27 06:35:33 Star-Command kernel: CR2: ffff88815cb58400 CR3: 0000000803ef8006 CR4: 0000000000772ef0 Jun 27 06:35:33 Star-Command kernel: PKRU: 55555554 Jun 27 06:35:33 Star-Command kernel: Call Trace: Jun 27 06:35:33 Star-Command kernel: <TASK> Jun 27 06:35:33 Star-Command kernel: ? blk_attempt_bio_merge+0x3a/0xe0 Jun 27 06:35:33 Star-Command kernel: ? blk_attempt_plug_merge+0x38/0x60 Jun 27 06:35:33 Star-Command kernel: ? blk_mq_submit_bio+0x25e/0x530 Jun 27 06:35:33 Star-Command kernel: ? __submit_bio+0x3e/0xe0 Jun 27 06:35:33 Star-Command kernel: ? submit_bio_noacct_nocheck+0x152/0x2e0 Jun 27 06:35:33 Star-Command kernel: ? unraidd+0x11eb/0x1280 [md_mod] Jun 27 06:35:33 Star-Command kernel: ? do_raw_spin_lock+0x14/0x20 Jun 27 06:35:33 Star-Command kernel: ? rawspin_lock_irqsave+0x1f/0x30 Jun 27 06:35:33 Star-Command kernel: ? md_thread+0xf6/0x130 [md_mod] Jun 27 06:35:33 Star-Command kernel: ? __pfx_autoremove_wake_function+0x10/0x10 Jun 27 06:35:33 Star-Command kernel: ? __pfx_md_thread+0x10/0x10 [md_mod] Jun 27 06:35:33 Star-Command kernel: ? kthread+0xec/0x100 Jun 27 06:35:33 Star-Command kernel: ? __pfx_kthread+0x10/0x10 Jun 27 06:35:33 Star-Command kernel: ? ret_from_fork+0x21/0x40 Jun 27 06:35:33 Star-Command kernel: ? __pfx_kthread+0x10/0x10 Jun 27 06:35:33 Star-Command kernel: ? ret_from_fork_asm+0x1a/0x30 Jun 27 06:35:33 Star-Command kernel: </TASK> Jun 27 06:35:33 Star-Command kernel: Modules linked in: xt_connmark xt_mark iptable_mangle xt_comment iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha veth ipvlan nf_conntrack_netlink xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nfnetlink xfrm_user xfrm_algo ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype md_mod zfs(PO) spl(O) ntfs3 tcp_diag inet_diag nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc qrtr_mhi xe drm_gpuvm drm_exec gpu_sched drm_ttm_helper drm_suballoc_helper intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp i915 kvm_intel qrtr kvm ath12k iosf_mbi drm_buddy mhi crct10dif_pclmul ttm crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 qmi_helpers i2c_algo_bit drm_display_helper sha256_ssse3 sha1_ssse3 mac80211 btusb aesni_intel drm_kms_helper btrtl crypto_simd btbcm cryptd btintel bluetooth drm rapl mei_hdcp mei_pxp Jun 27 06:35:33 Star-Command kernel: joydev input_leds nvme cfg80211 intel_cstate mpt3sas mei_me wmi_bmof intel_gtt intel_uncore mxm_wmi igc i2c_i801 nvme_core agpgart mei i2c_smbus raid_class ahci tpm_crb rfkill scsi_transport_sas i2c_core tpm_tis libahci libarc4 tpm_tis_core led_class tpm thermal fan video libaescfb ecdh_generic wmi ecc backlight acpi_tad acpi_pad button Jun 27 06:35:33 Star-Command kernel: CR2: ffff88815cb58400 I also noticed this nginx entry in the logs: Jun 27 02:04:15 Star-Command nginx: 2025/06/27 02:04:15 [crit] 6311#6311: ngx_slab_alloc() failed: no memory Jun 27 02:04:15 Star-Command nginx: 2025/06/27 02:04:15 [error] 6311#6311: shpool alloc failed Jun 27 02:04:15 Star-Command nginx: 2025/06/27 02:04:15 [error] 6311#6311: nchan: Out of shared memory while allocating message of size 13022. Increase nchan_max_reserved_memory. Jun 27 02:04:15 Star-Command nginx: 2025/06/27 02:04:15 [error] 6311#6311: *88661 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" Jun 27 02:04:15 Star-Command nginx: 2025/06/27 02:04:15 [error] 6311#6311: MEMSTORE:00: can't create shared message for channel /devices Jun 27 02:04:15 Star-Command webgui: Nchan out of shared memory. Reloading nginx Jun 27 02:04:15 Star-Command rc.nginx: Restarting Nginx server daemon... Jun 27 02:04:15 Star-Command rc.nginx: Checking configuration for correct syntax and then trying to open files referenced in configuration... Jun 27 02:04:15 Star-Command rc.nginx: /usr/sbin/nginx -t -c /etc/nginx/nginx.conf Jun 27 02:04:15 Star-Command rc.nginx: Stopping Nginx server daemon gracefully... Jun 27 02:04:27 Star-Command nginx: 2025/06/27 02:04:27 [error] 6311#6311: MEMSTORE:00: force-reaping msg with refcount 1 ### [PREVIOUS LINE REPEATED 11520 TIMES] ### Jun 27 02:04:27 Star-Command rc.nginx: Nginx server daemon... Stopped. Jun 27 02:04:27 Star-Command rc.nginx: Starting Nginx server daemon... Jun 27 02:04:27 Star-Command rc.nginx: Nginx server daemon... Started. Jun 27 02:04:59 Star-Command monitor_nchan: Stop running nchan processes Jun 27 03:00:05 Star-Command shfs: copy_file: //..y/... I'm not sure if these 2 issues are part of a bigger issue or if they are unrelated. It takes an unclean shutdown to get the server back to a state where it is usable. However, the server only stays usable for a short time before it becomes inaccessible again. I just replaced the CPU and the Motherboard in the system so I'm not confident that either of those is the issue? Is this a bug in unraid 7? would a recommended fix here be to try to downgrade to unraid 6.12.15? Diagnostic zip attached star-command-diagnostics-20250627-0905.zip

I took apart my server fully and noticed that I had bent pins in the CPU slot of my motherboard. I had installed an LGA 1700 Thermalright contact frame at the beginning of my build. After I started having these issues, I did a little bit of research. What I found was these frames can cause issues. One of which is they really easy to overtighten and in doing so can bend pins in your CPU slot. If anyone is running into issues like this and you use a contact frame check your CPU slot because that could be the cause of your grief.

Do failing flash drives cause the issue called out in the call trace? Would it be beneficial to try and replace the flash drive to see if that helps?

I will try this, but I'd had the same configuration up and running without issues for months. Also, one of the things I left out in my troubleshooting steps was that I ran memtest before I did anything else, which passed. It would be coincidental for ram or CPU to fail at the exact time I replaced a couple of drives. May I ask where in the provided logs were you able to identify that the Unraid driver crashed. This information would be useful in the future.

I upgraded 2 my cache pool with brand new NVME drives. I attempted this task without watching a video on how it's done because how hard could it be right? Now I'm paying for it because I am having a multitude of issues due to my stupidity "Troubleshooting". I just hope I am overthinking things, and this is a simple fix I am missing. I don't want to have to start from square one and lose all my data. If anyone could throw some help my way it'd be much appreciated. I've added a lot of information below as well as my diagnostics zip. Unraid Version 7.0.1 System Board: MSI Z790 Tomahawk Max Wifi CPU: Intel i9 14900KS Memory: 32gb x4 Vengeance DDR5 5200MHz My Purpose: My 2 Intel SSDs were failing so I upgraded them with 2 1tb Crucial NVMEs. I also wanted to add another 500gb nvme for my /system/* and /appdata folders to live on. My process: I left in the 2 failing disks and added the NVMEs I created a mirrored BTRFS cache pool named Nvmecache with the 2 1tb NVMEs to use as main cache I create a BTRFS cache pool named appdatacache with the 1 500gb nvme to use for my /system and /appdata folders I changed the appdata and system shares storage cache => appdatacache I change all other shares from cache => nvmecache I invoked mover. After letting it go several hours it didn't look like mover was doing anything, so I started moving things manually through terminal (Big Mistake on my part). /mnt/user/system => /mnt/appdatacache/system /mnt/user/appdata => /mnt/appdatacache/appdata Changed docker from macvlan to ipvlan after having issues with random system freezes. Issues I'm now facing: My docker containers immediately stopped working. After having docker issues I recreated the image file. This has been done multiple times in an attempt to troubleshoot issues. I installed an initial container (Plex-Media-Server) and started library scans before bed last night and when I checked it this morning the container was unresponsive and become unhealthy after I attempted to restart it. I am unable to remove/stop/purge, when ever I try to do anything with this container in CLI I get "Error response from daemon: cannot remove container "/Plex-Media-Server": could not kill: tried to kill container, but did not receive an exit event" When I try from gui I get an execution error. It takes rebooting the system to get stop or remove this docker. Parity sync seems like it is running and starts out fast. After it's been running for a short time, it slows down considerably It's been running 2 hours and has only completed 0.7% Host refuses to reboot/shutdown via CLI or Webgui when parity is "running" and the Docker container is unstable. The only way to reboot is to poke the power button. Things I've tried: I moved folders back to their original locations /mnt/user/system /mnt/user/appdata I've recreated the docker.img file multiple times I've tried using a docker folder instead of an image file I use new permissions to set defaults on disks and shares. I've booted into safe mode and get all the same issues there I've tried remove and recreate containers in live and safe environments deleted the docker container manually from /var/lib/docker/containers/ As I think of more stuff that I tried I will add them to this thread. Also please let me know if more information is needed. Thanks in advance, Dabbler455 star-command-diagnostics-20250502-1050.zip

Is this case still available and can you add some photos to your posting?

star-command-diagnostics-20231231-1628.zip Out of sheer stupidity I initiated startx from terminal workspace 1 (alt+ctrl+f1) in an attempt to start the gui from command line only mode. Now when I attempt to boot into Unraid with GUI I get a blank screen on the default GUI workspace (ctrl+alt+f7) that never progresses to the GUI. If I switch to f8-f11 I get a black screen with a flashing cursor in left. I do have a p4000 quadro installed as well as an Intel onboard GPU via my i9 processor. I'm assuming that when I initiated X11 that it switched somehow over to the P4000 video card but I'm not confident on that. ***Update: I've rebooted the server in safe mode with GUI and the local GUI is accessible there so it seems like a plugin is causing my grief. Whats the best way to track down with plugin is the culprit?*** Things I've tried: Moved my display port cable from onboard port to the P4000 (no output) Removed Intel_GPU_Top because of the known GUI issue and rebooted. tried to restart rc.4 and rc.4.local from GUI mode workspace 1 I've also tried to initiate the slim command locally which didn't load the GUI added i915.conf to /boot/config/modprobe.d and rebooted I'm looking for suggestions on what else to try. Has anyone else done something similar and been able to fix it or am I the only lucky one Any help I can get would be appreciated. I've added the anonymized diagnostics zip. Let me know if there is any other information that'd be helpful in figuring out this issue. Thanks

I do the same with cloudflare DDNS, wasn't sure if there was a way to accomplish it using a cloudflare SSL cert. Sounds like it isn't supported by minecraft yet

I really just want to obscure my wan IP and be able to give my nephews a URL to connect to my server (i.e minecraft.somedomain.com)

Has anybody figured out a way to add a Cloudflare SSL cert to this Minecraft container for purposes of proxying the external facing IP? Is so how did you accomplish it? If it cannot be done this way than what are the best practices for securing an external facing Minecraft server?

And it appears that I'm in the wrong forum!