Jump to content

A folder will not be scanned


Mentalblaze

Recommended Posts

Mentalblaze

I use Emby on OpenMediaVault and I have four locations for tv-shows. All seems to work except the share on OMV itself.

I get multiple errors of this kind:

2015-12-22 14:47:59.0782 Error - FileSystem: Error determining LastAccessTimeUtc for /ior/Media/TVserier1/Fastlane/Fastlane - s01e05 - Ryde or Die.avi
	*** Error Report ***
	Version: 3.0.5781.4
	Command line: /opt/emby/MediaBrowser.Server.Mono.exe -programdata /media/a6eceb29-64d8-48b4-8703-1f79c9c59f08/emby -restartpath /usr/sbin/emby.sh
	Operating system: Unix 3.2.0.4
	Processor count: 2
	64-Bit OS: True
	64-Bit Process: True
	Program data path: /media/a6eceb29-64d8-48b4-8703-1f79c9c59f08/emby
	Mono: 4.2.1 (Stable 4.2.1.102/6dd2d0d Thu Nov 12 09:52:44 UTC 2015)
	Application Path: /opt/emby/MediaBrowser.Server.Mono.exe
	Not a valid Win32 FileTime.
	Parameter name: fileTime
	System.ArgumentOutOfRangeException
	  at System.DateTime.FromFileTimeUtc (Int64 fileTime) <0x7fcbfab5db10 + 0x0009a> in <filename unknown>:0 
	  at System.DateTime.FromFileTime (Int64 fileTime) <0x7fcbfab5dad0 + 0x0001b> in <filename unknown>:0 
	  at System.IO.FileSystemInfo.get_LastWriteTime () <0x7fcbfad5ac20 + 0x00026> in <filename unknown>:0 
	  at System.IO.FileSystemInfo.get_LastWriteTimeUtc () <0x7fcbfad5ad10 + 0x00027> in <filename unknown>:0 
	  at (wrapper remoting-invoke-with-check) System.IO.FileSystemInfo:get_LastWriteTimeUtc ()
	  at CommonIO.ManagedFileSystem.GetLastWriteTimeUtc (System.IO.FileSystemInfo info) <0x41518910 + 0x0003e> in <filename unknown>:0 

But there are other shows that won't show up at all. Not in the log nor in the Library.

Link to comment
Share on other sites

Mentalblaze

First I found a workaround, I added the folder in a new library, selecting category as "unset". That way averything is shown without then need for scanning.

But I also removed and readded the folder in the original library as well and now, a couple of days later, the shows have shown up.

Link to comment
Share on other sites

Well done. If changing to unset fixed it then it likely means there are some unsupported naming conventions being used.

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...