50hzhum

I was running the most recent BIOS when I set up the server a few months ago, but has been a new one since. Updated that and then set RAM to a lowly 1600 MHz. First parity check with 32GB completed as normal. Thanks again @JorgeB

Hi guys, Having a weird issue that I've been trying to resolve for a while now. My system (is supposed to) run 4 x 8GB RAM. When booted in this config, the system runs as expected for what can be weeks. File shares, dockers, VM's all working correctly. I've found that when running a parity check with 32GB RAM, the server will stop working but the GUI works correctly - I can switch between Dashboard/Main/Shares etc - but in the background nothing is working. I'm unable to access the shares or use media players etc. I'm also unable to reboot or shutdown once it's failed this way. RAM speeds are set to 1866MHz as per recommend settings at https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173 I've tested all the RAM - initially a 24 hour memtest with 32GB didn't flag any errors. I've since run each matched pair of RAM modules in both slots 2+4 and 1+3 (4 tests total), running a parity check each time as well as leaving the system running for a few days afterwards. The parity check completes correctly and the server carries on running without issue. When the system freezes, even though I can navigate to the diagnostics page, I'm unable to download anything. I set up a localsyslog in hopes it might capture something, and have attached it. The most recent failure was found in the morning of October 4th. I've also attached diagnostics from the recently rebooted 32GB system. No parity checks scheduled for another few months so I'm hoping it stays up until I can figure out a solution. Thanks in advance! syslog-192.168.1.201.log tower-diagnostics-20251005-1440.zip

Finally got some time to test everything. Ran memtest and got a heap of errors. Narrowed it down to a pair, and then a single stick of RAM (recently purchased I might add). Just received warranty replacement RAM, have run memtest on it and it passed with no errors. Haven't had the chance to properly test the server yet, but with such glaring failures in memtest I'm pretty confident that this is the root issue, so I'll mark it as a solution. Note for newbies - run memtest first. Thanks @JorgeB for holding my hand like I was a child haha.

Finally had another dropout during daily use. Diags attached this time since I was at home! tower-diagnostics-20250827-NoUserShares.zip

Dropped my RAM speeds to the ones suggested in the linked article, and then finally had the need to push a bunch more files through to the server - under 1GB, but a lot of files (over 100,000). Unfortunately I've had the same issue where the User Shares disappeared during the transfer. Didn't get the chance to download the diagnostics as I remote booted the system to allow others to keep using it. Any other ideas from my initial post? Cheers

I was unaware of the RAM limitations - thanks for that @JorgeB! I'll check my speeds next time I reboot and see how it performs moving forward.

Hi all, I'm a relatively new Unraid user and I'm having a few issues. A couple of times a week I'm losing access to either my Docker Service or my User Shares. It's never at the same time, but either of them happening will mean I need to reboot my system. After a reboot everything comes back up as expected and then runs for a couple of days. The errors generally occur when my partner is watching media on Jellyfin, but I've also had it pop up while writing files to the cache/array. From what I've seen from other posts, segfaults are usually a CPU or RAM issue. With a young son I don't have heaps of spare time to troubleshoot, so I was just wondering whether there's a way that I can narrow down which bit of hardware is likely the issue, or if it's something else entirely? Quite happy to run through the a memtest, but if it's a CPU or NVMe drive I currently don't have anything I can swap out so I'll have to deal with it for a wee bit longer. Thanks in advance! Being able to save a bit of time by decoding the diagnostics would be a welcome help. Also - please no judgement for the single drive pool with appdata etc on it - I'm saving for a second drive at the moment :) tower-diagnostics-20250725-2114.zip