JorgeB

Yes, it restarts the Samba (SMB) service.

Dec 5 01:37:50 Reginald kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Dec 5 01:37:50 Reginald kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] Agree, 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/

Nothing obvious, not surprisingly not logged as a disk issue, looks more like a power/connection problem.

If it supports bifurcation for the x16 slot it should support all 6.

Neither UD nor Unraid will create any partitions or format a device unless you press the format button.

It's a known btrfs issue, it happens when there's an odd number of devices in raid1.

x16 PCIe slot + x4 for the CPU M.2, the other M.2 goes through the PCH.

It's not being detected by Linux now, try a different PCIe slot if available.

Post new diags.

Don't know, never used encryption.

But it's failing to initialize by the driver, not much more we can do, you can maybe try an older and/or more recent Unraid release to see if there's any difference.

Safe mode also doesn't load any plugins.

Did you see the line below that one? Jan 10 15:25:16 HOMESERVER01 kernel: aacraid: aac_fib_send: adapter blinkLED 0xff. Jan 10 15:25:16 HOMESERVER01 kernel: Usually a result of a serious unrecoverable hardware problem So likely some hardware issue.

Make sure that spin down is disable, though that usually interrupts the test.

Best bet would be to post in the existing UD plugin support thread.

It's logged as a disk problem, you can try swapping cables with another one to rule that out, also you not recommend an SMR disk for parity since it will slow down all array writes.

Without valid parity disk1 can't be emulated, you can do a new config to re-enable it, but SMART is showing some issues, so it might fail again during the sync, if it does you can try to copy any dat to other disks or use ddrescue to clone it.

Don't see anything relevant logged, could be a hardware issue, sync errors might just be a result of the unclean shutdowns, one thing you can try it to boot the server in safe mode with all docker/VMs disable, 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.

If disabling EPC and low current spin up didn't help you'd need to use a non LSI controller, or different disks.

Enable the syslog server and post that after a crash.

Very weird, Intel SATA controllers are usually very reliable, could be a specific issue with that board.

There are some recovery options here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490

btrfs is detecting data corruption, you should run memtest.

Unfortunately there's nothing relevant logged, this usually suggests a hardware issue, one thing you can try it to boot the server in safe mode with all docker/VMs disable, 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.

You need to do a new config (tools -> new config) without it then re-sync parity.