Ocman76

Thanks, next time my server crashes I will try this method.

I've been having issues with my server crashing recently and it was recommended I replace the USB as one of the troubleshooting steps. I have a Team C188 USB that I bought new and have never used for Unraid. It has a unique serial ID number but is showing as blacklisted, do I have no choice but to buy another USB? Why would this USB be blacklisted?

Will do, I have a spare set of RAM sticks I can borrow so I will just swap them out and see if it prevents the crashes.

Does this mean the system logs won't help diagnose the issue? Where would you recommend I start? RAM? PSU? Motherboard? I assume I have to start swapping components out and see if it prevents the crash?

Edit: I stand corrected. My server does show the uptime as only a few days meaning the server is indeed rebooting and not just shutting off the array. What I now need to figure out is why the server is rebooting automatically as my intention was for it to never reboot automatically. The times in the past when it has been shut off for other accidental reasons it has not rebooted automatically so something has changed, perhaps a setting in Unraid. Original response: My server is not set up to reboot automatically. In order for it to restart after being shut off I have to manually press its power button and then enter a password to start it. Without these steps the online GUI and array cannot be accessed at all. I have separate passwords for starting the server to access the GUI, as well as for starting the array once in the GUI.

The array stopped. The server has not shut off at all since this issue has been occurring. The odd thing is I keep getting unclean shutdown errors which I thought could only occur when the server itself was shut off, rather than the array stopping.

This is part of what I'm struggling with. The only way I currently can tell when the array has shut off is when I manually check it (or any of my dockers) to see. I thought perhaps the logs would show when the array shut off but I'm not seeing anything. I could try manually checking multiple times a day to try and catch when it shuts off but it has been taking as long as a week to occur.

Recently my unraid array is stopping itself, even though the server itself is not shutting off or losing power. Each time this happens I get an unclean shutdown error, even though the hardware itself has not lost power. I can simply restart the array but cannot find any reason why it is stopping. I have now had this occur 4 times over the course of 3 weeks. Parity checks do not show any issues. Attached are logs. I've looked through them but cannot figure out where in the logs the array is stopping. The only way I know the issue has occurred is when I try to access any of the dockers I use and discover they are off because the array has been stopped. If anyone has any suggestions on how best to troubleshoot this help would be greatly appreciated. syslog syslog-previous

I did not. I posted both here and on the Unraid reddit and got no responses. I ended up using Filebrowser instead which works for my purposes and was much easier to set up. The only tricky part was setting up the ports correctly with Swag. If helpful let me know and I can post the port configuration I ended up using to get it to to work.

Try reverting to linuxserver.io plex docker version 1.29.2.6364-6d72b0cf6. That fixed the transcoding issue for me.

Hmm thats odd, perhaps you are experiencing a different issue. Have you tried reverting to linuxserver.io plex docker version 1.29.2.6364-6d72b0cf6? That fixed the transcoding issue for me, worth a shot.

ChuckPa on the plex forums has confirmed its a bug they are working on fixing: https://forums.plex.tv/t/quicksync-hardware-transcoding-error-4294967279/829247/6

Yes I'm using the igpu for hardware transcoding (intel quicksync). I already tried reinstalling the docker from scratch, manually reentering my settings & paths to confirm they are correct. ChuckPa on the plex forums has confirmed this is a bug they are working on fixing: https://forums.plex.tv/t/quicksync-hardware-transcoding-error-4294967279/829247/6

Definitely a known issue. https://forums.plex.tv/t/quicksync-hardware-transcoding-error-4294967279/829247/6

It happens with on most transcodes but always with 4K ones. ChuckPa on the plex forums has confirmed its a bug they are working on fixing: https://forums.plex.tv/t/quicksync-hardware-transcoding-error-4294967279/829247/6

Hi all, I have had hardware transcoding set up with my server’s i5 -11400 for a few years now with no issues. Today I am suddenly getting the following error message (~30 seconds after starting a transcode): Server Version#: 1.30.2.6563 (Linxserver.io Docker, Unraid 6.9.2) Player Version#: Multiple (Web, Windows Desktop, Android) This does not occur all the time, but does occur every time I try to transcode 4K content and only some of the time with 1080p content. When I start trying to transcode the video playback stops, and ~30 seconds later I get the error. From the server playback view nothing appears to be wrong. Hardware transcoding is shown and the time for the video playing continues to pass even though the screen is blank. There is about a 30 second period between when I start transcoding and the error message shows up. In addition I am seeing much higher CPU usage during my attempts to transcode than I normally see when hardware transcoding is working properly. I have confirmed this happens with both remote and local connections to my server, and across windows desktop client, web client and android (which makes sense as the transcoding issue appears to be happening on the server, not client side). I already tried uninstalling and reinstalling the plex docker but no luck. Any help is greatly appreciated.

I have just followed Spaceinvaderone's tutorial on setting up Nextcloud on Unraid. After I finish setting everything up (and make the changes to address the 502 bad gateway error) I try to start the Nextcloud webui and get the following error: Internal Server Error The server encountered an internal error and was unable to complete your request. Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. More details can be found in the webserver log. There are multiple other Unraid forum threads on this issue and I have tried all the solutions with no luck, including: Change the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31" and let it run. Then edit the docker repository again to "linuxserver/mariadb:latest" Source here. Opening a console on the mariadb docker and running the following commands: > cd /config/databases > rm ib_logfile0 > rm ib_logfile1 Then stopping and restarting both nextcloud and mariadb. Source here. Completing removing the mariadb docker and image and reinstalling from scratch. I do not see any errors in the mariadb logs. In the Nextcloud logs I see a repeated error: PHP Fatal error: Uncaught Error: Call to a member function getLogger() on null in /config/www/nextcloud/cron.php:192 In the Swag logs I see one warning: 2023-01-29 16:04:42,345 fail2ban.configreader [406]: WARNING 'allowipv6' not defined in 'Definition'. Using default one: 'auto' Does anyone have any suggestions on how to fix this?

I can confirm it does work. Running Unraid 6.9.2 with an i5-11400 and hardware transcoding is flawless.

Ok back with a new issue 😅. Just tried my first QSV x265 encode and immediately get an error with "Failure to initialise thread 'Quick Sync Video encoder (Intel Media SDK)'":

Ok I tried restarting my entire server and now I am able to see the QSV options... looks like a good old reset did the trick!

My server has no dGPU and uses the iGPU of the 11400 only. I was messing around with my VM yesterday and passing through my iGPU but it is now set to VNC so the iGPU should be free to be used for dockers? Quicksync is still working fine with Plex. I have no option for QSV in Handbrake unfortunately:

Hi All, I'm trying to passthrough my i5-11400 igpu to use quicksync (already have it working in Plex for transcoding), however the logs are showing: Is something perhaps wrong with my passthrough? Edit: I think I may have found the problem, but why is the docker looking for D128 instead of D129?

To confirm, you aren't experiencing any artifacts or crashes while hardware transcoding 4K HDR content? According to this plex forum thread, both Tiger Lake and Rocket Lake CPUs have confirmed issues ongoing. Which version of unraid and plex docker are you using? Could you elaborate on what you have done exactly to get it working?

Hi all, I'm an Unraid/Plex newbie and just set up my first server for Quicksync transcoding with an 11400. I have followed the tutorial in this thread to enable hardware transcoding and it appears to be working as the dashboard shows (hw) during transcoding. However I am unable to get 4K movies to transcode without introducing artifacts: Transcoding from 1080p files works fine. From reading through this thread it appears this may be some sort of issue on Plex's end? I am running Unraid 6.9.2 and the linuxserver version of plex however I am not sure how to determine the current version. Is what I am experiencing a familiar issue or something possibly wrong with my setup? Any help is greatly appreciated!