• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting troubleshooting missing libraries

     
    • 0 Vote(s) - 0 Average

    troubleshooting missing libraries

    Libraries disappear after reboot of host
    the-bort-the
    Offline

    Junior Member

    Posts: 12
    Threads: 4
    Joined: 2024 Feb
    Reputation: 0
    Country:United States
    #1
    2024-07-06, 03:49 PM
    Currently, after an unexpected power outage or reboot to host, my libraries aren't coming back. Turns out the mounted usb drives are being lost and I need to manually remount them. Is it preferred to just edit the /etc/fstab file with all the mounts? 

    It's also noticed that after re-mounting them and doing a scan of all libraries, it takes some time for them to show up in the UI.

    It's also not uncommon for me to also restart the docker container because they aren't showing up after a scan. I usually wait 15-20 minutes before noticing I need to restart the container.

    Version: 10.8.13 
    Operating System: Linux 
    Architecture: X64
    Efficient_Good_5784
    Offline

    Community Moderator

    Posts: 1,186
    Threads: 3
    Joined: 2023 Jun
    Reputation: 50
    #2
    2024-07-06, 03:55 PM
    Could you share your server logs using pastebin?
    the-bort-the
    Offline

    Junior Member

    Posts: 12
    Threads: 4
    Joined: 2024 Feb
    Reputation: 0
    Country:United States
    #3
    2024-07-06, 04:51 PM
    Is this sufficient? It's a really big file and exceeded the pastebin file size, so I chopped it.

    https://pastebin.com/A6xHN7Zm
    Efficient_Good_5784
    Offline

    Community Moderator

    Posts: 1,186
    Threads: 3
    Joined: 2023 Jun
    Reputation: 50
    #4
    2024-07-06, 05:59 PM (This post was last modified: 2024-07-06, 08:33 PM by Efficient_Good_5784. Edited 5 times in total.)
    Jellyfin most likely is booting up before the drives come online causing Jellyfin to mark that they're no longer present. Make sure the drives are mounted before starting Jellyfin.

    Jellyfin needs to rescan a library every time it moves in the system.

    Looks like the database got corrupted somehow.

    I'm going to guess the frequent shutdowns of the server caused that. You should let it do its thing instead and check the logs if you're questioning if it got hung up on something before restarting the container.

    As for the power outage failure, I suggest getting a UPS. It will save your data next time so that your server doesn't get shutdown during something important.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #5
    2024-07-06, 06:41 PM
    You can try my solution for a similar (the same?) problem in this thread.

    https://forum.jellyfin.org/t-jellyfin-de...5#pid22855

    Essentially you are telling the jellyfin service to not start until a particular mount is online.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    the-bort-the
    Offline

    Junior Member

    Posts: 12
    Threads: 4
    Joined: 2024 Feb
    Reputation: 0
    Country:United States
    #6
    2024-07-07, 10:12 PM
    I currently do not see a jellyfin.service file under the path you provided. Also there is no jellyfin.service file on the container file system. Should I create one to add the line you mentioned from the other thread?

    Code:
    $user@host: ls /etc/systemd/system/multi-user.target.wants/
    anacron.service        containerd.service      cups.path              e2scrub_reap.service    NetworkManager.service  samba-ad-dc.service    ufw.service
    avahi-daemon.service    cron.service            cups.service            ModemManager.service    nmbd.service            smbd.service            wpa_supplicant.service
    console-setup.service  cups-browsed.service    docker.service          networking.service      remote-fs.target        ssh.service
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #7
    2024-07-08, 01:59 AM
    I missed the part in the first post where you are running Jellyfin in docker. You can try doing the same thing in the docker.service file. I'm not sure if there is an equivalent way of forcing a container to wait for a mount directly in a docker compose or something.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    the-bort-the
    Offline

    Junior Member

    Posts: 12
    Threads: 4
    Joined: 2024 Feb
    Reputation: 0
    Country:United States
    #8
    2024-07-12, 01:48 PM
    Thus far I have been able to update the /etc/fstab and while it appears the host can reboot and see the drives mounted, it still took a manual rescan of all libraries. Next I will move onto your suggestion for adding the changes to the docker.service file.
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode