JorgeB

You can run an extended SMART test, if it takes at longer than the expected time, and that time is in the SMART report, if suggests a disk problem.

You can enable the syslog server and post that after a crash, but if it's a hardware problem, most likely there won't be anything logged.

It can be, and it's worth running, but keep in mind that memtest is only definitive if it finds errors, since you have multiple sticks you can also try running the server with just one, if the same try with a different one, that will basically rule out bad RAM.

Recommend changing the docker network to ipvlan, if you really need macvlan disable bridging for eth0, more info here: https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces

No, Unraid cannot mount ntfs, you can keep passing through the device to a VM, or format it with a supported filesystem if you want to use it in a pool.

Recommend doing that ASAP, since at least part of the problem, may have been caused by that.

There are ATA errors with disk2, replace the cables and post new diags after array start.

Correct, once a disk gets disabled, and it doesn't matter what caused it, it will never be re-enabled automatically.

If you have a spare, and assuming parity is valid, the best way would be to do a direct replacement, if that disk is the problem, it would start to work better after it's removed.

This is a Windows filesystem, so it will never mount with Unraid, maybe you were passing through that device to a VM?

Multiple call traces, but don't see what's causing them, you can try to boot the server in safe mode with all docker containers/VMs disabled, 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.

This looks more like a general support issue, post the output of: blkid and fdisk -l /dev/nvme1n1

Looks more like a power/connection issue, replace or swap cables to rule that out and try again, if the emulated disk is still mounting and contents look correct you can rebuild on top: https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

There's something creating this folder before array start: Apr 22 22:08:12 MahBukkit emhttpd: error: malloc_share_locations, 7199: Operation not supported (95): getxattr: /mnt/user/Music That will cause the problems you are seeing.

Please post the diagnostics after array start.