binghunlong Posted June 30, 2022 Share Posted June 30, 2022 My unraid server suddenly became inaccessible and had to be restarted manually. I would like to know if it is a hardware problem or a software problem? This is the second time this has happened and I have no clue about it. tower-diagnostics-20220630-1011.zip Quote Link to comment
itimpi Posted June 30, 2022 Share Posted June 30, 2022 The problem is that the logs in the diagnostics only show what has happened since you rebooted as by default they are only held in RAM and are thus lost on reboot. To get a log that survives a reboot you should enable the syslog server so that if it happens again we have more to work with. Quote Link to comment
binghunlong Posted July 23, 2022 Author Share Posted July 23, 2022 (edited) I saved the logs from before the server became inaccessible to Synology. These are screenshots. Can you tell where the problem is? Thanks a lot! It looks like it's been out of whack since 00:00 last night. It dropped completely at 11:00 today. I had to restart the server at 4:30 this afternoon. Edited July 23, 2022 by binghunlong Quote Link to comment
trurl Posted July 23, 2022 Share Posted July 23, 2022 1 hour ago, binghunlong said: screenshots Can you not zip and attach the log files? Quote Link to comment
trurl Posted July 23, 2022 Share Posted July 23, 2022 Why do you have 500G docker.img? Quote Link to comment
trurl Posted July 23, 2022 Share Posted July 23, 2022 Not related to crash, but your appdata, domains, system shares have files all over the array. Combined with the 500G docker.img your configuration needs some work. Quote Link to comment
binghunlong Posted July 23, 2022 Author Share Posted July 23, 2022 38 minutes ago, trurl said: Can you not zip and attach the log files? log_2022-7-23-19_40_12.html.zip Sorry, this is my log file, it's a bit big, 102MB. Quote Link to comment
trurl Posted July 23, 2022 Share Posted July 23, 2022 Too much trouble to work with for me. Try setting up syslog server again to store its files to a share on your Unraid server. Quote Link to comment
trurl Posted July 23, 2022 Share Posted July 23, 2022 In the meantime, if it has been a while since you last rebooted new diagnostics might tell something. Quote Link to comment
trurl Posted July 23, 2022 Share Posted July 23, 2022 11 minutes ago, trurl said: Too much trouble to work with for me Can you get it as plain text instead of html and zip it? Quote Link to comment
binghunlong Posted July 30, 2022 Author Share Posted July 30, 2022 On 7/23/2022 at 8:09 PM, trurl said: Can you get it as plain text instead of html and zip it? syslog-192.168.2.55.log.zip It happened again, this time I am using the unaid system to record logs Quote Link to comment
JorgeB Posted July 31, 2022 Share Posted July 31, 2022 Jul 24 16:15:09 Tower kernel: macvlan_broadcast+0x116/0x144 [macvlan] Jul 24 16:15:09 Tower kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info. P.S. if you haven't yet you should also update to v6.10.3 1 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.