Option to not remove library items if library storage is offline

[cnstarz 27]

On 6/8/2024 at 11:04 AM, darkassassin07 said:

This behaviour hasn't changed really, but you can easily work with it to achieve what you want. It's all about how you structure your media folders:

 

Within the share you mount, you should have another folder that then contains your media folders, such as:

//sharename/media/movies/<movies>

//sharename/media/tvshows/<tvshows>

On the emby host, you want to mount the /media portion wherever (say /mnt/media for example), with the /movies and /tvshows folders within being created and removed by the mount. When unmounted, those two folders should disappear leaving an empty /mnt/media folder.

From here, if you add the folder /mnt/media/tvshows to emby, and then the share gets dismounted; emby will see that folder missing entirely instead of being empty; so it will not remove the media from your libraries.

 

This is exactly what I do, as my media is mounted via samba. Works great.

I can confirm that this isn't working the way you're describing it.  I'm set up almost exactly this way and Emby still clears out my metadata.  The docker container has the root of all of my media mounted like so:

--volume /mnt/nasdata/media:/mnt/media

 

 Then in Emby, I added a 'Movies' library that points to

/mnt/media/movies

 

And a 'TV' library that points to

/mnt/media/tv

 

My NAS lost power, my Emby server was brought online while the NAS was still offline, then the NAS was brought back online, and now Emby is taking all day to scan folders and download all the metadata.

[Justinnnnnnnnnn 0]

Since there isn't a real answer to this issue.  To me the common sense fix would be to also host the /config folder on the nas too.  That way if the nas is down, the media and the metadata database is offline together.  Just need a restart of emby when everything is back up.  Sure it can be slower than running the config folder locally this way. I would recommend using nfsv4 at a minimum, since it supports file locking.

[Luke 43544]

6 hours ago, Justinnnnnnnnnn said:

Since there isn't a real answer to this issue.  To me the common sense fix would be to also host the /config folder on the nas too.  That way if the nas is down, the media and the metadata database is offline together.  Just need a restart of emby when everything is back up.  Sure it can be slower than running the config folder locally this way. I would recommend using nfsv4 at a minimum, since it supports file locking.

Hi there, please attach the Emby server log from when the problem occurred:

How to Report a Problem

Thanks!