Reddog1400

So, back to the RAM filling up. Can anyone explain this? The python3 usage. 56.3359 MB ./dizquetv 57.9531 MB /app/Tdarr_Node/Tdarr_Node 61.5586 MB /app/Tdarr_Node/Tdarr_Node 62.5078 MB containerd 64.418 MB /app/Tdarr_Node/Tdarr_Node 75.1836 MB python3 93.9531 MB node 94.7031 MB /usr/bin/dockerd 97.7148 MB ./Tdarr_Node 107.613 MB /app/Tdarr_Server/Tdarr_Server 128.797 MB /usr/sbin/netdata 131.113 MB stash 132.156 MB /usr/lib/plexmediaserver/Plex 143.102 MB /app/Tdarr_Server/Tdarr_Server 154.414 MB /usr/bin/mono-sgen 169.484 MB /app/Tdarr_Server/Tdarr_Server 210.766 MB /usr/bin/mono 232.871 MB /usr/lib/prowlarr/bin/Prowlarr 241.945 MB /app/nzbget/nzbget 248.094 MB /app/Tdarr_Server/Tdarr_Server 255.129 MB /usr/lib/radarr/bin/Radarr 262.156 MB /usr/lib/readarr/bin/Readarr 290.891 MB /usr/local/sbin/shfs 366.051 MB /usr/bin/node 401.965 MB /usr/lib/lidarr/bin/Lidarr 520.562 MB /usr/bin/mono 531.918 MB /usr/lib/radarr/bin/Radarr 832.898 MB /usr/local/bin/unraid-api/unraid-api 1031.34 MB ./Tdarr_Server 15740 MB python3

I understand all of that. Since my media is across all disks, it should be set to /mnt/user, right? That is where I started with this whole thing.

So, what should be the path be? I had it set to user before.

Sorry, missed you asked for that in the original post. defiant-diagnostics-20230130-1316.zip

So, I shouldn't do that? So, what is your advice?

@trurl is this what you needed to see?

docker run -d --name='plex-gpu' --net='defiant1' --cpuset-cpus='4,5,6,7,12,13,14,15' -e TZ="America/Indiana/Indianapolis" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Defiant" -e HOST_CONTAINERNAME="plex-gpu" -e 'VERSION'='docker' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-22894283-12c9-ee8d-0da8-55e6693131b0' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/plex-icon.png' -p '32400:32400/tcp' -p '3005:3005/tcp' -p '8324:8324/tcp' -p '32469:32469/tcp' -p '1901:1900/udp' -p '32410:32410/udp' -p '32412:32412/udp' -p '32413:32413/udp' -p '32414:32414/udp' -v '/mnt/cache/Movies/':'/movies':'rw' -v '/mnt/cache/Television/':'/tv':'rw' -v '/mnt/cache/Music/':'/music':'rw' -v '/mnt/plex_cache/transcode':'/transcode':'rw' -v '/mnt':'/mnt':'rw' -v '/mnt/cache/appdata/dizquetv/':'/dizquetv':'rw' -v '/mnt/plex_cache/plex_appdata/':'/config':'rw' --runtime=nvidia 'linuxserver/plex' 48163179643e14218fa33e7afa3ca232d6d34585639184190ab4e9d6c1131996 The command finished successfully!

linuxserver/plex This is the repository I am using. This is with the GPU.

Ok, here are some Diags. Before Plex shutdown, after shutdown, and I restarted Plex after. After I shutdown Plex, the CPUs came down, but the RAM didn't. When I restarted Plex, the RAM cleared. defiant-diagnostics-20230120-0956 before Plex shutdown.zip defiant-diagnostics-20230120-1005 restarted Plex.zip defiant-diagnostics-20230120-0959 after Plex shutdown.zip

ok, my server ground to a halt so I restarted the array. I will do that the next time this happens. Then I will send new Diags.

I haven't tried that by itself. If I stop and restart the array it fixes it. Do you see what I can do to fix the Plex issue. This is all new to me. I mean I have been running a server for a couple of years, but I have just be self teaching myself stuff.

I had to wait for it to happen again. Right now it is pinned and RAM is at 91% defiant-diagnostics-20230119-1022.zip

I did this with a few and it seemed to work a little. Then it happened again. Did you notice certain dockers being the culprits? Also, is this why the RAM is maxing out too?

ok, thanks, I will give it a try.

Can you elaborate further? What is a disk share vs a user share?

Good morning all, I keep having issues with my CPU and my RAM maxing out randomly to the point where I need to restart the server. It happens almost everyday. I have attached logs. Thank you. defiant-diagnostics-20230110-1037.zip

So, something like this? https://www.newegg.com/lsi00302-sata-sas/p/N82E16816118183?Item=9SIB7VEH151745 With these cables? https://www.newegg.com/p/238-00A4-00003?Item=9SIACJF7BC9148 I am very new to SAS. I just want to make sure I am getting the right hardware.

I will go through and reseat and recheck all the cables. What is a recommended SATA board?

A few weeks ago, I had a disk that got disabled after some read errors. I thought maybe the disk was going bad, so I pulled it out of the array and precleared it. Disk passed preclear. I also bought another drive just in case. I have put the new drive into the array and the rebuild keeps throwing errors and shutting down the array. There have been a lot of wonky things going on the past couple of weeks. I am unsure what to do. I have attached diagnostics. defiant-syslog-20220810-1329.zip defiant-diagnostics-20220810-0927.zip

seems to be better. That Nvidia plugin is so touchy sometimes.

So, it wasn't downloading the Diganostics. I uninstalled the Nvidia plugin and restarted. It let me download the diagnostics. defiant-diagnostics-20210901-1209.zip

Today when I logged into my server, dockers didn't restart after backup. When I went to start, it took forever to come up. Then I tried to do some updates and it stalled. I did a restart and now my Dockers aren't showing up. I just have the UnRaid thinking symbol for about 20 min now. I looked at the logs, and there are a lot of things I have never seen and a lot of red lines. I have attached the sys log. I am trying to get the diagnostic logs, but they are taking forever to download too. defiant-syslog-20210901-1515.zip

Hello, This has happened a couple of times in the last couple of weeks. I will log in to the server in the morning and all the dockers are shutdown. I look at the logs and I see a ton of BTRFS errors. I have 2 cache drives. I suspect maybe one is going bad, but I can't tell from these errors. I have included logs below. defiant-syslog-20210421-1300.zip defiant-diagnostics-20210421-0900.zip

Hello, I have been dealing with some issues getting through a parity check after I replaced a drive that went bad. I swapped out one of the drives in my array and ran through the rebuild. All seemed okay. Then it ran a parity check and had like 6 sync errors. It finished just fine. When I logged on this morning, the server was hung and I had to force a shutdown. Naturally, when it came back up it started a check. 300ish errors and the Parity all but stopped. I am at a loss of what to do. I have attached my logs before I had to force another shutdown. There is one from this morning and this evening. defiant-diagnostics-20210306-1117.zipdefiant-diagnostics-20210306-1830.zip

Thanks, that did it. Just when I think I am figuring this out, something else stumps me.