Main images corrupted

[PVTD 37]

Hy!

 

I had to rebuild my hard drives due to upgrading to 8tb raid 5 drives.

 

As I copied everything and reasigned to folder paths, I encountered something weird.

 

First I thought it was a permission problem, errors spit our in logs about permission, so I decided to run emby as a service with admin rights.

 

The drives are located on a second server at home and should work as everyhting has access to them.

 

 

I thought maybe to remove EVERY .jpg from the movie folders, I dont mind having my server find everything again between about 10k movies and series.

 

Is this a good idea? Or is there a better way to deal with this sort of problem? (the image below is just an example, about 30% acts this way, and identifying them again with replacing images does not fix it)

 

PS: Newly added items don't seem to have this problem... I had the disk run chkdsk and ran also defrags on them frequently.

 

Logs; https://www.dropbox.com/s/g8638x0us0b7ocq/server-63616665600.txt?dl=0

 

Thanks for your time to help me out

 

BTW im at Semi-noob level...

[Happy2Play 9783]

Permissions issue looks like your W:\ drive.

Access to the path is denied.

Edited December 7, 2016 by Happy2Play

[PVTD 37]

 

Permissions issue looks like your W:\ drive.

Access to the path is denied.

Awkward... Its the same drive on the remote server... Just different pointed folders to the Emby server with same permissions...

 

 

Confirmed that permissions are all the same, and the error should also point to X: as it has the same problem in images...

Edited December 7, 2016 by PVTD

[Happy2Play 9783]

How did you set your library paths up? 

[PVTD 37]

Hmm, seems like Emby did not run as a service?

 

Because Emby started automatically, the service did not start I think. Now I killed the emby icon in task bar and manually started the Service, maybe that fixes it up?!

 

To answer your question

[PVTD 37]

First thing I notice when scanning after reboot... This is access denied?

2016-12-07 16:00:19.1519 Error LibraryMonitor: Error watching path: Y:\
	*** Error Report ***
	Version: 3.0.8500.0
	Command line: C:\Users\Admin\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe -service
	Operating system: Microsoft Windows NT 6.2.9200.0
	Processor count: 16
	64-Bit OS: True
	64-Bit Process: True
	Program data path: C:\Users\Admin\AppData\Roaming\Emby-Server
	Application Path: C:\Users\Admin\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	The directory name Y:\ is invalid.
	System.ArgumentException
	   at System.IO.FileSystemWatcher..ctor(String path, String filter)
	   at MediaBrowser.Server.Implementations.IO.LibraryMonitor.<>c__DisplayClass37_0.<StartWatchingPath>b__0()
	
2016-12-07 16:00:19.1519 Error LibraryMonitor: Error watching path: W:\
	*** Error Report ***
	Version: 3.0.8500.0
	Command line: C:\Users\Admin\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe -service
	Operating system: Microsoft Windows NT 6.2.9200.0
	Processor count: 16
	64-Bit OS: True
	64-Bit Process: True
	Program data path: C:\Users\Admin\AppData\Roaming\Emby-Server
	Application Path: C:\Users\Admin\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	The directory name W:\ is invalid.
	System.ArgumentException
	   at System.IO.FileSystemWatcher..ctor(String path, String filter)
	   at MediaBrowser.Server.Implementations.IO.LibraryMonitor.<>c__DisplayClass37_0.<StartWatchingPath>b__0()
	
2016-12-07 16:00:19.1519 Error LibraryMonitor: Error watching path: V:\
	*** Error Report ***
	Version: 3.0.8500.0
	Command line: C:\Users\Admin\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe -service
	Operating system: Microsoft Windows NT 6.2.9200.0
	Processor count: 16
	64-Bit OS: True
	64-Bit Process: True
	Program data path: C:\Users\Admin\AppData\Roaming\Emby-Server
	Application Path: C:\Users\Admin\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	The directory name V:\ is invalid.
	System.ArgumentException
	   at System.IO.FileSystemWatcher..ctor(String path, String filter)
	   at MediaBrowser.Server.Implementations.IO.LibraryMonitor.<>c__DisplayClass37_0.<StartWatchingPath>b__0()
	
2016-12-07 16:00:19.1519 Error LibraryMonitor: Error watching path: X:\
	*** Error Report ***
	Version: 3.0.8500.0
	Command line: C:\Users\Admin\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe -service
	Operating system: Microsoft Windows NT 6.2.9200.0
	Processor count: 16
	64-Bit OS: True
	64-Bit Process: True
	Program data path: C:\Users\Admin\AppData\Roaming\Emby-Server
	Application Path: C:\Users\Admin\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	The directory name X:\ is invalid.
	System.ArgumentException
	   at System.IO.FileSystemWatcher..ctor(String path, String filter)
	   at MediaBrowser.Server.Implementations.IO.LibraryMonitor.<>c__DisplayClass37_0.<StartWatchingPath>b__0()

[Happy2Play 9783]

Since those are all remote shares I would use network path not mapped local shares.

[PVTD 37]

Since those are all remote shares I would use network path not mapped local shares.

I will take your advice, and already changed the folder to \\server\drive\folder.

 

Will get back to you in a day or so when it finishes

To bad emby cannot work faster with 2x 2.8Ghz Octa core CPU's and 128Gb ram haha it only uses 5% at most (not in rendering ofc)

[Luke 42083]

Let us know how you get on. Thanks.

[dcook 299]

You should not use mapped network drives, use the UNC path instead, its more reliable and faster.

 

 

 

Hmm, seems like Emby did not run as a service?

 

Because Emby started automatically, the service did not start I think. Now I killed the emby icon in task bar and manually started the Service, maybe that fixes it up?!

 

To answer your question

[Luke 42083]

Yup, great advice.

[PVTD 37]

You should not use mapped network drives, use the UNC path instead, its more reliable and faster.

I did what you asked, and it kind of fixed half of everything.

Some items got fixed, some are not.

 

I copied 1 error string while it was looking for subtitles:

12/9/2016		SubtitleDownloadFailure	Info	Subtitles failed to download for The Duel	Provider: Open Subtitles	Access to the path '\\Astrid\y\MOVIES\The Duel (2016)\The.Duel.2016.1080p.BluRay.x264-[YTS.AG].eng.srt' is denied. System.UnauthorizedAccessException at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean useAsync) at CommonIO.ManagedFileSystem.GetFileStream(String path, FileMode mode, FileAccess access, FileShare share, Boolean isAsync) at MediaBrowser.Providers.Subtitles.SubtitleManager.d__15.MoveNext()

I have no idea how to open up even more permissions O.o

I'm afraid I will just open up my entire library to the outside world without any security haha.

 

Sorry to be such a burdon

 

PV

[Luke 42083]

You need to ensure emby server has write access to your media folders if you want it to be able to save subtitles.

[PVTD 37]

As an update:

 

Somehow the RAID5 drives got corrupt... I lost a good 60% of all the video's, SRT and Artwork of a 22Tb RAID5 drive (sadpanda)

 

So this is what caused most of the problems I have had in the past few days.

I am still troubleshooting what caused this to happen (I ran a windows defrag not long before I found out) chkdsk did not report anything abnormally eighter and the raid says my drives are healthy and S.M.A.R.T reports that my drives are fitter then fit with only about 400h of uptime on each of them.

Windows Server 2012 R2 is kind of not 100% from the shelves, but its the same that I used over the past few years without any trouble.

 

Emby is thus NOT the culprit of my trouble and I am sorry to have bothered you with this.

 

Now my plans are to change my system into one big server.

Hardware RAID5 (maybe 10...). I think I should make a video of the build to promote emby a bit

[Luke 42083]

Ah, thanks for the update and good luck !