• Posts

  • Joined

  • Last visited

Everything posted by The_Mountain

  1. It somehow fixed itself after running for 10 min or so and killing all the old connections off. Strange, but at least its working now
  2. I updated to the latest release and getting the container unable to start up. Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ 2021-10-21 10:45:45.221305 [info] Host is running unRAID 2021-10-21 10:45:45.249269 [info] System information Linux Tower 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux 2021-10-21 10:45:45.283320 [info] OS_ARCH defined as 'x86-64' 2021-10-21 10:45:45.315574 [info] PUID defined as '99' 2021-10-21 10:45:45.373661 [info] PGID defined as '100' 2021-10-21 10:45:45.450751 [info] UMASK defined as '022' 2021-10-21 10:45:45.480493 [info] Permissions already set for '/config' 2021-10-21 10:45:45.520571 [info] Deleting files in /tmp (non recursive)... 2021-10-21 10:45:45.555228 [warn] TRANS_DIR not defined,(via -e TRANS_DIR), defaulting to '/config/tmp' 2021-10-21 10:45:45.629444 [info] Starting Supervisor... 2021-10-21 10:45:45,924 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2021-10-21 10:45:45,924 INFO Set uid to user 0 succeeded 2021-10-21 10:45:45,927 INFO supervisord started with pid 7 2021-10-21 10:45:46,930 INFO spawned: 'plexmediaserver' with pid 71 2021-10-21 10:45:46,932 INFO spawned: 'shutdown-script' with pid 72 2021-10-21 10:45:46,932 INFO reaped unknown pid 8 (exit status 0) 2021-10-21 10:45:47,932 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-10-21 10:45:47,933 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) I made no changes to the config files just simply updated to latest release.
  3. Clicked on update OS as well as Update Assistant and there is no update showing.
  4. Will there be other options besides raid1? raid0? raid10? FYI, I am excited for the new changes and TYVM for the replies.
  5. Am I correct in assuming these pools will NOT have parity support like the current array does?
  6. 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.
  7. 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?
  8. 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.
  9. i disabled my ipv6 on my controller and then restarted avahi-daemon and restarted docker service, and i have not seen the error since.
  10. 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
  11. 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.
  12. Here is my diagnostics.
  13. Looking back at my logs, i am seeing it started on July 4th just before 2AM for me.
  14. Is there any reason i would not see an update available for the container when i am several versions back
  15. I am loving the new black theme.