sheldon

my 2 cents: Your Memtest screenshots show that the BIOS test detected 4000 MHz corsairs while the test from Unraid shows you are clocking them at 4800 MHz. Did you by any chance leave the memory clock settings on AUTO? Most motherboards are horrible at auto detecting and setting correct values for memory. It's possible on your previous test with the BIOS the memory clocked at the default 4000 Mhz speed while on later reboots it thought your system could handle more and started overclocking (they call that AI overclocking but it's really bad in my experience). Anyhow, my suggestion is to verify what settings you have for the memory/CPU speed in the BIOS. Disable any auto overclocking features, use XMP when possible and set the correct voltage for DDR5 as per the Ram sticks you bought. Run the test again and if it still fails maybe something else is going on but it's also possible you simply haven't found the perfect voltage/speed/CAS settings for your memory. I run an AMD setup for Unraid but even on Intel the biggest problem I always face is finding the right settings for memory. It can take hours to find the perfect sweet spot to run stable (even without overclocking).

Reporting back with final fix/solution During the Unraid upgrade to 6.12.6 something happened to the Plex docker and it updated itself to the BETA release branch instead of the STABLE release branch. I have Plex Pass so it makes sense that I technically have access to it but I never opted in, still my docker ended up going there and that's what has seemed to cause all my issues. When I tried to manually set a version by specifying a version through repository I ended up getting an orphan image and PLEX was completely gone Well I downloaded Plex docker again and noticed repository went from linuxservers to lscr.io but I have no idea if that just was because it was an old docker pull previously. The new docker now pulls the latest stable release automatically instead of BETA. Anyhow, I have survived 2 full nights sine the rebuild and my CPU has been hurting for a full 24h to re-analyze all the media files (55TB takes a while), so I'm sure that CPU/RAM clocking is good or would have crashed during those analyzing times. Long story short - Issue was a bad Plex docker taking the server down. Check your Plex console and logs to see what it's doing and what version you are running - if you ended up on the 1.40 branch you on the BETA and could explain random lockups.

My server finally survived a night when disabling PLEX before it's maintenance starts. Now I have to dig into Plex and see what causes my server to crash during maintenance since it runs fine throughout the day with multiple 4k transcodes (I don't use HW transcode at this time). I'll update / report back once I have a solution in case someone else has the same problem. I did read through the support forum for the linuxserver.io group and there are a few reporting plex crashes as well as extended power consumption beyond the maintenance window since the latest updates- my hunch tells me that it might use all my resources and crashes unraid or maybe it analyzes a file that is somewhat corrupt and locks everything up trying to access it? Not sure but I'll dig into it further.

First of all - I think this might be my very first cry for help since I got Unraid, so be gentle to me Let's start at when this was still working great: 6.12.4. I had it running for about 100 days without issues. Then randomly the parity drive failed on me. Turned unraid off, checked and re-seated the cables for the affected drive and powered back up. Then ran a memory check as well as SMART self-test. All came back clear so I had unraid simply rebuild the drive without issues. Gave it a few days and noticed that PLEX was shut down by Unraid for filling up my 32 gigs of ram according to the logs. It's never done that in the years of running unraid so I started limiting PLEX Memory allocation to 16GB but all it did was continuously giving me warnings that memory was full and unraid shut the process down. I removed the memory limitation again and the alarms in the logs stopped. I wrote it off as a fluke for the time being but figured I should mention it in there just in case it's important. Since everything seemed fine at the moment I decided to finally pull the trigger and upgrade to 6.12.6. I ran it for about 5 days or so with nightly lockups. Got tired of it and decided to downgrade to 6.12.4 again but the nightly lockups continued. Stumped that it didn't fix it I started a barrage of "fixes" but none of them fruitful To help me troubleshoot I did start to copy the syslog to flash but it doesn't record anything useful. it simply stops recording when unraid hangs. Funny thing is Unraid will continue to ping BUT nothing works - can't access GUI, can't SSH, can't access shared drives, nor dockers. I tried hooking up a monitor but also get no output there. Now here are the things I've tried or have currently set: -Upgrade BIOS to latest and greatest -Disable all C-states (it's a Ryzen 5950x build on a 570x chipset) as well as AMD Cool 'n quiet to be on the safe side - Power supply state is set to normal during idle -Switched MACVLAN to IPVLAN as well as removed bonding (that was how I got to 100 days running before upgrading). -Copied the contents of the flash drive from my previous version on 6.12.4 over in case the built-in downgrade doesn't work so well -Ran memory test with multiple successful passes It always seems to lock up between 2am and 7am, regardless of when I start Unraid. That does seem like some scheduled task is causing all this but all I can think of is either the mover (3am) or PLEX tasks (2am through 5am). I'm going to shut down PLEX tonight before I get to bed to test it out but I was hoping I can have someone look over my request in the meantime to collect some additional ideas or maybe something I completely overlooked. Thanks in advance! tower-diagnostics-20240104-0806.zip syslog-01-2024

Great docker -thanks for the hard work to get this going! Now question: is there a way to link my hex client (windows) with the docker? -You may wonder why do this? Simple, my unraid docker runs all the time so all the messages posted in a channel are always there, while my windows client disconnects whenever it goes to sleep or I turn it off (therefore losing the history of what was posted while I was gone). In addition the notification/flashing isn't really notifying me of new messages when running in the browser/docker. If I could link my windows client with the docker somehow, it could connect showing all the previous posts and alert me when new messages appear.

I was just about to ask for the same thing when I saw they already completed this request yesterday :) "08.06.18: Bump qbitorrent to 4.1.1." Thanks guys!

Thanks Trurl - I'm truly a noob for not thinking of including that right away Here it is. tower-diagnostics-20180416-1651.zip

Hi Guys, I feel bad posting for the first time in the support area with a problem rather than a praise. So let me say first of all - I appreciate all the work and effort that is put into supporting this docker and features Now let me get to my problem and hope someone has a great idea: I've been running Plex server on unraid for about 6 months without any issues whatsoever. However within the last week or 2 I get frequent Plex crashes and the only thing I can see is within the unraid log file is this: CPU: 7 PID: 21779 Comm: Plex Media Serv Tainted: G D 4.14.26-unRAID #1 This message appears every time Plex crashes. Within unraid the docker appears to be still working fine but the only way I can get it to work is his the restart button on the docker. I'm running unraid on version 6.5 and all other dockers seem to be working fine and haven't crashed once in the same time Plex has crashed 10 times. Does the above error message indicate anything useful? I'm not sure what to do with this. Is this more of an unraid issue or Plex? Since Plex is the only thing that has crashed on me so far I figured I start here.