ItsRaining

I have tried absolutely everything. I cannot figure out this FPS drop and I am just going to go back to windows.

You are the man! I cannot believe this was the issue. So the ethernet is part of a Kensington Dock. Is there a way I can force Unraid to unbind it or something similar to allow the dock to be passed through?

The ethernet is part of a dock. I will try without using the dock thank you for the tip.

Here is the diagnostics zip file. itsrainingpc-diagnostics-20220810-0852.zip

Thank you for the reply. I am not trying to passthrough the Unraid USB group. I want to passthrough the USB controller I have (its a PCIe controller not part of the mobo). Its in group 18 (04:00.0).

No matter what settings and port combination I try. I CANNOT get this USB Controller to passthrough. To my understanding when it is grayed-out like this Unraid is using it. I removed all my VMs and have nothing else running in Unraid but no matter what the controller is grayed-out. MSI B550-Creator Motherboard with VM ACS set to Both. I have been trying to get a decent gaming VM to work for months. When passing just the devices there is a huge FPS drop and I just cannot figure out why I cannot pass the USB controller through. I am close to just using Windows again but there are so many limitations.

Would it be possible to add support for theme.park like the LinuxServer.io dockers? Not sure how difficult to implement. Thanks. https://docs.theme-park.dev/setup/#docker-mods

Hello binhex, I use a few of your dockers and they are great! Regarding this one, do you have any intentions of keeping the docker up-to-date with the prowlarr version? I notice you are a few versions behind and the constant update available is there. Curious if there is a reason you are behind or plan to update? Thank you!

I have been using Mover Tuning with days old and percent enabled for about 6 months now. When setting this in mover tuning the expected result would be when cache reaches percent used it will trigger a move only files older than a specified days old. Instead what happens is mover will trigger at percent used and move all files regardless of age.

I would like to confirm that the value is persisting after restart. I have restarted my server three times during maintenance today. I have another 1 hour maintenance window tomorrow to replace a drive and will do another restart or two to confirm today wasn't a fluke.

I noticed the update. Sorry for the late response I have been working overtime before the Holiday. This weekend I am performing server maintenance and will restart the Unraid server a couple times. I will report back if the value persists after restart. Thank you!

I am sorry I meant to say 524288. The default value.

Hello all! I have some questions I hope someone more knowledgeable prople can answer for me. Below is a list of my current Unraid build. I am getting a NIC for Christmas and would like to install it. Here is my question. My current motherboard has three 16x lanes and one 1x lane. Which device should I put on the 1x with a riser and/or should I look for a four 16x motherboard. Motherboard: Gigabyte X570 Aorus Master CPU: AMD 3600x PCIe 1: Nvidia P2000 PCIe 2: LSI Broadcom SAS 9300-8i-8-port PCIe 3: LSI Broadcom SAS 9300-8i-8-port New NIC: Dell 0RT8N1 Mellanox Connectx-2 The reason for the dilemma is because I am not sure regarding the limitations of a riser when it comes to the data transfer rate which is why I was leaning towards the GPU. Suggestions and thoughts would be appreciated!

Good to know. I will restart to confirm its persisting then. So far it has not persisted but I was messing with sysctl.conf. Update: The issue I am having where plex is unable to scan the EAC3 audio files is still persisting and the inotify.max_user_watches stays at 512k. Leading me to believe the value is not setting for Unraid. Going to try and reach out to Unraid support because I have not been able to get this working since day 1 on my server.

Thank you for helping me confirm the tweaks applied. I see it in the logs. That is perfectly acceptable that it does not persist on reboot.

Here is what I tried doing. After restarting the server, tips and tweaks had it set to 4194304 but on the right it was the default. Opening the file in the terminal also showed the default (and showed a default conf file with no extra parameters - seems to have reset the conf upon restart). After inputting 4194304 again tips and tweaks showed the number on the right. This does not persist when I restart but honestly not a big deal if its working but I do not know a way to confirm this until plex tries to detect intros on an EAC3 audio file. Which was the original reason I went down this rabbit hole.

Yeah vi was a dumb mistake nano was the way. I was able to set the value in both the conf and tips and tweaks. This setting however, does not survive a restart of the system. Not a big deal but I want to ensure the setting is actually working. Does anyone know of a way to do this?

I was able to open the file using nano and successfully edit the sysctl.conf. I will see if this actually worked.

When I change the setting and hit apply. The setting does change on the right. However, it changes back on reboot. I am not sure if that is by design. Finally, when set through this GUI how can you confirm it is applied? When I apply the setting, it shows in the GUI on the right side but did not show in the terminal when running sysctl.conf -p.

I really hope someone will help me as this is my third post regarding this issue. I have been reading and wrapping my brain trying to to change the Max Watches 'fs.inotify.max_user_watches' variable. I started trying to use the terminal using the following command: sudo sh echo fs.inotify.max_user_watches=4194304 >> /etc/sysctl.conf sysctl -p This ended up just adding fs.inotify.max_user_watches=4194304 to the sysctl.conf and did not replace the variable. After reading a bunch of forum posts regarding the issue I was directed towards using the "tips and tweaks" plugin. Setting this variable to 4194304 did not actually change anything. I also tried 999999, 1048576, and 2097152. Realizing I needed to probably restart the server for the changes to take effect I restarted. I am still showing the default value in the terminal and tips and tweaks. Here is my original post on the Plex Linux Docker: https://github.com/linuxserver/docker-plex/issues/291 Unraid Forums Post: Any assistance would be appreciated! diagnostics-20211130-0645.zip

To my understanding changing it for the host changes the value for all the containers. As the container pulls this value from the host. I do not understand why I am unable to change the value for the host even using vi. I will submit my forth post to the tips and tweaks support thread. Hopefully they can help.

I have been reading and wrapping my brain trying to to change the Max Watches 'fs.inotify.max_user_watches' variable. I started trying to use the terminal using the following command: sudo sh echo fs.inotify.max_user_watches=4194304 >> /etc/sysctl.conf sysctl -p This ended up just adding fs.inotify.max_user_watches=4194304 to the sysctl.conf and did not replace the variable. After reading a bunch of forum posts regarding the issue I was directed towards using the "tips and tweaks" plugin. Setting this variable to 4194304 did not actually change anything. I also tried 999999, 1048576, and 2097152. Realizing I needed to probably restart the server for the changes to take effect I restarted. I am still showing the default value in the terminal and tips and tweaks. Here is my original post on the Plex Linux Docker: https://github.com/linuxserver/docker-plex/issues/291 Any assistance would be appreciated! diagnostics-20211130-0645.zip

Yes I put it together. It wasn't my first time and used PCPartsPicker to check compatibility. Do you want the full specs? It was working just fine I do not understand this sudden change. Edit: After bringing it to a trusted friend he switched out the motherboard and everything worked great. I am currently in the process of replacing the motherboard through the manufacturers warranty.

Yes all the fans turn on, lights start up, the server was working (except the above errors) before I shut it down to pull the USB stick.

Wow you are correct. I am not getting a BIOS screen. Any suggestions, I have never had this before. Faulty motherboard?? This is freaking me out because all the parts are only a month old and I believe just past the return date.