Hi, I have a large collection of music and TV programs etc installed in Jellyfin on Bookworm.
Is there a way to transfer my Jellyfin data to a new install of trixie?
why not doing an inplace upgrade from Bookworm to Trixie?
HI Joulinar, thanks for your reply.
In answer to your question there are 2 main reasons, firstly I did try updating using the supplied script but I experienced some problems but the main reason for wishing transfer the Jellyfin data was that I wanted to start from a new install because the current Bookworm installation has a problem with the hot-spot not allowing connections. It takes me many hours to start again inputting the Jellyfin data from scratch.
The location of the Jellyfin data has changed in the last couple of years.
Database and such are stored in /mnt/dietpi_userdata/jellyfin, respectively the JELLYFIN_DATA_DIR given in /etc/default/jellyfin. Configs are stored in /etc/jellyfin. Those those 3 paths should be transferred (including /etc/default/jellyfin).
Checking the install code, best is to install Jellyfin freshly first, then stop the service, and copy/overwrite with the old data/configs afterwards. Otherwise, if /mnt/dietpi_userdata/jellyfin exists already, a bunch of setup steps are skipped and would need to be done manually. Room for enhancement our end.
Thank you Michaing,
I am not sure I have understood your information.
I have 2 PI5’s 192.168.123.111 and 192.168.123.112
192.168.123.111 has a working jellyfin on it, and I want to copy it to 192.168.123.112
I have installed a new jellyfin on 192.168.123.112 and ran it so it completed the first run.
Then I stopped the service ‘service jellyfin stop’
I deleted recursively on 192.168.123.112 the following folders
/mnt/dietpi_userdata/jellyfin
/etc/default/jellyfin
/etc/jellyfin
I then copied from 192.168.123.111 to 192.168.123.112 the following folders
/mnt/dietpi_userdata/jellyfin
/etc/default/jellyfin
/etc/default/jellyfin
The rebooted 192.168.123.112 but jellyfin does not start anymore.
can you provide the service log?
see below
Oct 10 13:23:10 DietPi (jellyfin)\[1018\]: jellyfin.service: Changing to the requested working directory failed: Permission denied
Oct 10 13:23:10 DietPi (jellyfin)\[1018\]: jellyfin.service: Failed at step CHDIR spawning /usr/bin/jellyfin: Permission denied
Oct 10 13:23:10 DietPi systemd\[1\]: jellyfin.service: Main process exited, code=exited, status=200/CHDIR
Oct 10 13:23:10 DietPi systemd\[1\]: jellyfin.service: Failed with result ‘exit-code’.
Oct 10 13:23:11 DietPi systemd\[1\]: jellyfin.service: Scheduled restart job, restart counter is at 4.
Oct 10 13:23:11 DietPi systemd\[1\]: Started jellyfin.service - Jellyfin Media Server.
Oct 10 13:23:11 DietPi (jellyfin)\[1020\]: jellyfin.service: Changing to the requested working directory failed: Permission denied
Oct 10 13:23:11 DietPi (jellyfin)\[1020\]: jellyfin.service: Failed at step CHDIR spawning /usr/bin/jellyfin: Permission denied
Oct 10 13:23:11 DietPi systemd\[1\]: jellyfin.service: Main process exited, code=exited, status=200/CHDIR
Oct 10 13:23:11 DietPi systemd\[1\]: jellyfin.service: Failed with result ‘exit-code’.
Oct 10 13:23:11 DietPi systemd\[1\]: jellyfin.service: Scheduled restart job, restart counter is at 5.
Oct 10 13:23:11 DietPi systemd\[1\]: jellyfin.service: Start request repeated too quickly.
Oct 10 13:23:11 DietPi systemd\[1\]: jellyfin.service: Failed with result ‘exit-code’.
Oct 10 13:23:11 DietPi systemd\[1\]: Failed to start jellyfin.service - Jellyfin Media Server.
how did you copied the files? Which commands do you used?
I used midnight commander
not sure how MC is working but you would need to preserve permissions while doing the file copy. As well have a look if user ID for jellyfin user is different between systems
This is from the working jellyfin on 192.168.123.111
root@DietPi:\~# id jellyfin
uid=101(jellyfin) gid=108(jellyfin) groups=108(jellyfin),44(video),105(render),1000(dietpi)
root@DietPi:\~#
This is from the non working jellyfin 192.168.123.112
root@DietPi:\~# id jellyfin
uid=100(jellyfin) gid=102(jellyfin) groups=102(jellyfin),44(video),991(render),1000(dietpi)
root@DietPi:\~#
ok both don’t match. You would need to reset permissions if needed.
THE OBJECTIVE IS TO COPY A WORKING JELLYFIN FROM 192.168.123.111 TO 192.168.123.112 TO A NEW PENDRIVE WHICH HAS TRIXIE INSTALLED ON IT
192.168.123.111 has a working jellyfin on it, and I want to copy it to 192.168.123.112
I have installed a new jellyfin on 192.168.123.112 which has just been flashed with Trixie and ran it so it completed the first run.
Then I stopped the service ‘service jellyfin stop’
I deleted recursively on 192.168.123.112 the following folders
/mnt/dietpi_userdata/jellyfin
/etc/default/jellyfin
/etc/jellyfin
I then copied from 192.168.123.111 to 192.168.123.112 the following folders using Midnight Commander
/mnt/dietpi_userdata/jellyfin
/etc/default/jellyfin
/etc/default/jellyfin
chown -R jellyfin:adm /etc/jellyfin
chown -R root:root /etc/default/jellyfin
chown root:root /mnt/dietpi_userdata
chown -R jellyfin:jellyfin /mnt/dietpi_userdata/jellyfin/
REBOOT
Hopefully success IT WORKED FOR ME
1 Like
It would be very nice if someone who is very kind could make a script to automate this process.
Regarding permissions, this should do. No need to change the GID of jellyfin, and there might be another group with the same GID already.
chown -R jellyfin: /etc/jellyfin /mnt/dietpi_userdata/jellyfin
The : assigns the primary group of the user, i.e. practically the same as jellyfin:jellyfin. An alternative would be jellyfin:root make it slightly more secure and and ignore the group, which is relevant only if you actually require other users/processes to access the data and add them to the group. root has always the same UID/GID “0”, so no need to chown e.g. /etc/default/jellyfin.
Just copy&paste the commands you used from your console history (~/.bash_history) into a file, and prefix with #!/bin/bash shebang.