+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Updated container has gone all wrong (/t-updated-container-has-gone-all-wrong)
Pages:
1
2
RE: Updated container has gone all wrong - Femur4889 - 2024-05-08
(2024-05-08, 09:21 PM)3216 Wrote:(2024-05-08, 09:06 PM)Femur4889 Wrote: There is something very wrong going on here.
I have tried several times to simply start up a fresh JF container with /config and /cache in a totally separate location from this original one. This new container always wants me to log in with an EXISTING user, which there should not be. I looked at /config/system.xml and find that the line <IsStartupWizardCompleted> is set to FALSE, implying that JF should be prompting me to create a new user.
That’s probably a browser issue. Try accessing the new Jellyfin instance with the browser in private/incognito mode, that should let you configure Jellyfin, and once configured you can go back to a normal browser session and log in.
Thank you, I tried multiple browsers.
RE: Updated container has gone all wrong - Femur4889 - 2024-05-08
I solved it.
TL;DR - Check your /etc/fstab to make sure that the /config and /cache files which you seem to be interacting with are actually on a drive which is mounted.
The disk that used to contain /config and /cache used to be mounted at startup using fstab. At some point in the past without my now remembering I commented this drive out in fstab.
Now in the present and after commenting that drive out, the mount point for this drive (/mnt/500gb) still existed on my root disk, which is not surprising. What is surprising to me, however, was that I was able to interact with all of my docker files which were previously mounted here. I altered the docker compose file and it saved/persisted, AND I pointed my docker compose file at the /cache and /config areas which DID exist when the drive was mounted in fstab but actually now contained no information since that disk wasn't mounted, though I was able to interact with the files on the command line.
I happened to glance at my GUI file browser and notice there was a disk which was unmounted. I thought this was strange because I thought I was aware of how many disks should be installed on this server. I checked out fstab, saw the commented-out old drive and made note of its UUID. Then, I mounted this newly-found drive and inspected it where I noticed it had the same UUID as the one listed in fstab.
All of my correct docker /config and /cache files were on this disk which had been unmounted all along, even though I thought it was mounted because the old mountpoint showed not only the folder structure but the actual /cache and /config files AND I was able to interact with them.
Once this disk was mounted and docker compose was set up correctly, my newly updated Jellyfin instance worked flawlessly using my old data.
Hopefully I've explained this well enough to save someone two days of troubleshooting.