Server keeps forgetting folder contents

[trancemitr 1]

I recently added a new hard drive to my computer, and I created a "Movies" folder on it containing sub-folders for MKVs, Blu-Ray rips, etc.  I then added this folder to the Movies library the same way I did with other Movies folders on other hard drives.  Everything appeared to work fine.  The problem is that every time I restart the server the content from that newest folder disappears from whatever app I use to watch content (WMC, Theater, Android).  Oddly enough the folder still appears in the "Media Library - Movies - Manage folders" with the others.  If I remove the folder and re-add it the content reappears.  This is just frustrating; I really don't want to have to do this every time.  Any thoughts?

 

I'm using version 3.0.5781.8.  I've also attached a log file that covers a period of me starting the server, removing the folder, re-adding it, and restarting the server.

 

Thanks.

trancemitr emby log file.txt

[Luke 42083]

Hi, welcome. I notice your log has a library scan. Is it possible the content is unavailable during the time of the scan? If so then you'll want to adjust the time your library scan runs to a time that is better for you.

[trancemitr 1]

The library scan happened automatically after I removed and re-added the new Movies folder.  And it only takes a few moments since there's hardly anything on that drive yet. 

[Luke 42083]

It sounds like this is normal operation then? if you're removing and re-adding your movies folder just run a scan after adding and that should take care of it. or is there something i'm missing?

[trancemitr 1]

Let me try again.

 

When I restart the computer (or just the server software) Emby drops all of the contents of the newest Movies folder, "Movies4".  Everything from all of the other media drives/folders appears just fine.  Movies4 still shows up with the Movies1-3 and Documentaries folders when I go to Manage Server -> Library -> Movies -> Manage Folders, but the contents are nowhere to be found. 

 

To get the contents of the Movies4 folder to show up I have to remove the folder from Manage Folders, re-add the folder, and then re-scan the library.  The contents then show up, but they disappear the next time I restart.

[ebr 16187]

Is that folder on a different device than the others?  Is it an external (like USB) device?  Is it possible it is not fully initialized at the time the system starts up?

[trancemitr 1]

The folder in question is on a hard drive internal to the system.  Last night I tried swapping which SATA connector it goes to on the motherboard.  No change in behavior.  I then copied all the contents from that drive to an identical drive and swapped them out of the tower.  However, it's still showed the same problem. 

 

After playing around some more I found that I don't have to remove and re-add the folder from the Manage Folders area, I just need to re-scan the library for it to show that folder's contents.  As a work-around I just found under "Scheduled Tasks" that I can set the server to scan the library each time I start up the software.  That seems to have worked.  I still don't know why it was forgetting the movies in the newest folder, but this seems to "fix" the problem.​

[G0M 4]

Hi,

 

I have exactly the same issue here. My Emby is installed on a Ubuntu 12.04 OS.

I have something like 820 movies and sometimes Emby will only display 500 to 600 of them. This is quite annoying since it will screw up the incremental update of my Kodi database as well :s.

If i want my missing movies to reappear, I have to rescan my library. Since it takes up to 5min to rescan my whole library, i would like to know if some of you had some other ideas

 

Thanks for your help!

[Luke 42083]

We have some overhauls on the dev branch, it will take a little more time before they reach beta and stable, but hopefully this post offers you some encouragement:

 

http://emby.media/community/index.php?/topic/28101-305813-64-bit/page-5&do=findComment&comment=282550

 

In the meantime if you're experiencing this the workaround is just to run a library scan after starting the server.