SOLVED: Collection problem - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: SOLVED: Collection problem (/t-solved-collection-problem) Pages:
1
2
|
RE: Collection problem - Afgin - 2024-05-22 (2024-05-22, 04:53 PM)TheDreadPirate Wrote: We can work through that. dev/sdb2 /media/mutka/Seagatetwo exfat rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,iocharset=utf8,errors=remount-ro 0 0 /dev/sda2 /media/mutka/Exos1 ntfs3 rw,nosuid,nodev,relatime,uid=1000,gid=1000,windows_names,iocharset=utf8 0 0 /dev/sdc2 /media/mutka/seagate ntfs3 rw,nosuid,nodev,relatime,uid=1000,gid=1000,windows_names,iocharset=utf8 0 0 also added the third drive with same command RE: Collection problem - TheDreadPirate - 2024-05-22 Code: sudo systemctl stop jellyfin At the bottom of /etc/fstab put this in Code: /dev/sda2 /media/mutka/Exos1 ntfs defaults 0 0 Then save, quit. Code: sudo mount -a This will mount all the drives defined in /etc/fstab. Let me know if you run into any problems. RE: Collection problem - Afgin - 2024-05-22 trying to unmount with umount. "target is busy" dunno which is using it RE: Collection problem - TheDreadPirate - 2024-05-22 Reboot. It will apply the new mount parameters during boot up. RE: Collection problem - Afgin - 2024-05-22 (2024-05-22, 05:58 PM)TheDreadPirate Wrote: Reboot. It will apply the new mount parameters during boot up. Yea I did that, and this was a result after sudo mount -a ntfs-3g-mount: failed to access mountpoint /media/mutka/Exos1: No such file or directory mount: /media/mutka/Seagatetwo: mount point does not exist. # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/nvme0n1p2 during installation UUID=593b83f6-03bf-4388-bef1-424af1e22c05 / ext4 errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=8248-C7D1 /boot/efi vfat umask=0077 0 1 /swapfile none swap sw 0 0 /dev/sda2 /media/mutka/Exos1 ntfs defaults 0 0 /dev/sdb2 /media/mutka/Seagatetwo exfat defaults 0 0 /dev/sdc2 /media/mutka/seagate ntfs defaults 0 0 this is what the fstab file looks like. does UUID things interfere? Tried also with putting hash infront of them RE: Collection problem - Afgin - 2024-05-22 I have an itch that the problem with the Exos is that it is asleep. In the disk management there is zzz icon. It has only woken up by pressing the icon. Then it wakes and mounts RE: Collection problem - TheDreadPirate - 2024-05-22 Ah. The place we told it to mount to doesn't exist. I assumed the folders were still there from the previous mounts. Code: sudo mkdir -p /media/mutka/Exos1 /media/mutka/Seagatetwo /media/mutka/seagate Then try "sudo mount -a" or reboot. RE: Collection problem - Afgin - 2024-05-22 (2024-05-22, 06:17 PM)TheDreadPirate Wrote: Ah. The place we told it to mount to doesn't exist. I assumed the folders were still there from the previous mounts. Hey. I did a reboot, and now it seems to auto mount! I didn't need to click on the icon. jellyfin server found and played the files straight. So it should be fine now I guess. Now that second part where mounting is ensured before jellyfin launches? RE: Collection problem - TheDreadPirate - 2024-05-22 You shouldn't need to do that part anymore. RE: Collection problem - Afgin - 2024-05-22 Seems to work right. You are amazing man! Thank you so much for helping me. Was kinda scared at one point that something will go very wrong, but it all went perfect in the end. |