Big meta data trouble after migration - need assistance

[MatthiasM 6]

Hello community!

1st this is not a NAS or Synology issue, but my problems began after a successful migration to a new NAS.

I run Emby Server a couple of years in this configuration without any meta data trouble so I'm not very firm solvong problems like this.

After the mirgration I recognise some wrong showed images at the Emby start screen:

Soon I find out that there are some access right problems and that the emby user didn't have the nessesary rights with the file structure of the NAS.

After fixing that access right issue I restart Emby and the wrong images was still in place. I try to renew the metadata within Emby but it won't work.

So I recover my metadata folder from brackup and I end up with this:

It is not nessesary to say that I spend more tha a year to organize and pimp my meta data with Emby and I hope that was not for the waste.

I did make backups from everything EmbyServer-, Emby- and all content-directories. In these directories are all meta infos within the .nfo files and all folder images.

 

How did I get my meta data back in sync with my content?

Thanks for any help ladies and gentlemen!

 

Best regards

Matthias

[Carlo 4561]

Hi, what version of the server were you on prior to the migration?  What version are you running now?

[MatthiasM 6]

sorry cayars, I miss to write that information.

I ran Emby Server 4.6.4 on a Synology NAS DS718+ and migrate it to a DS920+.

The Emby Server is still 4.6.4.

cheers

Matthias

[Carlo 4561]

OK so no version change. Is this DSM 6 on both?

[MatthiasM 6]

DSM 6 latest on both.

After the migration Emby Server was not able to read the content directories due to locked shared folders.

I think that was the initial issue why Emby starts to change the metafiles.

[Carlo 4561]

How long did it take to copy everything over?  Do you still have the original setup on the 718+ ?

[MatthiasM 6]

No. I choose the migration by swapping the disks to the new NAS. There are a cupple of backup generations I did make with HyperBackup of all Emby folders - I did also make a tar.gz every saturday from /volume1/Emby and /Volume1/@appstore/EmbyServer and backup it to a 2nd NAS

[Carlo 4561]

Any chance we could do a remote support session so I can get a better look and maybe help you get back on track?

[MatthiasM 6]

Thanks for the offer cayars but that is not possible.

I help myself by restoring an old backup of /volume1/Emby and /volume1/@appstore/EmbyServer witch contains Emby v4.5.4

All metadata are back in place.

I cannot proof it but I think the upgrade from 4.6.3 to 4.6.4 just before migrating the NAS does made changes to the metadata.

I will do a cupple of copies of the 4.5.4 directories and try to upgrade 4.6.0.50, 4.6.2 , 4.6.3 and 4.6.4 to see what will happen.

I'll keep you informed

[Carlo 4561]

Yes please let us know how you make out.

[MatthiasM 6]

Ok here is the update and what I was able to reconstruct:

1. after the migration of the NAS the 1st boot will start Emby automaticly but Emby has no access to the locked shared folder of the NAS and also not to the folder images
2. the mainscreen at Emby looks unusal, the images are displaced by other images but covers
3. I did a metadata rescan with Emby (this was my main mistake during the migration) but with still no access to the content directories
4. all images and all customization was gone and end up with the screen shown up in the top of this treat.

The right way is simply stop or shutdown Emby after the NAS has booted. Unlock all folders what is usaly nessesary just 1 time after migration. Restart Emby and all your metadata should be in place. Migration finished.

But life is not that easy! Why did I start this threat and why does my restore of the Emby Server 4.6.4 didn't work.

As I described above I do a restore of a Emby Server 4.5.4 and all my problem with the metadata are gone. A restore of 4.6.4 didn't bringt that cure.

After restoreing 4.5.4 I make many copies of the depended directories, make upgrades in each copy and switch between the version by setting some softlinks.

So I can switch backward and forewards trough the versions.

With 4.5.4 the CD covers looks correct:

After upgrading to 4.6.0.50 the CD covers looks damaged:

And this effekt looks similar to the DVD covers after the migration of the NAS. The covers disapear and alternative images was shown.

I does investigate what happen during the migration of the NAS but I have no clue what happen during the upgrate to 4.6.0.50.

Last upgrade was to 4.6.4 and the look is equal with some differences within the listing:

I don't know what exact happen to the covers but maybe you can change the behavior of the upgrade prozess or better what within the content scan at the start of Emby Server happen to the metadata.

Looking foreward to get a solution

Thanks, Matthias

 

 

 

[Luke 42080]

@MatthiasM are your images located in your music album folders? If so then make sure to configure the music folder structure option on your music library. It is one of the first couple options in the library settings dialog.

[MatthiasM 6]

thx @Luke I did that already with my music library and my problems with that issue are gone.

I just wrote that last post in this topic to keep the community informed about the issue of the missing file permissions aftre migration to a new NAS.

emby will autostart after the mirgration but miss the nessesara file rights to read the libraries and that looks very terrible

best regards

Matthias

[Luke 42080]

4 minutes ago, MatthiasM said:

thx @Luke I did that already with my music library and my problems with that issue are gone.

I just wrote that last post in this topic to keep the community informed about the issue of the missing file permissions aftre migration to a new NAS.

emby will autostart after the mirgration but miss the nessesara file rights to read the libraries and that looks very terrible

best regards

Matthias

Hi, sure, but that's a new server machine, new system user. That sort of thing is up to you to manage.

[MatthiasM 6]

That right Luke. But it is not nessesary that someone else traps in that pit

thx

Matthias