maroil Posted January 4, 2023 Share Posted January 4, 2023 Hello, So, 6 months ago I started facing some real issue with my unraid server with some kernel panics ! i tried switching CPU/Motherboard/RAM ... but still i couldn't fix it, each time the crash keep going back. Recently i added this command at boot to disable C-State / i did put my ram to run at 2400MHz even if it can be used at 3200MHz, i switched to ipvlan in docker configuration, i stopped all containers that use br0 mode, but still the issue keep happing again and again ! Can someone please check my diagnostics extract and check if he can see somethings that can explain the issue ! Thank you ! server-diagnostics-20230104-1907.zip Quote Link to comment
JorgeB Posted January 4, 2023 Share Posted January 4, 2023 Enable the syslog server and post that after a crash. Quote Link to comment
maroil Posted January 4, 2023 Author Share Posted January 4, 2023 Hello @JorgeB, Thank you for the fast answer ! Syslog is already enabled, i have some historical logs. The last crash happened today (January 4, 2023) arround 3 pm (15h00) But nothing is catched in the logs as you can see in the file Quote Jan 3 22:34:35 Server webGUI: Successful login user root from 192.168.1.93 Jan 3 22:39:35 Server emhttpd: spinning down /dev/sdc Jan 4 03:18:36 Server emhttpd: read SMART /dev/sdg Jan 4 03:19:13 Server emhttpd: read SMART /dev/sdc Jan 4 03:49:22 Server emhttpd: spinning down /dev/sdc Jan 4 03:50:51 Server emhttpd: spinning down /dev/sdg Jan 4 18:52:42 Server root: Delaying execution of fix common problems scan for 10 minutes Jan 4 18:52:42 Server emhttpd: Starting services... Jan 4 18:52:42 Server emhttpd: shcmd (53): /etc/rc.d/rc.samba restart Jan 4 18:52:42 Server wsdd2[1985]: 'Terminated' signal received. Jan 4 18:52:42 Server winbindd[1989]: [2023/01/04 18:52:42.138625, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Jan 4 18:52:42 Server winbindd[1989]: Got sig[15] terminate (is_parent=0) I enabled mirroring logs to Flash, hopping it will provide more insignts !! syslog-192.168.1.10.log Quote Link to comment
JorgeB Posted January 5, 2023 Share Posted January 5, 2023 Unfortunately there's nothing relevant logged this usually suggests a hardware problem, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one. 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.