JorgeB

Current pool is a mess with multiple profiles: Overall: Device size: 1.82TiB Device allocated: 388.28GiB Device unallocated: 1.44TiB Device missing: 0.00B Used: 365.34GiB Free (estimated): 746.54GiB (min: 744.60GiB) Data ratio: 1.99 Metadata ratio: 1.80 Global reserve: 170.03MiB (used: 0.00B) Data Data Data Metadata Metadata Metadata System System System Id Path single RAID1 DUP single RAID1 DUP single RAID1 DUP Unallocated -- --------- ------- --------- ------- --------- --------- -------- -------- -------- -------- ----------- 1 /dev/sdd1 1.00GiB 188.00GiB 2.00GiB 1.00GiB 3.00GiB 2.00GiB 32.00MiB 96.00MiB 64.00MiB 734.33GiB 2 /dev/sde1 - 188.00GiB - - 3.00GiB - - 96.00MiB - 740.42GiB -- --------- ------- --------- ------- --------- --------- -------- -------- -------- -------- ----------- Total 1.00GiB 188.00GiB 1.00GiB 1.00GiB 3.00GiB 1.00GiB 32.00MiB 96.00MiB 32.00MiB 1.44TiB Used 1.50MiB 182.29GiB 0.00B 512.00KiB 387.03MiB 0.00B 0.00B 48.00KiB 0.00B You should backup and recreate with the single SSD.

Difficult to say, only that Realtek NIC drivers have been hit-and-miss for years with Linux, that's why we recommend using an Intel NIC whenever possible, much less likely to run into trouble.

That won't work with all SMR drives, SMR drives from Seagate and Toshiba look normal on speed tests, even before use, at least the ones I tested with, only WD drives do that, likely firmware related.

Looks like a cable problem, replace SATA cable.

Both disks share the same Asmedia controller and dropped at the same time: Aug 17 21:17:17 NAS kernel: ata8: softreset failed (1st FIS failed) Aug 17 21:17:17 NAS kernel: ata8: reset failed, giving up Aug 17 21:17:17 NAS kernel: ata8.00: disabled Aug 17 21:17:17 NAS kernel: ata8: EH complete Aug 17 21:17:17 NAS kernel: ata7: softreset failed (1st FIS failed) Aug 17 21:17:17 NAS kernel: sd 8:0:0:0: [sdh] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Aug 17 21:17:17 NAS kernel: sd 8:0:0:0: [sdh] tag#1 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Aug 17 21:17:17 NAS kernel: print_req_error: I/O error, dev sdh, sector 0 Aug 17 21:17:17 NAS kernel: ata7: reset failed, giving up Aug 17 21:17:17 NAS kernel: ata7.00: disabled Asmedia controllers usually work fine with Unraid, but there could be an actual problem with it, that or the disks for example share a power splitter/cable with issues.

Try another NIC if available, ideally from Intel.

Yes, you can also rename the .plg extension to anything else.

It might not need rebuilding, but it won't hurt.

Probably the easiest way.

This is a fairly typical problem with the SATA controller on Ryzen boards, there are reports that updating to the latest beta helps due to the much newer kernel, disabling IOMMU should also help if it's not needed. That's OK but note that the rebuilt disk will be corrupt once the errors started.

Cache device dropped offline: Aug 19 03:47:16 Tower kernel: ata5: hard resetting link Aug 19 03:47:21 Tower kernel: ata5: COMRESET failed (errno=-16) Aug 19 03:47:21 Tower kernel: ata5: reset failed, giving up Aug 19 03:47:21 Tower kernel: ata5.00: disabled Aug 19 03:47:21 Tower kernel: ata5: EH complete With SSDs this is usually a connection/cable problem.

You are excluding all disks from the user shares, with the array stopped go to Settings -> Global Share Settings -> Excluded disks and unselect them all.

Disk dropped offline and then reconnected with a different ID: Aug 17 03:41:35 NAS kernel: sd 5:0:4:0: attempting task abort! scmd(00000000389ba74e) Aug 17 03:41:35 NAS kernel: sd 5:0:4:0: [sdf] tag#118 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Aug 17 03:41:35 NAS kernel: scsi target5:0:4: handle(0x000e), sas_address(0x50030480013831f5), phy(21) Aug 17 03:41:35 NAS kernel: scsi target5:0:4: enclosure logical id(0x50030480013831ff), slot(9) Aug 17 03:41:35 NAS kernel: sd 5:0:4:0: device_block, handle(0x000e) Aug 17 03:41:37 NAS kernel: sd 5:0:4:0: device_unblock and setting to running, handle(0x000e) Aug 17 03:41:37 NAS kernel: sd 5:0:4:0: [sdf] Synchronizing SCSI cache Aug 17 03:41:37 NAS kernel: sd 5:0:4:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Aug 17 03:41:37 NAS rc.diskinfo[8980]: SIGHUP received, forcing refresh of disks info. Aug 17 03:41:38 NAS kernel: scsi 5:0:4:0: task abort: SUCCESS scmd(00000000389ba74e) Aug 17 03:41:38 NAS kernel: scsi 5:0:4:0: rejecting I/O to dead device Could be a connection issue, but SMART is also showing some issues, you should run an extended SMART test, also see here for better pool monitoring.

Depends mostly on the disk size, around 2/3 hours per TB.

Yes, SAS1 LSI HBAs are limited to 2TiB, you can use the Intel SATA ports if available or get a SAS2/3 LSI HBA.

That suggests you're using a controller with a 2TiB max size limit, please post the diagnostics.

Just this.

Still much more likely to be the cable (or port) than the drive, you should try another cable in a different port.

Only this Exos model is SMR:

Try running the server as a basic NAS for a couple of days, boot in safe mode and disable all dockers/VMs, if it still crashes like that you likely have a hardware problem, if it doesn't start enabling services one by one.

Those are CRC errors, usually a bad SATA cable, but could also be the controller or in extremely rare cases the disk itself.

Those 14TB Exos are CMR.

Please post the diagnostics: Tools -> Diagnostics

There are plugins for that. IPMI plugin has fan control for supported boards, there's also the Dynamix System Autofan.

Please post the diagnostics: Tools -> Diagnostics