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