Server takes 12-24h to detect new media

[Thomas5020 3]

Been having this issue for the past couple of months, server takes up to 24h, sometimes a little more to detect new media. Real time monitoring is enabled, and forcing a library scan doesn't work. 

I've added new media and forced a rescan, then downloaded the log but to my untrained eye I'm not seeing anything off. Running docker container on Unraid 6.11.5

embyserver.txt

[Luke 42078]

Hi there, can you please provide a specific example? Thanks.

[Thomas5020 3]

1 minute ago, Luke said:

Hi there, can you please provide a specific example? Thanks.

Hi, 

 

I've added Harry Hill's TV Burp S6E1 today, forced rescan, currently waiting on that to show up. 

I also added Everybody Love Raymond S1-S9 on Sunday afternoon, and it took until Monday night to show up. 

 

[Luke 42078]

Just now, Thomas5020 said:

Hi, 

 

I've added Harry Hill's TV Burp S6E1 today, forced rescan, currently waiting on that to show up. 

 

 

There's no mention of it in the log file provided. Are you sure it's the right one?

[Thomas5020 3]

10 minutes ago, Luke said:

There's no mention of it in the log file provided. Are you sure it's the right one?

It's the only log file that's been written to recently. I forced a scan again and the same file was written to. Pulled it again and reattached just in case 

embyserver-1.txt

[Thomas5020 3]

Cracked it... 

Problem with the cache pool, reason it's taking so long is Emby is waiting on the fiels to hit the hard disks. 

Adjusted docker config and library settings, resolved. 

[Luke 42078]

Thanks for following up.

[Syztemlord 7]

On 11/07/2023 at 21:23, Thomas5020 said:

Cracked it... 

Problem with the cache pool, reason it's taking so long is Emby is waiting on the fiels to hit the hard disks. 

Adjusted docker config and library settings, resolved. 

I'm getting the same issue, could you just explain in a little more detail what you did in the docker config and library settings?

[Thomas5020 3]

5 minutes ago, Syztemlord said:

I'm getting the same issue, could you just explain in a little more detail what you did in the docker config and library settings?

Basically what I'd done is set the library path to the folder on disk1. This is obviously incorrect as it was only looking at that specific hard drive, so data on the cache pool was ignored until the mover ran at 3am and pushed the data to disk1. Had to change it to look at the array itself. So I had to adjust the docker to be able to access the array, not just disk1, then adjust the library settings in emby to reflect the same. 

I just gave it admin rights and then made the changes, and it worked. 

 

Edited August 28, 2023 by Thomas5020

[Syztemlord 7]

9 minutes ago, Thomas5020 said:

Basically what I'd done is set the library path to the folder on disk1. This is obviously incorrect as it was only looking at that specific hard drive, so data on the cache pool was ignored until the mover ran at 3am and pushed the data to disk1. Had to change it to look at the array itself. So I had to adjust the docker to be able to access the array, not just disk1, then adjust the library settings in emby to reflect the same. 

I just gave it admin rights and then made the changes, and it worked. 

 

Aah, ok.  I don't have anything move over disks on my setup.  I think real time monitoring stopped working a couple of releases ago for me.  By the looks of other threads in the beta section it is fixed but I'm not too keen on going to a beta release incase it breaks something else.

 

Thank you for the reply!