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.

Well I did warn everybody that I'm a windows guy so my point of view is a bit different than unraid reality .. But it does sound we are all on the same page now. Thanks again for the follow up and the additional information.

That makes sense. I could have thought of that myself When I first created it I was afraid of using cache for that folder as I have several very large files and I figured I might manage to fill it up before the mover invokes. However I obviously managed to do that even without it - lol. Sounds like a reasonable solution - I'll do just that. Thanks!

Sorry I probably didn't explain this correctly. Bear with me while I try to make sense out of this Here some background information and maybe things will be clearer: I have an application/docker that downloads files from the internet. These files are stored on a folder/share that uses only the cache drive, not the array (therefore mover won't touch these files). The reason I need to set it up this way is because of the drive performance. Files stored under the array cannot keep up with my gig fiber connection but files on my cache drive can. So as files are downloaded and when I no longer require them to be accessible on the internet (which can be weeks) I move them manually onto the array for long term storing and where performance is no longer an issue. That's when I use MC to move the files from the shared folder that's marked to use SSD/cache drive only to a shared folder that is marked to use the spinning drives/array only (no SSD). I tried this over SMB/windows (copy/paste/move) for a while but the performance is sub-par while using MC is much faster as I don't need to involve my workstation as a middle man. However as described above MC actually doesn't really move the file(s) it only places "shortcuts" (for a lack of a better word) on the array while leaving the real file on the cache disk. In terms of how the file structure looks like after I "move" a file via MC: * Here is where the file shows up (from a global perspective): /mnt/user/download/file1.mov * However when looking at where the file has been physically stored it actually is here: /mnt/cache/download/file1.mov * Where I was hoping to find the file was here: /mnt/diskx/download/file1.mov tower-diagnostics-20181127-1617.zip

Hi Guys, I've been using Unraid for almost 1 year now and loving it. At first it was a bit scary (being a windows guy, running Linux for all my important stuff) and not knowing how to handle a problem when/if it shows up. However by now I feel fairly confident I can handle a good chunk of things on my system. BUT there is something I recently came across where I could use some advice: I have a 500GB M2.SSD for my cache drive and for the first time I accidentally filled it up without realizing it (at first). This of course caused all kinds of crazy things to happen. The first thing I noticed was several of my dockers crashed and could not be restarted, then I saw lots of errors in the Unraid system log and realized the only real fix is a reboot (after freeing up some space on the cash drive). After a quick reboot and everything was good again I started poking around what caused my cache drive to fill up in the first place. I found out the problem was partially Midnight-commander or my use of it. When "moving" files around from my share folder running solely on my SSD to any other share that runs exclusively on the array (excluding cache drive use) it doesn't actually move the files. It simply creates a shortcut (there is probably a better Linux acronym for this but coming from Windows that's what it looks like to me) on the array but leaves the "meat" on the SSD cache drive. SO after doing this for a while and not knowing what I unintentionally did I filled up the SSD yesterday while moving a 100gb file. So after all this here the question: Is there a better tool than Midnight-commander to move files on my unraid without involving my windows system (which takes a lot longer for larger files) or is there an application like the mover that will see those left over files and move them? I noticed that the "fix common problems" app actually warned me about files on my cache for which there was no official share for but I didn't quite realize what that meant until yesterday. So Unraid/fix common problems did see the problem creeping up but I didn't know what to do with the information until it was too late. However I'm thinking now if unraid/fix common problems can see it happening (slowly or not) isn't there some app or function that will tackle this so I don't have to manually move files from my cache mount to my disk mount? Again the problem was that I moved files from my shared folders not from the actual disk mounts.

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.

Thanks for all the advise received so far. I did see some past issues with Ryzen but haven't seen anything recent so I assumed it was resolved by now. I guess I'll give it a try with the trial and see how things goes. Luckily I'm not moving anything to the server as of yet, so any issues I run into would not cost me a huge headache, I'll just wipe it and try again.

Hi Guys, I've been lurking around for the past 2 weeks, reading up on unraid, dockers, hardware requirements and common problems. I'm at a point where I have the hardware sitting next to me and needing advise if I should go with unraid and if so what the best way to set this thing up. I got the basic installation steps and how to install dockers (again, only read about it - haven't touched a thing yet). Here is what I have: Motherboard: MSI B350 AMD chipset CPU: Ryzen 7 1800x PSU: EVGA 650W Mem: 32GB DDR4 3200 HDD: 4x 6TB WD Black (1 Parity, 3 Storage) & Samsung M.2 500GB (Cache) GPU: 710gt (just to get through the basic installation) PCI-e card: SYBA SI-PEX40108 (to add 4 additional SATA ports for future expansion) Here is what I want to do at the moment. Maybe more down the line but this is bare minimum: * Plex media server (saw the docker, so this should be a no-brainer) * qtorrent (everybody refers to transmission but I really like and got used to qtorrent, so my heart is kind of set to it) * DVDfab Video conversion - Occasionally I would like to run DVDFab to convert movies from x264 to x265 At the moment I manually transfer files received through qtorrent to my movie folders where Plex picks it up and does it's thing. If I have 1 docker for Plex server and another one for qtorrent how do I easily move files from the download folder to where Plex looks? Should I maybe setup a windows VM for qtorrent and DVDfab and RDP into it if I want to convert files? I could easily move files through network shares if I have to. What about the cache drive? I understand it's purpose and that files get moved from it to the unraid later but I'm not sure how that will work with the above mentioned applications. Should I have Plex download and read all the media files to it but what happens when it moves off the cache drive? is there some sort of pointer/shortcut that tells plex look at the drive array instead of the cache disk to find it? Same for qtorrent: downloaded torrent files are initially on the cache, get moved over night to the disk array and it still finds them later? This part is a bit confusing to me. Generally speaking I get the cache drive but I'm not sure how that works in setting it up in unraid and pointing to it for config files or meta data, etc. I'm looking for the most efficient way to complete the tasks I'm doing right now just through a dedicated unraid server. I would appreciate any ideas or best approach so I can set this up via the trial, verify it works as intended and join the unraid community. Thanks in advance!