Emby won't start after upgrade

Hello, I noticed that is new Emby-server upgrade so I start dietpi-software reinstall 41 and after reboot Emby don’t work.

root@DietPi:/home/dietpi# dietpi-services status
[ SUB1 ] DietPi-Services > status 
[  OK  ] DietPi-Services | avahi-daemon		active (running) since Thu 2020-12-17 17:00:37 CET; 1h 37min ago
[  OK  ] DietPi-Services | proftpd		active (running) since Thu 2020-12-17 17:00:37 CET; 1h 37min ago
[  OK  ] DietPi-Services | nfs-kernel-server	active (exited) since Thu 2020-12-17 17:00:39 CET; 1h 37min ago
[  OK  ] DietPi-Services | redis-server		active (running) since Thu 2020-12-17 17:00:39 CET; 1h 37min ago
[  OK  ] DietPi-Services | mariadb		active (running) since Thu 2020-12-17 17:00:41 CET; 1h 37min ago
[  OK  ] DietPi-Services | php7.3-fpm		active (running) since Thu 2020-12-17 17:00:42 CET; 1h 37min ago
[  OK  ] DietPi-Services | lighttpd		active (running) since Thu 2020-12-17 17:00:42 CET; 1h 37min ago
[FAILED] DietPi-Services | ● emby-server.service - Emby Server is a personal media server with apps on just about every device.
   Loaded: loaded (/usr/lib/systemd/system/emby-server.service; disabled; vendor preset: enabled)
   Active: failed (Result: signal) since Thu 2020-12-17 17:00:43 CET; 1h 37min ago
  Process: 821 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=SEGV)
 Main PID: 821 (code=killed, signal=SEGV)

Dec 17 17:00:42 DietPi systemd[1]: Started Emby Server is a personal media server with apps on just about every device..
Dec 17 17:00:43 DietPi systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Dec 17 17:00:43 DietPi systemd[1]: emby-server.service: Failed with result 'signal'.
[  OK  ] DietPi-Services | medusa		active (running) since Thu 2020-12-17 17:00:43 CET; 1h 37min ago
[  OK  ] DietPi-Services | jackett		active (running) since Thu 2020-12-17 17:00:43 CET; 1h 37min ago
[  OK  ] DietPi-Services | noip2		active (running) since Thu 2020-12-17 17:00:43 CET; 1h 37min ago
[  OK  ] DietPi-Services | cron			active (running) since Thu 2020-12-17 17:00:43 CET; 1h 37min ago
[  OK  ] DietPi-Services | ssh			active (running) since Thu 2020-12-17 17:00:37 CET; 1h 37min ago
[  OK  ] DietPi-Services | fail2ban		active (running) since Thu 2020-12-17 17:00:13 CET; 1h 38min ago
[  OK  ] DietPi-Services | dietpi-ramlog	active (exited) since Thu 2020-12-17 17:00:12 CET; 1h 38min ago
[  OK  ] DietPi-Services | dietpi-preboot	active (exited) since Thu 2020-12-17 17:00:13 CET; 1h 38min ago
[  OK  ] DietPi-Services | dietpi-boot		active (exited) since Thu 2020-12-17 17:00:37 CET; 1h 37min ago
[  OK  ] DietPi-Services | dietpi-postboot	active (exited) since Thu 2020-12-17 17:00:37 CET; 1h 37min ago
[ INFO ] DietPi-Services | dietpi-wifi-monitor	inactive (dead)
root@DietPi:/home/dietpi#

Anyone have that problem or it’s only mine because I move Emby installation from old sd-card to new one (copy /opt/emby-server and /var/lib/emby folders) and that may be reason. Before upgrade I reinstall Emby two times but nothing happen.
Regards,
Przemek

you can have a look to the journalctl

journalctl -u emby-server.service

Hi, there’s nothing more:

-- Logs begin at Thu 2019-02-14 11:11:58 CET, end at Fri 2020-12-18 07:10:54 CET. --
Dec 17 20:03:43 DietPi systemd[1]: Started Emby Server is a personal media server with apps on just about every device..
Dec 17 20:03:43 DietPi systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Dec 17 20:03:43 DietPi systemd[1]: emby-server.service: Failed with result 'signal'.
Dec 17 20:35:13 DietPi systemd[1]: Started Emby Server is a personal media server with apps on just about every device..
Dec 17 20:35:13 DietPi systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Dec 17 20:35:13 DietPi systemd[1]: emby-server.service: Failed with result 'signal'.
Dec 17 23:21:48 DietPi systemd[1]: Started Emby Server is a personal media server with apps on just about every device..
Dec 17 23:21:48 DietPi systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Dec 17 23:21:48 DietPi systemd[1]: emby-server.service: Failed with result 'signal'.

Regards,
Przemek

ok this don’t give us anything. Can you try to start emby manual

sudo -u emby /opt/emby-server/bin/emby-server

Hi Joulinar I try that it says: Segmentatin fault.
I open thread on Emby forum: https://emby.media/community/index.php?/topic/93121-emby-server-dont-start-after-upgrade/, maybe they will now something.

Regards.

probably your emby executable did not fit to the architecture of your board.

I burn 32 bit image for my Rpi4. I t works OK before, they change something in Emby?

on my test system (RPi3B+ 32bit) emby is working fine. Probably something went wrong as you moved installation manually from one SD card to another.

I will try to install fresh and move only /var/lib/emby. If that doesn’t help I will install fresh at all.
Thanks for help.
Regards,
Przemek

OK, it works now. I uninstall Emby, remove /opt/emby-server, then copy backup of old /var/lib/emby to /var/lib/ but without 3 folders: .cache, .dotnet and /cache.
Thanks for help.
Regards,
​​​​​​​Przemek