OneWhippet

Members
  • Posts

    14
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

OneWhippet's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Cool. That got the two drives back online with the 3rd emulated. I'm running a backup now and will replace the failed drive tomorrow. Any recommendations on a controller card that won't break the bank. This is a small system that can hold a max of 6 drives.
  2. Logged in to the server this morning to find drive 3 failed and 1 & 2 showing Unmountable: No file system. Diagnostics zip attached. Any help would be appreciated. tower-diagnostics-20180601-0948.zip
  3. After the update, I'm getting the following error on the docker page: Fatal error: Cannot redeclare class DockerTemplates in /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php on line 48 ETA: all of my dockers are functioning.
  4. So, I updated recently to beta 8 and selected XFS for the array and btrfs for the cache drive. My question is, what file system is the parity drive using? I just checked and it doesn't give you the option to choose.
  5. Interesting. On the plus side, I'm getting an OK in the log. On the weird side, the IP address that duckdns updates to is not my IP address. I rebooted my modem to make sure I had a new IP address, an the docker and then ran update IP on the duckdns site. It shows a successful update but it's not my IP. I tried recreating the container with no change. I was going to try creating a new domain and then redoing the duck.conf file but, when when I created the new domain, the IP for my current domain updated also. It may have just been a weird delay on their side or who knows what. At the end of the day, everything seems to be working now. Many thanks and great work. Now I just need an openvpn server docker.
  6. Definitely not getting anything like that. I'm getting &ip=en=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxdomain.duckdns.org. It is showing my actual token and domain, just not with anything else or in the correct format. It's also not creating the log file now.
  7. Still no luck. I tried running Docker logs for the container but, nothing shows up. Here's my sys log but, I'm not sure what it's showing me. Sep 1 16:42:44 Tower php: DuckDNS Sep 1 16:42:44 Tower php: Sep 1 16:42:44 Tower avahi-daemon[2647]: Withdrawing workstation service for veth7cfa. Sep 1 16:42:44 Tower kernel: docker0: port 4(veth7cfa) entered disabled state Sep 1 16:42:44 Tower kernel: device veth7cfa left promiscuous mode Sep 1 16:42:44 Tower kernel: docker0: port 4(veth7cfa) entered disabled state Sep 1 16:43:13 Tower php: /usr/bin/docker start DuckDNS Sep 1 16:43:14 Tower kernel: device veth8d1e entered promiscuous mode Sep 1 16:43:14 Tower avahi-daemon[2647]: Withdrawing workstation service for veth16da. Sep 1 16:43:14 Tower kernel: docker0: port 4(veth8d1e) entered forwarding state Sep 1 16:43:14 Tower kernel: docker0: port 4(veth8d1e) entered forwarding state Sep 1 16:43:14 Tower php: DuckDNS Sep 1 16:43:14 Tower php:
  8. By duck.sh script, do you mean the duck.conf file? If not, where would I find the script? I just created a new domain and generated a new toke, updated the duck.conf file and restart the container with the same KO in the log.
  9. Getting the same thing. KO. It does not appear to be updating my IP. I rechecked my domain information mulitple times and it's all correct.