Leaderboard

So I have been watching this thread for a while...as I was the guy that originally had the problem. Since I downgraded back to 6.6.7, I have had zero problems with database corruption. I have NOT changed the data to point to a single disk, although I planning on doing it this weekend and testing. From the answers here though...that is not going to fix the issue. The corruption is still occurring for some people. I've read through some of the other threads that are "just plex" or some other application...and people are pointing them back to the application creators for fixes. It is NOT just happening for me with Plex, but with every application that uses the sqlite database. Like some of you, I'm questioning things in the kernel or something else that changed in 6.7. And I'm not crazy about updating again until I see an iteration of the OS that provides some fix. Just my thoughts....and yes, I am an absolute newbie to the system. Less than 1 year. thanks rm

This is a major issue and seems to not be getting the attention it deserves. I’m pretty much begging for this to get priority by the unraid devs. My 6.7.0 system is now so unreliable. Data loss or corruption needs to be a top priority. This isn’t isolated. We can point to many people who have this problem. I love unraid and this community, but right now unraid is causing me and a lot of others much pain. I’m willing to donate money for a fix.

Did some numa node & infinity fabric benchmarking CPU's and a graphics card (GTX 980ti Classified). I ran 3D Mark Timespy with the CPU's on the same numa node as the card and off and what I found was interesting. The GPU scores were in the same range but the CPU scores dropped off node . 2.2% slower on Timespy Extreme 4K and 9.5% slower on the regular Timespy. A Passmark CPU benchmark with no graphical aspects other than Windows itself scored 0.6% faster on node. Each benchmark was repeated 5 times and the results averaged.

Do you know how to do this? Then, looking at the SAB website, it appears you can specify different folders for incomplete and complete downloads: https://sabnzbd.org/wiki/configuration/2.3/folders So, it looks like all the pieces are there for you to try it out for yourself.

I don't do any NIC passthrough since 2x1Gb is plenty for 4 machines and some dockers to share. Since mine is mostly setup for a gaming machine, I rarely saturate the network. I haven't measured load yet- but can tell you that I can max all cores and GPUs without hitting my 1000w ceiling. Heat isn't too terrible and the machine is in the same room as the 4 gamers playing. It does make some noise at full load but hardly more than my previous single gamer setup. The heat is noticeable after a while and we may kick on the AC that blows from the ceiling to keep us cool, but my rig never thermal throttles- it's temps stay in 55C area on CPU and 75Cish on GPU for max. Sound issues just required me to run the msi fix and use the hdmi sound from each card. I have no sound issues and don't pass the sound card to anything. I also don't use any of the on board USB and got a card with 4 controllers to pass one to each system- saves me a ton of headaches with peripherals. I agree with bastl- threadripper is a better way to go since it has so many PCIE lanes and cores available. Unraid does need some CPU power for itself and I have found that leaving 2 cores/ 4 smt available for it is the best plan for it to breathe freely. Plus- as he indicated- if you want to BLEED go CUTTING EDGE. It will definitely hurt until it heals with patches and updates.

I manage to work with forge.. you have done great work.... I appreciate your help. As for spigot server i do not know a lot.. I tried local but as I saw it wants only mods from the site and not some that i want...

Support for Ryzen 3000 no one really knows yet, what will change and what kernel tweaks are needed with this new chips. Maybe it works right out of the box, maybe not. Always keep in mind the TR4 platform has way more PCIe lanes available and you can directly connect more devices to the CPU. Sharing the lanes between the slots you always end up in a situation, where the devices are grouped together. For passthrough this isn't what you want. Each manufacturer is slightly different how they handle the groupings in there BIOSes and with each revision it can change. The final versions aren't out yet. On most x399 if they have multiple Nics, they are grouped together. On some boards you can split them with ACS override, on some this isn't possible. This also depends on the BIOS revs you're running. If you can, avoid the ACS patch and use a dedicated ethernet card. On TR4 no problem, you have enough slots and lanes 😁

Look at the status before and after applying them. Any that stay mitigated are being handled via microcode Sent via telekinesis

Can you check this setting:

Best ports, in decreasing order of "best-ness": Internal USB 2.0 ports. You can buy a cheapo USB2.0 internal to external adapter (basically a small little cable with internal USB 2.0 plug on one end and external USB2.0 socket on the other) and plug the Unraid USB stick on there. Alternatively, you can use your case USB2.0 header or some all-in-one USB2.0 internal hub. Reason for "best-ness": (1) USB2.0 has the least compatibility issues when booting (almost none); (2) few people have any other use for internal USB2.0 headers and (3) the USB2.0 motherboard controller can't be passed through to a VM even with ACS multifunction (many have tried and many have failed). Internal USB 3.0 ports. Similar to USB2.0 above, just that USB3.0 ports sometimes have boot issues. External USB 3.1 port (the red one at the back). This port can't be passed through to a VM similar to the internal USB2.0 port but give it's externally available, you might want to use it for some other purposes instead of booting Unraid (about 10s saving in boot time and that's it). External USB 3.0 ports (the 8 blue ones at the back). These are on their own controllers (2 controllers, 4 ports each) and in their own IOMMU group so they can be passed through to your VM with ease (need vfio stubbing). Note that they have identical IDs so if you stub 1 controller, you will end up stubbing both (I vaguely remember there's a way around that so you might want to google if required). USB 3.1 type C - because why would want to do that? Highly NOT recommended to overclock Unraid. Instability on a server is at best a nuisance (e.g. needing to run Parity check whenever things crash) and at worst causing crippling issues (e.g. data corruption). You are better off to use AMD Precision Boost. It's an effort-free per-core on-demand overclock. Sure all-core boost can only reach 3.8GHz but that's only 5% lower than your best-effort overclock that more likely than not is less stable and definitely uses a lot more power. On a side note, don't use the latest BIOS (AGESA 1.1.0.2), use the one right before that (AGESA 1.1.0.1a). The current BIOS has AMD PB cut down a little bit on the voltage which runs 1-2 degrees cooler but has caused me some unexpected stability issue with certain workloads.

Did you read the link the prompt recommends for Amazon? I'll include it again for you. It explains your problem up front in the "important section" https://rclone.org/amazonclouddrive/

Well the good news is that the server is no longer accessible from the internet- not sure if that means that they finally fixed it, or if it is still just turned off. I'll check on it for a while to make sure it doesn't come back up.

I sent info to LT- they will contact them. I powered it down for now.

This is a nice tool! Once it is installed it handles the installation of other Plex channels for you. I pretty much followed the instructions from here: https://github.com/dagalufh/WebTools.bundle/wiki/Installation Updated 9/14/2017 Guide to installing the WebTools 2.4.1 channel in Plex High level overview These instructions appear quite long, so here is a high level overview to show that it isn't really that complicated: Download the WebTools zip file, unzip it, and place it in the Plex appdata plugins directory. If the copy fails, fix the permissions and try again. After a delay the channel will automatically be installed and you can access WebTools here: http://<unraid IP address here>:33400/ Short instructions Download WebTools.bundle.zip from https://github.com/dagalufh/WebTools.bundle/releases/latest and extract it to your desktop. Locate the "Webtools.bundle" folder. Copy the Webtools.bundle folder to your Plex Plug-ins directory here: \\<tower>\appdata\<Plex appdata>\Library\Application Support\Plex Media Server\Plug-ins If you get a permission denied error, you'll need to SSH to the server and: cd "/mnt/user/appdata/<Plex appdata>/Library/Application Support/Plex Media Server/" chmod a+w Plug-ins then try copying the directory again When it is done you should be able to navigate to: \\<tower>\appdata\<Plex appdata>\Library\Application Support\Plex Media Server\Plug-ins\WebTools.bundle\Contents If you are able to pull up the Content directory directly under Plug-ins\WebTools.bundle, then everything is in the right place. Wait a few minutes, then login to Plex. Go to the Channels area and you should see WebTools (although if you click the image the wrong url will be displayed.) If it isn't listed, wait longer and try again. If you want to kick-start it, restart the Plex docker, wait some more and check again. Once you see the channel listed, you can access WebTools at this url: http://<unraid IP address here>:33400/ Long instructions: "tower" is the default name of an unRAID server, but you may have renamed yours. Wherever you see <tower> written here, substitute the name of your server, without the <> characters. Open your unRAID webgui and go to the Dockers tab. Click on the Plex icon and choose Edit. Find the "host path" that corresponds to the container path "/config". It will look like this: /mnt/user/appdata/<Plex appdata>/ Make note of the folder name that appears after "appdata" and use that wherever you see <Plex appdata> in this guide. In other words, if your host path looks like this: /mnt/cache/appdata/Plex Media Server/ then your <Plex appdata> is "Plex Media Server". From your desktop computer, navigate to the Plug-ins directory here: \\<tower>\appdata\<Plex appdata>\Library\Application Support\Plex Media server\Plug-ins Download Webtools.bundle.zip from https://github.com/dagalufh/WebTools.bundle/releases/latest and extract it to your desktop. Locate the "Webtools.bundle" folder. Copy the WebTools.bundle directory from step 4 to the Plug-ins directory you located in step 3. If that copy works, great! If you get a permissions error you will need to SSH in to the server to fix it. Once you have SSH'd in, you need to cd to the Plug-ins directory. We'll do this in steps. I recommend copy/pasting what you type and the results into a text file so you can ask for help if there are problems. If you get an error message from mistyping something, it should be fine to simply retry that step. If you get completely lost, type "exit" and start over. You should now be able to copy the WebTools.bundle directory into the Plug-ins directory. To make sure you put the directory in the right place, confirm you can navigate here from your desktop computer: \\<tower>\appdata\<Plex appdata>\Library\Application Support\Plex Media server\Plug-ins\WebTools.bundle\Content If you are able to pull up the Content directory directly under Plug-ins\WebTools.bundle, then everything is in the right place. Wait a few minutes, then wait some more, then login to Plex. Go to the Channels area and you should see WebTools (although if you click the image the wrong url will be displayed.) If it isn't listed, wait longer and try again. If you want to kick-start it, restart the Plex docker, wait some more and check again. Be patient, wait some more Once you see the channel listed, you can access WebTools at this url: http://<unraid IP address here>:33400/ Need Help? If you are still unable to get this working, please provide the following information: A. From step 1 - What is the name of the server you are using in place of <tower>? Also, is your system working fine other than this? If you have underlying issues with Plex or your server, you should resolve those before installing a new channel. B. From step 2 - What is the full host path that corresponds to the container path for "/config"? And what are you using for the <Plex appdata> value? C. From step 3 - Are you able to access \\<tower>\appdata\<Plex appdata>\Library\Application Support\Plex Media server\Plug-ins ? If not, where does it break? i.e. which of the follow does not work: \\<tower>\ \\<tower>\appdata\ \\<tower>\appdata\<Plex appdata> \\<tower>\appdata\<Plex appdata>\Library \\<tower>\appdata\<Plex appdata>\Library\Application Support \\<tower>\appdata\<Plex appdata>\Library\Application Support\Plex Media server \\<tower>\appdata\<Plex appdata>\Library\Application Support\Plex Media server\Plug-ins D. From step 4 - Look in your "Webtools.bundle" folder. It should contain subfolders for "http" and "Contents", plus a few other files. If it doesn't you should re-download / re-extract and try again. E. From step 5 - Do you get any errors when copying Webtools.bundle to the Plug-ins directory? F. From step 6 - If you had to do step 6, attach the text file where you were saving the results of all the commands you typed. G. From step 7 - Are you able to access these directories? \\<tower>\appdata\<Plex appdata>\Library\Application Support\Plex Media server\Plug-ins\WebTools.bundle \\<tower>\appdata\<Plex appdata>\Library\Application Support\Plex Media server\Plug-ins\WebTools.bundle\Content H. Attach "Plex Media Server.log" from the logs directory: \\<tower>\appdata\<Plex appdata>\Library\Application Support\Plex Media Server\Logs If "com.plexapp.plugins.WebTools.log" exists in the the "PMS Plugin logs" sub-directory, attach that as well.