T_Matz

I dont know where to even begin figuring this out. I have my appdata split between 2 nvme drives. 1 drive is soley for Plex the other drive is for all other appdata dockers and plugins. Would that cause an issue?

Im just so confused, this is the 3rd set of RAM, 2nd motherboard, 2nd CPU ive used in unraid in about 2 years and i seem to have constant RAM issues like nonestop. but then i put this exact same equipment in a new build running windows and experience zero issues

I'll run a memory test again, did that 4 months ago and had no issues. If there are no issues again what else should I be testing?

It just happened again. Last night I was watching shows off of Plex. This morning the Plex docker was gone. Reinstalled and Plex was back up and working like it never stopped working. tower-diagnostics-20241001-0527.zip

ive had the server up and running now for over 2 years with zero issues. I rarely go in and edit dockers anymore. These problems started once I upgraded to 6.12.13, or so it seems. I have plenty of space on the array and on my cache drive. Not sure where to even go to start testing this. Its so random that I'm not sure what is happening.

Before. Last night two dockers dropped off (OMBI and BAZARR) and I didn't reboot the device. It has been up for a few days now (Uptime 5 days 1 hour 5 minutes) . The odd thing is I was using OMBI last night and then today it was gone off the machine, the only reason I realized was I was trying to use it today Other dockers it will be missing for days before I realize. I reinstalled it like the other dockers before it and its functioning normally. Im on OS 6.12.13

For about the past 2 weeks I keep having Dockers uninstall themselves. Ive had to reinstall about 10 dockers (OMBI, BAZARR, SONARR, JACKETT, IMMICH, POSTGRES, REDIS, and the list keeps going) its strange. Ill be using the service one day and the following its just gone, I cant access it, and when I go to look its gone from UNRAID. I can reinstall from previous dockers and it comes back with zero configuration just fine. Not sure what is going on or how to fix this! tower-diagnostics-20240922-1601.zip

I still cant get a few of these dashboards to work not sure where im missing the mark here

Varken starts fine for me and is running on 6.12.11, the dashboard has been updating as well.

I tore the GPU, and the power supply blackout and plugged everything back together another time and everything seems to be working again

This week, my Windows 10 VM will randomly not run with a 3050 passed through to it. When I restart Unraid, the VM will be running, but I can not log into the VM by any means, and it does not seem to be running. Everything was running smoothly but last week I noticed that one of the pinned CPU cores was staying at 100% constantly. When I stopped the VM, the CPU core at 100% utilization returned to normal, but the VM would not start back up, and I got an error message. If I remove the 3050 GPU and the 3050 soundcard, the VM will start normally. I'm not sure what to do to fix this issue. I have verified that the power is going to the GPU, the fans are spinning, and I put the card on a different computer, and it worked on that computer as well. So, it seems to be an issue with Unraid itself.

Sorry for the late reply, I was on vacation and did not have access to the internet. No, 120 seconds was not enough. It was only when I reached 300 seconds that it updated successfully. I am using an SSD-based pool. The only docker with which I am experiencing this issue is Immich. It happened again with the last update, and I had to increase the timeout to 300 seconds before it updated. Once I increase the time out it successfully updates, I set it back to the default following the update with zero issues with any other dockers.

Immich was not completing an update, I increased the time out by 30 seconds and would keep trying. I had to get up to 300 seconds before it completed the time out. It was successful at 300 seconds. I put it back to 10 seconds after the update and everything seems fine.

I was able to get most of the data added into the fields there are still a few sections that Im struggling with. All of this data is on unraid so I just dont know what i need to change in grafana

So there's no way to actually get data to populate those panels I just have to remove them? I thought I read that I could use inputs.sensors to get similar data.

Love the dashboard! ive got almost everything up and running and its amazing! I have been having a few issues though with the sensors. I do not have IPMI sensors so I know I need to make changes to some of the fields but not sure where I should be making them. Ive combed through the forum here and I see it asked a few times but couldn't see the actual edits I needed to make. Its strange because it seems like Im getting some of the data but not all of it. I have uncommented the inputs.sensors, added it to the post arguments.

The exporter does state that it is running. Ad guard home is up and working. I'm going to uninstall everything and delete the folders reinstall and see if that fixes it. Quick question, the exporter connects to ad guard home via port 80 or the 9617?

Nope, states site can't be reached.

I'm not quite sure what you mean. Here is a snap shot of the exporter. I've read that changing the password is a pain but I'll work through that and see if it makes a difference.

I have ad guard exporter up and running, it starts just fine but I can't get it to work in Prometheus. The link is always down in Prometheus. I added the target to the yaml. I have other exporters up and they work with zero issues so not sure what the problem is. Ad guard runs on a stand alone device with a static IP. I'm able to ping ad guard from unraid. The ad guaurd exporter is running. It's added to the Prometheus yaml. The one thing I can't confirm is that I was told it might not work if there are special characters in the pass word, is this still a fact or is this a question better suited on the ad guard support page? Any insight anyone can provide would be greatly appreciated

I have the ad guard exporter up and running, it starts just fine but I can't get it to work in Prometheus. The link is always down. I added the target to the yaml. I have other exporters up and they work with zero issues so not sure what the problem is. Ad guard runs on a stand alone device with a static IP. I'm able to ping ad guard from unraid. The exported is running. It's added to the Prometheus yaml. The one thing I can't confirm is that I was told it might not work if there are special characters in the pass word, is this still a fact or is this a question better suited on the Prometheus support page? Any insight anyone can provide would be greatly appreciated

Wanted to follow up. I am still getting a memory leak through the Plexpass docker. It requires me to restart the docker periodically to fix. Yesterday my plex docker was using 22 GB of RAM even though nobody was using plex at the time. I do have my docker using RAM as the transcode directory and i do see the docker use more RAM as it transcodes a movie/tvshow but it doesn't seem to release the memory back when the stream stops. It just slowly keeps growing. There is nothing in the logs to show any warnings or errors so I didn't include any logs in this post but did attach my docker config. Is there anything I can do to help this or just keep restarting the docker periodically?

Does anyone know how to safely shrink a windows 10 VM. I have followed all the tutorials and guides, but I can not get it to shrink. Ive gone in the VM shrank the volume and went into the unraid console to shrink the volume. I think it wont work because the the windows recovery partition is at the end of the disk in disk manager. The unallocated space goes after the C drive. So the drive looks like C drive, unallocated, recovery partition. Is there a way to do this now based on this?

Running parity check and only 10% in and I'm already seeing almost 4000 fixed parity errors.

Quick update: I think I fixed it. I got home and reconnected all the cables, and I'm no longer receiving those errors. My parity check is back to a normal speed (280 mb/s). I do not understand how this all changed, but I'll report back if anything changes again.