6.9.2 freezes

[DZLSWAG]

Hello Ghostriders,

 

I appreciate  the hard work for the DEV and unraid.  My unraid server has been freezing up on me more and more after i reverted from 6.10 back to 6.9.2 . I am considering move to 6.10.3  but unsure why i have these issues. if anyone can help would be cool. 

unraid-diagnostics-20220616-2038.zip

Edited June 17, 2022 by DZLSWAG
type o

[JorgeB]

Look for a BIOS update to see if it helps with that log spam, then enable the syslog server and post that after a crash.

[DZLSWAG]

sorry now i have syslog enabled nnow  i will wait for the crash

 

Edited June 18, 2022 by DZLSWAG

[DZLSWAG]

On 6/16/2022 at 11:52 PM, JorgeB said:

Look for a BIOS update to see if it helps with that log spam, then enable the syslog server and post that after a crash.

here is the syslog

syslog-10.0.7.60 (1).log

[DZLSWAG]

Happy fathers day for anyone reading this

 

[JorgeB]

Unfortunately the log is still being spammed, and don't see anything relevant to a crash, do you know the time it crashed?

[DZLSWAG]

12 hours ago, JorgeB said:

Unfortunately the log is still being spammed, and don't see anything relevant to a crash, do you know the time it crashed?

syslog-10.0.7.60 (4).log here another log that it  crashed. It seems it crashes within 24 hours. . I have upgrade to 6.10.3 . I dont know what else to do.  I do see in the log when the syslog stop reporting and continues to log after i turn it on again.  I dont mind someone remoting in to help solve this if needed.

[DZLSWAG]

new crash log. I did see there a time sync issue. I dont know if that can cause it

[DZLSWAG]

now that i updated to 6.10.3 unraid dies within 2 hours of starting it

[JorgeB]

Jun 18 23:57:14 UnRaid kernel: macvlan_broadcast+0x116/0x144 [macvlan]
Jun 18 23:57:14 UnRaid kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]

 

Now there's something, 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.

https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/

See also here:

https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

[DZLSWAG]

17 hours ago, JorgeB said:

Jun 18 23:57:14 UnRaid kernel: macvlan_broadcast+0x116/0x144 [macvlan]
Jun 18 23:57:14 UnRaid kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]

 

Now there's something, 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.

https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/

See also here:

https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

 

 

so i have my running and have all my dockers off. since they are not running i hope it does not crash. I will update you in 24hours  if it does not crash

 

[DZLSWAG]

5 hours ago, DZLSWAG said:

 

 

so i have my running and have all my dockers off. since they are not running i hope it does not crash. I will update you in 24hours  if it does not crash

 

i deleted the  docker that had a ip on it and and it still crashed. 

syslog-10.0.7.60 (3).log

[DZLSWAG]

5 hours ago, DZLSWAG said:

 

 

so i have my running and have all my dockers off. since they are not running i hope it does not crash. I will update you in 24hours  if it does not crash

 

i deleted the  docker that had a ip on it and and it still crashed. 

 

 

question ... is there a way to have a fresh install on a flash drive and keep my data on the disk array

 

[JorgeB]

You don't need to delete dockers:

23 hours ago, JorgeB said:

switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right))

 

[DZLSWAG]

yea i know i did not need to delete it.  It was a docker that i can re add  later if i want to . the plex and the other two docker are more important.  But so far unraid is still up from last night.  Thank you all on who guided me through this.  This is a great community and help me grow to ask less question over time..

 

 

when i install the docker i delete i will add the ipvlan when it get installed.

 

 i just have to fix my plex issue from all the crashes now...