xrqp

Members
  • Content Count

    118
  • Joined

  • Last visited

Everything posted by xrqp

  1. How do I setup paths for this Emby container for two tv folders? Here are the two I want: /data/media/tv/ (used for tv shows from Usenet) /data/media/tv antenna/ (used for tv shows from antenna and Emby DVR) My share is "data". Here is for 1. data/media/tv Do I need to create a another container path for "tv antenna" for recordings? If yes, what do I put for container path and host path? The following did not work:
  2. I clicked "fix" and it fixed it. Easy peasy. Now my "fix common problems" is clean, which I like. Thanks.
  3. Roon and Emby seem to be working now. Maybe it just needed one or two reboots. xthursdayx, do you mean that the TEMPLATE URL warning is to be expected, but of no concern, and that it is OK, regardless if i click nothing, click fix, or click ignore? If the answer is "yes" that would be good news.
  4. 10 minutes later. With emby kept 1900 to 1900, I rebooted unraid. Both roon and emby containers autostarted. Emby works correct - I can delete files. But now I get a "fix common problems" message that says Before clicking "apply fix" i look at roon container settings and it says "Docker Hub URL: https://hub.docker.com/r/steefdebruijn/docker-roonserver/ " Is this bad? Is it a result of UPNP not working? Should I click "apply fix"? Next, I turned off all autostarts then rebooted again, started only roon, kept emby off, and I still get the same warning about
  5. Wikipedia says "UPnP uses UDP port 1900". Now I find, for some reason, both Roon and Emby experts find it easy to overlook that they both use port 1900 for UPNP and DLNA, but when pointed out, they agree it is true. https://community.roonlabs.com/t/roon-server-udp-1900/58299/10 https://emby.media/community/index.php?/topic/61815-what-are-embys-linux-server-ports/. With emby port 1900 kept as 1900, I noticed, if I start emby container first, then roon, then they both start, but I cannot delete files from within emby. And, if roon container is started first, I ca
  6. My cache is btrfs, but my array is xfs. I think the number of inodes is fixed for xfs, so I was interested if Roon, using so many small files would have a problem. But the more I researched it, the less I was concerned, and now I have no concern at all. Now that you mention cache using btrfs should show zero inodes, I am glad you explained it, and that it can self adjust as needed.
  7. I like this explanation of inodes http://www.linfo.org/inode.html From it, i learned how to do my first command line and got this, today, and I can see I have used 1%, or less, of my inodes. root@Tower:~# df -hi Filesystem Inodes IUsed IFree IUse% Mounted on rootfs 2.0M 12K 2.0M 1% / devtmpfs 2.0M 492 2.0M 1% /dev tmpfs 2.0M 3 2.0M 1% /dev/shm cgroup_root 2.0M 13 2.0M 1% /sys/fs/cgroup tmpfs 2.0M 67 2.0M 1% /var/log /dev/sda1 0 0 0 - /boot overlay 2.0M 12K 2.0M
  8. What is the default limit on an unraid array for inodes (or for files and directories)? I was reading about this at http://www.linfo.org/inode.html Does unraid allocate inodes space at roughly one inode per 2kB of HDD? If yes, then does it follow that a 20TB array can have about 10 billion inodes? Currently my Roon appdata is only 21 GB, but uses 91k files and 47k directories. That is about 130kB per inode. The music itself is about 3TB using 272k files and 76k directores. that is about 20MB per inode. I guess there is no concern about running out of inodes?
  9. So, using something like Krusader, I go to the disk, in this case disk3, and see if there is a "lost+found" folder right under that. If not, then there are none, and that is good. Thanks. Do you think it makes sense, on occasion, to check all the disks with -n or -nv? In my case, I had a lot of problems and did not know why, until I ran filesystem repair on disk3. Should I just run a check on all of the disks to put that potential problem to rest?
  10. I had "metadata errors" so I ran Check file system (xfs repair) many times, many ways ( with -n, with -vn, with nothing, with -L). In the end, it seemed to fix my problems. On one run, it said "moving disconnected inodes to lost+found". After restarting in normal mode, I cannot find a folder called "lost+found". Where is it, or where are these lost and founds inodes? Or, can I ignore them?
  11. So you figured out that same port was being used for roon container and other container? How? The way I did it: looking at error logs when trying to start emby said somethin like "conflict with port 1900". Roon did not say what it used, so I stopped Roon container. Only then was I able to start emby. Then I remapped emby 1900 to 1901. Then both could run. Maybe someone here can figure out how to see what ports it uses.
  12. What ports does this container use? Can I somehow see which ports it uses, like with most containers? I had a conflict, where an Emby container wanted to use port 1900. Some trial and error gave me a clue that this Roon container may have used 1900. I reassigned emby port 1900 to 1901, so now emby runs, but not well. I have had problems with emby, and other unraid things, so now I wonder if this was the cause.
  13. Just now, I updated from v 1.8 build 790 to 1.8 build 795 and it went good on everything: Unraid core, ipad, iphone, and Win10 desktop. 😀Good job! Only 305 builds to go to reach build 1000. 🤪
  14. Did anybody do the Roon update that came in about May 20? I am afraid to be the first. Every time I start the program it nags me.
  15. I think I saw that the overall docker image is also called "docker.img". Is that correct?
  16. I was getting a lot of array errors, so I replaced one disk, then another. Array appeared all good. No more errors. Then I noticed about 70% of my media files disappeared when I ran NzbGet, then came back when i rebooted Unraid. Repeat, repeat. This occurred when viewing from Win10 Windows Explorer. It might have occurred while I was having array problems, I can't recall for sure. Then I tried so many things, and had so many new problems in the process, like Sonarr, Emby will not run correctly. I can not recall the order, but it includes: In case the files
  17. These questions are in the context of me coming from windows and windows explorer. I guess if I only browsed "disk1" "disk2" etc, then it would behave like windows and windows explorer, correct? But when we want to browse the user shares, it is different, and that diff is what makes Unraid what it is, correct? Mapping is used often in Linux in general, correct? I installed Krusader per Spaceinvader with this mapping First I thought "media" is in this mapping to represent physical media (as in physical material, not media like movies
  18. Or can Win10 only see what you share, like smb? Is there any app i can add to Win10 to do this? Or is there a Krusader container alternate that shows trees?
  19. I'm interested too. I am doing more with my unraid than I first thought I would, so I want 4 cores or more -maybe 8 cores would about right. I want low power like TDP 35 Watts or less. Intel screwed me with the 1151 socket then they quickly made all new CPUs incompatible. I have to choose betrween buying an old used Intel i7-7700T for about $300, or get a new CPU and Motherboard. It seems AMD give a much longer life to the sockets.
  20. I used to think that it was OK to call a container a docker. But now that I have a docker problem (not a container problem) I don't think it is OK anymore. But I will not say anything when people misuse it, cause they'll think I am an ass. Plus the misnomer in this thread's subject is official.
  21. Now I see "how" to do it. It is in Settings tab (Settings/ Docker). Found help here Docker Mgmt, down at "Re-Create the Docker image file". I was incorrectly looking in the Docker tab. I was confused about docker image file described here ***OFFICIAL GUIDE*** RESTORING YOUR DOCKER APPLICATIONS IN A NEW IMAGE FILE I do not know if I should do this, but I don't know what else to try, so I will try.
  22. I may be misunderstanding the posts and the guides, about re-installing containers, vs reinstalling the docker engine (or docker service). I had a problem with a container, so I reinstalled it, but it did not help. Then the same happened again with a second container. Should I now try to re-install the Docker Engine (and all the containers since they are under the engine) ? How? I read this ***OFFICIAL GUIDE*** RESTORING YOUR DOCKER APPLICATIONS IN A NEW IMAGE FILE but it seems it only for the containers, I am not sure.