Long scan times

[satyr 2]

Running newest Emby version on freenas 9.3, which goes through a kodi plugin. Also running sonarr and couchpotato, but the scan problems I'm having seem to only be related to current media (i.e. scans that take place following no media changes still take 20+ minutes). I tried removing my entire music collection and cleaning up the TV shows that it couldn't scrape...to no avail.

 

At this point, I see some of the errors populating in the logs, but can't identify the source of the problem. It notes some errors in watching collections, but I don't know how to resolve those issues because there clearly isn't a connection failure/loss. An interesting part of the problem is that it completes 63% of the scan within 15-20 seconds, only to take 20+ minutes to finish the remaining 37%.

 

I've attached the latest bug log. Note that no changes were made to the database since the last scan.

 

Any help is appreciated.

 

http://paste2.org/DJWNf7AI

Edited July 28, 2015 by satyr

[satyr 2]

Here's another log file. Scans are still taking 25+ minutes.

http://paste2.org/eYddKO2P

[Luke 42081]

can you enable debug logging under advanced, restart emby and then repeat the test? thanks.

[satyr 2]

Here's a brand new log w/ debugging enabled: http://paste2.org/69sdfGAG

 

Since my original post, I've deleted and reinstalled the whole Emby server, and I never added any of my music to the system (to eliminate that variable).

 

The scan will go to ~52% within seconds, but then the remaining 48% takes around 25 minutes. No new media had been added in between this and my previous scans.

[satyr 2]

Bump for any help. Still haven't resolved this.

[satyr 2]

Bump for any help. Still haven't resolved this.

 

I deleted all metadata and removed any shows/movie that were not scraping correctly to eliminate them as possible issues. Rescanned the whole system without an issue, but the repeat scans are still taking 20+ minutes.

Here's the newest log file of just the scan. It looks like it complete successfully before the error showed at the bottom--I don't know what that error is telling me, either.

 

http://paste2.org/NIJ1C4JB

​

[Luke 42081]

I wouldn't worry about it. Once you get the next stable release, the startup scan will be removed and no longer necessary. Scans will be much less frequent, and subject to the performance of your disk I/O. So if it's occurring much less frequently, then it probably won't bother you.

[satyr 2]

I wouldn't worry about it. Once you get the next stable release, the startup scan will be removed and no longer necessary. Scans will be much less frequent, and subject to the performance of your disk I/O. So if it's occurring much less frequently, then it probably won't bother you.

Okay. The only time it really bothers me is when I've added new media that I want to watch immediately, or in the case of TV shows picked up by Sonarr, it takes almost the whole scan before they populate for me. 

 

Does it appear there's an error or is it just the size of my database (4000 tv shows, 1500 movies)?

[ebr 16187]

Holy cow!  I didn't even know there were 4,000 TV shows  or did you mean episodes...?

[Happy2Play 9783]

Have no idea if the OS is making a difference since you are on (Unix 9.1.0.0).

 

I guess it is hardware and/or network related but the server should make available newly added content with 1-2 minutes.  Or at least in my case it does.

 

Small server (Windows)

Movies 2573

Series 220 (episodes 11691)

Music (140 albums, 7 Artists)

[Nathanio 35]

I'm running the latest server and have also been suffering long scan times. I don't know what the trigger is for it suddenly to have started. 

 

Server specs are quite substantial:

 

• Xeon E3-1240
• 8GB DDR3
• 9TB shared pool of storage
• WHS2011

It causes poor performance when web-browsing to the server. 

 

I have a small 32GB SSD that I was thinking of using for my metadata cache store. 

 

Any other tips?

 

EDIT: Took 27 minutes to do the last scan. 

Edited August 31, 2015 by Nathanio