JorgeB

Try this: https://forums.unraid.net/topic/123369-ssh-errors-operation-not-permitted-when-attempting-to-ssh-into-another-unraid-server/?do=findComment&comment=1126266

Please post the diagnostics.

Try using an exclusive share (or disk share), both will bypass FUSE, which is known to impact performance a lot with small files.

If the disks are not detected in the BIOS they also won't be detected by Unraid, swap both cables from a non working disk and see if it's detected.

Apr 19 16:18:52 iPlex kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Apr 19 16:18:52 iPlex kernel: ? _raw_spin_unlock+0x14/0x29 Apr 19 16:18:52 iPlex kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.

Apr 19 08:19:57 TUX kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10 Apr 19 08:19:57 TUX kernel: nvme nvme0: Does your device have a faulty power saving mode enabled? Apr 19 08:19:57 TUX kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug NVMe device dropped offline, try adding those options to syslinu.cfg

You can use for example rsync over SSH.

Looks like the OOM is being causes by Prowlarr, it was using a lot of RAM, I assume the RAM usage is already limited for that container?

Does the disk mount now? Looks like xfs_repair didn't finish successfully, if it doesn't mount try running it again, also update to v6.12.10 before running.

There's nothing relevant logged, and the server still crashing in maintenance mode points more to a hardware issue, could just be overheating, or power related, since a rebuild will use more power/cause more heat. Reformatting the emulated drives will delete all data there, and IMHO nlikely that the disks are the problem, I would check CPU temps and/or try again with a different PSU, if available.

Check filesystem on disk4, run it without -n, and if it asks for it use -L

Yes, and my suggestion was to try the above to see if the issue returns or not, or wss this a one time thing?

I would recommend resetting the current stats and monitoring the pool for future issues, since it can be much harder to resolve a problem if a bad or dropped device goes undetected for some time.

Please post the diagnostics.

More zfs related crashes, I would recommend backing up and re-formatting the zfs pool.