February 10, 20224 yr I went to bed last night around 10pm and a preclear was running and due to finish on a new drive this AM. When I checked this AM, the GUI had crashed. Putty didn't work. The keyboard and monitor directly attached to the system didn't do anything. Lights were on. Nobody home. I ended up doing a hard reset and I'm running ANOTHER parity check, which is getting annoying. I had syslog mirroring to flash, so I'll attach that and the diagnostics. Obviously I couldn't get the diagnostics until I reset the server. Any help is appreciated. I notice the logs stop around 5:20am, and then no new entries until I hard reset the system after work around 19:25. orcrist-diagnostics-20220209-2005.zip orcrist-syslog-20220210-0304.zip
February 10, 20224 yr Community Expert Could be related to this: https://forums.unraid.net/bug-reports/prereleases/69x-610x-intel-i915-module-causing-system-hangs-with-no-report-in-syslog-r1674/?do=getNewComment&d=2&id=1674
February 14, 20224 yr Author On 2/10/2022 at 12:48 AM, JorgeB said: Could be related to this: https://forums.unraid.net/bug-reports/prereleases/69x-610x-intel-i915-module-causing-system-hangs-with-no-report-in-syslog-r1674/?do=getNewComment&d=2&id=1674 Maybe, I read through it and not sire what I can do about it. New logs after another crash syslog.ziporcrist-diagnostics-20220213-2135.zip
February 14, 20224 yr Community Expert 6 hours ago, mikesp18 said: I read through it and not sire what I can do about it. You can disable loading the i915 driver, but since the current log has this: Feb 13 00:03:25 Orcrist kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Feb 13 00:03:25 Orcrist kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] The problem is likely this one: Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 and switching to ipvlan might 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/
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.