MowMdown

Pretty typical for a single threaded application

Just in case anybody wants to know, yes it's possible to pass an optical drive to a remote machine using iSCSI... I was even successfully able to flash firmware to mine. Edit: I do not recommend using "/dev/sr#" in the event it changes if you add additional disc drives, instead use the "/dev/disk/by-id/ata-HL-DT-ST_BD-RE_BU40N...." whatever your disc drive is so it always stays the same. Why would I want to do this you ask? Due to the lack of proper IOMMU support on my motherboard, and the flashing tool being windows only, how else would I flash the firmware without tearing my NAS apart and flashing it on another host? I made it into an iSCSI target. Initiated it on a windows VM and flashed it. I had to use targetcli in order to set up the target but it was relatively simple. I used this as a guide Config: o- / .........................................................................................[...] o- backstores ..............................................................................[...] | o- block ..................................................................[Storage Objects: 0] | o- fileio ................................................................ [Storage Objects: 0] | o- pscsi ..................................................................[Storage Objects: 1] | | o- dvd_backend ..........................................................[/dev/sr0 activated] | | o- alua ...................................................................[ALUA Groups: 0] | o- ramdisk ................................................................[Storage Objects: 0] o- iscsi ............................................................................[Targets: 1] | o- iqn.2003-01.org.linux-iscsi.tower.x8664:sn.xxxxxxxxxxxx ...........................[TPGs: 1] | o- tpg1 ..................................................................[gen-acls, no-auth] | o- acls ..........................................................................[ACLs: 0] | o- luns ..........................................................................[LUNs: 1] | | o- lun0 ............[pscsi/dvd_backend (/dev/disk/by-id/ata-HL-DT-ST_BD-RE_BU40N) (None)] | o- portals ................................................................... [Portals: 1] | o- 0.0.0.0:3260 .................................................................... [OK] o- loopback ........................................................................ [Targets: 0] o- vhost ........................................................................... [Targets: 0] o- xen-pvscsi ...................................................................... [Targets: 0] Windows Device Manager:

It applies to the SONOFF Dongle E as well as it uses the same hardware. These are the only two radios compatible with Multiprotocol firmware. (or any coordinators which use the Silicon Labs EFR32MG21 radio) Any further discussion I would prefer to take to private messages to not take away from the OP.

@Vr2Io, As I mentioned in my previous comment, it was just something I wanted to share with OP as a precaution. Related or not. I know what 2.4GHz is and what devices utilize it. The explanation was unnecessary. I own several running my own custom firmware.

Just want to say that HA does NOT recommend Multiprotocol due to it being a buggy mess and not really compatible with the hardware. Link

It's not supposed to be different.

My setup has a "media" share that I use to store my "movies" and "tv shows" the host path of this location is "/mnt/user/media" So for plex, I would map /media to /mnt/user/media so when you're inside plex, and you add a library, you'd navigate to /media/movies for the movies library and /media/tv shows to add a tv shows library

See if you can restore the DB from a backup: https://support.plex.tv/articles/202485658-restore-a-database-backed-up-via-scheduled-tasks/

I see a couple things you can improve on here: 1. Your media should be stored in a root share that you would have created. For example: /mnt/user/plexmedia and then inside that would be your plex library folders "movies" and "tv shows" Your first path should be changed from /mnt/user to /mnt/user/plexmedia (or whatever you call it) 2. The transcode path is not a valid unraid location, ideally you'd just delete this or leave it blank and let plex handle it. If you prefer to transcode to your system RAM you could change it from /config/transcode to /dev/shm These should fix your issue.

Click on the plex docker icon, click edit, that's the template.

You need to fix your container volumes/paths to stop plex from writing data inside the docker.img. Post a full screenshot of your plex docker template, if necessary redact your plex claim token if one is visible.

You don't have a terminal window open on a different machine browsing disk4 do you? If you do, kill it. Same goes for any processes that might be accessing that disk, kill those too.

Files being "Unprotected" means you do not have a Raid1 or Mirror cache configuration(parity for cache basically). First you can use mover to try and move the files back to the Appdata share on the cache but if there are any duplicate files, mover won't move them because it will not override files of the same name. To do this, under the Appdata share settings, assign the primary storage to your cache pool, set the secondary storage to the array, set the mover option "Array --> Cache." Stop the entire docker service from the settings menu and run mover. Once you're done, set the secondary storage option back to "None" If you have files left over you need to decide how you want to proceed further.

New Test Build: 1.41.1.9065-2a572c0eb Features included in addition to previous features: - Colorspace fixes on mac and potentially others - Fixed the dovi playback issue on android (FYI, we do not have the license to transcode dovi so it is stripped from all transcodes) - Added settings for DVR transcodes to allow for more control over size/quality

@bally12345 You don't use the full URL for this method. You only need this part of it: https://artifacts.plex.tv/plex-media-server-experimental/

FYI, there is a newer test version available: https://forums.plex.tv/t/hevc-encoding-forum-preview/888127 Version: 1.41.1.9043-2ace0d939 Chris over at Plex:

Then all you need is to do is just add this to the "extra parameters" section --device=/dev/dri The Nvidia stuff is ONLY if you're using an Nvidia GPU card.

@bally12345 what happens if you console into the plex container? Can you see the "custom-cont-init.d" folder and script inside? what happens if you try and execute it while you're inside the container?

That's strange, no idea why it works for me? Maybe try copying it from this URL where I got it from originally? https://gist.github.com/vertigo235/051b076f2ad79132b87c7da37158e1b8 Here's the Plex forum post with the links to the .deb files too: https://forums.plex.tv/t/hevc-encoding-forum-preview/888127

I made a mistake, I created a folder called "custom" inside my plex appdata folder, then for the script pathing just map to the "custom" folder and leave out the script. That's my bad. Also looks like I used an underscore instead of a dash in the script name. Edit: See updated instructions:

@bally12345 did you save the script locally? Does it have permission to execute? chmod +x /mnt/cache/appdata/plexmediaserver/custom-install.sh (note: the file path has to match where you saved the script, the above was just an example from my own setup) you should see this in the plex docker log Edit: It appears you have a trailing "/" after the script in your Host Path 5, remove it.

Edit 2: There is an easier way to do this, simply change or these to you container configuration: The full URL for this is: https://artifacts.plex.tv/plex-media-server-experimental Edit: Can confirm it works:

Are there any known issues with QSV AV1 Encoding? Can't seem to take a 4K HDR source and encode it down into 1080p (10bit or 8bit) using AV1 QSV (Intel Arc A310) Unraid keeps spitting out Segfaults like this: Tower kernel: ghb[2951134]: segfault at 1ffff216b ip 000014c5c025ab36 sp 000014c5bb402850 error 4 in libmfx-gen.so.1.2.10[14c5c0050000+487000] likely on CPU 8 (core 0, socket 0)

Did you properly pass the GPU through into the container?