JorgeB

You can move from the old drives mounted with UD to a user share on the new array.

Copying smaller files is always slower, even from SSD to SSD, but spinners will be even slower.

Should be fine, but if you're going to use it with SATA drives don't forget the max cable length is 1 meter, since it doesn't have an expander.

Check filesystem on disk3, but note that a new config is not usually the right thing to after a disk drops, and you now need to run a correcting check.

Docker image is corrupt, delete and re-create, also due to a previous bug your cache pool is not redundant, see here.

If the extended SMART test passes the parity check should also complete without read errors.

That suggests there could be a real problem with the NVMe device, try the copy again, if you get the same errors probably not much more you can do, you can try reformatting the device but any more similar errors probably best to replace it.

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.