Energen

Members
  • Posts

    516
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Energen

  1. So you essentially need the databases folder for watched status, etc. You can use a script like this to back up on a schedule. https://forums.unraid.net/topic/102290-user-script-for-important-plex-data-backup-v3/?tab=comments#comment-943802
  2. No. You can sign into your plex server from plex.tv at any time from anywhere, doesn't matter what ports it's on or any subdomain that it might be connected to .. so you're only making more work for yourself. But you can continue to set it up, doesn't really matter. It's obviously a port issue if you're not getting outside access, and/or a forwarding issue for the domain. Do you have 32400 open? I believe that's required no matter what.
  3. Why are you trying to run in through a reverse proxy? Just sign into plex.tv and your server is available world wide.
  4. I completely agree.. they (radarr/sonarr) are terrible. Not as easy to use either. You CAN go back by reverting to an older build, but like Urban said.. the new ones are going to be the ones that are most worked on. It's kind of adapt or get left behind, but if you want to you can change your repository to linuxserver/radarr:v0.2.0.1504-ls37 and pull it down again.. that was the last version I had before they changed the GUI. The databases converted for the new UI version as well so if you go back you'll lose any changes that you've had since going to the new UI.
  5. Well yes, that would seem to indicate that it's running at 200 Mhz, vs the ~1600mhz it's supposed to be running at. You'd have to look into your BIOS settings.
  6. Originally I used a simple 2 line script to only back up the Plex databases since I excluded Plex from CA Appdata Backup because I didn't want nightly backups with 20GB+ of Plex metadata. That idea sparked @Cpt. Chaz to further modify that basic idea with some improvements and a great @SpaceInvaderOne-type video on YouTube showing the implementation and use of his script. His version of the script gave me some ideas on improving my original version, which led to this new version. A lot to follow, right? The main difference between Cpt. Chaz's script and mine is that I use a tar archive for backup and he copies the files, which can easily be changed to using tar if you wanted to. I also back up the Plug-ins preferences directory which includes settings for scrapers, plugins, etc. Then I took it a step further (for fun, and learning) to not only back up the important Plex data but to also have the ability to create periodic full Plex appdata backups (like you'd ultimately get with CA Appdata Backup). I run CA Appdata Backup nightly but I do not need or want full Plex backups every single night, so this is my solution. If you run the script manually you'll end up seeing something like this... I just created a fresh set of backups. Find the script here and you can contribute to any changes / fixes. https://github.com/rcodehub/unraid-plex-script Enjoy!
  7. I might try changing the RPC setting... on my box the endpoint is /rutorrent/plugins/rpc/rpc.php See if seedbox.io has the wrong endpoint (maybe from an older version) I used seedbox.io many years ago, don't remember why I switched though.. Edit - Nevermind, my endpoint is also rutorrent/plugins/httprpc/action.php ... I was looking at config settings from an old version I had saved
  8. Yes.. I'm scratching my damn head now, seems like you are going in circles like the new Biden press secretary! Let's circle back... Actually it's not too bad.. I understand what you're wanting to do and that's basically how things should work. Let's start with this... have you followed all the instructions from seedbox.io for connecting sonarr? https://panel.seedbox.io/index.php?rp=/knowledgebase/41/How-to-connect-Sonarr-to-your-service.html
  9. I don't believe there is any way to disable parity except to unassigned the parity drives. I agree the speed issue is annoying but the trade off is you disable parity to move the data and then have to create parity each time you do this. That might not be as annoying since you can do parity in the background but my parity checks/creations take around 8-10 hours, and I'm uneasy about writing new data to the array during that time, but that's just me. So is a slower transfer better or a long parity creation time? That's your choice. 2 parity drives does not effect the speed in either way.
  10. Ah, I'm not familiar with the Synology hardware. Seems that jonathanm has a solution for you to try in his post above. Sounds like it could be quite a process.
  11. A quality brand flash drive should not give you any problems. I've been using my Ultra Fit since 2017 (the same one, never changed) and have not had any issues with it. Any anecdotal evidence to the lifespan of mini drives I would imagine relies heavily on outside factors. I'm just guessing there. But since purchasing my first license on 5/20/2017 I have not had any problems with my Ultra Fit 16gb mini usb flash drive. According to the sales page of Unraid, you cannot use any other USB based SSD/drive as the boot drive. [quote]Unraid OS is only supported to boot from USB flash-based storage devices. Other boot devices such as SD card readers, HDDs, or SSDs are not supported at this time.[/quote] This really is not a concern you need to think about --- I'd guess that very few people have actually had a flash drive fail on them through normal usage. If the drive actually did fail, you can transfer the license to a new USB relatively easily with a short amount of down time. Graphics cards are generally only needed if you plan to use a dedicated VM and need graphics passthrough, or if you want a card that will transcode for Plex/media players. Other than that the only time you would really need any kind of graphics is to initially set up your PC BIOS for booting from the flash drive. As for moving the data it's going to be a completely manual process --- you will do what you have to do in order to -- at the very least, to start --- move all data off one or more of your drives so that they are empty and can be moved to your Unraid box and added to the array. Unfortunately this is the most tedious, time consuming, aggravating part of the process. When you aren't starting with new empty drives it's a pain in the rear end. The order in which you do things is dependent on how much data is actually on your drives. Ideally I would want to be able to clear off two of the 8TB drives and add those to Unraid. Then I would move the data from the 4x4TB drives onto Unraid onto the 2x8TB drives. Then add those 4x4TB drives to Unraid and move the rest of the remaining data to them. At that point I'd probably shift some of the data around to balance out the drives a little bit (using Unbalance plugin scatter the data) and finally add the last 2x8TB drives to Unraid as your parity drives and create your parity. The reason I'd do the parity drives last is to have full(er) speed for moving data between disks without creating parity at the same time. In my experience moving data without parity drives assigned (with Unbalance) is around 140mb/s compared to 80mb/s with parity. If all your drives are completely full of data, well you have yourself an issue that will require 1) deleting data to be able to move empty drives over, or 2) buying new drives to use in Unraid.
  12. To each his own I'd "prefer" scripts, in general, that don't require me to check if they still work after updates. We accomplish the same thing in different ways.
  13. Change your docker from the latest branch to the develop brach, should pull down 0.8 Repository: linuxserver/lidarr:devlop
  14. Ryzen 5 or 7 should suffice and give you enough processing power for a lot of things. Motherboard isn't too important since you won't use 80% of the features. You need USB/LAN/SATA ports, and not much else. NVME if you want to use them. The number and type of PCI slots might be considered for future upgrading to add SATA cards for more ports. RAM you should at least start with what you're willing to spend right now with ability to add more later. I'd personally start with no less than 32GB (2x16) so you can add another 32 later if you find that you want it. There are people that run on 16GB but that's not going to give you a ton of availability for different dockers/vms/whatever you end up doing. And I'm just old school so I still think that more RAM is better even if less RAM is more efficient than it ever used to be. ECC is mainly only for "peace of mind" that any memory errors are corrected but the odds at actually needing it I don't think anyone actually knows. ECC is more expensive and both the motherboard and CPU have to support ECC. Is it worth it? Can't say for sure. I have ECC but no idea if it actually does me any good. Cache drive size isn't too important as generally it doesn't store a ton of data at a time. 500GB would most likely be more than enough. Unraid needs a flash drive, a pen drive. 16GB is enough, 32GB for the fun of it. Use a quality brand name drive like Sandisk, and think about the back of your case where the USB ports are and the "bumpability" of a flash drive sticking out of the back. You don't want to hit it and break it. I use an Ultra Fit drive like this so nothing is sticking out https://shop.westerndigital.com/products/usb-flash-drives/sandisk-ultra-fit-usb-3-1#SDCZ430-016G-A46
  15. Easiest thing to do is to check all your SMART values for your drives, run some tests on them. Parity errors don't necessarily mean any drives are failing, only that at some point there was an error -- power failures, bad copies, etc.. anything could cause it.
  16. You may want to read through this topic, seems that people have it working on the latest beta Unraid. https://forums.unraid.net/topic/92910-is-intel-gen10-supported/
  17. So for storage only you can go with lower end hardware but you absolutely have to consider the future possibilities. Right now you say storage only (just like I did) but then started to venture off into different things with dockers and vms and this and that. I just spent more money on a new motherboard and cpu when I could have / should have got it the first place had I known I was going to do all this other stuff with my Unraid server. Fortunately for you now there are some good price to performance stuff out there like Ryzen 5/7 that will keep costs lower while also giving you a world of possibilities. Questions you need to ask yourself: 1) I have 8 drives right now but need capability to restore two failing drives -- so do I want to have 6 data drives and 2 parity drives from my current 8 drives or do I want to keep 8 data drives and add two new parity drives? If you need to keep your current 8 drives then you need to buy 2 new 8TB drives also (parity drives must be as large as the largest drive in the array). 2 failing drives at the same time would require 2 parity drives. 2) Do I want to have cache drives? Cache drives usually are ssd/nvme for fast access -- i.e. your docker appdata, fast write speed to the array (data goes to cache first then moves to array). I'd suggest plan on having a cache drive even if you don't initially plan on using it. So those two questions get you to a minimum of 8 SATA ports, up to 10 with 2 parity drives, and another 1 or 2 with dual cache drives or alternatively 1/2 nvme slots. So motherboard with enough SATA ports or plan on using a addon card. Then you have to circle back around to are you actually only going to use Unraid for a NAS, or will you start using it for other things too... that's going to determine your CPU and RAM options.
  18. Yes, still the same way. Even if you didn't have an error you'd still have to set up all the dockers again.
  19. Nice looking script. The only problem with it though, long term, is that it relies on Unraid's built in functions that may change without notice. To make it work universally with no "outside dependencies" you should simplify it down to only working with the flash drive and your script, nothing Unraid specific involved. I use this for file by file backup to Dropbox ... when I get around to it I'll change it to using tar archives as I'm doing with Plex databases.. but the concept will remain the same that it doesn't matter what functions Unraid ever has/uses/changes the script will not break because of those changes.
  20. Didn't follow the whole conversation for what you're trying to do but you can run your own user script that backs up the flash drive to a sync folder on the share for nextcloud.
  21. So not sure which one you're actually asking about as you've mentioned just about every scenario. There are multiple reasons for slower transfers, and many threads on them. ANY network related speed issues the first bottleneck is going to be your network itself. If you have 1gbps LAN ports and network hardware your transfer speed is limited to 1gpbs (~100mb/s), nothing you can do to change that except upgrade all your network hardware. SSD to Array -> limited by HDD write speed and parity calculation.. my time with using Unbalance to move data typically gave me ~80mb/s with the parity drive enabled. Array to SSD -> limited by HDD read speed and the potential for filling up the SSD fast write cache which then limits you to actual write speed on the SSD. These are basic explanations, but they should give you a starting point as to why things are slower than you might expect.
  22. I belive this is only accomplished by turning off SSL under Settings > Management Access.
  23. It doesn't matter which physical disk you move the data to, my point was only that you have to initially move it from disk share to disk share and not disk share to user share. There are many topics on this as well as some talk about it in the Wiki I believe. Never move files between disk shares and user shares, only disk share to disk share or user share to user share. When you get your drives installed set up all the shares you want and then move the data from the 6TB drive to whatever disks you want in the same folder hierarchy... maybe it would be easier to initially set a Movie share to only disk1 and a Pictures share to only disk2 so it's easier to see where to move data. When it comes to Plex you'll point it at the share for media/pictures.. doesn't matter which disk the data is actually on.
  24. Any container that you would want to access to from the outside world would require a reverse proxy.
  25. Yes I think you've pretty much got it figured out. If you have the data you want from the 5*4TB drives then you can start adding/formatting those drives for Unraid. When using Krusader/double commander just make sure that you are moving data from the 6TB drive on the disk share level and not the user share level. i.e. move data to disk2 and disk3 and not a user share like /Media