xrqp

A month ago, my CPU heatsink was not mounted correctly. In the dashboard I could see it was very hot, so it apppeared to be throttled, based on dashboard showing utilization of each core. But I do not recall seeing any warning in FCP (fix common problems). Maybe I missed it. Thanks to dashboard, I fixed it.

It should be easier to get good data about energy consumption. Idle power, watts per caclulation, etc. I guess not enough people care. Until then, the TDP is a practical data point. I assume the mobile versions of CPUs (low power) would be appropriate. I ended up getting a used Intel i7-7700T for $250. The T at the end means for mobile (low power). Now, the lowest my entire unraid computer goes is 38 watts, I assume when nearly everything is idling. I have 6 hard drives and 1 nvme drive. My power supply is 450 watt, Seasonic G-450, 80 Plus Gold. I was hoping AMD may have a breakthrough on energy efficiency, but it seemed product availability was not good, and info on energy remains hard to find.

I searched this thread for the word "warning" but not much came up. I like that I get a warning for hard drive temps too hot. Can I get that for CPU temp?

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:

I clicked "fix" and it fixed it. Easy peasy. Now my "fix common problems" is clean, which I like. Thanks.

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.

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 roonserver template URL.

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 cannot start emby container. When i remapped my emby container port 1900 to be 1901 on the host, it did allow me to start emby when roon was running, but now I cannot delete media files (on unraid array) from within emby. I turned off Roon and kept it off, set the port back to 1900 for emby, and then emby worked good and could delete media files. So I have not solved my problem yet, but I am sure it is to do with port 1900. If anyone knows how to fix this, please tell. Here is my emby settings. UPDATE 2021-6-20: I fixed a path problem in Emby and then no longer had any port problems with Emby and Roon.

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.

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 1% /lib/modules overlay 2.0M 12K 2.0M 1% /lib/firmware tmpfs 2.0M 1 2.0M 1% /mnt/disks tmpfs 2.0M 1 2.0M 1% /mnt/remotes /dev/md1 746M 409K 745M 1% /mnt/disk1 /dev/md2 466M 87K 466M 1% /mnt/disk2 /dev/md3 746M 12K 746M 1% /mnt/disk3 /dev/md4 746M 522K 745M 1% /mnt/disk4 /dev/md5 746M 443K 745M 1% /mnt/disk5 /dev/nvme0n1p1 0 0 0 - /mnt/cache shfs 3.4G 1.5M 3.4G 1% /mnt/user0 shfs 3.4G 1.5M 3.4G 1% /mnt/user /dev/loop2 0 0 0 - /var/lib/docker root@Tower:~# ^C root@Tower:~#

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?

Thanks very much for the info.

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?

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?

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. UPDATE 2021-6-20: I fixed a path problem in Emby and then no longer had any port problems with Emby and Roon.

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. UPDATE 2021-6-20: I fixed a path problem in Emby and then no longer had any port problems with Emby and Roon.

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. 🤪

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.

I think I saw that the overall docker image is also called "docker.img". Is that correct?

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 were corrupt, i copied my backup media files (movies, tv) to the media folders. that seemed to stop the disappearing. Then Sonarr and Emby stopped working correctly. I restored Unraid config backups like app data. No help. I installed the containers from previously installed apps, which did not work. I then installed containers from fresh install (not from previously installed apps). Still cannot get them to work. PLANNING TO START OVER TO LARGE DEGREE I am thinking I should start over as clean as possible. Delete containers, deleted configs, even delete the share and share files. Then recreate it all. Is there a chance that will help? Before I recreate everything, are there any tips on what I must delete to really get a fresh start? Squid told me, in Krusader "The only thing Unraid related is /media, /UNASSIGNED, /FLASH, /config". I think I should not touch UNASSIGNED or FLASH. In config I see this, should I delete it all? In media/user/ I have all my shares, but the only share that gave me the trouble described in this subject was the "data" share with all my movies and tv shows in the "media" folder you see here: So can I delete it from Krusader, or should I delete it from Unraid Web UI for Shares? Which way deletes it most completely, so it does not leave config remnants or other hidden remnants, if any?

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), except now I see it also has the "user" folder with all the shares. A little further down, I ask what is this "media". When it first opens it goes to "Home" like this: What is Home and why does it start there? Then I click "go up" and this appears: It went to Root/home. Makes no sense to me. So it is still in home, but seems like a different home with little "h", and inside Root. Then I click "go up" again and this seems more normal cause it goes to Root. Here is what I see in Krusader, but if I click on "mnt" it's not what I expected and is somewhat empty, so I go back up to Root. Next click "root" and it says "error: cannot open". Why is little root inside big Root? But when I click on "media" it gets me where I want to go. Now I see the disks AND I see "user" which is what I want - my user shares. I assume it is something to do with the container mappings of /media <--> /mnt/ I kind of understand the /mnt/ since we use it a lot. But I don't understand where /media comes from or if it is an arbitrary word and could be replaced by any word? And when I ask "calculate occupied space" of a folder "old appdata" it QUICKLY shows this good info. If I go to windows explorer, it TAKES FOREVER for it to count up 42k folders. (My guess is it is Roon music database files, cause Roon makes thousands of folders and files). But Krusader does the count very fast, I guess Krusader is more direct to get the size and counts of folders and files in unraid. But when I use Krusader to delete the folder, it takes forever. maybe because I did not turn off .Recycle.bin first? Thanks for any replies.

thank you, John M.

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?

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.

hotmail