Jump to content

JonathanM

Moderators
  • Posts

    16,167
  • Joined

  • Last visited

  • Days Won

    65

Everything posted by JonathanM

  1. https://lime-technology.com/wiki/index.php?title=Troubleshooting#What_do_I_do_if_I_get_a_red_ball_next_to_a_hard_disk.3F
  2. You are welcome to post here about issues with the docker itself, as I'm not sure the author has any other web presence for support. However, you are kind of on your own getting it running and dealing with issues peculiar to your specific setup. Once you do get it running, I suggest reading through the entire thread to get an idea of how to use it and what it can and can't do.
  3. Left click on the unmanic icon in the docker section of the dashboard of Unraid. You are running Unraid, correct? This is the support forum for Unraid.
  4. Did you check the email registered with limetech? Sometimes their emails end up in the spam folder for some reason. Yes, you should have a new key file to put in the config folder on the flash drive. Until you get that sorted, you could always temporarily unplug the new drives that put you over the limit.
  5. Well, in that case it's not the unrar doing it, I got the same exact hang with the new container, which is why I started investigating. You said you included stable 5.6 in the test build, and when I saw 5.7 I assumed something didn't go right with the build.
  6. Yep, docker exec sh-5.0# unrar UNRAR 5.70 freeware Copyright (c) 1993-2019 Alexander Roshal sh-5.0# which unrar /usr/sbin/unrar
  7. Well, I pulled :test yesterday after you said it was built, but it's still using 5.7. Did I pull too early?
  8. While I've got everyone's attention, how do you find the nzbget version in the GUI? Settings about nzbget is useless for that purpose, system has an update button, but doesn't show the current version. I'm lazy and don't feel like googling, anybody know off the top of their head? Or do I have to read the log file to get the version?
  9. Dirt simple, hourly cron with docker restart binhex-nzbget Hopefully it won't be necessary any more though.
  10. Pulled and running, restart script disabled, I'll let you know. As I said, it's hard to force the issue, so we'll see.
  11. Honestly, I quit digging when I found out restarting solved my issue and didn't damage anything. I THINK it's the unpacking, but I can't be 100%. I suppose it could be the handoff between verifying / rebuilding par and unpacking.
  12. That's what is so maddening. It can work PERFECTLY for days, then sometimes it will hang several times in one day. Change some setting, think you fixed it, bang, it hangs. Change another setting, works great for a while, then it doesn't. Restarting the docker every hour ensures everything works smoothly, and I've never seen a restart munge a download, so it's a great solution if the real issue doesn't get handled. I've had mine on autorestart for several months now, time flies, it may be as much as a year.
  13. It will take me a few days, maybe a week of running with a test version, as the issue is hard to replicate. Do you want to use a special tag so it's not the :latest? Maybe use :test again?
  14. Since you are wanting multiple VM's plus a fair number of dockers, including plex, I'd recommend as much CPU as you can justify. A super cheap processor will probably function, but I don't think you would be happy under load. Hard to say exactly what is enough and what is overkill though, I've never heard anyone complain that their machine was too fast. (Not counting trying to play a CPU cycle locked game on a 368DX without a working turbo button)
  15. Regardless of whether it works for you or not, it's not good to use somebody else's IP addresses in your private network. It can make for some confusing troubleshooting, The 19.16.17.X block of addresses is owned by Ford Motor Company in the USA. I'd advise using blocks of addresses that are reserved for private use, the 192.168.X.X, 10.X.X.X, etc.
  16. Schedule this to run every hour or so in the user scripts plugin. #!/bin/bash docker restart binhex-nzbget
  17. Well, you are going to have to find some system that can read ufs and xfs at the same time, or temporarily stand up 2 boxes, one with nas4free and one with unraid.
  18. Unraid can be just a NAS if you want, pretty much as low or high powered as desired. There are people running everything from 2TB to 100's of TB. Depending on the hardware you run it on, it can host docker applications or virtual machines as well. What did you expect it to be when you first found it?
  19. Does the system used to create those UFS drives know how to write to XFS or BTRFS?
  20. Correct, as long as unraid knows it's full. You have to tell unraid how much free space to hold back to start passing new writes to the parity protected portion. Settings, global share settings, cache settings, min free space. As far as cache disk usage, it's different for different usage, so you will get a variety of opinions. If you are constantly filling the cache, you probably need to change your strategy.
  21. NO! Parity doesn't and can't restore individual files. it only restores the entire drive with the existing filesystem as is, even if there is corruption. If you change the requested filesystem type it will assume you want to erase the drive and put the new empty filesystem on it, and offer to format the drive. Parity will be updated to reflect the new empty filesystem, and all your files will be gone. If at any point you format a drive, all the contents will be gone.
  22. With the array as it is right now, can you start it and see the files on the emulated red ball disk and the rest of the array?
  23. Since you posted in the support area for a VERY old version of unraid, I'm guessing the quickest option would be to examine the syslog.
  24. A trial installation of unraid would be easier since you don't have to install it to a hard drive, just assign all disks as data disks, be very careful not to assign anything to the parity slots. Or, a standard linux mint install media has a live mode, but you would probably need to mount the disks manually. Maybe a more thorough explanation of what happened to your unraid install that necessitates a recovery might get better suggestions.
×
×
  • Create New...