JorgeB

No, there's a SATA port multiplier.

Firmware update is usually very easy, though some models can be more complicated when changing firmware type.

If you see RAID support in the description I would assume it comes with RAID firmware.

LSI HBAs can have IT or RAID firmware, IT is recommended for Unraid, that model appears to come with RAID firmware, though they can usually be flashed with either firmware.

Click on the first pool device, then scroll down until this section: Click on "perform full balance", chose the profile you want to convert to then click on "Balance"

This is usually a hardware issue, try the card in a different PCIe slot if available, BIOS update might also help, if everything else fails this can usually suppress the error to avoid filling up the log:

Should be good for roughly 250MB/s per drive, so likely not a bottleneck. No, batteries are for RAID controllers with onboard cache RAM, those are not recommended with Unraid. Yes. Correct.

Not sure about the error but you started the array with only one pool device assigned, so just need to wait for the balance to finish, which it already did by now, so you can just add the new device.

xfs or btrfs?

It would also be my main suspect.

Please post the diagnostics.

Check filesystem

What do you mean? Disk6 is empty so any data there is lost, you can see the rest of the array data.

It's not, there's even a big pop warning about it: If you still have the old disk intact and assuming it's not dead you should be able to recover data from there, see if it mount with the UD plugin, if it doesn't post the diagnostics.

Stock Unraid doesn't report temps or controls fans, you need to rely on the available plugins for that, of course the plugins will only work if your hardware is compatible.

Disk look healthy, errors occurred right after spin up, so you might want to try and disable spin down if it happens again in the same circumstances.

Apr 23 05:08:42 NNC kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Apr 23 05:08:42 NNC kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] If the server sometimes crashes see below. 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/

It's not, SMART tests failed so it needs to be replaced.

Trying to run memtest when booting UEFI generally just restarts the server, but you can try memtest86, it's UEFI only.

SMART looks completely healthy for that drive. https://forums.unraid.net/topic/86337-are-my-smart-reports-bad/?do=findComment&comment=800888

It an Unraid boot option: It only works with CSM boot, not UEFI

It's likely hardware related, if it's not the GPU it could be PSU, board, etc., you can also try v6.10.0-rc to rule out any kernel compatibility issue.

Btrfs is detecting data corruption, first thing you should do is to run memtest.

The only thing of note I see is multiple of these: Apr 24 00:11:12 Andromeda kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] Apr 24 00:11:12 Andromeda kernel: caller _nv000651rm+0x1ad/0x200 [nvidia] mapping multiple BARs Including one just before the crash, can't say it's related, but worth trying running the server without the Nvidia GPU, or installing it in a different PCIe slot if available.

Btrfs is detecting a lot of data corruption, you should run memtest.