JorgeB

Diags are just after rebooting, so not much to see, you can try this.

Start here.

Order doesn't matter for the cache pool, just make sure all members are assigned, and parity valid check box if for the array only. No risk, also since there was only one data disk parity is a mirror of that, so in this case you can also use either one as parity/data.

There are some known issues with Macs and SMB, I'm not a Mac user, but if you search the forum or even google you might find some things that help.

That is almost certainly not the problem, I would guess that over 99% of drives used with Unraid are 512E, and they perform as expected, and they should as long as the partitions are 4k aligned, which Unraid does by default. Posting the diags might give some clues on the actual problem.

Docker image is corrupt, delete and re-create.

Try adding more RAM, this might also help.

Please use the existing docker support thread:

This might help.

If another disk failed during the rebuild of disk12 the rebuilt disk will be corrupt, you can still try a filesystem check, though even if all looks well after that there will likely still be corrupt files.

It should work there, try it.

Specs say: Bus type PCI Express 2.0 (2.5 GT/s) Which is strange since 2.5GT/s is PCIe 1.0, in any case and IIRC it's a known issue those NICs.

Stats are reset with all reboots, so it's not that for sure, and there are problems with various devices, including both cache devices, e.g.: Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] 40961 512-byte logical blocks: (21.0 MB/20.0 MiB) Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] Write Protect is off Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] Mode Sense: 7f 00 00 08 Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] tag#1374 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] tag#1374 CDB: opcode=0x28 28 00 00 00 00 00 00 00 01 00 Jul 15 12:50:51 UNRAID kernel: print_req_error: I/O error, dev sdi, sector 0 Jul 15 12:50:51 UNRAID kernel: Buffer I/O error on dev sdi, logical block 0, async page read Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] tag#1375 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] tag#1375 CDB: opcode=0x28 28 00 00 00 00 01 00 00 01 00 Jul 15 12:50:51 UNRAID kernel: print_req_error: I/O error, dev sdi, sector 1 Jul 15 12:50:51 UNRAID kernel: Buffer I/O error on dev sdi, logical block 1, async page read Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] tag#1376 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] tag#1376 CDB: opcode=0x28 28 00 00 00 00 02 00 00 01 00 Jul 15 12:50:51 UNRAID kernel: print_req_error: I/O error, dev sdi, sector 2 SSDs are best not connected to a SAS2 LSI since trim might not work, it's also on a very old firmware, could also be a power/connection problem.

Install the Tips and Tweaks plugin and try changing some of the NIC settings, there are some reports that performance with those NICs is better with NIC Offload disable.

That usually happens when the flash drive drops offline, if it happens again grab the diags before rebooting.

Please post the diagnostics: Tools -> Diagnostics, you can also run an extended SMART test on that disk.

NIC isn't loading a driver, try v6.9-beta25

No, it's after append and before initrd, like so: That should be harmless.

If the drives are not detected by the LSI BIOS the same will be the case for Unraid, try a different cable.

It was reported on the log as an actual media error, and SMART suggests the disk has seen better days, still and since the SMART test passed it's OK for now, but keep an eye on these attributes, if they keep increasing it will likely fail again soon: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 501 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 41 P.S. you also have an issue with on one of your cache devices (cache1) Jun 20 23:10:51 Tower kernel: sd 7:0:2:0: [sdj] tag#5577 CDB: opcode=0x28 28 00 07 8b 60 68 00 00 28 00 Jun 20 23:10:51 Tower kernel: scsi target7:0:2: handle(0x000b), sas_address(0x4433221102000000), phy(2) Jun 20 23:10:51 Tower kernel: scsi target7:0:2: enclosure logical id(0x500605b005d921f0), slot(2) Jun 20 23:10:51 Tower kernel: sd 7:0:2:0: task abort: SUCCESS scmd(00000000f0051dde) Jun 20 23:10:51 Tower kernel: sd 7:0:2:0: attempting task abort! scmd(00000000c3de18bf) Jun 20 23:10:51 Tower kernel: sd 7:0:2:0: [sdj] tag#5576 CDB: opcode=0x28 28 00 07 8b 60 40 00 00 20 00 Jun 20 23:10:51 Tower kernel: scsi target7:0:2: handle(0x000b), sas_address(0x4433221102000000), phy(2) Jun 20 23:10:51 Tower kernel: scsi target7:0:2: enclosure logical id(0x500605b005d921f0), slot(2) Jun 20 23:10:51 Tower kernel: sd 7:0:2:0: task abort: SUCCESS scmd(00000000c3de18bf) Jun 20 23:10:51 Tower kernel: sd 7:0:2:0: Power-on or device reset occurred Jun 20 23:10:51 Tower kernel: repair_io_failure: 5 callbacks suppressed Jun 20 23:10:51 Tower kernel: BTRFS info (device sdj1): read error corrected: ino 2781520 off 1757184 (dev /dev/sdj1 sector 275203400) Jun 20 23:10:51 Tower kernel: BTRFS info (device sdj1): read error corrected: ino 253968 off 11206307840 (dev /dev/sdj1 sector 70707144) Jun 20 23:10:51 Tower kernel: BTRFS info (device sdj1): read error corrected: ino 253968 off 11206438912 (dev /dev/sdj1 sector 70919640) Jun 20 23:10:51 Tower kernel: BTRFS info (device sdj1): read error corrected: ino 253968 off 11206324224 (dev /dev/sdj1 sector 70768960) Jun 20 23:10:51 Tower kernel: BTRFS info (device sdj1): read error corrected: ino 253968 off 11206303744 (dev /dev/sdj1 sector 70605544) Jun 20 23:10:51 Tower kernel: BTRFS info (device sdj1): read error corrected: ino 253968 off 11686825984 (dev /dev/sdj1 sector 126595704) Jun 20 23:10:51 Tower kernel: BTRFS info (device sdj1): read error corrected: ino 253968 off 11687796736 (dev /dev/sdj1 sector 126575096) Jun 20 23:10:51 Tower kernel: BTRFS info (device sdj1): read error corrected: ino 253968 off 11206344704 (dev /dev/sdj1 sector 70877376) Jun 20 23:10:51 Tower kernel: BTRFS info (device sdj1): read error corrected: ino 253968 off 11206340608 (dev /dev/sdj1 sector 70872680) Jun 20 23:10:51 Tower kernel: BTRFS info (device sdj1): read error corrected: ino 253968 off 11206299648 (dev /dev/sdj1 sector 70445032) Replace cables or connect it to a different controller.

There's a known issue with those NICs, it's not detected on most PCIe 2.0 or newer slots, e.g.: https://www.dell.com/community/PowerEdge-Hardware-General/Intel-PRO-1000-PT-PCI-E-Quad-EXPI9404PTBLK-T110/td-p/3881138

Pool should show as new before array start, not after, now it's showing as unmountable, also those very high write numbers suggest a problem, please post the diagnostics: Tools -> Diagnostics

SMART looks fine, complete diags might show something more.

This is normal after a new config, as long as all the original pool members are assigned the original pool will be imported (there can't be a "all data on this device will be deleted after array start" or similar warning for any of the devices.

That won't matter, it will still show any errors and the filenames on the syslog, just when you try to access the file it shows the checksum error but not the filename.