JorgeB

SMART report for disk2 is incomplete, see if you can get a manual SMART report, but the disk does appear to be failing: smartctl -x /dev/sdf

Not really, just check that is running latest firmware. Yes to both.

Try recreating the flash drive, then restore only the config folder from the backup.

Problem with the onboard SATA controller: Jul 10 05:04:11 Ribeye kernel: ahci 0000:02:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0xdf604000 flags=0x0000] This is quite common with some Ryzen boards, look for a BIOS update or use and add-on controller.

It may have, but RAM is overcolocked and that's a known issue with Ryzen, at least make sure it still crashes when running on spec.

Disk look fine, replace/swap cables/slot to rule that out and rebuild on top.

Enable syslog mirror to flash and post that log after a crash.

Constant ATA errors on disk1: Jul 12 23:10:56 Obelix kernel: ata1: COMRESET failed (errno=-16) Jul 12 23:10:56 Obelix kernel: ata1: hard resetting link Jul 12 23:11:02 Obelix kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 12 23:11:02 Obelix kernel: ata1.00: configured for UDMA/133 Jul 12 23:11:02 Obelix kernel: ata1: EH complete Jul 12 23:11:02 Obelix kernel: ata1: limiting SATA link speed to 3.0 Gbps Jul 12 23:11:02 Obelix kernel: ata1.00: exception Emask 0x50 SAct 0x2000088 SErr 0x4090800 action 0xe frozen Jul 12 23:11:02 Obelix kernel: ata1.00: irq_stat 0x00400040, connection status changed Jul 12 23:11:02 Obelix kernel: ata1: SError: { HostInt PHYRdyChg 10B8B DevExch } Jul 12 23:11:02 Obelix kernel: ata1.00: failed command: READ FPDMA QUEUED Jul 12 23:11:02 Obelix kernel: ata1.00: cmd 60/00:18:48:04:00/04:00:00:00:00/40 tag 3 ncq dma 524288 in Jul 12 23:11:02 Obelix kernel: res 40/00:00:30:3c:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Jul 12 23:11:02 Obelix kernel: ata1.00: status: { DRDY } Jul 12 23:11:02 Obelix kernel: ata1.00: failed command: READ FPDMA QUEUED Jul 12 23:11:02 Obelix kernel: ata1.00: cmd 60/20:38:00:09:c5/00:00:ad:04:00/40 tag 7 ncq dma 16384 in Jul 12 23:11:02 Obelix kernel: res 40/00:00:30:3c:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Jul 12 23:11:02 Obelix kernel: ata1.00: status: { DRDY } Jul 12 23:11:02 Obelix kernel: ata1.00: failed command: READ FPDMA QUEUED Jul 12 23:11:02 Obelix kernel: ata1.00: cmd 60/08:c8:40:00:00/04:00:00:00:00/40 tag 25 ncq dma 528384 in Jul 12 23:11:02 Obelix kernel: res 40/00:00:30:3c:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Replace cables and post new diags, though filesystem is likely already damaged.

You should have saved the diags before rebooting, you can run a scrub on the rebuilt disk to look for corruption and run an extended SMART test in all disks, or at least any disk where this is non 0 (like disk17): Elements in grown defect list: 8189

Yes and yes.

If you are coming from v6.8.x there were several changes to spin down logic for v6.9, if it doesn't spin down manually with v6.9.2 likely it won't spin down with any v6.9 release.

Very possible, wait for the pre-clear to finish and the disk should finish formatting.

See if you can get the diags by typing "diagnostics" on the console.

You say you disabled the plugin and it still went to sleep? Then try uninstall it, but if you need support for the plugin itself you should use the existing support thread:

You're using Areca controllers, not sure they support spin down, at least without any additional config/modifcation, try searching the forum or using a recommended controller if that's an option.

This indicates there are other issues, manual spin down should always work, diags might give more clues.

For example: https://store.supermicro.com/supermicro-internal-reverse-breakout-cross-over-minisas-hd-to-4-sata-with-sideband-55-55-55-55-55cm-cable-cbl-sast-0631.html

If you uninstalled the plugin it could be crashing, start by looking here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

It could be in a VM XML.

You're not using parity, only thing you can do is a new config (tools -> new config), and re-assign the array devices as you want, any data on old disk1 will be lost.

That disk is failing to initialize: Jul 11 20:54:30 Gunhaver kernel: sd 7:0:7:0: Power-on or device reset occurred Jul 11 20:54:30 Gunhaver kernel: sd 7:0:7:0: Device offlined - not ready after error recovery Jul 11 20:54:30 Gunhaver kernel: sd 7:0:7:0: rejecting I/O to offline device Jul 11 20:54:30 Gunhaver kernel: sd 7:0:7:0: [sdk] Read Capacity(16) failed: Result: hostbyte=0x01 driverbyte=0x00 Jul 11 20:54:30 Gunhaver kernel: sd 7:0:7:0: [sdk] Sense not available. Jul 11 20:54:30 Gunhaver kernel: sd 7:0:7:0: [sdk] Read Capacity(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Jul 11 20:54:30 Gunhaver kernel: sd 7:0:7:0: [sdk] Sense not available. Jul 11 20:54:30 Gunhaver kernel: sd 7:0:7:0: [sdk] 0 512-byte logical blocks: (0 B/0 B) Jul 11 20:54:30 Gunhaver kernel: sd 7:0:7:0: [sdk] 0-byte physical blocks Jul 11 20:54:30 Gunhaver kernel: sd 7:0:7:0: [sdk] Write Protect is off Jul 11 20:54:30 Gunhaver kernel: sd 7:0:7:0: [sdk] Mode Sense: 00 00 00 00 Jul 11 20:54:30 Gunhaver kernel: sd 7:0:7:0: [sdk] Asking for cache data failed Jul 11 20:54:30 Gunhaver kernel: sd 7:0:7:0: [sdk] Assuming drive cache: write through Jul 11 20:54:30 Gunhaver kernel: sd 7:0:7:0: [sdk] Attached SCSI disk Try connecting it to the onboard SATA controller instead.

You can't, single profile requires all drives, if one drive fails the whole pool is gone, data is distributed to all devices evenly in 1GiB chunks, so a single file can end up in all the devices.

The error above is from the Docker folder plugin, update or remove it.

First make sure all plugins are up to date, if yes you can remove them all and then add one by one until you find the culprit then please report that in the appropriate plugin support thread.