JorgeB

Should be 1866, make sure XMP is disabled.

OK, and it doesn't really matter now, but I mentioned using one of the already assigned array drives, just connecting one of them to the HBA would be a good test.

Enable the syslog server and post that after a crash.

Just start a parity check with "write corrections to parity" unchecked, but it it detects errors stop and run a correcting check. Correct, should be set @ 1866MT/s with 4 dual rank DIMMs

You can see here the instructions for just updating an LSI firmware using Unraid, but since it has a RAID firmware you first must erase the current one, and the Linux utility does not work for that part, so you must use DOS/UEFI.

Glad it's solved, but I did ask for you to first try with a known good drive, that one should have worked, also mentioned to make sure the drives were spinning up.

Not sure what the error is about, but it's using an outdate RAID firmware, flash the latest IT firmware (20.00.07.00) to see if it helps.

Currently only with btrfs, soon you should be able to use zfs, though you can use zfs now with a plugin, btrfs raid5/6 still has some known issues, it can be used, I do in multiple pools, but also have good backups.

You need to format the devices first, next to array stop button.

This is apparently normal, the 1st smb process has a lower soft limit, at least I downgraded as far back as v6.9.2 and it's the same: root@Tower15:~# ps aux | grep smbd root 4202 0.0 0.4 87384 18048 ? Ss 18:52 0:00 /usr/sbin/smbd -D root 4205 0.0 0.2 85436 9460 ? S 18:52 0:00 /usr/sbin/smbd -D root 4206 0.0 0.1 85428 4476 ? S 18:52 0:00 /usr/sbin/smbd -D root 5962 0.0 0.0 3904 1988 pts/0 S+ 18:52 0:00 grep smbd root@Tower15:~# cat /proc/4202/limits | grep files Max open files 16464 40960 files root@Tower15:~# cat /proc/4205/limits | grep files Max open files 40960 40960 files @PhilipJFrywhat was the previous release you were running?

This will be unrelated to the trial license, but please post the diagnostics.

Should be plug and play.

Check that the flash drive is being detected and set as the 1st boot option.

Btrfs detecting corruption after resetting the pool suggests a hardware problem, did you revert RAM speeds to max supported like detailed in the link above?

Disk2 has a failing now SMART attribute, but it's not one of the worst, try rebuilding again.

No disk errors during the sync so that is good but since you are using a Ryzen server with overclocked RAM and that is known to sometimes cause data corruption I would recommend doing a non correct parity check to confirm before doing anything else, and change RAM speeds to max supported.

Disk 2 dropped offline, cancel the rebuild, check/replace cables on that disk and post new diags after array start.

You can change directly, make sure you are not using 6.11.2 since there's an issue.

Please do, and if you see the same issues post the diags in a new thread in the general support forum.

Diags from v6.11.3 should show the problem, when you downgraded back to v6.11.1 the pool devices were assigned again?

It's a know issue with that device, this has been reported to help: https://forums.unraid.net/bug-reports/stable-releases/6103-samsung-980-temp-warning-r2007/?do=findComment&comment=20180

You do appear to have RAM problems but those should be unrelated since you have ECC RAM and they are logged as corrected, still need to replace the faulty DIMM(s) ASAP. Since you did many rebuild attempts and new configs I would suggest first rebooting to clear the logs, then doing a new config with all the old disks, check parity is already valid but run a correcting parity check since a few since errors are expected, only after that's done without any issues try replacing the disks again, using v6.11.1 or v6.11.3, if any unmountable disk comes up at any point during that post new diags.

Nothing relevant logged, that usually suggests a hardware issue, I would start by downgrading back to the previous known good release to confirm it's not happening there now.

Please post the diagnostics after that happens.

See here: https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606