TOS 7 Stable and Latest Emby Issue Upgrading

[Racerprose 29]

It seems to be TerraMaster don't believe this needs to be fixed on their end and instead it is up to Emby devs to fix @Luke

[richt 103]

1 hour ago, svgetm said:

exec $APP_DIR/system/EmbyServer \
  -programdata $APP_DATA_DIR /Volume1/Emby \
  -ffdetect $APP_DIR/bin/ffdetect \
  -ffmpeg $APP_DIR/bin/ffmpeg \
  -ffprobe $APP_DIR/bin/ffprobe \
  -defaultdirectory /mnt/public \
  -updatepackage 'emby_TOS5_APP_{version}_x86_64.tpk'

Version 4.9.5.0.02 from tos store

tos - 7.0.0804

Replacing the line doesn’t fix it for me.

 

In the 2nd line, remove the space between "$APP_DATA_DIR" and "/Volume1/Emby"

The line should look like this

  -programdata $APP_DATA_DIR/Volume1/Emby \

 

[svgetm 0]

19 minutes ago, richt said:

In the 2nd line, remove the space between "$APP_DATA_DIR" and "/Volume1/Emby"

So, I honestly have no idea what TerraMaster changed there, but I installed Emby 4.10.0.23 beta from the Emby website, changed that line (by the way, I left the space there exactly as it was), and all my libraries, users, and settings came back.

Now I’m not even sure what to do next Should I keep experimenting, uninstall the beta and try the version from the TOS Store again? Or maybe install the stable version from the Emby website instead?

Or should I just leave it alone and stay on the beta since everything is working perfectly now and I’m happy with it?

[Luke 42936]

I've passed the info on to our build and packaging developer for review. They have made similar fixes in the past in silent fashion so it wouldn't be the first time.

[svgetm 0]

1 hour ago, svgetm said:

So, I honestly have no idea what TerraMaster changed there, but I installed Emby 4.10.0.23 beta from the Emby website, changed that line (by the way, I left the space there exactly as it was), and all my libraries, users, and settings came back.

Now I’m not even sure what to do next Should I keep experimenting, uninstall the beta and try the version from the TOS Store again? Or maybe install the stable version from the Emby website instead?

Or should I just leave it alone and stay on the beta since everything is working perfectly now and I’m happy with it?

Well, I decided to keep experimenting

I changed the directory back to the default one, removed the permissions from the system emby user, and then uninstalled Emby with the option to remove the configuration as well. The beta version was removed successfully.

Then I installed the 4.9.5.0.02 version from the TOS Store again, immediately stopped the server, changed the directory to the correct one:

-programdata $APP_DATA_DIR/Volume1/Emby \

and started the server again.

And, surprisingly, everything came back — and now everything works! Videos play normally and there are no more streaming errors.

So now the question is: what should I do from here? Who actually needs to fix this — TerraMaster or Emby? And is it correct/safe to leave the programdata path like this permanently?

[Luke 42936]

The 4.10.0.24 beta build has incorporated a permissions change that terramaster sent to us.

[Racerprose 29]

3 hours ago, Luke said:

The 4.10.0.24 beta build has incorporated a permissions change that terramaster sent to us.

Anyone want to test this? I'm not blowing away my config to test lol

[richt 103]

I successfully installed 4.10.0.24 over a modified and working version of 4.9.5.0.02.  So far it seems pretty good. Will give it a day of testing before the victory shout.  

I did take a snapshot of /Volume1/Emby to be sure I could salvage my data and go back to current release if needed. (You cannot go back to stable once you've installed a beta without saving a copy of your libraries.)

 

Still FAILING to use hardware transcoding.  I'll open a separate ticket on that.  If anyone else id having this problem please post as well.

 

Edited August 13 by richt

[Racerprose 29]

13 hours ago, richt said:

I successfully installed 4.10.0.24 over a modified and working version of 4.9.5.0.02.  So far it seems pretty good. Will give it a day of testing before the victory shout.  

I did take a snapshot of /Volume1/Emby to be sure I could salvage my data and go back to current release if needed. (You cannot go back to stable once you've installed a beta without saving a copy of your libraries.)

 

Still FAILING to use hardware transcoding.  I'll open a separate ticket on that.  If anyone else id having this problem please post as well.

 

So that should be fine since you had a working version already. I'm more interested in someone using an unmodified version and seeing if the update breaks the config.

Edited August 14 by Racerprose

[ShoutingMan 101]

Is it safe to upgrade my F4-425 to TOS7? I don't use hardware transcoding. Or should I wait and check back in a couple weeks?

[lunerorbit 0]

I updated to the latest TOS7 and Emby versions and I lost my libraries. Annoying though it is, I decided just to rebuild the libraries. Emby started up fine and I tried to build a movie library. Went to add folder, scrolled to the appropriate hard drive and clicked on it. Nothing happened, it didnt open to reveal the folders. Its just like clicking on a line of text, all it does is highlight the text. Therefore, I cant rebuild the libraries.

All the networked pc's can see the drive and open its contents.

I dont know how to proceed.

[Luke 42936]

Our package on the beta channel has a permissions fix for TOS 7. It will be in the next stable release.

[brucesnelgrove 2]

Hidy Ho Luke,

The last time I upgraded Emby to 4.9.3, I experienced the problem of "no streams available". That problem never got resolved. To this day, I a different tool to playback my audio-because Emby can't.

I upgraded to 4.9.5 - didn't take-you didn't believe me last time. I upgraded to TOS 7. All configs got wiped-including my playlists-again,

Without exception, every Emby/TOS upgrade has been a complete nightmare - and I've been dealing with Emby off and on for 10 years`- never, never has it gone smoothly.

I am totally unqualified to do any kind of line editing, but I'm I'm willing to give it a go.

What editing tools do I need to do this? How much extra is it going to cost me to correct this?

Can you specify the line #s that need editing?

What screen shots would you like? I sent many to you last time and nothing got resolved. To this day, I can't use Emby to playback music, but hey, another audio player works just fine. Just not Emby.

Why is it every Emby/TOS upgrade is a complete nightmare?

I am really looking forward to a solution. My history with Emby has been a history of long painful excercises that involves hours of time, and multiple back and forth interactions, to the point where I give up and start again .

 

[richt 103]

1 hour ago, brucesnelgrove said:

I am totally unqualified to do any kind of line editing, but I'm I'm willing to give it a go.

If you have an aversion to line editing, how are you with manually installing the latest Emby version on your TM NAS?  While jumping to the beta track does have some risks, I've been running it on my F4-423 without any issues, but that does not guarantee your experience will be the same, as it is beta.  Considering all that, this is the easiest route,  You can find the most recent beta here --> https://emby.media/terramaster-server.html  Assuming you have an Intel based TM NAS, download the file linked at 

• 64-bit (TOS 5+)

That said, this previous post gave instructions on how to update the file.  It gives good info but I don't think you'll have the 'nano' command if you haven't installed Modbase1 from the Community App section, so you may want to do that first.  The terminal session can be started by logging into the TOS7 web UI and launching "Terminal".

 

[brucesnelgrove 2]

Thanks for the reply.

Couple of questions. Which folder is the correct folder? Data-or a nested folder within, Metadata - or a nested folder?

Also I noticed a "cd"command - do I have to do that to before doing execution on the next line?

Also, has the Mod1 third party app been updated for TOS 7?

.Net experience, terminal commands, other IT skills should not be required after every Emby/TOS upgrade. Since I've known Emby-years and years.

And to have a Beta as the only "guess" that it will resolve the issues is not fair to customers.( I was a premiere customer until this camel-back-breaking issue turned up.)

FYI - I tried to upgrade to 4.9.5 several times, both through TOS and manually. It was rejected every.single.time.

I decided to try on more time through TOS, and it took. Music is playing through Emby-which it didn't do in 4.9.3-I had to get a separate app .

The Emby TM relationship is a disgrace to their customers. If I could nuke TOS and replace it I would. As for Emby, no difference between Plex and Jellyfin. I have used all three extensively.

I used to repair old carburetor cars in the 70s-80s.Old. Clunky, had to appease car gods to get it running. Emby/TM reminds of that.

 

Sorry for the rant. Pay it forward.

 

 

[richt 103]

1 hour ago, brucesnelgrove said:

Couple of questions. Which folder is the correct folder? Data-or a nested folder within, Metadata - or a nested folder?

Don't understand this question.  Assuming you installed to Volume1, the file to edit is at /Volume1/@apps/emby/emby-server/bin/emby-server as noted in the previous posts
If you have "missing" Emby config folder, that is typically at /Volume1/Emby/ or whatever Volume you installed to. 

1 hour ago, brucesnelgrove said:

Also I noticed a "cd"command - do I have to do that to before doing execution on the next line?

Huh?  Don't see a CD command in any post I've referenced

1 hour ago, brucesnelgrove said:

Also, has the Mod1 third party app been updated for TOS 7?

I believe so, and it seems to work as it is

1 hour ago, brucesnelgrove said:

.Net experience, terminal commands, other IT skills should not be required after every Emby/TOS upgrade. Since I've known Emby-years and years.

As I stated previously, if you install the latest Emby beta version, it works as expected.  Luke has mentioned in other posts that the fix will be applied in future Emby releases.

1 hour ago, brucesnelgrove said:

And to have a Beta as the only "guess" that it will resolve the issues is not fair to customers

It's not a "guess".  It works.

Note: The editing of the file /Volume1/@apps/emby/emby-server/bin/emby-server is NOT required if you install the latest beta

Edited 1 hour ago by richt