Raspberry PI 1 B Model Issues with Media

Troubleshooting
21

Can you verify that the Raspbian Jellyfin repo has been installed as expected: cat /etc/apt/sources.list.d/dietpi-jellyfin.list
This should have been fixed with the first beta already: https://github.com/MichaIng/DietPi/commit/b80185a8a07d4fe5c0f0a0ae3353731204bf8623
If that does not support armv6l, then the repository is worthless as any other architecture can use the Debian Jellyfin repo.

22

MichaIng
I did another test on my RPi1B running DietPi v6.34.3. Jellyfin is failing

root@DietPi1:~# systemctl status jellyfin.service
● jellyfin.service - Jellyfin Media Server
   Loaded: loaded (/lib/systemd/system/jellyfin.service; disabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/jellyfin.service.d
           └─jellyfin.service.conf
   Active: failed (Result: signal) since Mon 2020-12-21 13:17:10 CET; 28min ago
  Process: 397 ExecStart=/usr/bin/jellyfin ${JELLYFIN_WEB_OPT} ${JELLYFIN_RESTART_OPT} ${JELLYFIN_FFMPEG_OPT} ${JELLYFIN_SERVICE_OPT} ${JELLYFIN_NOWEBAPP_OPT} (code=killed, signal=SEGV)
 Main PID: 397 (code=killed, signal=SEGV)

Dec 21 13:17:10 DietPi1 systemd[1]: jellyfin.service: Service RestartSec=100ms expired, scheduling restart.
Dec 21 13:17:10 DietPi1 systemd[1]: jellyfin.service: Scheduled restart job, restart counter is at 5.
Dec 21 13:17:10 DietPi1 systemd[1]: Stopped Jellyfin Media Server.
Dec 21 13:17:10 DietPi1 systemd[1]: jellyfin.service: Start request repeated too quickly.
Dec 21 13:17:10 DietPi1 systemd[1]: jellyfin.service: Failed with result 'signal'.
Dec 21 13:17:10 DietPi1 systemd[1]: Failed to start Jellyfin Media Server.
root@DietPi1:~#




root@DietPi1:~# sudo -u jellyfin /usr/bin/jellyfin --webdir=/usr/share/jellyfin/web --restartpath=/usr/lib/jellyfin/restart.sh --ffmpeg=/usr/lib/jellyfin-ffmpeg/ffmpeg
Segmentation fault
root@DietPi1:~#
23

And, as above check, the package is definitely installed from the Raspbian branch of the repository?

24 
Get:3 https://repo.jellyfin.org/raspbian buster InRelease [6637 B]
Get:4 https://fra1.mirror.jellyfin.org/debian buster/main armhf Packages [1639 B]
Fetched 8276 B in 6s (1464 B/s)

Seems to be fechted from debian?? But source list looks fine

root@DietPi1:~# cat /etc/apt/sources.list.d/dietpi-jellyfin.list
deb https://repo.jellyfin.org/raspbian/ buster main
root@DietPi1:~#
25

Oh… their mirror director does not respect the Raspbian/Debian separation. It seems that https://repo.jellyfin.org/raspbian is redirected to https://fra1.mirror.jellyfin.org/debian while https://fra1.mirror.jellyfin.org/raspbian would be actually available :roll_eyes:.

I just reported it: https://github.com/jellyfin/jellyfin-meta/issues/5

26

Okay, sad fact: Jellyfin cannot run on ARMv6 boards, i.e. Raspberry Pi 1 and Zero models. This is an issue with .NET core itself: https://github.com/dotnet/runtime/issues/7764
The “raspbian” repo directory only exists so that $( awk -F’=’ ‘/^ID=/{ print $NF }’ /etc/os-release ) from the downloads page can be used on Raspbian as well, but it is a symlink or internal rewrite to the Debian binaries anyway, so does not mean its Raspbian armv6hf binaries.

So we need to disable the install option on those boards. But to be clear, a media server on RPi 1 or Zero would anyway not be of joy I guess, unless it’s for SD videos or audio only :wink:.