Hello, 

 

my Unraid System (6.12.0-rc5) freezes randomly. And I am not able to find / fix it. 

 

Most likely it happed at that section of the Syslog: 

 

May 11 22:07:15 Tower emhttpd: read SMART /dev/sdb
May 11 22:10:46 Tower kernel: general protection fault, probably for non-canonical address 0xffff1116aeaf2f90: 0000 [#1] PREEMPT SMP NOPTI
May 11 22:10:46 Tower kernel: CPU: 14 PID: 86 Comm: ksoftirqd/14 Tainted: P S      W  O       6.1.27-Unraid #1
May 11 22:10:46 Tower kernel: Hardware name: To Be Filled By O.E.M. X570 Pro4/X570 Pro4, BIOS P5.01 01/18/2023
May 11 22:10:46 Tower kernel: RIP: 0010:percpu_ref_get_many+0x1f/0x2a
May 11 22:10:46 Tower kernel: Code: 0b 48 89 d8 5b 5d c3 cc cc cc cc 55 48 89 fd 53 48 89 f3 e8 10 38 ea ff 48 8b 45 00 a8 03 74 0a 48 8b 45 08 f0 48 01 18 eb 04 <65> 48 01 18 5b 5d e9 07 85 ea ff f6 47 54 01 75 0b 48 83 c7 10 be
May 11 22:10:46 Tower kernel: RSP: 0018:ffffc900004afd08 EFLAGS: 00010046
May 11 22:10:46 Tower kernel: RAX: ffff8886b0772f90 RBX: 0000000000000001 RCX: 0000000000000000
May 11 22:10:46 Tower kernel: RDX: ffff888100c33f00 RSI: 0000000000000001 RDI: ffff88817d5bbd88
May 11 22:10:46 Tower kernel: RBP: ffff88817d5bbd88 R08: ffff8887cfa7d8c0 R09: ffffffff810d6f6f
May 11 22:10:46 Tower kernel: R10: ffff8887cfa7d8c0 R11: 0000000000032080 R12: ffff88817d5bbd88
May 11 22:10:46 Tower kernel: R13: 0000000000000206 R14: ffff8881865bb500 R15: 00000000fffffff8
May 11 22:10:46 Tower kernel: FS:  0000000000000000(0000) GS:ffff888ffe380000(0000) knlGS:0000000000000000
May 11 22:10:46 Tower kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 11 22:14:59 Tower nmbd[1776]: [2023/05/11 22:14:59.083053,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
May 11 22:14:59 Tower nmbd[1776]:   *****
May 11 22:14:59 Tower nmbd[1776]:   
May 11 22:14:59 Tower nmbd[1776]:   Samba name server TOWER is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.246
May 11 22:14:59 Tower nmbd[1776]:   
May 11 22:14:59 Tower nmbd[1776]:   *****
May 11 22:14:59 Tower rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2102.0 try https://www.rsyslog.com/e/2359 ]

 

Hardware: 

• ASRock X570 Pro4 (most recent Bios Version)
• AMD Ryzen 7 5700G with Radeon Graphics @ 3800 MHz
• NVIDIA GeForce GTX 1070

 

I have the "/usr/local/sbin/zenstates --c6-disable" in the go file. 

 

Maybe somebody has a better understanding of the syslog file as I do. 

I really would appreciate any kind of help! 

 

Thank you very much! 
Best Regards, 
Richard

 

 

Edited May 12, 20233 yr by Richy1989

Start here:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

 

On 5/15/2023 at 4:18 AM, JorgeB said:

Start here:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

 

Hi @JorgeB, sorry to necro this thread but the issue happened again and I noticed in the syslog it gave the same general protection fault.

I checked your link but unfortunately I am running an Intel system so it may not apply.

I do think it may have failed shortly after I had connected to the system using the Wireguard VPN tunnel I had configured on it for my phone, trying to check the uptime/status of my server and pre-clear I was performing on an unassigned device.

I saw an error in my remote syslog similar to this thread. I've provided my diagnostics and included a copy of my remote syslog file named 'rsyslog' 

In the meantime I've disabled Wireguard on the server to avoid connecting to it.

 

 

alexandria-diagnostics-20240409-1807.zip

Edited April 10, 20242 yr by Varean

You can enable the syslog server and post that after a crash, in case it catches more info.

15 hours ago, JorgeB said:

You can enable the syslog server and post that after a crash, in case it catches more info.

I have a remote syslog server set up currently, I just took a copy of the log from shortly before I connected to the Wireguard VPN, until after the crash and named it 'rsyslog' and put it in the same directory as the actual syslog from the startup after. I can post the entire remote syslog file if you'd like.

8 hours ago, Varean said:

named it 'rsyslog' and put it in the same directory as the actual syslog

That syslog shows macvlan related call traces, but I see you are now using ipvlan, did you reboot after the change?