Fizzyade

Since upgrading to 6.12 and updating the nvdia I've been getting GPU errors, like the following: [56386.612293] NVRM: Xid (PCI:0000:08:00): 31, pid=17147, name=ffmpeg, Ch 00000008, intr 10000000. MMU Fault: ENGINE GRAPHICS HUBCLIENT_FE faulted @ 0x1002_06807000. Fault is of type FAULT_PDE ACCESS_TYPE_WRITE [57317.960662] NVRM: Xid (PCI:0000:08:00): 69, pid=27124, name=ffmpeg, Class Error: ChId 0020, Class 0000c1c0, Offset 00001b0c, Data 00008000, ErrorCode 0000000c I am using Emby in a docker container, it's the only thing that uses the GPU and once the GPU fault occurs, it kills that ffmpeg which then causes Emby to either just stop playing the stream that was being played, or it jumps ahead to the next episode if it's a TV series that is being watched. Nothing else has changed and the machine was 100% stable prior to updating. I know when I was on a previous Unraid release, I had stuck to an older driver and I never had any issues, when I checked the driver being used it was using "latest", so as a test I changed the settings in the plugin to use " v530.41.03" and all the issues have now gone away, it's back transcoding without any GPU faults.

64GB. I really wish that Unraid supported lxc containers though, I have a NUC running Proxmox which has a load of containers set up which I use for CI (TeamCity), but I need more containers to handle other builds and the NUC has no more ram (it's got 64GB as well) and unraid would be ideal if it supported them.

64GB although I could do with more, I have multiple virtual machines spun up at once for development work (Windows 10, Fedora, the latest Ubuntu in addition to the oldest Ubuntu LTS which is used to build AppImages. I also have VM's set to be CI agents. My NUC which runs proxmox also has 64GB.

I just upgraded to the latest rc and this is still broken for me. Modify the port in the XML and then go make a change in the GUI and the port reverts back to auto and -1. This drives me up the wall, especially with a fair few VM's and trying to remember what the port setting actually was.

If you change the VNC port in the XML to be a specific port instead of auto (which is the behaviour that you want, you want to connect to the same VM on the same port) and then sebsequently change any setting of the VM using the gui the port reverts back to the auto port, losing your nicely configured static port setting. We need to be able to show and set the port in the gui so that it can easily be configured to a static port and more importantly that the mapping isn’t lost when you make a GUI change. im forever having to go back and edit the XML to restore the vnc port.

Probably already said it, but set the VNC port in the GUI so it doesn’t get lost when changing configuration xml. Drives me absolutely nuts.

It's running right now and now emby is running like a slug.

Ok, I removed the mover plugin and so forth, only share that's set to use the mover is my downloads. Last night I could tell it was running (I get pauses when trying to start playing something in Emby), went to the server and sure enough every core full red.

it doesn’t, the reason I initially installed mover tuner is because the mover pegs the processor.

Right, I’m ready to give the mover another go. the only thing I’m interested in using it for is my downloads. are there any dos, do nots. Any sane settings I should start with. is it possible to set the mover logging to log to the array, so that if I end up having to restart the server due to the mover, I can produce a log file? thanks.

So it all went wonky again last night, every CPU pegged to 100%, system unresponsive, in the end I had to reboot it, of course that meant I lost the logs. There was only my media folder using the cache, the actual downloads were not cached. No overclocking. I just stopped docker & vm's, ran mover and then disabled the couple of shares that were using cache, then removed the cache drive.

I had actually only turned that on a few hours before I posted the screenshot just as something else to try, it’s been running disabled forever. ive just updated the plugin (to the correct one) enabled logging and redisabled turbo write.

Here's a screenshot of the mover tuning settings. I looked in the syslog file and couldn't see any mover entries. Thanks for your response, I know this isn't your issue. it's the mover, it shouldn't kill a 16 core machine though, even if IO bound I would have expected setting the priority low that everything else would take priority.

I'll do that now. The mover is actually doing my head in, so much so that I'm contemplating removing the cache drives because my machine absolutely tanks when it runs. I'm sure at one point I had this plugin working to solve the issue, but I just can't seem to get it to work, the mover runs and until it's finished I can't play any movies from Emby. I was so happy when I found this plugin.

Does this still work? No matter what I do, mover absolutely kills my machine, every core showing red on the dashboard. tried changing priority’s and it makes no difference. Mover has just started and now I can’t play anything on Emby because it’s killed the computer. I’m sure this plugin used to help, but I just can’t seem to change anything in it that helps.