JorgeB

I believe this happened before, toggle to speed instead, that should still show and it's much more useful.

Also the docker image is corrupt, delete and re-create.

Feb 22 18:33:49 MOORETOWER kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Feb 22 18:33:49 MOORETOWER kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] 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/

No, test the HBA in a different PC/Server, if available, to see if it's initialized correctly.

Feb 23 11:33:13 Big-Plex kernel: megaraid_sas 0000:01:00.0: Failed to init firmware Feb 23 11:33:13 Big-Plex kernel: megaraid_sas 0000:01:00.0: Failed from megasas_init_fw 6406 RAID controller is failing to initialize, test in another PC if available to confirm if it's board related or not.

It's not a question of how much power, it's a feature on some drives: https://documents.westerndigital.com/content/dam/doc-library/en_us/assets/public/western-digital/collateral/tech-brief/tech-brief-western-digital-power-disable-pin.pdf Though yours is an older model so probably not affected, do you hear it spining up and is the drive detected in the LSI BIOS?

Single device cache can be xfs or btrfs, multi device btrfs only.

Everything looks normal with the HBA, it's being initialized correctly, but nothing being detected, so likely a device/cable problem, also make sure the disk is spinning up, some won't if there's 3.3v on the connector.

You should post the diagnostics, sometimes SAS devices come with a non standard sector size or are write protected.

Please post the diagnostics.

Do this.

Yep, same controller issue.

It won't, would need to see the diags to confirm but like mentioned above it's most likely the same controller issue, it tends to be worst under load, like during a parity check or rebuild. You can cancel the current rebuild and try again later, ideally without using the onboard controller.

That suggests first one was non correct, if the second one was correct it would find the same errors, but this time fix them, you can post the diags to confirm, if you didn't reboot yet, or run another check and it should find 0 errors.

Not that I know of. It might help in the sense that if the disk isn't detected in the HBA BIOS the problem has nothing to do with Unraid, don't you have an older PC you could use just to test that? You don't even need to boot Unraid, just install the HBA and check if the disk is detected in the BIOS.

I didn't notice before you're using an Intel 500 Series board, these won't allow CSM boot using the iGPU: https://scottiestech.info/2021/04/13/why-cant-i-enable-csm-on-my-new-motherboard/

See here:

No, earlier release would disable spin down for SMART test, but not current one, and AFAIK still not fixed on v6.10-rc

Because wsdd contains sdd, same as the drive it's filtering.

Main page, click on circle on the left side of the device, the one that changes colors depending on the drive status. 4H is not enough for an extend test on an 8TB drive.

Those have nothing to do with drives, and if not needed you can disable WSD (settings -> SMB) to fix that.

Old disk4 does show some recent issues, other ones look fine, I would suggest doing this, keep old disk4 intact for now and reconnect the new one, then: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed, including the new disk4, replacement disk should be same size or larger than the old one -IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked) -Stop array -Unassign disk4 -Start array (in normal mode now), ideally the emulated disk will now mount and contents look correct, if it doesn't you should run a filesystem check on the emulated disk -If the emulated disk mounts and contents look correct stop the array -Re-assign disk4 and start array to begin.

Problem was cause by issues with the onboard SATA controller, this is quite common with some Ryzen boards, especially under load, BIOS update might help, or you can also use an add-on controller. As for the current situation, first you need to reboot to clear the controller problem, then you can re-enable the disable disks and try to rebuild again, though same thing might happen if the controller errors out again, we assume the disable disks are OK but since there's no SMART for any of them it's best to reboot now and post new diags, also keep the old disk intact for now in case it's needed.

You can also enable the syslog server and post that after a crash, it might catch something.

Enable the syslog server to see if it catches something, but a server rebooting on its own it's usually hardware related, like a bad PSU, etc, and if yes there won't be anything logged.