JorgeB

First post the diags after array start like asked, so we can see if the emulated disks are mounting.

Like mentioned if it's a power issue you should ear the drives clicking or spinning up/down during normal usage.

Most likely are not working then, but you can test in the working port to make sure.

Bad power, be it a failing PSU or a problem with the connections, can also cause reallocated sectors, in those cases you can usually hear the drives powering up/down when that happens.

The drive is not returning all zeros on post read as it should, run memtest, bad RAM can result in that issue.

There are also pending sectors, so yes, it should be replaced.

See if this applies to you, if yes, 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/

After the crash doesn't help since the regular log starts over after every reboot. Could be, persistent syslog should show that, if true.

Docker image is corrupt, delete and recreate.

That's a SATA SSD connected to the onboard SATA controller, if the SAS devices now have power boot Unraid and they should be detected there.

To avoid future issues I would recommend backing up and re-formatting cache.

What commend did you use to repair the filesystem?

Feb 7 08:19:37 Tower root: Verifying package nvidia-driver-2022.01.20.txz. Feb 7 08:19:37 Tower root: Installing package nvidia-driver-2022.01.20.txz: Feb 7 08:19:37 Tower root: PACKAGE DESCRIPTION: Feb 7 08:19:37 Tower root: Package nvidia-driver-2022.01.20.txz installed. Feb 7 08:19:37 Tower root: plugin: creating: /usr/local/emhttp/plugins/nvidia-driver/README.md - from INLINE content Feb 7 08:19:37 Tower root: plugin: running: anonymous Feb 7 08:19:38 Tower root: Feb 7 08:19:38 Tower root: +============================================================================== Feb 7 08:19:38 Tower root: | WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING Feb 7 08:19:38 Tower root: | Feb 7 08:19:38 Tower root: | Don't close this window with the red 'X' in the top right corner until the 'DONE' button is displayed! Feb 7 08:19:38 Tower root: | Feb 7 08:19:38 Tower root: | WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING Feb 7 08:19:38 Tower root: +============================================================================== Feb 7 08:19:38 Tower root: Feb 7 08:19:38 Tower root: -----------------Downloading Nvidia Driver Package v510.47.03------------------ Feb 7 08:19:38 Tower root: ----------This could take some time, please don't close this window!------------ That's from the nvidia plugin driver, please use the existing plugin support thread.

This is usually hardware related, you can try this to suppress the error.

Default allocation mode is high water, it will start writing to disk5 once disk4 is over 50% used, and to disk6 once disk5 is over 50% used, assuming split level setting allows it.

Enable the syslog server and post that after a crash.

Same for me.

You need to connect power, or the drives won't spin up.

Check filesystem on disk 9.

It should work in any motherboard with an appropriate slot, but sometimes there could be compatibility issues, unfortunately there's no way to tell unless you or someone else tried it.

One more thing, this is fairly obvious, but since it happened before, you did connect power to the SAS cables right?

Use this option, Intel onboard RAID is "fake" RAID, Linux will use AHCI mode/driver.

Feb 1 22:06:07 Tower kernel: XFS (md4): Filesystem has duplicate UUID b78aba02-8697-433d-801b-703da9c237d7 - can't mount This is the problem, post the output of: blkid

CSM Legacy boot must be enable, as well as OPT ROM for the PCIe slots, then CTRL + C during boot when you see the LSI BIOS.

Please post the diagnostics.