automatically creating a folder under /mnt/

[kicsrules]

Anyone knows where to look when a folder is automatically created after reboot...

 

i have a /mnt/videos folder created after each reboot, don't know where to look to modify this setting...

 

i don't use the folder, i do have emby / sonarr / transmmission but i already checked docker settings for each, no app/setting is requesting the creation of /mnt/videos ....

 

thnx in advanced

[JonathanM]

Does the folder still appear if the docker service is disabled in settings?

[kicsrules]

35 minutes ago, JonathanM said:

Does the folder still appear if the docker service is disabled in settings?

no, does not appear...

 

 

[trurl]

I know you said you checked, but you must have a container volume mapping with host path /mnt/video

[trurl]

2 minutes ago, trurl said:

a container volume mapping with host path /mnt/video

Or possibly a host path of just /mnt so the container is able to create the video folder there.

[kicsrules]

ok, so how do i look for it ?

 

since i already checked the mappings on the main settings

[kicsrules]

the only docker img that reference to /mnt/videos is emby, but on the settings app

 

[trurl]

That host path is clearly on disk2. Nothing obviously wrong with that container path depending on how the application uses it.

 

But, in any case, an incorrect container path can cause other problems (such as filling docker.img), but it cannot create a path on host storage. Only an incorrect host path can do this, because a container only has access to mapped host paths.

 

And since it doesn't happen with docker disabled, some container must be doing it

 

How many dockers do you have?

[kicsrules]

12.....

 

[trurl]

Edit each to see what host paths you have. Be sure to check under "show more settings"

 

Or

 

Get docker run command for each. The mapped paths will appear after each -v parameter, host path followed by colon followed by container path.

 

You need to find the host path that specifies /mnt or /mnt/video.

[kicsrules]

went 1 by 1 viewing advanced settings and none of them show /mnt/videos folder.....

 

how can i look the run command for each docker ? i updated 2 of them, no /mnt/videos after -v

[kicsrules]

went 1 by 1, modifying something in the docker settings and hitting apply, none of them show /mnt/videos 

[JonathanM]

2 hours ago, kicsrules said:

went 1 by 1, modifying something in the docker settings and hitting apply, none of them show /mnt/videos 

You forgot the important part, do any of them reference just /mnt all by itself?

[kicsrules]

yes, emby is the only one

 

[JonathanM]

21 minutes ago, kicsrules said:

emby

Set emby not to autostart, and see if the video folder is still created as long as emby doesn't get started.

[kicsrules]

the folder gets created when emby is started.... 

 

[itimpi]

2 hours ago, kicsrules said:

the folder gets created when emby is started.... 

 

That implies a mis-configuration of emby.  

 

Any idea why emby is configured to give it access to /mnt on the host in the first place as this seems unusual.    The location /mnt/videos it is creating is only in RAM so it’s contents are lost on reboot.

 

It might be worth asking in the emby support thread if you are not sure.

[trurl]

5 hours ago, itimpi said:

why emby is configured to give it access to /mnt

My guess is to simplify accessing other things in addition to user shares, such as an Unassigned Device. I don't use emby, does it have recording capability? Maybe something like that is misconfigured to write into /mnt instead of a user share or a mounted Unassigned Device.

 

Post your docker run command for emby.

[kicsrules]

docker run
  -d
  --name='EmbyServer'
  --net='host'
  --cpuset-cpus='0,1,2,3'
  -e TZ="America/Chihuahua"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="KXUNRAID"
  -e HOST_CONTAINERNAME="EmbyServer"
  -e 'TCP_PORT_8096'='8096'
  -e 'UID'='2'
  -e 'GID'='2'
  -e 'GIDLIST'='2'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8096]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/MediaBrowser/Emby.Resources/master/images/Logos/logoicon.png'
  -v '/mnt':'/mnt':'rw'
  -v '/mnt/disks/media2/media/videos':'/mnt/videos':'rw,slave'
  -v '/mnt/user/appdata/EmbyServer':'/config':'rw'
  --device='/dev/dri' 'emby/embyserver:latest'

6a4c9700e8dab0f7619f6563a38313dcc9d12a8b72481498c44fe2e70a51d601

The command finished successfully!

 

[trurl]

I see you already have a mapping to the Unassigned Device media2, so I don't see what is to be gained by having a mapping directly to /mnt. Seems like mapping /mnt/user would make a lot more sense if all you need to do is get to all of your user shares.

 

In fact, your mapping to the Unassigned Device is the container path /mnt/videos. But, you already have the container path /mnt mapped to the host path /mnt.

 

So, /mnt/videos is a container path inside the /mnt container path, which is mapped to the host path /mnt. In other words, /mnt/videos is inside the host path /mnt. So that pretty much explains how you are creating the /mnt/videos folder on the host. And that folder is in RAM just like the rest of the Unraid OS, since it isn't a mounted disk or user share.

 

What is the purpose of your Unassigned Device mapping? How did you decide to do it this way? It can't have ever worked correctly.

[kicsrules]

Quote

What is the purpose of your Unassigned Device mapping? How did you decide to do it this way? It can't have ever worked correctly.

the unassigned device is a ext4 usb drive (that was on another server omv)..... soon it will change it to an array folder....

[trurl]

The UD isn't really the problem. It is your mapping /mnt to /mnt. If you map /mnt/user on the host to some path in the container (could even be /mnt/user) then emby will have access to all your user shares.

[trurl]

I think it actually adds to the confusion if you try to make container paths the same as the host paths. And it makes it easier to make the sort of mistake you have made.

 

A better idea would be to map /mnt/user to /media, for example, then look in emby for your media in the /media folder. And you could map /mnt/disks/media2/media/videos to /video, and then look in emby for those files on that UD folder in /video.

 

 

[kicsrules]

removed /mnt -> /mnt

 

the folder no longer creates itself, now that path was on the docker settings.... appconfig data is in another folder, apparently everything is working correctly

 

[trurl]

10 hours ago, kicsrules said:

removed /mnt -> /mnt

Unless you added another mapping then emby will only have access to the UD (and its own appdata of course). Maybe that is all you want, but usually people put their media in user shares in the array.

 

Do you understand docker volume mapping?