crfiala 0 Posted March 15, 2021 Posted March 15, 2021 See Attached. I have adjusted all user accounts to have full access to all drives available. I just recently updated my Windows 10 PC which is running the server and Emby is up to date as well. After the updates, I get frequent "Playback Error - No compatible streams are currently available. Please try again later or contact your system administrator for details." I'm curious to see if this is an FFMPEG issue exclusively. ffmpeg-directstream-48896d85-c4ef-4ff0-8626-77026bb5bd17_1 (1).txt
Abobader 3464 Posted March 15, 2021 Posted March 15, 2021 Hello crfiala, ** This is an auto reply ** Please wait for someone from staff support or our members to reply to you. It's recommended to provide more info, as it explain in this thread: Thank you. Emby Team
Happy2Play 9780 Posted March 15, 2021 Posted March 15, 2021 (edited) Can you post a server log, but there would appear to be a issue with file permissions though. @crfiala Edited March 15, 2021 by Happy2Play
crfiala 0 Posted March 15, 2021 Author Posted March 15, 2021 embyserver log attached. Thanks @Happy2Playembyserver.txt
Happy2Play 9780 Posted March 15, 2021 Posted March 15, 2021 What is your E drive? As everything on it is not available/not ready. System.IO.IOException: System.IO.IOException: The device is not ready. : 'E:\Videos\Movies' 2021-03-15 16:58:18.569 Error App: Error in GetFilteredFileSystemEntries isPhysicalRoot: False IsVf: False *** Error Report *** Version: 4.5.4.0 Command line: C:\Users\Athena\AppData\Roaming\Emby-Server\system\EmbyServer.dll Operating system: Microsoft Windows 10.0.19041 Framework: .NET Core 3.1.9 OS/Process: x64/x64 Runtime: C:/Users/Athena/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll Processor count: 4 Data path: C:\Users\Athena\AppData\Roaming\Emby-Server\programdata Application path: C:\Users\Athena\AppData\Roaming\Emby-Server\system System.IO.IOException: System.IO.IOException: The device is not ready. : 'E:\Videos\Movies' at System.IO.Enumeration.FileSystemEnumerator`1.CreateDirectoryHandle(String path, Boolean ignoreNotFound) at System.IO.Enumeration.FileSystemEnumerator`1.Init() at System.IO.Enumeration.FileSystemEnumerator`1..ctor(String directory, Boolean isNormalized, EnumerationOptions options) at System.IO.Enumeration.FileSystemEnumerable`1..ctor(String directory, FindTransform transform, EnumerationOptions options, Boolean isNormalized) at System.IO.Enumeration.FileSystemEnumerableFactory.FileSystemInfos(String directory, String expression, EnumerationOptions options, Boolean isNormalized) at System.IO.DirectoryInfo.InternalEnumerateInfos(String path, String searchPattern, SearchTarget searchTarget, EnumerationOptions options) at System.IO.DirectoryInfo.EnumerateFileSystemInfos(String searchPattern, SearchOption searchOption) at Emby.Server.Implementations.IO.ManagedFileSystem.GetFileSystemEntries(String path, Boolean recursive) at MediaBrowser.Controller.Providers.DirectoryService.GetFileSystemEntries(String path) at MediaBrowser.Controller.IO.FileData.GetFilteredFileSystemEntries(IDirectoryService directoryService, String path, IFileSystem fileSystem, IServerApplicationHost appHost, ILogger logger, ItemResolveArgs args, Int32 flattenFolderDepth, Boolean resolveShortcuts) at Emby.Server.Implementations.Library.LibraryManager.ResolvePath(FileSystemMetadata fileInfo, IDirectoryService directoryService, IItemResolver[] resolvers, Folder parent, LibraryOptions libraryOptions) Source: System.IO.FileSystem TargetSite: IntPtr CreateDirectoryHandle(System.String, Boolean)
crfiala 0 Posted March 15, 2021 Author Posted March 15, 2021 @Happy2PlayIt is a virtual drive you can mount ".iso" files to. I'll go ahead and delete that drive if it's causing an issue.
crfiala 0 Posted March 15, 2021 Author Posted March 15, 2021 WOW! How did I not realize this at the beginning. The Drive letters have be reassigned... Apparently that can happen with a Windows Update? I assume fixing the paths will resolve this issue. Thanks @Happy2Play
Happy2Play 9780 Posted March 15, 2021 Posted March 15, 2021 2 minutes ago, crfiala said: WOW! How did I not realize this at the beginning. The Drive letters have be reassigned... Apparently that can happen with a Windows Update? I assume fixing the paths will resolve this issue. Thanks @Happy2Play Yes that can be problematic as everything is imported via a specific path.
rbjtech 5284 Posted March 16, 2021 Posted March 16, 2021 My advice is to always use UNC shares, even for local content. That way, you can add/remove drives all day and the UNC share stays the same. ie share d:\mymovies as \\myserver\mymovies If d: changes to e: etc - it won't make any difference as emby is mapped to \\myserver\mymovies still.
ebr 16184 Posted March 16, 2021 Posted March 16, 2021 18 minutes ago, rbjtech said: My advice is to always use UNC shares, even for local content. That way, you can add/remove drives all day and the UNC share stays the same. ie share d:\mymovies as \\myserver\mymovies If d: changes to e: etc - it won't make any difference as emby is mapped to \\myserver\mymovies still. That can potentially be a performance bottleneck - but may or may not amount to anything. My suggestion is drive pooling software so you never have to worry about physical disc configuration in apps again.
Guest Posted March 16, 2021 Posted March 16, 2021 The drive letter changing in a Virtual Software is odd, as though the configuration was changed.. And that would actually not be possible to mount a DVD or data disc in that manner. If the image was present over a network.. data stream bottleneck would occur compared to normal access from a native drive... I would suggest assigning the proper number of virtual drives with the appropriate letter to make sure it doesn't change. Plugging and unplugging devices to your system depending on what you have hooked up will alter the letter assigned by the system if not implicitly assigned.. Like mounting a share as a Network drive or having VirtualDrive mount a certain number of drives with letters assigned to each one. Usually a tray icon or service will maintain this on boot, and his leaves the remaining to be assigned by the system.
rbjtech 5284 Posted March 16, 2021 Posted March 16, 2021 7 minutes ago, ebr said: That can potentially be a performance bottleneck - but may or may not amount to anything. My suggestion is drive pooling software so you never have to worry about physical disc configuration in apps again. From my experience - I've never had an issue using UNC - had lots of issues using pooling software ...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now