ConnerVT

While I do have trust in the work which @dlandon provides the Unraid community, I am in agreement with @MowMdown 's concerns. If this was some random plugin, I would recommend not installing a plugin from outside the vetted Unraid Community Apps. But the Unassigned Devices suite of plugins are pretty much essential to most Unraid users. Now that @limetech is the owner/author of these plugins (due to unfortunate circumstances) I would hope that, in the future, they would check that any ancillary programs test okay without any breaking changes before releasing OS updates. If issues are found, they should make any required updates and release them to the CA, and perhaps even add these to the plugin checker which runs during the update process.

No. "Parity disk" implies that it is part of an Array. Pools and Array require an error free connection to all disks, something that can't be guaranteed by USB connected drives.

Well, then I got nothing. At least you have 2 less possible causes.

Haven't had an issue here. Suggest clearing cache and maybe cookies.

Between both servers, roughly $96,000 USD worth.

Parity is not a backup. Parity is a useful function to allow reconstruction/replacement of a failed drive while providing some HA (High Availability) of the server during array repair. But a proper backup is the only thing that will truly prevent data loss.

No matter which version of Unraid you are running, you need to select the correct version of Nvidia driver. This is due to how Nvidia fractured their drivers, in support of new Products and making others End Of Life. Fortunately, the Nvidia Plugin allows you to select the proper one (at least for every version of 7.x.x). At the time of this post: v580.x - For Pascal (such as P400) and older, though some Docker containers no longer support cards older than Pascal. These are all EOL. v595.x thru v610.x - Turing through RTX (except RTX 50 Series) Open Source Branch - RTX 50 Series

New trial needs new flash drive.

You're a good man, Charlie Brown.

Also, I would get rid of the 3 3TB drives in the array, and instead of dual parity just use one of the 14TB drives and change the second to be a data drive. Dual Parity is a bit overkill for 7 total drives (Parity is not a backup). So one parity drive for 4 drives is good, you will have an additional 5TB of storage, and will reduce power consumption, heat and points of possible failure.

Two thoughts came to mind. -- Check that there is no other drive activity taking place on the array, except for the parity check. It doesn't even need to be something the server originates, another system using the array for a network drive could be reading/writing. -- I see you have a mix of 14TB and 3TB drives. How far into the parity check was it? if it is near the end of checking 3TB, this is likely the slowest speed the parity check sees. 2 things to remember - Drives are their fastest at the first sector, slowest at their last; and (as long as the drives are syncing up nice) the parity check will only run as fast as the slowest drive in the array. Once the 3TB are done being read, I suspect speeds will jump back up significantly.

Sorry, but I disagree with this. Unraid is not a turnkey, take it out of the box and use it toaster. It is a highly configurable OS, an ecosystem which can be used as a basic NAS to a full blown home lab setup. Things which are highly configurable require an understanding of how they work before using. Not doing so is certainly a recipe for painful lessons. There are quite a number of tutorials, both written and video, readily available on the Internet which explain things from the basic configuration of arrays and pools, setting up Dockers and VMs, to much more complex things people do with Unraid. This support forum is frequented by people who use Unraid and share their knowledge without accolade or compensation. I find these folks to be some of the most helpful, especially compared to other support forums I have visited over many years. Other than your posts in this thread, I only see one other post you have made on this forum (with this Username). The author of the plugin replied to you the same day.

I have seen a number of cases where wonky transcoding or playback issues are due to a corrupted codec file. You can safely delete the Codecs folder from your Plex appdata. Stop Plex, delete the folder, and restart Plex. It will create and repopulate the folder with fresh codec files. I have had several folks post feedback they have done this and it resolved their issues. Also be sure to test with a dedicated PLEX client, and not the web browser. The web browser is well known to have issues, especially when switching resolutions or transcoding bandwidth. Switching off subtitles is also a must, as subtitles will most times switch to CPU transcoding.

I have been following several threads here for weeks about this. Answers have been very ambiguous about it, leaning toward it does count as additional drive towards the license limit.

Both of those are issues with these applications, not with Unraid. Best to work with the folks supporting the applications, either in the docker's support thread or with the application support itself.