marlinz357

Yes, absolutely, and I upgraded to 7.3.1, which did not help either. Please see the diagnostics as requested: diagnostics-20260601-1253.zip

yes, already tried --gpus all, also tried --gpus=all

The following is the last line of the "command failed" when trying to input --runtime=nvidia in extra parameters: docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error jailing process inside rootfs: open /proc/self/mountinfo: no such file or directory Does this explain anything meaningful to you?

the script was in the "user scripts" plugin, and we found it and deleted it. There just seems to be something with the updated docker that occured with the move to 7.3. Is there any other diagnostics that could help you figure out why I can't transcode with gpu suddenly?

ich777, are you going to help me?

What I was saying is that I have followed all the instructions in your original post for two years without any issue until updating to 7.3, then the issue immediately started (which means I am now not able to have anything in extra parameters box or the plex app won't start). Additionally, I had to figure out what an unlock script even is and have deleted it. Not sure why that matters but I am not that tech savvy with computers, and had a friend help me. So what can I do now to have my GPU transcode once again since I lost that ability with the Unraid 7.3 update?

Thank you, however this is exactly what I have had for over two years now and it has worked great, but since the moment I updated unraid from 7.2.4 directly to 7.3.0 it stopped working..

ich777, I don't see any big red text above.... not sure what you mean?

ich777, please let me know when you get a chance to view my diagnostics above.

Thank you for your help diagnostics-20260519-2054.zip

--gpus=all causes the container to fail to start. The container only starts if Extra Parameters is left blank, with Nvidia_visible_devices set to my GPU UUID and Nvidia_driver_capabilities set to all (which worked fine with --runtime=nvidia before going to 7.3 from 7.2.4). So without an extra parameter (hw) transcoding does not happen, only slams my processor h.264.

GTX 1660 Ti - --runtime=nvidia broken after upgrading to 7.3.0 (no HW transcoding anymore) After upgrading from 7.2.4 to 7.3.0, my GTX 1660 Ti no longer works with Plex using --runtime=nvidia. • Container fails to start with “bad parameter” / “command failed” when using --runtime=nvidia or --gpus all • Works fine with no GPU parameters (software transcoding only) • docker run --rm --gpus all nvidia/cuda... test works successfully • Tested on drivers 580.159.03, 590.48.01, and 595.71.05 • Plex-Media-Server container from Previous Apps It was working perfectly on 7.2.4 (I think this is the version I left to go directly to 7.3.0). Seems like a compatibility issue with the new Docker version in 7.3. Anyone else with cards (16xx series) having this issue?

So I did do change to exclusive shares and I still get the same problems. I did put docker and those shares on a fast M.2, but still have the issue.

Thanks JorgeB, I will try it and see if things change. Just don’t know why it suddenly changed.

Since about August 2025, the server has had issues when mainly sabnzbd files are downloading, unpacking, unrar and repairing files and server can become temporarily frozen or unresponsive along with containers until files finish completely. This also causes problems with errors in Sonarr, Prowlarr and Radarr temporarily while files are in this process. These files download download, unpack, repair and unrar way slower than usual (since around August 2025), and this is even after replacing pool zfs drives, and to a fast 16 core processor. Additionally, during the exact same timeframe my docker has been glitchy with certain containers stating they update successfully (or fail) but still show updates are needed. What is going on? Why is this happening, as I did not change any settings whatsoever and the server was way faster before. Attaching diagnostics zip file for consideration. Thank you for any help. Server-diagnostics-20251207-2128.zip

Thank you for the help, I was able to get back in to my server. Unfortunately Plex and Emby were weirdly corrupted and I am having a time trying to figure out how to fix, especially Plex.

Also, will I need to save my config folder or does it matter when running from flash backup? By the way, I tried to copy my config folder off corrupted drive onto desktop, but would not let me due to admin privileges, even though I am my admin…

So can I install my flash backup on my current os flash that was corrupted so that I don’t have to use my 1 key transfer I get every 12 months? if so, please explain the best way to do it, ie. Can I completely wipe the corrupted flash usb stick and then only install the flash backup and that is it?

Additionally, I really want to be able to retain my settings, applications, plugins, etc.

Yes, from unraid connect in cloud.

Please help, I copied all the bz* files from a new unraid 6.12.6 os on a new flash drive over to my current unraid os flash drive that has this bzfirmware checksum error, and now when trying to boot server it goes to bios only. What can I do?