Scan media library failed

[bocabill 1]

I started getting this error a few days ago.   No scan of the library would finish.

 

I'm running Emby Server for Windows, version 3.5.2.0 on a Windows 10 rig, the libraries are on a Drive Bender pool.  I tried stopping Emby, renaming the library db file, restarting and rescanning, but got the same outcome.   So I decided to not go with any half-measures and "went nuclear".   I removed Emby using Revo unistaller.   Choose the "remove all traces" option in Emby's uninstaller, and let Revo scan for and delete any registry entries it found.  I then removed any remaining folders/files that were left over.   I don't mind re-configuring Emby from scratch (it's not all that time consuming and it lets me explore the settings) so I am willing to re-rebuild the libraries again in order to get it back into working order.

 

I then did a Windows error check of my drives (it found and repairs some corrupt files) and ran a scan and repair on the files in the Drive Bender pool.   After that, I reinstalled Emby Windows server, gave it a "simple" library to scan (my photos), and the error still occurs.

 

 

 

Attached is the latest log.   In case it was a matter of plug-ins, I have removed all of mine, restarted the server, and scans still fail.   The timestamp on the log file after the removal of the plugins.

 

Any advice, insight or assistance would be most appreciated.   Thank you in advance.

 

Bill

Log.txt

[mastrmind11 722]

corrupt db?

[bocabill 1]

corrupt db?

 

I thought so too, but renaming it then rescanning (to created a new library.db) didn't resolve anything and neither did a complete uninstall-disk check/repair-reinstall of Emby itself.  The new db's from both approaches (if it is a corrupt db) still give the same error.

Edited August 19, 2018 by bocabill

[mastrmind11 722]

I thought so too, but renaming it then rescanning (to created a new library.db) didn't resolve anything and neither did a complete uninstall-disk check/repair-reinstall of Emby itself. The new db's from both approaches (if it is a corrupt db) still give the same error.

Try removing libraries and adding them back 1 by 1 until you find the one that's blowing up.

 

Sent from my SM-G965U using Tapatalk

[bocabill 1]

Try removing libraries and adding them back 1 by 1 until you find the one that's blowing up.

 

Sent from my SM-G965U using Tapatalk

 

I'll get started on that and report back how it goes.   But wouldn't the deinstall and manual removal of all Emby files/folders followed by a completely clean reinstall have removed all of the old db's and created completely new ones?

[Guest asrequested]

Can you create a test library that's not in a drive pool, and scan only that library?

[mastrmind11 722]

I'll get started on that and report back how it goes. But wouldn't the deinstall and manual removal of all Emby files/folders followed by a completely clean reinstall have removed all of the old db's and created completely new ones?

Yes, but I think one of your libraries has some bad metadata. The logs point to a DB constraint being violated on insert which likely means bad metadata in one of your libraries. I saw a Pictures library right near the error, so maybe try removing jus that library first and rescanning.

 

Sent from my SM-G965U using Tapatalk

[bocabill 1]

Yes, but I think one of your libraries has some bad metadata. The logs point to a DB constraint being violated on insert which likely means bad metadata in one of your libraries. I saw a Pictures library right near the error, so maybe try removing jus that library first and rescanning.

 

Sent from my SM-G965U using Tapatalk

 It was that library and I had made the mistake of thinking that images would "be simple files to run the test scan on".

 

Other libraries are scanning fine, now I just need to relocated and return those images to the library a folder at a time in order to find the offending files.

 

Thanks for the assistance!

[Luke 42083]

Thanks I'm glad you were able to resolve it. This is a difficult one to gauge on the current release but due to changes with the next release I'm pretty confident that it won't happen again. Thanks.

[gerry.emm 10]

Hi all...

 

I  am having the exact same problem.  I have done exactly the same thing...a complete un-install of EMBY followed by a "basic" re-install without any exotic plug-ins.  I even added one library at a time and let EMBY scrape each library before adding another...I'm not sure what is being referred to as a "drive bender pool" in this post, but my media libraries are contained on 7 external USB drives...I was hoping someone could possibly take a look at my latest log file and tell me which of my libraries is the offending one and how to correct / modify it to resolve the problem

 

THANK YOU  in advance for any help you can provide!!!  It is TRULY much appreciated!!!

 

Gerry

 

 

embyserver.txt

[mastrmind11 722]

Hi all...

 

I  am having the exact same problem.  I have done exactly the same thing...a complete un-install of EMBY followed by a "basic" re-install without any exotic plug-ins.  I even added one library at a time and let EMBY scrape each library before adding another...I'm not sure what is being referred to as a "drive bender pool" in this post, but my media libraries are contained on 7 external USB drives...I was hoping someone could possibly take a look at my latest log file and tell me which of my libraries is the offending one and how to correct / modify it to resolve the problem

 

THANK YOU  in advance for any help you can provide!!!  It is TRULY much appreciated!!!

 

Gerry

Your log is basically nothing but errors.  Disable DLNA if you aren't using it.  Not sure how far you got adding your libraries, but there are a bunch of ffprobe errors w/ the Glee Extras media.  Have you been able to add other libraries successfully?  If so, then I'd try removing that media from the library that's failing and see if it progresses.

[Luke 42083]

@@bocabill

A couple people have reported this scan failure and I haven't' yet traced it down.

 

It is resolved for the next release though on account that the code throwing the error here no longer exists. Based on that you could try running the beta server, or do a new fresh install and see if it happens again. Thanks.