quietas

Members
  • Posts

    20
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

quietas's Achievements

Noob

Noob (1/14)

0

Reputation

  1. It's definitely using one of my shares rather than a folder inside the docker. I'll have to look into docker directories. I've seen them mentioned a few times but the docker image has been around for many years with this Unraid system and I have yet to change it.
  2. I've been using auto-m4b bit and it works well enough, but I notice is it is one the biggest containers in docker.img. Any idea how this can be reduced? Name Container Writable Log auto-m4b 5.67 GB 4.51 GB 20.9 MB AMP 5.42 GB 759 MB 120 kB calibre 2.26 GB 327 kB 4.31 kB calibre-web 1.50 GB 746 MB 56.8 kB binhex-prowlarr 1.44 GB 219 MB 129 kB qbittorrent-vpn 1.34 GB 1.16 MB 7.58 MB Krusader 1.11 GB 3.12 MB 67.5 kB unifi-controller 756 MB 340 kB 36.0 kB audiobookshelf 626 MB 0 B 2.95 kB Foundry 422 MB 216 MB 65.6 kB plex 340 MB 46.8 kB 4.41 kB nzbget 208 MB 27.9 MB 24.3 MB tautulli 204 MB 2.66 kB 2.55 MB sonarr 195 MB 23.7 kB 149 kB Kitana 179 MB 619 kB 24.6 kB Tailscale 73.8 MB 209 B 792 kB Total size 21.7 GB 6.48 GB 56.8 MB
  3. I've been using auto-m4b bit and it works well enough, but I notice is it is the biggest container in docker.img. Any idea how this can easily be reduced? Name Container Writable Log auto-m4b 5.67 GB 4.51 GB 20.9 MB AMP 5.42 GB 759 MB 120 kB calibre 2.26 GB 327 kB 4.31 kB calibre-web 1.50 GB 746 MB 56.8 kB binhex-prowlarr 1.44 GB 219 MB 129 kB qbittorrent-vpn 1.34 GB 1.16 MB 7.58 MB Krusader 1.11 GB 3.12 MB 67.5 kB unifi-controller 756 MB 340 kB 36.0 kB audiobookshelf 626 MB 0 B 2.95 kB Foundry 422 MB 216 MB 65.6 kB plex 340 MB 46.8 kB 4.41 kB nzbget 208 MB 27.9 MB 24.3 MB tautulli 204 MB 2.66 kB 2.55 MB sonarr 195 MB 23.7 kB 149 kB Kitana 179 MB 619 kB 24.6 kB Tailscale 73.8 MB 209 B 792 kB Total size 21.7 GB 6.48 GB 56.8 MB
  4. Update: No changes have been made to hardware or settings, but this morning I checked on the server and it was not pingable. I still had the monitor up and I was able to log in. I could not ping anything which is weird but networking was all there and the port was up. Here's the updated syslog. syslog-192.168.42.15.log
  5. Yesterday Plex had two scanning processes lock up and would not continue for hours. I tried stopping the container but it would not stop. I decided to restart unRAID so I killed the Plex process and closed the open files. The array would not stop and kept retrying. Eventually I restarted, everything came up OK. I just checked a few minutes ago and it appears the server rebooted on it's own about an hour and 45 minutes ago. Previously the server had been rebooting on it's own for about a week but then stopped. I attached the syslog. syslog-192.168.42.15.log
  6. Recently my unRAID system has been dropping off the network and I am not sure why. Hard reboot does work, but powering it off and then running through parity check every couple of days is not good. This morning it was offline after being up for the last 3 days no problems. I can't ping the IP, manually assigned, outside of DHCP range. The web page, shares, and all dockers are offline. I checked the server monitor (normally headless) I have plugged in I see a normal login prompt. I tried root and my password but it does not login. I hard reset the server and it came right up. Parity is running again. The hardware is a previous gaming system from a couple upgrades ago and it's been running unRAID for years now. I'm suspecting hardware, but how do I track down the failure with unRAID? I attached the diagnostics from after the reboot. Also after reboot I could log into the CLI. Any ideas for what to look at? tower-diagnostics-20230320-1103.zip
  7. I found this post from a couple years back. It talked about avahi and how to disable it. I did not have a /boot/config/share.cfg so I made one and added shareAvahiEnabled="no" as the only thing in it. This seems to work once I rebooted the server. https://forums.unraid.net/topic/91825-dns-servers-not-retained-in-resolvconf-on-unraid-reboot/ Is this correct and will it break anything in the long run other than not using Apples Bonjour/Avahi stuff that I don't use anyway? If anyone is looking at this in the future, this is what I did. nano /boot/config/share.cfg shareAvahiEnabled="no" <ctrl-x> <enter>
  8. On a side note, I see lots of posts with similar issues but no solutions. Why people? I hate it when people post a problem and don't come back to post what worked in the end.
  9. DNS on my unRAID system has stopped working completely. My array, SMB, docker containers, VMs, everything else works fine except things like Plex which need DNS to function. I can ping IP addresses inside and outside, but I can not ping any named address. I used to have Pi-Hole installed, but I saw many people had problems with it so I removed that container. While it was installed, and currently, I have been using 9.9.9.9, 8.8.8.8, and 1.1.1.1 as the DNS which had been working just fine until last week. I have changed the DNS to static, I have also set the IP to DHCP and neither are working. I have also set the DNS to my router (USG4Pro) with no luck. The unRAID server has been rebooted multiple times. Currently the VMs and Docker are off. The only thing I see as major problem is that /etc/resolv.conf is empty, completely blank. If I add in the nameservers everything works fine until I reboot of course. Also /boot/config/network.cfg looks fine and has the nameservers listed. Another thing I notice is that /etc/resolv.avahi.conf is populated correctly. Any ideas? tower-diagnostics-20220210-0655.zip
  10. I don't think that is it, I haven't had any failed logins. I checked the pwfail folder and it's empty. I tried changing the IP it still did not let me in. I thought something might be blocking the MAC address rather than IP, so I changed the MAC address and still had no luck getting the web gui to load.
  11. So my normal daily driver laptop seems to have one NIC blocked from accessing any of the web pages, GUI and dockers. The built in NIC works fine, so does the wireless, but the Dell WD19TB dock ethernet is not able to access unRAID anymore. Chrome just spins and spins. My other computers in the house seem to be fine, same with the phones. It's just this specific NIC on this one computer which has stopped being able to open any web pages on the unRAID box. I've swapped cables, changed routers, changed switches, changed IPs. The only thing that works for this computer is to move the Ethernet cable to the onboard NIC or use wifi. Any ideas?
  12. Let me rephrase. I understand that this docker is just repackaging the released files from Ubiquiti. This support thread has many people saying current 6.x versions are unstable, not to use them, and to stick with 5.x or 5.y... The second post says not to use the :latest tag as it is often broken or buggy. I wanted to know if there is an accepted version 6.0.34 or greater which is considered stable enough to be used? I ask because I used a Cloud Key Gen2 with the current firmware and seemingly had no issues. Not a huge amount of time on it, but it seemed to work fine.
  13. Will this be updated to be stable enough to work with the new v6 needed for the Unifi 6 lite?
  14. Good to know. I did that and it works just as you said. I just created a couple and I see that it fixes the permissions.