Unraid Crashing while starting array


Wuast94

Recommended Posts

My unraid server stops running after an online time about a few days. I didn't do anything with the server at this moment. 
unraid crashes and boots up, after I enter the encryption key and hitting start the server crashes again. 

so I did tail the log "tail -f /var/log/syslog" 
it runs to the point where the docker container boots up: 

Dec 19 04:00:09 Server kernel: docker0: port 19(vetha153c45) entered blocking state
Dec 19 04:00:09 Server kernel: docker0: port 19(vetha153c45) entered disabled state
Dec 19 04:00:09 Server kernel: device vetha153c45 entered promiscuous mode
Dec 19 04:00:09 Server kernel: IPv6: ADDRCONF(NETDEV_UP): vetha153c45: link is not ready
Dec 19 04:00:09 Server kernel: docker0: port 19(vetha153c45) entered blocking state
Dec 19 04:00:09 Server kernel: docker0: port 19(vetha153c45) entered forwarding state
Dec 19 04:00:09 Server kernel: docker0: port 19(vetha153c45) entered disabled state
Dec 19 04:00:10 Server kernel: eth0: renamed from veth3e07bc1
Dec 19 04:00:10 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth352a4a0: link becomes ready
Dec 19 04:00:10 Server kernel: docker0: port 16(veth352a4a0) entered blocking state
Dec 19 04:00:10 Server kernel: docker0: port 16(veth352a4a0) entered forwarding state
Dec 19 04:00:11 Server kernel: docker0: port 20(vethce2356b) entered blocking state
Dec 19 04:00:11 Server kernel: docker0: port 20(vethce2356b) entered disabled state
Dec 19 04:00:11 Server kernel: device vethce2356b entered promiscuous mode
Dec 19 04:00:11 Server kernel: IPv6: ADDRCONF(NETDEV_UP): vethce2356b: link is not ready
Dec 19 04:00:11 Server kernel: docker0: port 20(vethce2356b) entered blocking state
Dec 19 04:00:11 Server kernel: docker0: port 20(vethce2356b) entered forwarding state
Dec 19 04:00:11 Server kernel: docker0: port 20(vethce2356b) entered disabled state
Dec 19 04:00:11 Server kernel: eth0: renamed from veth5b5b5ea
Dec 19 04:00:11 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe941427: link becomes ready
Dec 19 04:00:11 Server kernel: docker0: port 17(vethe941427) entered blocking state
Dec 19 04:00:11 Server kernel: docker0: port 17(vethe941427) entered forwarding state
Dec 19 04:00:13 Server kernel: docker0: port 21(vethf34c5ce) entered blocking state
Dec 19 04:00:13 Server kernel: docker0: port 21(vethf34c5ce) entered disabled state
Dec 19 04:00:13 Server kernel: device vethf34c5ce entered promiscuous mode
Dec 19 04:00:13 Server kernel: IPv6: ADDRCONF(NETDEV_UP): vethf34c5ce: link is not ready
Dec 19 04:00:13 Server kernel: docker0: port 21(vethf34c5ce) entered blocking state
Dec 19 04:00:13 Server kernel: docker0: port 21(vethf34c5ce) entered forwarding state
Dec 19 04:00:13 Server kernel: docker0: port 21(vethf34c5ce) entered disabled state
Dec 19 04:00:13 Server kernel: eth0: renamed from veth0662c75
Dec 19 04:00:13 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth83fcb3f: link becomes ready
Dec 19 04:00:13 Server kernel: docker0: port 18(veth83fcb3f) entered blocking state
Dec 19 04:00:13 Server kernel: docker0: port 18(veth83fcb3f) entered forwarding state

and there it stops. i think its between the docker containers starting.. I have more containers booting up at start as I can count in this log file. 

is there any docker log I can look at or anything else where I can find this problem ? 

Link to comment

and here is the anonymized server diagnostics after booting and before try to bring the array online. 

server-diagnostics-20191219-0410.zip

 

EDIT: meanwhile I get error on disk 4 but this wasn't before and now when I start the array (hitting the checkbox that I want to start the array without disk 4) it starts without problems. so was the diening disk the issue ? 

Edited by Wuast94
Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.