SOLVED: Synology 100% wipe of JF to start fresh

[MoonOverMiami]

At my wits end. Updated to 10.9.6 on Synology. It plays videos but Scan is still failing.
My initial setup from 3 years ago was/is incorrect and I lost all config data during the 10.9.6 update (2nd time, first time was during a 10.8.x update). That tells me it's really broken, must be something I set up wrong in 2021.

How do I erase everything Jellyfin from Synology so I can start from zero as a fresh install?

Erase/delete hidden data, old config files etc so I can get this set up correctly as a New User on 10.9.6.

Is it as simple as 'delete the containers and start over' or are there ghosts in the file system I need to hunt down and remove.

I see one ghost. There are no containers except for Jellyfin. Restarted the container and it shows as Jellyfin-backup. Only container I did not delete was Jellyfin. The -backup was deleted before Restart. And the -backup was 10.9.2.

Example of broken initial JF install.... there are no folders in my Docker folder in File Station. There should be a Jellyfin folder but it's not there.

Thank you in advance for the guidance.

https://postimg.cc/gallery/Jn5MF95

[TheDreadPirate]

Perhaps share your jellyfin log on pastebin to see if we can fix this instead of starting over?

If you just want to start over, you have to delete the storage for Jellyfin. The paths in the UI are virtual paths. In the Synology UI for Jellyfin it should provide the actual paths on the host.

[MoonOverMiami]

Do not have external access enabled for my Jellyfin instance so I'll delete and rebuild.
How do I find the folders? Not showing in File Station. Would I need to ssh into the NAS?
thanks

[TheDreadPirate]

I had assumed Synology would have some way to access the file system directly in the UI. If not, you will need to SSH. I don't have a Synology NAS, but I recall screenshots from other users where the Jellyfin config page showed you where it was writing Jellyfin's /config directory to on the host.

[3216]

I had assumed Synology would have some way to access the file system directly in the UI.

It does. File Station gives you a full file browser where you can move/delete/rename as appropriate.

---

What you need to do will vary slightly depending on how you’ve set up the container, but you probably just want to stop the container from within Container Manager, delete the contents of whichever folders you’ve mapped as /config and /cache in the container, and restart the container.

[Efficient_Good_5784]

@MoonOverMiami

Could you take a picture of your container's settings? Specifically the host mount section?

I'm wondering if you actually mapped folders outside of the container or not.

[MoonOverMiami]

Please let me know if you need more.
https://postimg.cc/gallery/gFx1xYb8

[Efficient_Good_5784]

Yeah, you never mounted the config folder (or any other) outside your container. Deleting the container will 100% take all the Jellyfin data with it.

The only exception is metadata that might have been stored along with your media files if you enabled that in your libraries.

You will want to mount the config folder externally next time you redo the container. It will make it easier on you when you want to update your Jellyfin server and keep your previous settings and metadata.

[MoonOverMiami]

I understand what the issue is. Reinstalled (deleted old image) and have these settings automatically populated. Is this correct or was this the initial problem?
https://postimg.cc/gallery/V87tVw8c

Should lines like JELLYFIN_CONFIG_DIR be set at '/config/config' ? Meaning, is that inside the Container (again) or should I manually change those to something else instead of config/config.

[Efficient_Good_5784]

No, keep those as they are. Those are your environment variables.

What you want is to map the config under the volumes section.
So do the following:

1. Create a folder on the NAS for Jellyfin. In the folder make another folder named "config".
   
2. In the container volume settings, map the config folder you created before as --> /config
   
3. The config folder should now be created in the config folder you made in step one.