Jump to content

The_Mountain

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About The_Mountain

  • Rank
    Member

Converted

  • Gender
    Undisclosed
  1. Will there be other options besides raid1? raid0? raid10? FYI, I am excited for the new changes and TYVM for the replies.
  2. Am I correct in assuming these pools will NOT have parity support like the current array does?
  3. I love the flexibility in being able to grow my storage as my needs change over time. I have been loving unraid for over 3 years now and share my knowledge with others as best i can. I would love the ability to have multiple disk arrays allowing for the use of more than the 30 disk limitation with the current array.
  4. Does anyone have a breakdown on the different remote tunnel types? Like the differences and limitations of each type and why or when you would want one over the other?
  5. I was doing some disk testing as well to see if there was anything similar on my system. disk speed tests When i tested a speed test on my unassigned appdata disk, my system froze and crashed. It appears to have kernel panicked and I attempted to pull diagnostics prior to a reboot, but was not successful. kernel panic failed diagnostics attempt I attempted a graceful reboot, but that hung as well and was forced to reset the machine.
  6. i disabled my ipv6 on my controller and then restarted avahi-daemon and restarted docker service, and i have not seen the error since.
  7. Looking back at my syslog, and it first appeared right after loading avahi-daemon. Jul 4 06:22:17 Tower kernel: docker0: port 6(veth7d57666) entered forwarding state Jul 4 06:22:18 Tower avahi-daemon[22640]: Joining mDNS multicast group on interface veth7d57666.IPv6 with address fe80::682c:f0ff:fe8f:7f06. Jul 4 06:22:18 Tower avahi-daemon[22640]: New relevant interface veth7d57666.IPv6 for mDNS. Jul 4 06:22:18 Tower avahi-daemon[22640]: Registering new address record for fe80::682c:f0ff:fe8f:7f06 on veth7d57666.*. Jul 4 11:47:45 Tower root: error: /gcsp/2.0: missing csrf_token Jul 4 11:47:45 Tower root: error: /gcsp/2.0: missing csrf_token Jul 4 11:47:45 Tower root: error: /gcsp/2.0: missing csrf_token
  8. Being that this did not start until July 4th for me, makes me believe this is probably related to one of my docker containers, rather than the OS it self. Server has been up since the end of June but this did not start until 4-5 days later.
  9. tower-diagnostics-20190712-0658.zip Here is my diagnostics.
  10. Looking back at my logs, i am seeing it started on July 4th just before 2AM for me.
  11. Is there any reason i would not see an update available for the container when i am several versions back