unRAIDuser7

Bumping my own question.

unraid-api restart - is this something we run from the terminal? I have the same Graphql is offline and have no idea what it means, or how to fix it.

Hey quick question. DelugeVPN is up and running, without issues as far as I can tell, but the ICON is showing up as a ?. Clicking on it I have no option for the webui. I did a search for the it in CA which comes up and says it's installed. When I select actions 'edit' I get "CreateXML: XML file was missing" Anyone have any idea what the deal is? Still looking to know how I can get into the GUI or how to fix the error above.

I needed to use the unRAID creator tool 5 days ago, January 10 and received the same error message. How is this constantly being ignored...? “Unraid USB Creator.app” can’t be opened because Apple cannot check it for malicious software This software needs to be updated. Contact the developer for more information."

Noted. Thank you. Just seems strange that if you delete them in the configuration they still show up. Why even offer the option to delete them if they're not actually deleted.

Just migrated to this docker from hot.io. While setting up the docker I chose to remove all the unnecessary port mappings; 1900, 3005,32410 etc. I apply the settings, the docker is downloaded and setup. I go back to the docker tab, only to find out is has added/created all the port mappings I deleted. WHY!? Network type is HOST. How do I remove the unnecessary port mappings. I only require port 32400 for the webui.

Cheers thanks for the info.

As the title states, I have a recent error "Machine Check Events" as per Fix Common Problems. Attached is the diagnostics log, any assistance is appreciated. unraid-diagnostics-20210307-1401.zip

In the end, this is what I ended up doing, setting the permissions within sonarr/radarr itself. I don't understand why the UMASK variable doesn't work from within the docker settings. If it doesn't work, then why even have it in there?

UMASK value and files permissions incorrectly set, or at least I believe them to be. I originally had the Binhex version of Sonarr installed, but wanted to use v3, so I 'migrated' to the linuxserver version by changing the Repository value to linuxserver/sonarr:preview and hitting apply. This all worked without a hitch and all data was kept and everything worked as it should. I recently noticed that a lot of my file permissions on unRAID were set incorrectly, so I fixed all those using chmod and chown. After noticing this I set all relevant dockers; NZBGet, Radarr, NZBHydra and Sonarr to have the UID = 99, GID = 100 and UMASK = 002. Based on all the info I've read a mask value of 002 should give 664 for files -rw-rw-r--. However, after the file is imported by Sonarr and renamed, the file permissions keep showing up as 644, -rw-r--r--. I did notice that the Binhex version of Sonarr has the UMASK key value as "UMASK", where this version is "UMASK_SET". I have since modified this, reloaded the docker, but the files keep showing up with -rw-r--r--. My last ditch effort would be to completely remove Sonarr, install it again, and start over to see if this fixes the issue. I figured I might as well ask here 1st to see if anyone has any input as to why this would occur. I looked at the file through the terminal, while it was still in NZBGet and the file permissions are what they should be -rw-rw-r--. Anyone have any ideas?

This worked for me as well. Thank you.

Confirmed that changing both the PGID and PUID to 0, I can actually see the drive now. I have other issues now - Error 'Scsi error - HARDWARE ERROR: TIMEOUT ON LOGICAL UNIT' occurred while reading 'BD-RE HL-DT-ST BD-RE WH16NS40 1.02' at offset '1048576'

I never received a reply on either of my two posts, just above yours. It doesn't seem too promising that you'll get a reply.

Have been running nzbgetvpn since my last post above, May 21, without issue. I have however noticed that log is continually being written to every few seconds with junk, see below. 8:42:31,062 DEBG 'start-script' stdout output: R 2020-05-28 18:42:32,258 DEBG 'start-script' stdout output: W 2020-05-28 18:42:33,022 DEBG 'start-script' stdout output: rW 2020-05-28 18:42:36,097 DEBG 'start-script' stdout output: R 2020-05-28 18:42:38,191 DEBG 'start-script' stdout output: rW Does anyone know why this is happening? I have DEBUG set to false No, nothing is being downloaded. I have the console set where it DOES NOT automatically refresh. I just changed the 'writelog' to rotate as it's already created 6 log files today, all are 10.5 MB each. Would really like to know why this is happening!

Good to know. I just assumed it was 2 for each. I don't know that I'd ever need more than 2 for cache, but either way, thanks for the info.

I have a couple of questions as I'm looking to move to this container over the sabnzbvpn one. **I figured it out myself - see bottom of this post** 1. Will this essentially operate the same way sabnzbvpn does, where I can route sonarr/radarr/nzbhydra via proxy out the nzbgetvpn container? 2. Page 1 of this topic states that you need the following servers installed and running for nzbgetvpn to work. [*]Redis [*]Postgresql Why is that, do they just allow nzbget to work over VPN? Asking as sab didn't require any additional components. 3. On the dockerhub page for nzbgetvpn it show the following options for installation, more specifically those highlighted in yellow. However, when I install nzbgetvpn from CA, *without Redis & Postgresql installed, I have no options for those highlighted in yellow above. Even after selecting 'advanced view'. Am I supposed to be creating these variables myself? I assumed installing this would have been the same/similar as sabvpn, modify/add some variables and change any required locations and we're set. So far, it doesn't appear to be that way, at least not for me. If anyone can answer or provide any information that would be greatly appreciated. ============================================================================================================ ============================================================================================================ ****** The docker nzbgetvpn works the same as sabnzbdvpn, at least it seems to be working the same for me. I did not need Redis or Postgresql to get this working. I added all the variables that were highlighted in the first picture. I also had to add Host Port 2, with a value of 8118, which is the port that Privoxy uses. Since a picture says a 1000 words, here's what my config looks like, VPN user/pass info removed. I also removed keys 5 and 6 as I didn't need them for this to work.

"I will be getting 4 970 EVO Plus M.2 drives that will be Raid 0 for a Cache drive" Unless I'm missing something, you can only use 2 drives for cache in unRAID.

Does anyone know if you can run preclear on a different system, then put it in another system and it know that a preclear has already been run? I'm asking as my unRAID server only has USB 2.0, which is PAINFULLY slow. Bought an 8TB MyBook and hooked it up to my server, currently running a preclear on it. It's been running for 5 hours and it's only at 7% of the pre-read EEKS. Would it be possible to throw unRAID on a USB key, boot from it on my main PC, which has USB 3.0, run a preclear on it to make sure it's all good, shuck it, then throw it in my server. Would the unRAID server know it has already been precleared? I don't know if something is written to the drive itself to indicate that it's been run. Thanks for any info.

Been following this thread as I believe I'm also having the issue. Just wanted to list what I've come across in the off chance this is of any use to anyone else. I stopped all the dockers containers leaving docker still enabled like @nas_nerd did. There were no writes of any sort to the cache drive overnight while all the docker containers were stopped. Docker Containers binhex nzbHydra2 binhex plexpass binhex radarr binhex sonarr binhex sabnzbdvpn Process I followed I rebooted unraid, after all the dockers above were up and running (as I forgot I had them set to auto-start), I had around 30,000 writes to cache. I stopped them all one-by-one, and the writes stopped around 39,000. All docker containers were stopped overnight and no writes occurred. The next morning I enabled the dockers listed above, ~ 44 hours ago, and I'm now sitting at 1,220,283 writes. My next step is to stop all docker containers, disable auto-start, reboot unraid, then enable one docker at a time (without actually using them) and monitor the number of writes to the cache to see if I can find an offending docker container.