Emby Server Crashing - I/O device error

[BrettJ 0]

Hi Guys,

 

Firstly I wanted to say up until recently I have had fantastic experience with Emby I think its a great product. This is why I really want to get it working again. Basically Emby server keeps crashing (disappearing from system tray) and dropping off network. I have tried re-install, then a full clean re-install with no luck. Then I enabled debug logs. The latest log is huge at over 4mb.

 

Here is the first error in the log:

 

*** Error Report ***

Version: 3.1.184.0

Command line: C:\Users\brett\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe

Operating system: Microsoft Windows NT 6.2.9200.0

Processor count: 24

64-Bit OS: True

64-Bit Process: True

Program data path: C:\Users\brett\AppData\Roaming\Emby-Server

Application Path: C:\Users\brett\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe

The request could not be performed because of an I/O device error.

 

System.IO.IOException

  at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

  at System.IO.FileStream.ReadCore(Byte[] buffer, Int32 offset, Int32 count)

  at System.IO.FileStream.Read(Byte[] array, Int32 offset, Int32 count)

  at System.IO.StreamReader.ReadBuffer(Char[] userBuffer, Int32 userOffset, Int32 desiredChars, Boolean& readToUserBuffer)

  at System.IO.StreamReader.Read(Char[] buffer, Int32 index, Int32 count)

  at System.Xml.XmlTextReaderImpl.ReadData()

  at System.Xml.XmlTextReaderImpl.FinishInitTextReader()

  at System.Xml.XmlReaderSettings.CreateReader(TextReader input, String baseUriString, XmlParserContext inputContext)

  at MediaBrowser.XbmcMetadata.Savers.BaseNfoSaver.AddCustomTags(String path, List`1 xmlTagsUsed, XmlWriter writer, ILogger logger)

  at MediaBrowser.XbmcMetadata.Savers.BaseNfoSaver.Save(IHasMetadata item, Stream stream, String xmlPath)

  at MediaBrowser.XbmcMetadata.Savers.BaseNfoSaver.Save(IHasMetadata item, CancellationToken cancellationToken)

  at MediaBrowser.Providers.Manager.ProviderManager.<SaveMetadata>d__60.MoveNext()

 

Then there is about 20 lines of image fetching (scraping for TV I think) and that looks ok, then another error:

 

*** Error Report ***

Version: 3.1.184.0

Command line: C:\Users\brett\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe

Operating system: Microsoft Windows NT 6.2.9200.0

Processor count: 24

64-Bit OS: True

64-Bit Process: True

Program data path: C:\Users\brett\AppData\Roaming\Emby-Server

Application Path: C:\Users\brett\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe

The request could not be performed because of an I/O device error.

 

System.IO.IOException

  at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

  at System.IO.FileStream.ReadCore(Byte[] buffer, Int32 offset, Int32 count)

  at System.IO.FileStream.Read(Byte[] array, Int32 offset, Int32 count)

  at System.IO.StreamReader.ReadBuffer()

  at System.IO.StreamReader.ReadToEnd()

  at MediaBrowser.XbmcMetadata.Parsers.BaseNfoParser`1.Fetch(MetadataResult`1 item, String metadataFile, XmlReaderSettings settings, CancellationToken cancellationToken)

  at MediaBrowser.XbmcMetadata.Parsers.BaseNfoParser`1.Fetch(MetadataResult`1 item, String metadataFile, CancellationToken cancellationToken)

  at MediaBrowser.XbmcMetadata.Providers.BaseVideoNfoProvider`1.Fetch(MetadataResult`1 result, String path, CancellationToken cancellationToken)

  at MediaBrowser.XbmcMetadata.Providers.BaseNfoProvider`1.<GetMetadata>d__0.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)

  at MediaBrowser.Providers.Manager.MetadataService`2.<RefreshWithProviders>d__4c.MoveNext()

 

This repeats like this for most of the file then down the last error is:

 

*** Error Report ***

Version: 3.1.184.0

Command line: C:\Users\brett\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe

Operating system: Microsoft Windows NT 6.2.9200.0

Processor count: 24

64-Bit OS: True

64-Bit Process: True

Program data path: C:\Users\brett\AppData\Roaming\Emby-Server

Application Path: C:\Users\brett\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe

One or more errors occurred.

System.AggregateException

  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)

  at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__1d.MoveNext()

InnerException: System.Net.WebException

The remote server returned an error: (404) Not Found.

  at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)

  at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)

 

I can upload the whole log if needed

 

Thanks in advance

 

 

[Luke 42085]

Hi, an I/O device error is exactly that. It's something you're going to have to look into and that probably means starting with hardware diagnostics. There isn't really anything for us to fix here other than potentially handling the situation a little more gracefully.

[BrettJ 0]

Hi, an I/O device error is exactly that. It's something you're going to have to look into and that probably means starting with hardware diagnostics. There isn't really anything for us to fix here other than potentially handling the situation a little more gracefully.

 

Thanks Luke, I was guessing that was the case. But where do I start with that? Is there a way to get more info as to what hardware it could be?

I'm guessing its Hard Drives?

[ebr 16195]

Look at the log and determine what items are being accessed when those errors occur.  Then test the drives where those are.