dgreig

Sorry for wasting your time. I feel like such a fool

As requested: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='emby' --net='bridge' --cpuset-cpus='10,11,12,13,14,15,26,27,28,29,30,31' --log-opt max-size='10m' --log-opt max-file='3' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'UID'='99' -e 'GID'='100' -e 'GIDLIST'='100' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-66d7bffd-998c-3fd7-c9eb-f71063803d75' -e 'UMASK_SET'='000' -p '8096:8096/tcp' -v '/mnt':'/mnt':'rw' -v '/mnt/user':'/unraid':'rw' -v '/tmp':'/config/transcoding-temp':'rw' -v '/mnt/cache/appdata/EmbyServer':'/config':'rw' --runtime=nvidia 'emby/embyserver:beta' 26d948bb9ae05b57247936dc185bfc3f79713fc8acce655f5b05ae8ecc266653 The command finished successfully! The script I wrote to identify these issues runs every day and picked up the following this morning: Script Starting Fri, 06 Sep 2019 06:45:01 +0100 Full logs for this script are available at /tmp/user.scripts/tmpScripts/Fix File Permissions/log.txt Fixing files not conforming to unRAID permissions standards in XXX share /mnt/user/xxx/xxx/xxx/xxx.nfo : -rw-r--r-- /mnt/user/xxx/xxx/xxx/poster.jpg : -rw-r--r-- /mnt/user/xxx/xxx/xxx/fanart.jpg : -rw-r--r-- /mnt/user/xxx/xxx/xxx/landscape.jpg : -rw-r--r-- /mnt/user/xxx/xxx/xxx/logo.png : -rw-r--r-- Fixing directories not conforming to unRAID permissions standards in XXX share Fixing files and directories not conforming to unRAID user:group standards in XXX share Fixing files not conforming to unRAID permissions standards in YYY share Fixing directories not conforming to unRAID permissions standards in YYY share Fixing files and directories not conforming to unRAID user:group standards in YYY share Fixed all issues where found

Having an issue with the new UMASK_SET variable. I've set this to 000. However new images get created in my media folders with the wrong permissions. I have a user script to tidy these up but it would be good if Emby created files with the correct permissions. The files it creates seem to be using the default UMASK of 022 as created files are 644 and backdrops directories are 755. I want 666 files and 777 directories if at all possible.

Sounds like an issue with the HBA / Raid Card he is using. I had an issue sever versions ago where I had to replace a HBA to get drives to mount properly or even to see certain drives. May be an issue like that. Check against a d HBA or onboard SATA. Also it’s probably best that your issue is in a separate topic. the rc1 and rc2 testing was supposed to be limited to make sure that no problems are introduced since 6.70 stable