Jump to content

roppy84

Members
  • Content Count

    25
  • Joined

  • Last visited

Community Reputation

0 Neutral

About roppy84

  • Rank
    Member

Converted

  • Gender
    Male
  • Location
    AZ
  • Personal Text
    Complete Noob
  1. I have done what was suggested but still getting " Docker Service Failed to Start" . I have attached a new Log this should show from when I turned on my server to when I disabled docker service and deleted Image file. I am still seeing the error message in my logs but I don't know what it means Nov 20 07:18:38 Unraid kernel: BTRFS critical (device sdc1): corrupt node: root=7 block=787021824 slot=233, bad key order, current (18446744073709551606 128 28971700224) next (18446744073709551606 128 20387368960) unraid-diagnostics-20191120-1419.zip
  2. Can I delete my docker image through SMB on my window computer or am I going to run into permission issues? Sent from my Pixel 3 XL using Tapatalk
  3. Here is the Diagnostic file. sorry for the delay. unraid-diagnostics-20191116-1821.zip
  4. My Emby docker stopped working in the middle of me using is so I turned it off and tried to restart but I go an "Error 403", So I proceeded to safely shut down my server and reboot. Once it was back online all my dockers were gone for the main screen and under dockers I got a message "Docker Services Failed to Start". Looking at my logs I keep seeing "Unraid kernel: BTRFS critical (device sde1): corrupt node: root=7 block=787021824 slot=233, bad key order, current (18446744073709551606 128 28971700224) next (18446744073709551606 128 20387368960)"
  5. Thank you for your help I am back up and running.
  6. Please confirm if that is correct. I already have CA/Appdata Back running once a week so I should be good there when it comes to restoring my appdata correct. Now I took the server offline and unmounted my cache drive and then remounted it. When I start the array up I get this do I check the format box and format???
  7. Okay, How do I back up Cashe File, Reformat and Restore? Can/should you back up Cashe drive if the file system is corrupt. Sorry for the dumb question but everything I know is from watching YouTube videos.
  8. sorry that was an old one that I had. I don't know what is going on. When I try pull up a docker web UI I get servier error or servier erroe 403. I have tried to delete my dockers but that does not work. unraid-diagnostics-20190421-1932.zip
  9. I have been using the same system to 3 years now with no issues. Today I am not able to use any on my dockers. I have tried shut down and restart, restoring most resent app data backup, I tried deleting my dockers but get an execution error. I am at a loss. unraid-diagnostics-20181004-0713.zip
  10. @H20_King89 My Have not touched my temples since I set up the docker years ago. I only messed with the version variable this morning as a last resort
  11. Having an issue with my Plex Docker I hope I can get some help with. My symptom is I am unable to reach Plex through the WebUi however I am able to play videos from my Plex Clients both on my network and remote. Here is what I have done myself to resolve it. 1. Shutdown and restarted the docker 2. Force update docker 3. run fix common problem (nothing came up) 4. edited version variable from "latest" to "public" Nothing as worked, I have been running the same docker on my unraid server for a few years now with no issues. I am currently running version 6.5.3 on unraid. here are my logs. Thank you for your help. () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-dbus: executing... [cont-init.d] 30-dbus: exited 0. [cont-init.d] 40-chown-files: executing... chown: cannot dereference '/config/cache-1a98c3a17a08': No such file or directory chown: cannot dereference '/config/cache-41fb74ecd2bd': No such file or directory chown: cannot dereference '/config/cache-4709c844cb0b': No such file or directory chown: cannot dereference '/config/cache-6c6bcc225956': No such file or directory chown: cannot dereference '/config/cache-6fa6032cb0a0': No such file or directory chown: cannot dereference '/config/cache-7294e2131caa': No such file or directory chown: cannot dereference '/config/cache-8a1a21a84351': No such file or directory chown: cannot dereference '/config/cache-98fd69812c98': No such file or directory chown: cannot dereference '/config/cache-9b3fd7de629c': No such file or directory chown: cannot dereference '/config/cache-a3457bb92419': No such file or directory chown: cannot dereference '/config/socket-1a98c3a17a08': No such file or directory chown: cannot dereference '/config/socket-41fb74ecd2bd': No such file or directory chown: cannot dereference '/config/socket-4709c844cb0b': No such file or directory chown: cannot dereference '/config/socket-6c6bcc225956': No such file or directory chown: cannot dereference '/config/socket-6fa6032cb0a0': No such file or directory chown: cannot dereference '/config/socket-7294e2131caa': No such file or directory chown: cannot dereference '/config/socket-8a1a21a84351': No such file or directory chown: cannot dereference '/config/socket-98fd69812c98': No such file or directory chown: cannot dereference '/config/socket-9b3fd7de629c': No such file or directory chown: cannot dereference '/config/socket-a3457bb92419': No such file or directory chown: cannot dereference '/config/tmp-1a98c3a17a08': No such file or directory chown: cannot dereference '/config/tmp-41fb74ecd2bd': No such file or directory chown: cannot dereference '/config/tmp-4709c844cb0b': No such file or directory chown: cannot dereference '/config/tmp-6c6bcc225956': No such file or directory chown: cannot dereference '/config/tmp-6fa6032cb0a0': No such file or directory chown: cannot dereference '/config/tmp-7294e2131caa': No such file or directory chown: cannot dereference '/config/tmp-8a1a21a84351': No such file or directory chown: cannot dereference '/config/tmp-98fd69812c98': No such file or directory chown: cannot dereference '/config/tmp-9b3fd7de629c': No such file or directory chown: cannot dereference '/config/tmp-a3457bb92419': No such file or directory [cont-init.d] 40-chown-files: exited 1. [cont-init.d] 50-plex-update: executing... No update required [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting dbus-daemon Starting Plex Media Server. [services.d] done. Starting Avahi daemon Found user 'avahi' (UID 102) and group 'avahi' (GID 103). Successfully dropped root privileges. avahi-daemon 0.7 starting up. No service file found in /etc/avahi/services. *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** *** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** Joining mDNS multicast group on interface vethee15877.IPv6 with address fe80::a82a:15ff:fea9:1fe1. New relevant interface vethee15877.IPv6 for mDNS. Joining mDNS multicast group on interface vethc169f23.IPv6 with address fe80::a8b0:14ff:fe50:1e64. New relevant interface vethc169f23.IPv6 for mDNS. Joining mDNS multicast group on interface veth2e5d3ce.IPv6 with address fe80::745e:9eff:fe3c:add8. New relevant interface veth2e5d3ce.IPv6 for mDNS. Joining mDNS multicast group on interface veth2cedc4a.IPv6 with address fe80::5434:9fff:fedc:2745. New relevant interface veth2cedc4a.IPv6 for mDNS. Joining mDNS multicast group on interface veth29bf380.IPv6 with address fe80::b47d:64ff:fe4c:11a9. New relevant interface veth29bf380.IPv6 for mDNS. Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:98ff:fe6e:6da6. New relevant interface docker0.IPv6 for mDNS. Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. New relevant interface docker0.IPv4 for mDNS. Joining mDNS multicast group on interface br0.IPv6 with address fe80::50a5:b4ff:fe57:a822. New relevant interface br0.IPv6 for mDNS. Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.13. New relevant interface br0.IPv4 for mDNS. Joining mDNS multicast group on interface eth0.IPv6 with address fe80::6ef0:49ff:fe09:c643. New relevant interface eth0.IPv6 for mDNS. Joining mDNS multicast group on interface lo.IPv6 with address ::1. New relevant interface lo.IPv6 for mDNS. Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. New relevant interface lo.IPv4 for mDNS. Network interface enumeration completed. Registering new address record for fe80::a82a:15ff:fea9:1fe1 on vethee15877.*. Registering new address record for fe80::a8b0:14ff:fe50:1e64 on vethc169f23.*. Registering new address record for fe80::745e:9eff:fe3c:add8 on veth2e5d3ce.*. Registering new address record for fe80::5434:9fff:fedc:2745 on veth2cedc4a.*. Registering new address record for fe80::b47d:64ff:fe4c:11a9 on veth29bf380.*. Registering new address record for fe80::42:98ff:fe6e:6da6 on docker0.*. Registering new address record for 172.17.0.1 on docker0.IPv4. Registering new address record for fe80::50a5:b4ff:fe57:a822 on br0.*. Registering new address record for 192.168.1.13 on br0.IPv4. Registering new address record for fe80::6ef0:49ff:fe09:c643 on eth0.*. Registering new address record for ::1 on lo.*. Registering new address record for 127.0.0.1 on lo.IPv4. Server startup complete. Host name is Unraid.local. Local service cookie is 586039704. unraid-diagnostics-20181004-0713.zip
  12. I did as well, I hope it is okay for me to post on this thread since we have the same thing. unraid-diagnostics-20170418-0808.zip
  13. Does this help or show anything? unraid-diagnostics-20170131-0820.zip
  14. Can someone tell me what happened to my server while I was at work... I came home to find my server on but not started. I will attach my log for someone much smarter then me to decipher. I added an APC to my server a few weeks ago because I was having random power outages. The display on the the APC says there were no events, I'm at a lost. The only other thing I did a few days ago was change some settings over to auto update my docker and plugins. Thanks in advance for the help unraid-syslog-20170130-1746.zip