JorgeB

No, with dual parity you can lose two drives, with single just one.

Look for the 9211-8i, in the legacy section.

It means there's likely a failing DIMM, System/IPMI event log might have more info on exactly which one it is.

I would start with board/CPU.

Usually yes.

Using USB is possible, but not recommended for array or cache devices, USB is usually very bad at error handling.

Did you try installing the intel-gpu-top plugin like mentioned in the other thread above?

See if disabling spin down for that disk helps.

It will work, but it's not recommended, and keep in mind that for example two 4TB drives in raid0 will be slightly smaller than one 8TB drive, so parity will always need to be larger than the data drives you intend to use.

This looks more like a hardware issue, though strange that it appears to be caused by a particular docker.

That points to another issue, not the disks, is the controller the same you were using before? Also check which CPU scaling governor is in use.

You should, reiser is no longer being activily developed and has several known issues, mostly performance related.

20MB/s slow or just slower? Parity check can't go faster than the slowest disk at any point.

Check filesystem on that disk, also good idea to convert all your disks from reiser to xfs.

Stock Unraid doesn't support fan control, please use the existing plugin support thread:

Jul 13 14:07:54 ADL-Server kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Jul 13 14:07:54 ADL-Server kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. 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/ There are also a lot of ATA errors on disks

There are a couple of call traces but can't see the reason, could be the kernel doesn't like your board, the number one issue for crashes on v6.9.2 appears to be this: Though this is usually visible in the syslog, still might be worth checking if it applies to you.

You just need to boot with DOS and run that command, if the board has UEFI support you'll need to use a UEFI shell instead, it's possible to update an LSI using Unraid but unfortunately the Linux binary doesn't work with the delete BIOS option.

You can just delete it: https://forums.unraid.net/topic/12114-lsi-controller-fw-updates-irit-modes/?do=findComment&comment=632252 Note: with multiple controllers you need to select the controller or it will delete the BIOS from the first one.

Try deleting the BIOS, it's not needed for Unraid.

This is normal with different size devices, used/free will be correct.

They will spin down with a Supermicro JBOD (or similar direct connect JBDO) they should also spin down with Netapp, but you should search for that, and SAS devices might not spin down even with the plugin.

Yep.

No, other way around, rebuild aborted because the disk got disabled. Disk looks healthy, you should update the LSI firmware though, that version has known issues.