brutalmethod

I've use AI to sum up the problems my english is not my native language. Hi everyone, I'm looking for help diagnosing a persistent system freeze that I have been unable to solve after several weeks of troubleshooting. HardwareUnraid 7.3.1 Huananzhi X99 F8D Plus Dual Xeon E5-2697A v4 64GB ECC DDR4 (2x32GB SK Hynix RDIMM) Intel Arc B570 (used for Jellyfin hardware transcoding) 2 × LSI SAS9300-16i (SAS3008 IT mode) Multiple HDDs (24TB parity) Two onboard Realtek RTL8125 2.5Gb NICs (bonded in Active Backup mode) The ProblemThe server randomly freezes completely. When it happens: WebGUI becomes unreachable. SSH stops responding. Tailscale reports the server offline. Nginx Proxy Manager returns 504 Gateway Timeout. Docker containers become inaccessible. The only recovery is a hard power reset. Sometimes Jellyfin can still open its homepage briefly through the local IP, but playback never starts. Eventually everything becomes completely unresponsive. When does it happen?The freeze seems to occur during relatively heavy I/O activity, for example: Unbalance moving files Jellyfin playback / transcoding General file activity However, it is NOT easily reproducible. The server can sometimes run for over a day without problems, including normal Docker usage. What has already been checkedStorageParity check completed successfully. 24TB parity finished with 0 errors. Filesystems were checked and repaired previously where needed. No obvious disk errors found. HBABoth LSI controllers are detected correctly. PCIe link status: PCIe Gen3 x8 PCIe Gen3 x8 No mpt3sas reset storms appear in the logs. NetworkUsing Realtek r8125 driver. No evidence of: link down NIC reset transmit timeout Bond status is healthy: Active Backup Link Failure Count = 0 on both interfaces CPU / MemoryNo overclocking. Using ECC RDIMM. Fix Common Problems reports Hardware Failure because the diagnostics contain repeated: mce: [Hardware Error]: Machine check events logged However, I cannot determine what hardware component is actually generating the MCE. GPUIntel Arc B570 is detected correctly. Hardware transcoding works normally until the freeze occurs. Additional observationsEarlier I was powering CPU1 and CPU2 from different PSUs because one EPS cable was too short. I have since rewired the system so that each CPU receives dedicated power correctly. After rewiring, a full parity check completed successfully (0 errors), but the random freezes still occur. DiagnosticsFix Common Problems reports hardware failure because of repeated Machine Check Events. Diagnostics are attached. QuestionsHas anyone experienced complete freezes like this on a Dual Xeon X99 platform? Could this be related to: Huananzhi X99 motherboard? PCIe subsystem? SAS3008 controllers? Machine Check Events? BIOS settings? Is there anything specific in the diagnostics that points toward CPU, RAM, motherboard, or PCIe instability? Any suggestions would be greatly appreciated because I feel I've exhausted the usual troubleshooting steps. Thank you! tick-unraid-diagnostics-20260628-1057.zip

Thank you so much! I'll definitely give this a try as soon as my parity check finishes. Quick follow-up question: Since I will be switching to a Docker image file and I'm running around 5-6 containers (including Jellyfin and the full *Arr stack), what would be the recommended size for the docker.img? Can I just set it to a very large size (like 50GB-100GB or more) just to be safe, or does a larger size negatively impact performance?

Hi everyone, I am experiencing an issue where multiple, unrelated Docker containers (Jellyfin, Radarr, etc.) are randomly crashing at different times on my Unraid server. The container logs consistently show Exit 139. In Jellyfin, this often causes the container to drop into an (unhealthy) state due to websocket timeouts and video stream packet corruption right before the crash. My Hardware Specs:CPU: Intel Xeon E5-2697A v4 Motherboard: HUANANZHI X99-F8D PLUS Memory: 64GB DDR4 ECC Server RAM Cache Pool: 2x NVMe SSDs in a ZFS Mirror (where appdata is hosted) What I Have Tested So Far:Memtest86+: Since Exit 139 is a Segmentation Fault (pointing to memory access issues), I ran Memtest86+ for nearly 8 hours (completed 1 full pass) and it returned 0 errors. The physical RAM sectors appear to be fine. ZFS Status: The pool shows as ONLINE, though I did find a corrupt file/inode (????????? permissions) inside Radarr's appdata directory right around the time these crashes started happening. System Boot Issue: After forcing a reboot to clear the app crashes, my motherboard temporarily hung at Debug LED Code 92 (PCI Bus Initialization). The Dilemma:Since Memtest passed completely, what else could be causing random Exit 139 segfaults across multiple containers? Could it be silent data corruption caused by memory timing instability on this Chinese X99 motherboard under heavy OS workloads (even if Memtest passes)? Or is it more likely that a failing NVMe cache drive/controller is causing file system corruption that triggers these segfaults when Docker tries to read the corrupted data? Any insights or troubleshooting steps on how to isolate this would be greatly appreciated. Thanks! tick-unraid-diagnostics-20260430-0921.zip

I'm using Steam headless just for local network transfers, but currently the maximum speed is only 1 Gbps, even though my entire system is 2.5 Gbps. Could you please tell me if there's a solution? Thank you.

i'm new to setup lancache frontend and backend too. can acess webui but nothing to see . i can see the frontend version but not for backend. if there any help would be appreciated.

it's 8125 i've found it on ca apps . thanks alot

the last part .about extra driver where to find and check that's work properly mine is TP-Link TX201 Realtek RTL812

ok i better get home then re-enabler that onboard lan again. appreciated

thanks all but in network setting i couldn't find network rules (i'm on 7.1.4). do i have to disable docker and vm to see it? appreciated

Dear Unraid Community, I'm incredibly frustrated and hoping for some guidance here. I've been struggling to get my new 2.5G PCIe NIC working properly with a static IP on Unraid (version 6.12.10). Apologies if this has been asked many times before, but I'm truly at my wits' end. My Goal: To replace my old onboard LAN with a new 2.5G PCIe NIC and have Unraid use a static IP address (specifically 192.168.1.111) for all services, just like my previous setup. My Setup & What I've Tried So Far: Hardware: Unraid Version: 7.1.4 New NIC: PCIe 2.5G TP-Link TX201 Mainboard: Has 2 onboard LAN ports. Router IP (Gateway): 192.168.1.1 Router Subnet Mask: 255.255.255.0 Router DHCP IP Pool Range: 192.168.1.33 - 192.168.1.254 Desired Static IP for Unraid: 192.168.1.111 Initial Problem: New 2.5G NIC detected as eth2: When I first installed the 2.5G NIC, Unraid detected it as eth2 (likely because my mainboard has two onboard LAN ports: eth0 and eth1). Solution for eth0: To make the new 2.5G NIC eth0, I went into my mainboard's BIOS and disabled all onboard LAN ports. After disabling onboard LAN in BIOS and rebooting, the new 2.5G NIC was successfully recognized as eth0. This part works when Unraid uses DHCP. Current Problem: Static IP & Networking Issues: Once I have WebUI access (via DHCP with the 2.5G NIC as eth0), I try to apply my desired network settings (like setting eth0 to Static IP 192.168.1.111). I also tried to disable "Bonding" in the Unraid network settings (as I don't need it for a single NIC). However, every time I "Apply" these settings (Static IP, disable bonding, etc.), after the server reboots: The LAN status light on the 2.5G NIC goes completely out. I lose all network access to Unraid (cannot access WebUI, server does not appear in router's client list). The only way to regain access is to connect a monitor/keyboard directly, stop the array, rm /boot/config/network.cfg, and reboot. This forces Unraid back to DHCP, and I can access the WebUI again. What I Don't Understand / Need Help With: It seems like any attempt to apply manual network configurations (static IP, disabling bonding) causes the network to completely fail. I suspect it's related to: IP Conflict: My desired static IP (192.168.1.111) falls within my router's DHCP IP Pool Range (192.168.1.33 - 192.168.1.254). Could this be causing the NIC to go offline completely? A misunderstanding of Unraid's network configuration process: Am I missing a crucial step or setting that needs to be done before applying static IP? For example, is there a specific order for disabling bonding vs. setting static IP? Any guidance on how to properly configure my 2.5G NIC with my desired static IP without losing all network access would be greatly appreciated. I'm really pulling my hair out here trying to get this working. Thank you so much in advance for your help! (my english it's not great . so i've use what i ask ai to sum thing up)

i'm new here. is this still work in 2025?

Security flaws found in all Nvidia GeForce GPUs. Update drivers ASAP! https://www.pcworld.com/article/2504035/security-flaws-found-in-all-nvidia-geforce-gpus-update-drivers-asap.html is this will effects unraid with nvidia GPU? thank you

Sorry if it has been asked. I'm also new to unraid. Actually I want to use dynamix stop shell plugin. (already installed) because my unraid won't reboot and the GUI crash (done powerdown -r and it's not work). All I could do is shh. I don't understand how to use this plugin and I couldn't find the tutorial anywhere. Call me stupid but I've tried for many days. helped would be appreciated (sorry for my english)