Docker Container not starting when "unassigned device" share is offline

[Pixelpaule]

Hello all,

I have two Unraid servers. Server 1 stores my personal data, music collection and photos. The second server is my data storage for my backups, movie & series collection.

The Emby server runs as a Docker container on server 1. The shares movies & series are mounted with the unassigned devices plugin as remote SMB shares on server 1 and then mounted in the Docker container. When server 2 now goes into sleep mode, the Emby Docker container on server 1 crashes after some time (this can be a few hours). If I try to restart it and server 2 is still in sleep mode, it does not work. The Docker container can then no longer be started.

Is there any way I can implement my scenario cleanly so that the remote shares only work?

[Squid]

How does it "Not Start"  I do the same thing with Plex and have basically zero issues (short of the obvious that half the movies / TV is missing from the library)

[Pixelpaule]

Thank you for your answer. If the datastore is in sleep mode, then the Docker container can no longer start. I don't know what the problem is either! Are there any log files I can provide? After some time the error message "Execution Error" comes up....

 

Unraid Version: Version: 6.10.3

UD Plugin: 2022.08.07

 

 

 

Edited August 11, 2022 by Pixelpaule

[Squid]

1 hour ago, Pixelpaule said:

After some time the error message "Execution Error" comes up....

When this happens again, edit the template make a change (any change) and then revert it.  Then Apply  The docker run command will pop up which will tell us the error that is happening

[Pixelpaule]

hey, here is the output:

 

[Squid]

Try changing the references from /mnt/remotes/... to instead be /mnt/disks/... and see if that immediately lets it start up

[Pixelpaule]

@Squid After chaning the Path the emby docker start up. But unfortionaly i cant access to the data on these shares.

[Pixelpaule]

Hello all, 

Please excuse my late feedback, but the last time was a bit stressful and then I was still on vacation.
Unfortunately the problem still exists. When I look in the terminal under /mnt/disks/ "Remote Share Name", there is no data. But as soon as I change to the directory /mnt/remotes/ "Remote Share Name", the data is displayed accordingly. However including the shares in Emby Docker with /mnt/remotes/ "Remote Share Name" unfortunately results in an error and Emby can no longer be run when the remote server goes into stand by.

I hope someone can help me.

[Squid]

On 8/12/2022 at 2:20 AM, Pixelpaule said:

@Squid After chaning the Path the emby docker start up. But unfortionaly i cant access to the data on these shares.

Try setting the access mode when editing the template on that path to be RW: SLAVE

[Pixelpaule]

Hmm, unfortunately it does not work. As before, Emby cannot access the data. Also in the terminal I can't see any data when I print /mnt/disks/ "Remote Share Name" via the terminal.

 

Do I need to set anything else elsewhere in Unraid? Can I provide any logs?

Edited September 7, 2022 by Pixelpaule

[Squid]

Any thoughts @dlandon

[dlandon]

The correct path for your remote share is /mnt/remotes/DATENLAGER_filme/.

 

The issue seems to be with the Emby Docker trying to mkdir on /mnt/remotes/DATENLAGER_filme/.  Emby is tyrying to create that mount path.  Emby should only be using that path for gathering media.

 

Post a diagnostics file.

[dlandon]

What docker are you using from CA?  I'd like to give it a try.

[Pixelpaule]

I use the offical Docker from the Emby. I have attached the diagnostic files.

 

@dlandon Sorry but i think i don't understand your first post. XD

 

You are correct, the path to my movies on the second unraid server (the remote server) ist /mnt/remotes/DATENLAGER_Filme/ as you can see in my screenshots from the "Apple" terminal. If i use /mnt/remotes/Datenlager_Filme/ in the Emby Docker settings, emby can access the data correctly if the server is started. But if the server goes to sleep mode the Docker container crash. If i use /mnt/disks/Datenlager_Filme/ emby can't access to the data. Not even if the remote server is started.

 

heimzentrale-diagnostics-20220907-1818.zip

[dlandon]

2 hours ago, Pixelpaule said:

Sorry but i think i don't understand your first post.

If you look at the failure of starting the docker, it is because Emby is trying to create the directory 'mkdir /mnt/remotes/DATENLAGER_filme/' and it fails because that mount point exists.  It was already created by UD.  I'm not understanding why a docker is trying to make a directory that should already exist and should be used to access existing media.

[dlandon]

It doesn't look like you are mapping the folders properly.  Emby is set to use /mnt/ and you map the media folders in the docker itself:

 

Once inside Emby, you select the folders for the media you want to use:

and choose the folders for each media type:

or probably the best approach:

 

Substitute your server name for 'Tower'.

[Pixelpaule]

yes that's right, i have create for each library folder it's own folder path in the docker settings. I wanted to configure the read and write permissions for each path in Docker itself. So this seems to be the problem?! I have attached screenshots of the path settings as they are currently configured.

 

 

[Pixelpaule]

11 hours ago, dlandon said:

or probably the best approach:

 

Substitute your server name for 'Tower'.

 

Do I need to specify the server name of the Unraid server that Emby Docker is running on, or the name of the Unraid server that the remote share is on?

Edited September 8, 2022 by Pixelpaule

[dlandon]

1 hour ago, Pixelpaule said:

 

Do I need to specify the server name of the Unraid server that Emby Docker is running on, or the name of the Unraid server that the remote share is on?

Use the remote share if it is a smb share.

[Pixelpaule]

Yes, the remote share is also available via smb. okay i change it. Thanks for your help! I think now it works!