2025-02-14, 06:51 AM
(This post was last modified: 2025-02-14, 06:53 AM by ryogamasaki. Edited 1 time in total.)
Sorry to bump, but I found this thread after experiencing the same issue. I have dozens of playlists curated over several years, ported over from previous tools I've used like Ampache. So I was... disappointed when everything was empty after restarting my machines and Jellyfin came up before the NAS was mounted. This setting should not be on by default, imho. In any software, any option that deletes should always be opt-in...
But I am happy to find that the logs dutifully recorded each item that was removed, so to anyone who also experienced this, you can grep the logs for "cannot be found at" which includes the name of the playlist and the path to the file, e.g.:
jellyfin20250213.log:[2025-02-13 14:40:21.103 +09:00] [INF] Item in "♾️BGM・ノリノリ" cannot be found at "/mnt/nas/Music/K/Kadomatsu Toshiki - Parasail [FLAC]/01 PARASAIL〜シュールホワイトのテマ.flac"
It should be not overly difficult to write a script to use that information to recreate the xml file for each playlist stored at /var/lib/jellyfin/data/playlists
Hope this helps.
But I am happy to find that the logs dutifully recorded each item that was removed, so to anyone who also experienced this, you can grep the logs for "cannot be found at" which includes the name of the playlist and the path to the file, e.g.:
jellyfin20250213.log:[2025-02-13 14:40:21.103 +09:00] [INF] Item in "♾️BGM・ノリノリ" cannot be found at "/mnt/nas/Music/K/Kadomatsu Toshiki - Parasail [FLAC]/01 PARASAIL〜シュールホワイトのテマ.flac"
It should be not overly difficult to write a script to use that information to recreate the xml file for each playlist stored at /var/lib/jellyfin/data/playlists
Hope this helps.