JorgeB

It confirms the disk wasn't the problem, check/replace cables and if contents on the emulate disk1 look correct you can rebuild on top: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

Jun 18 23:57:14 UnRaid kernel: macvlan_broadcast+0x116/0x144 [macvlan] Jun 18 23:57:14 UnRaid kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan] Now there's something, Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan should 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/

Did you try

Disk 4 must have been repaired before.

That's better, at least there's a fix option, click on "run with correct flag"

RAM is running @ 3600MT/s, with your config it should be set @ 2667MT/s, overclocked RAM is known to cause salability issues and even data corruption with some AMD servers, more info here.

Should be.

Result will likely be the same but try checking filesystem again, with UD, click on the highlighted area:

Please post new diags.

You might need to wait some time, It's the middle of the night in California now, also a Sunday.

First update the LSI firmware to latest, all p20 release except the latest one have known issues, if errors continue post new diags before rebooting, diags you posted above are clean.

Cloned disk won't mount in the array because it's larger than the original, but a filesystem check will still work, let it finish to see if it can find a backup superblock, strange if all are damaged, failing that unassign the disk and try to mount it with UD to see what fs error you get.

Yes, assuming it's not a fake.

Jun 18 09:41:01 DarkRack kernel: sd 8:0:1:0: Power-on or device reset occurred Multiple errors like the above, this is usually a power/cable problem.

Try rebooting Unraid now that all browser windows are closed.

Sorry, that was a stupid question, you're not using the command line, is that filesystem check screenshot from UD?

Make sure you don't have multiple browser windows opened on the GUI.

This would be better posted in CA's support thread, but I'm getting the same, also "Action Centre enabled" so it's likely normal or if it's not I'm sure @Squidwill fix it soon.

Best bet is to use the docker support thread/link:

Please post new diagnostics.

Extended SMART test will take several hours, also make sure spin down is disabled for that disk.

Unfortunately the log is still being spammed, and don't see anything relevant to a crash, do you know the time it crashed?

I don't use macs but there are some optimizations you can do in Unraid to get better SMB performance with macOS, try searching the forum.

Please post the full command did you used to run xfs_repair.

That's not possible, but you can still install the controller and disks to confirm if they are detected or not, just won't be able to start the array with them connected until you upgrade your license.