Jump to content

lionelhutz

Members
  • Content Count

    3720
  • Joined

  • Last visited

Community Reputation

15 Good

About lionelhutz

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Did you setup the media share? Link /tv in the container to the location of your TV series. Then, when you add a series you can just use /tv/ as the folder. Once you do it, it should just keep re-using it. Same as the quality, it re-uses the last choice. I have a share called TV shows so I have /tv -> /mnt/user/TV_Shows/ It has to be the top level location of the TV series because it creates a directory for each series and then subdirectories for each season. Well, I believe you can change that so it dumps them all into a single series directory but it doesn't make much sense not to use season directories.
  2. No, complete and incomplete are sub-directories in the download share. You don't set them up as docker paths. You setup the apps internally where their setup asks for those directories. When you set up the download share, make sure the container path and host path are exactly the same for every one. Then, you use the container path in the internal app setup. A NZB indexer is for Usenet. A torrent indexer is for torrenting. You have to match the indexer to the type of download. I use Usenetserver and it's been good, but there are others that will work just as well. I have no idea what indexer is best to sign up with today. I used to run my own.
  3. As far as setup. Sonarr and Radarr are to find the stuff to download. They send the info to download clients like Deluge or SABnzbd to actually download it. They also monitor the download and sort it once it's downloaded. The indexer is used by Sonarr and Radarr to find what to download. You need an indexer that matches the type of download you want to do. Some docker containers have the ability to link compete and incomplete folders to directories on the server, which is normally completely unnecessary. I don't know why the developers make it complicated like that. I recall one container wanted an incomplete path setup. I just deleted it. Others probably had it too. Containers between different authors might have different path names too. Fix them so they are all the same. The easiest is to link every app to a downloads directory. I have a Downloads share and setup every docker container to have a path pointing /downloads in the container to /mnt/user/Downloads/ on the server. Only this one. Then, in each app I set the downloads directory to be /downloads. Some of the apps have the place to enter compete and incomplete directories. I entered /downloads/complete and /downloads/incomplete. The main thing with the paths is to make sure you put the SAME setup for every docker container. Be very consistent with this. I suggest linking a single share for downloads. Call it downloads or Downloads or whatever, but use it for every container. Just make sure the unRAID share side and container side are consistent. Notice how I used a capitalized share name but small case name on the docker side? Then you refer to that single directory in each app setup. If you don't keep it consistent, then you can have issues with the apps finding stuff the other app has put in the directory.
  4. For initial setup I'd use the most free allocation method and set the split level to 1 or only split the top level. That way, each new series will start on the most empty disk so it has the most room to grow but it will all stay together on that disk. I've used that setup for years and it's worked well. Only had a disk run low on space a couple of times and require manual intervention.
  5. I'm running 9 Docker containers and a W10 VM on a 4-core i5-6400. I even transcode 1 stream for internet viewing with Emby using the Intel GPU and 1 core. No 4k media here yet. It"s a rather pathetic CPU compared to what you are considering but I can't convince myself to upgrade yet because it's still handling the current loading just fine. Overall, your CPU choice looks great if you you don't have any processor intensive tasks planned besides Plex. I do want to get into Tensorflow camera image processing in Home Assistant and once I start doing that then I'll likely need a better processor. Something for the new house to provide some security and also a more accurate way to activate outside lights instead of old school motion sensors.
  6. I can't see this being implemented. I bet the majority of users barely understand the basic allocation methods. I hope you get the script figured out. But then, do some searching because I bet someone has a solution to sort like you want.
  7. The Linuxserver Radarr docker container has been perfectly stable. You likely are doing something wrong or your hardware has issues if you can't keep it operating stability. Why pull up a 5 year old thread about a long dead plug-in anyways?
  8. What's the typical reported UPS load in watts? That UPS is around 20 minutes at 100W of load. Your server and router and modem could easily draw well over that when the server is working with all disks spun up. There is no simple way to make existing hardware more efficient to much extent. About all you can do is make sure the CPU is speed stepping and the fans are speed controlled based on the temperature of the devices they are cooling.
  9. To run real peripherals with a VM, they must be connected to the server. For example, you pass through a USB card and a video card to the VM and then connect your monitor and USB keyboard and USB mouse to the server to operate the VM.
  10. Without parity, there is no ability to swap a device and let unRAID rebuild it as you have already figured out. You could install the new drive as another disk and copy the data over. Copy the files over the network using a PC or use Midnight Commander from the unRAID command line by typing MC. I've found it doesn't take that long to move 1T blocks of data at a time using a PC. For what you are doing, I would copy though. Make sure you copy disk to disk - DO NOT copy using the share or share to disk. Once complete, do a new config to get rid of the old drive. You could also move the old data drive to the cache position and replace the old data drive with the new drive. A new config would be required here. Once setup, you run the mover and it would move the data off the old drive to the new data drive or possibly other data drives depending on the share settings. Then, do another new config to remove the old drive from the cache position.
  11. After reading the level of work that must have gone into the Stuxnet attack, this type of attack sounds completely believable. China is well known to have a massive state operated hacking organization and is also well known for counterfeiting complex integrated circuits, so it isn't far fetched at all for them to be hardware hacking new products being produced there. Another big question to be asked is how many compromised products don't we know about?
  12. Interesting stuff. From the detail, it's likely true.
  13. You still won't want to hear it, but you'll likely have to start swapping major components to figure this out. Something in there is a piece of crap and the only way to fix it is to replace it.
  14. There's are good reasons orange isn't really a desired product or marketing color.
  15. I'm not seeing any big changes in the font size causing issues with stuff fitting the screen except for the following, On the main Docker tab the Advanced view no longer fits my screen width due to the added load columns. As for the basic view, I hate those drop down arrows - all they achieve is cluttering the screen up to hide a few lines of text. Then, when I click them I have to click both the port and volume mapping because some goofy bottom justify thing is happening. I vote just get rid of attempting those arrows all together. See the screenshot of what happened clicking the volume mapping down arrow. The other thing is the hard boxes around all the options to set. Example places would be a VM edit screen or the disk setting screen. The hard lined boxes around each setting are very odd to see compared to how it's done by pretty much everyone else these days. I think it also contributes to requiring more space between items that isn't necessary to have and just causes more scrolling. If you want to talk how it's a modern layout, hard outlined setting boxes like that are very old school and not modern at all. It looks good otherwise. The other main tabs seem to fit the screen about the same as before.