JorgeB

You need to set the filesystem to encrypted then reformat, any data there will be lost.

Yes, there legacy BIOS and UEFI boot options, if you're trying to boot UEFI you need to first enable UEFI support in the Unraid flash drive.

The rebuild would continue, with single parity there would be some data corruption, disk sectors are usually 512B, so that would be the minimum corruption size, or possibly it would affect a block, which is 4KB. No, but it's also good to have if you care about data integrity. Yes.

Looks like a power/connection problem, could also be the controller, but if you already replaced cables I would try a different PSU first.

You can try UFS explorer or other similar file recovery util.

Those support faster RAM, but the c-states related crashes can still happen, though they are usually fixed with the power supply setting.

Sorry, no since I've never used them, but it would mean something misconfigured, you can ask to confirm your config in the existing support threads for those dockers

No corruption, files were deleted by someone or some misconfigured app.

Make sure you're using the correct "power supply idle control" setting, more info here.

Except for disk10 your disks are mostly empty, is that expected? Filesystem Size Used Avail Use% Mounted on /dev/md1 3.7T 26G 3.7T 1% /mnt/disk1 /dev/md2 3.7T 4.3G 3.7T 1% /mnt/disk2 /dev/md3 3.7T 40G 3.6T 2% /mnt/disk3 /dev/md4 3.7T 26G 3.7T 1% /mnt/disk4 /dev/md5 3.7T 5.8G 3.7T 1% /mnt/disk5 /dev/md6 3.7T 26G 3.7T 1% /mnt/disk6 /dev/md7 3.7T 3.8G 3.7T 1% /mnt/disk7 /dev/md8 3.7T 26G 3.7T 1% /mnt/disk8 /dev/md9 3.7T 7.0G 3.7T 1% /mnt/disk9 /dev/md10 3.7T 610G 3.1T 17% /mnt/disk10 /dev/md11 1.9T 1.9G 1.9T 1% /mnt/disk11 /dev/md12 7.3T 172G 7.2T 3% /mnt/disk12

Sometimes Unraid fails to add a device to a pool, but can't see why in this case because it's was before current diags.

Driver is there, but NICs are failing to initialize: Feb 22 11:55:54 Chuncklord kernel: netxen_nic 0000:01:00.0: Error getting board config info. Feb 22 11:55:54 Chuncklord kernel: netxen_nic: probe of 0000:01:00.0 failed with error -5 Feb 22 11:55:54 Chuncklord kernel: netxen_nic 0000:01:00.1: 2MB memory map Feb 22 11:55:54 Chuncklord kernel: netxen_nic 0000:01:00.1: Error getting board config info. Feb 22 11:55:54 Chuncklord kernel: netxen_nic: probe of 0000:01:00.1 failed with error -5

Cache4 is currently not part of the pool despite what the GUI shows, try this: stop array, unassign cache4, start array, stop array, re-assign cache4, start array.

Many using those baords and Unraid, including myself, are you attempting to boot with legacy or UEFI?

That repair is already stopped, you need to use -L.

Please don't double post, the VM section is the correct one for this issue:

Redo the flash drive and restore only super.dat (disk assignments) and the key, if it boots correctly like that reconfigure the server or start copying other parts of the config until you find the problem.

Those photos aren't very helpful, try this and post that log after a crash.

Please post the diagnostics: Tools -> Diagnostics

Disk looks fine, if the emulated disk is mounting and data looks correct you can rebuild on top, but should also replace that controller ASAP.

It is a btrfs bug, but it affects pools with an odd number of devices.

Possibly just a controller problem,, SASLP is not recommended for a long time, but since the disk dropped there's no SMART, power cycle the server and post new diags.

Update the LSI firmware to latest, CRC errors are a known issue of the version you're using.

It appear to be balancing still, though it should be part of the pool already, something strange is going on with that pool, probably best to just start over, system profile is still single.