Urban

Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

5 Neutral

About Urban

  • Rank
    Newbie
  1. I finally got around to fixing Sonarr and Radarr after the recent iptables update. However I'm still having trouble getting the FireFox extension Torrent Control (similar to delugesiphon on chrome) to work anymore. I'm using it on my normal desktop computer with a DHCP assigned IP address without a port number so I cant just add the port to the "VPN_INPUT_PORTS" variable in the template like I did for the others. Do I need to change the deluge server address setting in the extension on top of any other changes in the template?
  2. Yes this has been the case from at least 6.8 through to the current 6.9.1. If you change the network type to "none" and then add "--net=container:<ContainerName>" to extra parameters in order to route it though a different container it removes the "WebUI" option from the context menu. Everything else works fine but its just incredibly annoying accessing containers setup this way.
  3. There's a small typo in the description after the recent name change. Instead of "Tandoor" it says "Tanmdoor". Obviously not a big deal but thought id let you know.
  4. There is two posts here explaining how to it with FreeNAS but I have no experience to know how to translate it to Unraid. I also feel like simply disabling NFS based logs would work as well if that is possible. https://forum.proxmox.com/threads/iscsi-reconnecting-every-10-seconds-to-freenas-solution.21205/post-247628
  5. Anybody have any experience with this?
  6. I found an old thread where a Proxmox dev stated "Hi Every 10s seconds, we check the status of the NFS server with 'showmount' and then gather statistics about disk usage *if* 'showmount' successfull. We need to report early if a NFS server is down, hence the regular check.". There doesn't seem to be an easy toggle or anything. I see some later threads about the issue with workarounds for FreeNAS. Ill see if I can gather info from those and apply it to Unraid. If that fails is there a command I can use on Unraid to disable all logs related to NFS?
  7. There probally is but this is the one that will be getting all the support from the devs so I dont suggest it personally.
  8. Until now Ive been using SMB on windows but i've recently made the switch to Linux and I can't seem to get NFS to work correctly on this machine. I had a single NFS share setup before for a different machine and that one worked correctly so I understand this might not be an Unraid issue but when asking for support from in other places I was told its most likely a permissions issue with my server. The problem is If I just use my Unraid IP I only see the "mnt" folder and if I try clicking on it I get "invalid protocol". If I specify the path using "nfs://"ServerIP/mnt/" then I can s
  9. While diagnosing a separate issue a helpful moderator on here noticed that my logs were being spammed. Looking at them I know exactly what is causing it. I have set up my Unraid server to be used as external backup for a Proxmox server I'm using to separate some services on different hardware. I created a dedicated share on Unraid and pointed Proxmox to that share and everything has been working correctly but unknowingly this has been spamming my logs and I can't figure out why. If I disable the connection on Proxmox the log spam stops. Any idea why this is happening and how I can stop it?
  10. After a reboot the drive showed no errors and I have run a second parity check it it has come back clean as well. I guess theres nothing to do now but to monitor it like you said. The log spam seems to come from the fact I have a NFS share mouted to a proxmox machine for backups, can you point me in the right direction for how I can fix that?
  11. I recived an error after a parity check telling me I have 128 read errors on a drive but once the parity check finished it said completed without error. I assume what it means is parity is still vallid but one of my data drives has issues? However I can seem to see what the problem is. I ran an extended SMART test on the drive in question and it came back clean. No Reallocated sectors or pending sectors. Im very new to this so Im probally missing something. Can anybody tell me the the problem and where I should go from here? I have a attached my diagnosics file below. tower-di
  12. I recently setup a new pfSense box which involved me bridging my modem and changing the IP range from 192.168.x.x to 10.0.x.x. Once that was done UnRaid picked up a new DHCP IP address as expected and I was able to connect to the machine no problem however after I set up a new static IP for UnRaid on pfSense I seem to be having an issue. I can still access the WebGUI with the new static IP I setup no problem but when I try and access any of my containers using the WEBGUI it tries to connect to the IP address at it was auto assigned by pfSense using DHCP. If I manually input the IP and port I c
  13. I remember this being a setting when installing unraid but I cant find it now that its installed, do you happen to remember how you did this?