Hey all, so I have a few issues here that might be related, they are really starting to stack up. I recently upgraded to 6.12.4 and now 6.12.6. I use macvlan (bond yes, bridge no, host access yes) with my UDM pro, seems to work best for Plex forwarding, Nginx, cloudflare, HA VM etc but recently I am having connectivity issues and crashes overnight where the server becomes unresponsive.

 

After an unplanned shutdown last night I am now stuck partway through a parity check (non error correcting) that I cant pause or stop. The parity check is just over 1200 errors, this is more than I've ever seen previously. My last couple monthly parity checks listed only around 100 (another issue I hadn't got to looking into). As it stands currently, stopping VMs and Docker doesn't seem to unlock the network settings, and when they are running all my dockers and HA VM seem to function fine.

 

I've had no recent hardware upgrades (and no disk errors showing), only some jumping around network settings to get everything working right following the 6.12 upgrade, just when I think I've nailed it I get crashes or more errors. Nothing of note jumping out in fix common problems either. I have attached current diagnostics, also looks as if there are some lines in the live Unraid Logs mentioning Call Trace (maybe I need to give ipvlan another shot). If anyone is able to shed some light on some or all of the above that would be greatly appreciated.

 

Quote

Jan 23 13:42:04 WILD-MACHINE kernel: CPU: 2 PID: 20991 Comm: unraidd0 Tainted: P      D    O       6.1.64-Unraid #1
Jan 23 13:42:04 WILD-MACHINE kernel: Hardware name: ASUS System Product Name/PRIME Z590-A, BIOS 0402 01/08/2021
Jan 23 13:42:04 WILD-MACHINE kernel: RIP: 0010:do_exit+0x87/0x923
Jan 23 13:42:04 WILD-MACHINE kernel: Code: 24 74 04 75 13 b8 01 00 00 00 41 89 6c 24 60 48 c1 e0 22 49 89 44 24 70 4c 89 ef e8 76 dd 80 00 48 83 bb b0 07 00 00 00 74 02 <0f> 0b 48 8b bb d8 06 00 00 e8 78 dc 80 00 48 8b 83 d0 06 00 00 83
Jan 23 13:42:04 WILD-MACHINE kernel: RSP: 0018:ffffc900042b7ee0 EFLAGS: 00010286
Jan 23 13:42:04 WILD-MACHINE kernel: RAX: 0000000080000000 RBX: ffff8881084b16c0 RCX: 0000000000000000
Jan 23 13:42:04 WILD-MACHINE kernel: RDX: 0000000000000001 RSI: 0000000000002710 RDI: 00000000ffffffff
Jan 23 13:42:04 WILD-MACHINE kernel: RBP: 0000000000000009 R08: 0000000000000000 R09: ffffffff82245f10
Jan 23 13:42:04 WILD-MACHINE kernel: R10: 0000000000000000 R11: ffffffff8295ef16 R12: ffff8881072d9400
Jan 23 13:42:04 WILD-MACHINE kernel: R13: ffff88816a2a9080 R14: 0000000000000000 R15: 0000000000000000
Jan 23 13:42:04 WILD-MACHINE kernel: FS:  0000000000000000(0000) GS:ffff88901fa80000(0000) knlGS:0000000000000000
Jan 23 13:42:04 WILD-MACHINE kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 23 13:42:04 WILD-MACHINE kernel: CR2: 0000000000040014 CR3: 00000004196c6005 CR4: 0000000000772ee0
Jan 23 13:42:04 WILD-MACHINE kernel: PKRU: 55555554
Jan 23 13:42:04 WILD-MACHINE kernel: Call Trace:
Jan 23 13:42:04 WILD-MACHINE kernel: <TASK>
Jan 23 13:42:04 WILD-MACHINE kernel: ? __warn+0xab/0x122
Jan 23 13:42:04 WILD-MACHINE kernel: ? report_bug+0x109/0x17e
Jan 23 13:42:04 WILD-MACHINE kernel: ? do_exit+0x87/0x923
Jan 23 13:42:04 WILD-MACHINE kernel: ? handle_bug+0x41/0x6f
Jan 23 13:42:04 WILD-MACHINE kernel: ? exc_invalid_op+0x13/0x60
Jan 23 13:42:04 WILD-MACHINE kernel: ? asm_exc_invalid_op+0x16/0x20
Jan 23 13:42:04 WILD-MACHINE kernel: ? do_exit+0x87/0x923
Jan 23 13:42:04 WILD-MACHINE kernel: make_task_dead+0x11c/0x11c
Jan 23 13:42:04 WILD-MACHINE kernel: rewind_stack_and_make_dead+0x17/0x17
Jan 23 13:42:04 WILD-MACHINE kernel: RIP: 0000:0x0
Jan 23 13:42:04 WILD-MACHINE kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
Jan 23 13:42:04 WILD-MACHINE kernel: RSP: 0000:0000000000000000 EFLAGS: 00000000 ORIG_RAX: 0000000000000000
Jan 23 13:42:04 WILD-MACHINE kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
Jan 23 13:42:04 WILD-MACHINE kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Jan 23 13:42:04 WILD-MACHINE kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
Jan 23 13:42:04 WILD-MACHINE kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Jan 23 13:42:04 WILD-MACHINE kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Jan 23 13:42:04 WILD-MACHINE kernel: </TASK>
Jan 23 13:42:04 WILD-MACHINE kernel: ---[ end trace 0000000000000000 ]---

 

wild-machine-diagnostics-20240123-1518.zip

Unraid driver crashed, this is usually a hardware issue, but you can try downgrading to a known good release and retest in case it's a kernel compatibility issue with your hardware.

Thanks for your reply JorgeB. I manually downgraded to 6.12.4 and ran a parity check, it completed this time albeit still with 418 errors (but valid). I also switched back to ipvlan (bond yes, bridge yes, host access yes) which seems to be playing nice with my UDM Pro for now and my tunnels and plex etc all happy. Ill ride this for a while and see if I get some decent stability and no errors in my logs.