Jump to content

"no compatible streams" error on 1 of 3 (LAN'd) media drives


metropical
 Share

Go to solution Solved by metropical,

Recommended Posts

further issue.  Emby server runs on a MacMini Intel 2018 i7/64G running Big Sur.

The media is stored on a LAN'd MacPro3,1 running Mavericks.  The LAN is wired.

The MP has 4 internal drives.

Boot SSD, which has no media.

The 3 others do.

1 drive has no issues playing via Emby (4.6.4).

The other 2 won't play anything, suddenly.  "no compatible streams."  Neither from the TCL/Roku TV or on the desktop (macMini) server app.

All was well the other night.

I restarted the MP and Emby server.  No change.

The files will play fine without Emby, using VLC, both directly on the MP and via the LAN thru the MacMini.

Log attached.

embyserver-63772182009.txt

Link to comment
Share on other sites

Emby (4.6.4) server runs on a MacMini Intel 2018 i7/64G running Big Sur.

The media is stored on a LAN'd MacPro3,1 running Mavericks.  The LAN is wired.

The MP has 4 internal drives.

Boot SSD, which has no media.

The 3 others do.

2 drives have no issues playing via Emby.

The other 1 won't play anything.  "no compatible streams."  Neither from the TCL/Roku TV or on the desktop (macMini) server app.

All was well the other night.

I restarted the MP and Emby server.  No change.

The files will play fine without Emby, using VLC, both directly on the MP and via the LAN thru the MacMini.

Logs attached.

ffmpeg-directstream-322e081d-cd3c-43ba-b1a0-4e41db92665b_1.txt embyserver-63772269517.txt embyserver.txt

Link to comment
Share on other sites

Hi, notice this in the ffmpeg log:

23:27:23.002 /Volumes/Bugs/• more TV/Family Guy/S19/Family Guy S19E01.mkv: No such file or directory
23:27:23.002 
Link to comment
Share on other sites

Your storage is either offline or emby server may be unable to reach it due to permissions. If you can resolve this then you'll likely be good to go.

Link to comment
Share on other sites

  • Solution

the issue seems to have come up when I changed the server from a 2013 MBA running HS to a 2018 Intel Mini running BS and the Emby server app update to 4.6.4.

The drive extension name was wrong and hidden until I did some further looking.  The permissions were fine but the path, because of the extension, was wrong.

I ended up renaming the drive and then renaming it back.  As well as renaming the TV and Movie folders.

Probably did not need to do the later, but since I was there.


I restarted the Mini and Emby as well, after.  All seems good now.

Thanks for the leads, Luke.

 

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
 Share

×
×
  • Create New...