MowMdown

QSV Device is blank. I know it says to leave it blank but I think you need to fill it in with /dev/dri/renderD128

Possible scenarios: 1. Jellyfin was not setup to use the iGPU in it's own transcoder settings. 2. Your media is not in a supported codec for encoding and/or decoding. If even one of those cannot be done on the iGPU it will drop back to the CPU. Jellyfin should have something telling you the transcoder status. Double check the transcoder settings to make sure it's configured to use the iGPU.

This is going to show all 0% because the iGPU is not doing anything. There's no load on it from a docker. But yes, technically all you need to do is add --device=/dev/dri to the extra parameters field like so: Then if you open the docker's console from unraid webGUI You should be able to see the iGPU by navigating to /dev/dri If card0 and renderD128 do not appear, it will need to be investigated further.

Under the GPU Stats plugin, what do you see here? I assume if this can see the GPU that it's functioning properly. It will just be a matter of properly passing it through to the dockers. I did not see anything in the diagnostics that would indicate it shouldn't work.

Post your diagnostics.

What @JorgeB said, if you see any orange warning triangles on the "Shares" page that means that the share is unprotected. See my own example:

If the segments aren't being cleaned up it could lead to a ballooning docker image.

I don't know much about Frigate but to my understanding it does transcode video streams from your surveillance system. These files have to be written somewhere right? Where are you transcoding the video streams to? Could this be your issue is frigate is transcoding the video into the docker image instead of onto a disk? What about the mount for /tmp/cache?

1. You will need to move the data off of disk1 onto disk2 and disk3, you can use the "Unbalanced" plugin for this. Once you've done, this you will need to reset the array drive assignments using the "New Config" tool. 2. You will not be able to add the now removed SSD to the existing cache pool unless you decide to swap filesystems from XFS to either BTRFS or ZFS. You will need to add it as a second cache pool or move the data off the old cache drive onto the array and re-format the cache drive while adding the 2nd SSD to the cache pool and putting them into either a ZFS mirror or BTRFS RAID 1 (both default options) Edit: If you go with step 2, don't forget to move the data back on to the cache drives.

Just for giggles, if you can afford the time and space, I would re-create your cache pool with the two identical kingston NVME drives and leave out the Sata SSD as it's about 15x slower. (7000MB/s vs 500MB/s)

It will eventually load. It did this for me when I first upgraded from 6.x.x to 7 beta

Why on earth do you have a docker.img that is 768GiB??? Are you running 300+ docker containers? Go to the docker tab and click "Container Size" at the bottom. What does that output? For example:

Im sorry, I mis-spoke, you will set level 2 split for your media share. However, because of the allocation method choices, you cannot really pick which specific disks are used UNLESS you create two separate shares one for movies and one for tv shows. Only then can you select which disks each share can occupy. You can also use the unbalanced plugin and manually "gather" the files to the correct disks periodically.

Split Level 2 I believe is what you want for your media share. "Automatically only split the top two levels as required"

I’m gonna be honest here, you need to do a thorough analysis of your docker container path mappings. I think you have your dockers mapped to wrong locations and are putting the blame on Unraid. for example, you said you have a “Media” share and a “Movies” share. That alone tells me you messed up mapping movies in one of your dockers and it created a Movie share. You should have mapped your “Movies” to /mnt/user/Media/Movies but instead you probably have /mnt/user/Movies. this has nothing to do with “user” and “user0” which I think you’re wrongly putting blame on. also the screenshots up a few posts of your host paths edits you’re putting /mnt/user to /mnt/user/Movies/TV. You’d never do this instead you’re supposed to map /TV on the container side to /mnt/user/Media/TV TL;DR you need to check every docker path map to make sure they’re properly mapped to the host locations. Also make sure you’re properly using capitalization because it matters (Movies and movies would be two separate locations) you also need to move any files that are outside the Media share back into the media share under the respective directories or you won’t see all your files. you can use the unbalanced plugin to move them. DO NOT MOVE FILES BETWEEN USER AND USER0

I noticed that myself. I had 3 IronWolf 12TB drive and would easily have a 200MB/s average parity check speed. I added a couple of WD Red Plus drives of same capacity 12TB drives and it easily slowed the process quite a bit. I will say that I also went from single parity to dual parity as well.

IMO with unraid, you really don't have to worry about much linux stuff unless you want to really get into it for some super custom stuff. Linux is really optional when in comes to setting up and using Unraid. With that said, try this: Go to the "Tools" page on your unraid dashboard, there should be an option called "Docker Safe New Perms," click on it, click the checkbox, and run it. This will set the correct permissions for all files and directories. Hopefully this fixes your plex media deletion issue. You should be able to delete the media off your NAS through the plex docker. Im honestly surprised it isn't deleting. The only other thing I can think of is the mountpoint for your media is set to "read only" instead of "read/write." To check this, click on plex docker, hit the edit button to open the docker configuration page and make sure the Access Mode is set to read/write

What is your plan when an update breaks your system before you can get control?

/root/.ssh is a pointer to /boot/config/ssh/root/

Press the Green "Lock" Icon in the upper right hand corner, drag and drop, press it again to lock it.

When I posted about this type of issue, I was told to just monitor if more occurred. So far I've only had one on my system.

The term "Cache" is a misnomer. It's just the name for the SSD in a pool outside the array, the default name for the first pool is "Cache" and your appdata share will default to it. My "Cache" pool consists of two SATA SSDs in a ZFS Mirror and contains:

@dellorianes Find the “Users” menu either in the header itself or under Settings. click on root or whatever account you’re using, you can remove it from there.

@Djoss - Anyway to get the image updated to contain makemkv version 1.17.8? Looks like the build failed on github.

There is a much more simple way to figure this out, simply enter 'lsscsi -g' and get the following: lsscsi -g [9:0:0:0] cd/dvd HL-DT-ST BD-RE BU40N 1.03 /dev/sr0 /dev/sg6