Jump to content

Unable to install 4.6.7 to DSM 7.0


stuartgib

Recommended Posts

1ch_h4lt

@cayars 

I not that sure any more if I uninstalled before upgrading to DSM7.

I have no third party packages installed (anymore, except of docker images) running on my Synology

For me, most of my clients a capable of doing the transcoding by them self. It is just a wish to merge functionality to get rid or at least to shut down my big servers. 

No, I am not able to access the BIOS setup of my Synology

@Luke

I tried to install emby-server-synology7_4.7.5.0_x86_64.spk 

Didn't work as you can see within the screenshot. Something like "Wrong File Format. Please contact the developer of this package"

image.thumb.png.a49e1b24477a14f3364e72630c175ee2.png

Edited by 1ch_h4lt
Link to comment
Share on other sites

I'm wondering if you hit some kind of snag as I have (about 6 times). I've not figured it out yet but something happens in DSM 7 due to a conflict (I think) of some kind that won't allow any version of Emby after 4.6.7 to run or sometime not allow it to install.

The only way I can then get it to install is doing a NAS reset which reinstalls DSM (doesn't touch your data). What's strange is that I can create a Synology DSM Virtual Machine and it installs and runs there. That pretty much says it's configuration issue of some kind.

I've had this happen using completely stock config with no NVMe, with NVMes, with stock memory and with additional memory so it would seem to not be related to that. I've been trying to reproduce it keeping track of exactly what's been installed. My Synology isn't a production machine per say in my environment so it ends up being more of a test setup and gets lots of things installed and removed to try and match customer setups when something is acting strange.

Yesterday I reset mine back to defaults using out of the box setup and then grabbed a backup of the NAS (skipping Volumes) to get the core setup. I've got plenty of space on one of my ZFS clusters so my intention is to backup with Emby 4.6.7 then install a couple programs I would normally have installed, followed by an Emby upgrade. If it' works I restore the backup that has 4.6.7 Emby version then re-install the same programs again and back that up which becomes the base version. Might take a while but with a systematic approach that I'm trying now, hopefully will figure out what the issue is or at least find in my case the software or change that seems to be the trigger.

Previously, I've been through all the logs on the machine probably 10 different ways previously which hasn't helped. It's quite puzzling actually which is annoying as I usually can figure out the source of an issue like this pretty quickly but no dice. :(  Not being able to use standard Linux tools doesn't help otherwise I'd attach a debugger during install or startup to trap where the issue is but not an option.

This could be a one-off issue caused by some 3rd party software that is unique to my machine but as soon as I get to the point I've got a base that works then a change or install that breaks things will know where to focus investigation.

One thing I've notice is that /dev/md0 seems to want to fill up faster on DSM 7 then it did on DSM 6 which is the boot/system volume. If it filles up typically you can't login, and of course nothing can be written to logs as the system is full so I'm keeping an eye on that. I've noticed /dev/md0 filling up during an install then dropping after the install. So it's possible it fills to the point of failing but then recovers so looking at it after the fact looks normal.  I'm keeping an eye on that and similar things.

Link to comment
Share on other sites

stuartgib

 

On 7/1/2022 at 5:58 AM, Luke said:

Can you please try installing 4.7.5 from our website and let us know if that helps? Thanks.

Still "Invaid file format. Please contact the package developer." with 4.7.5 on my 414j.

Link to comment
Share on other sites

  • 3 months later...
stuartgib

Still "Invalid file format. Please contact the package developer" with the NAS now running DSM 7.0.1-42218 Update 5.

I suspect the only resolution to this would be a factory reset of the NAS, but that doesn't seem worth the risk as this is now just a media storage device and something else is the server.

  • Thanks 1
Link to comment
Share on other sites

  • 1 year later...
olli4711

Hi all, has there ever been a resolution to this?
Just updated DSM 6.x to 7 following the instructions at 

 

Uninstalled Emby (which was pretty fast) updated to 7.0x and got "Invalid file format. Please contact package developer." when trying to manually install Emby.
Package Center Version gives the same error.
Updated to DSM 7.1 but still cant get Emby to install. Any hints?

Link to comment
Share on other sites

On 12/23/2023 at 4:50 PM, olli4711 said:

Hi all, has there ever been a resolution to this?
Just updated DSM 6.x to 7 following the instructions at 

 

Uninstalled Emby (which was pretty fast) updated to 7.0x and got "Invalid file format. Please contact package developer." when trying to manually install Emby.
Package Center Version gives the same error.
Updated to DSM 7.1 but still cant get Emby to install. Any hints?

Hi, what is the exact error that you get with DSM 7.1? Are you updating to DSM 7.2?

Link to comment
Share on other sites

olli4711

Hi, here are some more details.
On DSM 6 I have updated to emby-server-synology_4.7.14.0_x86_64.spk and verified Emby is working. Then I unistalled Emby.
I updated DSM 6 to 7.0 and tried to intsall emby-server-synology7_4.7.14.0_x86_64.spk via manually installation and package center installation.
Both methods give the error "Invalid file format. Please contact the package developer."

Install via shell gives this error: sudo synopkg install ./emby-server-synology7_4.7.14.0_x86_64.spk
{"error":{"code":0},"results":[{"action":"install","beta":false,"betaIncoming":false,"error":{"code":313,"description":"failed to revise file attributes"},"installReboot":false,"installing":true,"language":"enu","last_stage":"prepare_install","package":"EmbyServer","packageName":"Emby Server","spk":"./emby-server-synology7_4.7.14.0_x86_64.spk","stage":"install_failed","success":false,"username":"","version":"4.7.14.0-704071400"}],"success":false}

Same error on DSM 7.1.1.
My Rackstation is not compatible with 7.2 so I cant update.

As a workaround I have now latest Emby running in Docker, but would like to get it running again directly on Synology.

Edited by olli4711
Link to comment
Share on other sites

olli4711
16 hours ago, Luke said:

Are you able to install from Synology package center rather than the manual download?

Sadly no, gives the exact same error than the manual one: "Invalid file format. Please contact the package developer."

Link to comment
Share on other sites

3 hours ago, olli4711 said:

Sadly no, gives the exact same error than the manual one: "Invalid file format. Please contact the package developer."

I don't suppose you're willing to reformat and reinstall DSM?

Link to comment
Share on other sites

olli4711
16 hours ago, Luke said:

I don't suppose you're willing to reformat and reinstall DSM?

I have read about that resolution but this would mean too much hassle for me. I would stay with the docker solution then.
Just thought there would have been a solution to this error as the last post in this threat thread was over a year old.

  • Thanks 1
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
×
×
  • Create New...