Gursh Posted January 8, 2020 Share Posted January 8, 2020 Hi all, I recently rebooted my system and normally it it reboots and i can login to the server again. This time, the server took so long to reboot I have to manually do hold the power button and restart it. It does the same for shutdown. Is this normal? after restart here is the log, I don't see any errors, just wondering if i need to fix something for reboots and shutdowns to happen normally. Also not sure if this is the right log lol as I'm new to unraid, let me know where to get the right one and i can post it. Thanks in advance. Jan 8 12:08:37 AulakhHome kernel: docker0: port 5(veth93823ed) entered blocking state Jan 8 12:08:37 AulakhHome kernel: docker0: port 5(veth93823ed) entered disabled state Jan 8 12:08:37 AulakhHome kernel: device veth93823ed entered promiscuous mode Jan 8 12:08:37 AulakhHome kernel: IPv6: ADDRCONF(NETDEV_UP): veth93823ed: link is not ready Jan 8 12:08:37 AulakhHome kernel: docker0: port 5(veth93823ed) entered blocking state Jan 8 12:08:37 AulakhHome kernel: docker0: port 5(veth93823ed) entered forwarding state Jan 8 12:08:38 AulakhHome kernel: eth0: renamed from veth88dd2d3 Jan 8 12:08:38 AulakhHome kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth93823ed: link becomes ready Jan 8 12:08:38 AulakhHome rc.docker: sonarr: started succesfully! Jan 8 12:08:38 AulakhHome kernel: docker0: port 6(veth252811d) entered blocking state Jan 8 12:08:38 AulakhHome kernel: docker0: port 6(veth252811d) entered disabled state Jan 8 12:08:38 AulakhHome kernel: device veth252811d entered promiscuous mode Jan 8 12:08:38 AulakhHome kernel: IPv6: ADDRCONF(NETDEV_UP): veth252811d: link is not ready Jan 8 12:08:38 AulakhHome kernel: docker0: port 6(veth252811d) entered blocking state Jan 8 12:08:38 AulakhHome kernel: docker0: port 6(veth252811d) entered forwarding state Jan 8 12:08:38 AulakhHome kernel: docker0: port 6(veth252811d) entered disabled state Jan 8 12:08:38 AulakhHome avahi-daemon[3877]: Joining mDNS multicast group on interface veth2322a5e.IPv6 with address fe80::10b6:1bff:feb1:70ed. Jan 8 12:08:38 AulakhHome avahi-daemon[3877]: New relevant interface veth2322a5e.IPv6 for mDNS. Jan 8 12:08:38 AulakhHome avahi-daemon[3877]: Registering new address record for fe80::10b6:1bff:feb1:70ed on veth2322a5e.*. Jan 8 12:08:38 AulakhHome kernel: eth0: renamed from vethdb98e42 Jan 8 12:08:38 AulakhHome kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth252811d: link becomes ready Jan 8 12:08:38 AulakhHome kernel: docker0: port 6(veth252811d) entered blocking state Jan 8 12:08:38 AulakhHome kernel: docker0: port 6(veth252811d) entered forwarding state Jan 8 12:08:38 AulakhHome rc.docker: tautulli: started succesfully! Jan 8 12:08:39 AulakhHome avahi-daemon[3877]: Joining mDNS multicast group on interface veth93823ed.IPv6 with address fe80::d0ed:e5ff:feb8:bc28. Jan 8 12:08:39 AulakhHome avahi-daemon[3877]: New relevant interface veth93823ed.IPv6 for mDNS. Jan 8 12:08:39 AulakhHome avahi-daemon[3877]: Registering new address record for fe80::d0ed:e5ff:feb8:bc28 on veth93823ed.*. Jan 8 12:08:39 AulakhHome avahi-daemon[3877]: Joining mDNS multicast group on interface vethc26062b.IPv6 with address fe80::1437:e7ff:fe04:aee0. Jan 8 12:08:39 AulakhHome avahi-daemon[3877]: New relevant interface vethc26062b.IPv6 for mDNS. Jan 8 12:08:39 AulakhHome avahi-daemon[3877]: Registering new address record for fe80::1437:e7ff:fe04:aee0 on vethc26062b.*. Jan 8 12:08:40 AulakhHome avahi-daemon[3877]: Joining mDNS multicast group on interface veth252811d.IPv6 with address fe80::147f:a7ff:fe3c:ae92. Jan 8 12:08:40 AulakhHome avahi-daemon[3877]: New relevant interface veth252811d.IPv6 for mDNS. Jan 8 12:08:40 AulakhHome avahi-daemon[3877]: Registering new address record for fe80::147f:a7ff:fe3c:ae92 on veth252811d.*. Jan 8 12:08:44 AulakhHome kernel: tun: Universal TUN/TAP device driver, 1.6 Quote Link to comment
Gursh Posted January 9, 2020 Author Share Posted January 9, 2020 See the attached below. syslog.txt Quote Link to comment
testdasi Posted January 9, 2020 Share Posted January 9, 2020 You need to enable syslog server (in the settings) to save it your flash. That would allow you obtain log cross-boot. Your post-reboot log is pretty useless as any issue was logged in the pre-reboot. 1 Quote Link to comment
Gursh Posted January 9, 2020 Author Share Posted January 9, 2020 Sounds good, ill set that up and post it when I have the chance this week. Thanks! Quote Link to comment
Gursh Posted January 11, 2020 Author Share Posted January 11, 2020 So I did a shutdown and restart and it worked fine this time, I think it has something to do with the parity check. Anyways would love your thoughts as well. Thanks in advance!🙏 syslog.txt Quote Link to comment
trurl Posted January 11, 2020 Share Posted January 11, 2020 Just thought I would mention Diagnostics, since you're new and it wasn't mentioned in the thread. Tools - Diagnostics will let you download a zip file which contains many of your settings, SMART for all attached disks, syslog (since last boot), information about your shares, the results from running some simple commands, and other things which give a much more complete understanding of your situation. We usually prefer diagnostics instead of only syslog, but in cases of crash, it can also be useful to have syslogs from before reboot. And since diagnostics won't have those syslogs, Syslog Server is needed to get those for us. 1 Quote Link to comment
Gursh Posted January 11, 2020 Author Share Posted January 11, 2020 I have attached it below. Thanks for all the help guys aulakhhome-diagnostics-20200111-1333.zip Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.