2025-04-02, 03:13 PM
I chatted with @theguymadmax and we've both come to the same conclusion. Since the library XMLs and mblink files don't contain / as a library root folder, that indicates it is still in the database somewhere and now Jellyfin is in a difficult to recover from state if you don't know your way around SQLite.
We think the best path forward is to start over.
Then you will need to clear your browser cache or use an incognito/private browser window so that the startup wizard will load.
![[Image: attachment.php?aid=5082]](https://forum.jellyfin.org/attachment.php?aid=5082)
![[Image: attachment.php?aid=5083]](https://forum.jellyfin.org/attachment.php?aid=5083)
We think the best path forward is to start over.
Code:
sudo systemctl stop jellyfin
cd /var/lib
sudo mv jellyfin origJellyfin
cd /etc
sudo mv jellyfin origJellyfin
cd /var/cache
sudo mv jellyfin origJellyfin
sudo systemctl start jellyfin
Then you will need to clear your browser cache or use an incognito/private browser window so that the startup wizard will load.