Hi, I’ve been running my server through the Linuxserver Plex docker package through my Synology for months without issue. However, recently, I’ve noticed that hardware transcoding is no longer working and I’m not sure what has changed. I remade the server over and over with my original Docker settings through Putty, and tried this across public and beta packages last night and this morning, but no changes. The only thing I can think of is that there was a power cut in my house 48 hours ago and this was the first time in 3 months my Synology restarted - I restarted the NAS again whilst trying to fix the issue myself and remake the image. I don’t know how this would have affected the Quicksync drivers but this is the only major change I can think of.
That was why it was a bit of a surprise, I’ve rebooted before and not had the issue. Either way it’s back to normal now - I wouldn’t have noticed myself as I can direct play 99% of stuff, but other users attempting any 4k file were in for a bad time.
I went and looked – Nothing changed on the Plex side
I rebuilt my container (plexinc/docker) – All working as it should with HW tone mapping. (did both rm and rmi then a fresh pull)
I hate to sound dumb, but could it have anything to do with the improper shutdown caused by the power outage? Perhaps a normal shutdown and boot doesn’t cause issues, but the unexpected shutdown made it turn off any non-default permissions until manually re-enabled? I might test later if restarting my NAS gets rid of HW transcoding again, but tbh I can’t be bothered with going through the issues again right away after a couple of days of it!
Do iiiiiit. Sounds like it has been a rough couple of days on the support side due to update issues. RUN. If there’s an issue just keep it in mind for next week!
Hi, the same problem happened to my Synology 918+ but ‘chmod -R g+rw /dev/dri’ was not enough to fix it.
I had to run ‘chmod -R ugo+rwx /dev/dri’
It’s maybe too much but it works.
Last week, I updated DSM and the Docker package. Maybe this is the cause of the regression.
chmod of /dev/dri will vanish the next time the NAS is restarted because /dev is created and populated by the kernel during initialization.
In DSM 6 (native package) I add the udev rule which changes /dev/dri to allow access.
In Docker, without the native package installed, you’ll want to match the GID as created by the kernel.
You only need make certain to have functional equivalent file permissions such (dir = 755, and files = 644) which you can have by using the normal file station gui ( Everyone = read )
