September 11, 20205 yr i've had unraid for a few years now but for the past few months it just keeps freezing on me and i have to hard reboot it i started saving the syslog to the flash drive a few days ago the 1st crash was on the 7th the another on the 10th and today it did freeze but firefox wouldn't work and none of my computers saw it on the network when i read the log i look for "microcode: microcode updated early to revision" and that's the first log that i see when i reboot my server after it freezes syslog Edited September 11, 20205 yr by James_Darkness
September 11, 20205 yr Community Expert Macvlan call traces are usually cause by dockers with a custom IP address, more info here, also issues with the NICs, but might be related since they start after the macvlan errors, also some out of memory errors.
September 15, 20205 yr Author On 9/11/2020 at 10:49 AM, JorgeB said: Macvlan call traces are usually cause by dockers with a custom IP address, more info here, also issues with the NICs, but might be related since they start after the macvlan errors, also some out of memory errors. so i uninstalled some out of date dockers but now it crashed differently this time i think. the only dockers i have on are plex and lancache bundle Sep 14 19:31:01 syslog
September 15, 20205 yr Community Expert Still macvlan call traces, are those dockers using custom IP?
September 16, 20205 yr Author On 9/15/2020 at 1:53 AM, JorgeB said: Still macvlan call traces, are those dockers using custom IP? lancache-bundle has to and that's it
November 25, 20214 yr Author On 9/16/2020 at 12:07 PM, JorgeB said: One is enough. i put the sys log into the zip file. i removed the docker that had its own ip and moved it to a vm. on wed my server crashed it said bad psu so i replaced one and it boots again but only for a day unraidnas-diagnostics-20211123-2257.zip
November 26, 20214 yr Community Expert There are still macvlan call traces, also the server is constantly running out of RAM.
November 27, 20214 yr Author 18 hours ago, JorgeB said: There are still macvlan call traces, also the server is constantly running out of RAM. i just added ram and ill try turning off vms and dockers Edited November 27, 20214 yr by James_Darkness
November 27, 20214 yr Community Expert Probably should have been enough RAM unless you are running a lot of VMs, so maybe something else going on with that. Also, your docker.img is ridiculously large, and I don't think anyone has ever needed more than the default 1G for libvirt.img.
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.