Jump to content

Slow library scan


wickedlemon
Go to solution Solved by Malmgren,

Recommended Posts

wickedlemon

To think it was over a year ago when I started this thread:

 

https://emby.media/community/index.php?/topic/68467-slow-almost-non-existent-scan/

 

Due to a hardware switch round I'm back to running Emby on an Odroid C2 and the library scan is still so slow. It's currently stuck at 86.4%. It added the titles pretty quickly. But so far only one has a cover image and nothing is happening. Running 4.4.0.40, a library folder with only 41 movies all in their own folders with pre-exisitng nfo files. I have debug logging turned on and it's telling me nothing at all is happening other then web gui calls. Surely debug log should show everything that is going on?

 

Bored of waiting, I installed Emby on my Windows desktop PC and it tool less than 30 seconds to scan the lot and add all images.

 

So is there any more news on why Emby behaves like this on some systems? 

 

I've attached the log, in case it helps.

 

 

log.txt

Link to comment
Share on other sites

wickedlemon

Hi there, can you please attach a log file from a library scan? Thanks.

 

That is it! See my point?

 

2020-03-28 17:46:14.590 Debug TaskManager: Executing Scan media library

Link to comment
Share on other sites

wickedlemon

I started again with fresh Linux and Windows, set up with exactly the same setting on a small test folder.

 

Here's the logs of both.

 

Windows finished in 19s, Linux is still at 86.4%.

windows.txt

linux.txt

Link to comment
Share on other sites

wickedlemon

I would just give it time and allow the scan to finish.

 

Really? There are 10 movies. There are no new entries in the log, so what exactly is being scanned at the moment? 

What am I waiting for? I could manually add 10 movies to a database quicker :)

Link to comment
Share on other sites

Happy2Play

Not really seeing anything in the log, but it has to be something isolated to this specific setup or everyone would be reporting the same thing.

Link to comment
Share on other sites

wickedlemon

Not really seeing anything in the log, but it has to be something isolated to this specific setup or everyone would be reporting the same thing.

 

I think it's specific to ARM SBCs. Had the same issue on a Pi which was set up completely differently to the Odroid. My problem is that, even with debug logging, Emby either isn't telling me what's going on. There are no log errors or slow log entries. Debug logging should be showing everything surely?

 

Just installed Plex on the Odroid and that was FAST scanning my media, although the server doesn't fit my needs. Emby is still sitting at 86.4%.

Link to comment
Share on other sites

wickedlemon

So sometime over night, the library got its images.

 

I've had a quick scan through the logs for file paths and it seems the only scanning activity I can see was between 7 and 8 this morning - so about 13 hours later?. I've added all the logs for this period in case you can work out what's going on.

embyserver.txt

embyserver-63721036801.txt

embyserver-63721028734.txt

embyserver-63721030501.txt

embyserver-63721031470.txt

Link to comment
Share on other sites

  • Solution
Malmgren

How is your movie library mounted? I had this exact problem (on my rock64, ie arm sbc) when my library was nfs mounted. Changed to cifs instead and problem was solved. There are dozens of threads about this problem, seems nobody knows exactly what is the problem.

  • Like 1
Link to comment
Share on other sites

wickedlemon

How is your movie library mounted? I had this exact problem (on my rock64, ie arm sbc) when my library was nfs mounted. Changed to cifs instead and problem was solved. There are dozens of threads about this problem, seems nobody knows exactly what is the problem.

 

Wow. Changed to smb and the scan was a lot quicker. Thanks.

Link to comment
Share on other sites

Malmgren

Wow. Changed to smb and the scan was a lot quicker. Thanks.

Nice! This should be put in a FAQ somewhere. It's really beyond my understanding why it would matter how the movie share is mounted but obviously it does.

Link to comment
Share on other sites

Malmgren

How exactly did you do this?

I had the movie share shared from a nas as both cifs and nfs so for me it was basically an umount, changed a few characters in /etc/fstab and then mounted again...

Link to comment
Share on other sites

wickedlemon

I had the movie share shared from a nas as both cifs and nfs so for me it was basically an umount, changed a few characters in /etc/fstab and then mounted again...

 

I did the same. Using the path substitutions I'm still able to use the NFS paths from the client so it doesn't make any difference other than the library scan.

Link to comment
Share on other sites

  • 3 months later...
roshanconnor

Oh man

I am having the exact same issue

I mounted my gdrive via rclone and used emby to scan

It took 4 hours until now and is stuck at 86.4 with same issues as yours..really dont know what to do

I use plex too and it completed the scan in like few minutes

@MalmgrenHow exactly can i use your solution to work here

Thanks

Edited by roshanconnor
Link to comment
Share on other sites

Malmgren
1 hour ago, roshanconnor said:

How exactly can i use your solution to work here

No idea really. Obviously Emby has a bug somewhere giving problems when scanning libraries that's mounted in specific ways (for example nfs). Until someone solves the bug I guess the only solution is to mount in other ways (for example cifs). In your case it sounds like you have to find some other way of reaching your movies.

Link to comment
Share on other sites

roshanconnor

Update:

So my library scan finished around 1 hour back

So it took around 22 hours apparently for 15TB of stuff (maybe 45k number of files)

18 hours ago, Malmgren said:

No idea really. Obviously Emby has a bug somewhere giving problems when scanning libraries that's mounted in specific ways (for example nfs). Until someone solves the bug I guess the only solution is to mount in other ways (for example cifs). In your case it sounds like you have to find some other way of reaching your movies.

Thank you

Link to comment
Share on other sites

Malmgren
20 hours ago, Luke said:

The problem unfortunately is in the .net core runtime.

Oh... Has it been reported upstreams? Is this Microsoft libraries we are talking about?

2 hours ago, roshanconnor said:

So it took around 22 hours apparently for 15TB of stuff (maybe 45k number of files)

That was fast! I waited for three weeks before I gave up and I only have around 2TB of content 😝

  • Haha 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...