Emby Docker - No longer exporting any metadata

[itsrumsey 4]

Hey guy, this has been going on awhile and behavior has gotten stranger.  I have always used the docker image on Unraid.

 

So what is happening is starting around November 2016, Emby stopped downloading extra fanart on its own and exporting it automatically.  Here is an example of how a folder would look before November - Emby would automatically get all art + extra fanart + create nfo files for media:

Staring in November the extra art folders would no longer download, and then it looks like this:

You can see it still grabs the poster and one backdrop, as well as creates an nfo, but no extra art.

 

And then finally, as of around 3/1-3/3, it is now writing no metadata to disk, as so:

No poster, backdrop, extra art, or nfo file (the one you see here - orig.nfo, is a carryover from CP rename).  Literally nothing.  I have tried toggling my Emby metadata settings off and on to no avail:

 

And if you look at the profile in Emby WebUI for the newer films missing all metadata, it still purports to have them downloaded:

 

I thought perhaps this could be a permissions issue, so I changed the user to root, but that didn't fix it:

 

 

I've checked in the logs and didn't see any failure to write to disk or even any attempt to write to the disks, so I am pulling my hair out trying to figure out why Emby decided one day it hates metadata.  Any help would be appreciated.

Edited April 7, 2017 by itsrumsey

[Luke 42078]

Hi, go into Emby library setup, click on each library and ensure it is configured the way you want it. Let us know if this helps. Thanks.

[itsrumsey 4]

Hi, go into Emby library setup, click on each library and ensure it is configured the way you want it. Let us know if this helps. Thanks.

 

This fixed it!  I should have asked when the problem started happening and the settings location change would not have crept up on me slowly over such a long time.  Now I have ~6 months worth of TV missing metadata nfos though, is there any way to mass update and generate metadata missing on disk?

[Luke 42078]

Several months ago. You could do refreshes from top level folders using the metadata manager. You can also just not do anything, and over time as things get saved then you'll see metadata files start popping up in the folders.

[itsrumsey 4]

Several months ago. You could do refreshes from top level folders using the metadata manager. You can also just not do anything, and over time as things get saved then you'll see metadata files start popping up in the folders.

 

Mostly I mean for individual episodes that aired during those months.  Can I go to the /config folder and delete the locally cached Emby metadata (images & nfos) for the entire library, and Emby will notice there is missing metadata and redownload / write it to disk?  If so, which folders contain the locally cached metadata?  I found all the images in /metadata/library but I am not sure where the text metadata is stored.

 

 

For instance, Metadata manger thinks these movies already have all their metadata even though it isn't written to disk:

 

I want to wipe out any locally cached metadata in Emby's /config folder so that next time it scans, it shows all the art and metadata for these items as missing.  That way I can do a refresh for missing data instead of mass update thousands of items and redownload images that already exist.

Edited April 7, 2017 by itsrumsey

[Luke 42078]

 Either refresh from top level folders using the metadata manager, or just not do anything, and over time as things get saved then you'll see metadata files start popping up in the folders.

 

For that screenshot above, those items do have metadata somewhere, and that is why they are shown the way they are.

[itsrumsey 4]

Yes all items have metadata stored in Emby, but not on disk (since November) which is the problem.

 

To anyone else who had this issue, ultimate I had to do another docker installation of Emby (didn't bother linking to ID), set metadata options, and add / scan the libraries.  Took several hours and the new Emby folder was >30GB by the time it finished, but it did the trick.  Then I just deleted the instance, restarted my "real" Emby docker, and performed a library refresh.

[Luke 42078]

That was clever. Thanks for reporting back.