JorgeB

This is enough, single stream is default

For testing you should use a single stream, and if all is working correctly it still should give close to line speed.

There are issues with that disk since early on the boot process, swap cables with another one (power + SATA) and see if it makes any difference, also and IIRC that model is susceptible to the 3.3v issue.

If 2.5GbE is currently not supported by the driver I would expect it would be in the near future, LT is currently using the Realtek provided drivers, so they are the ones that need to implement Linux support.

I don't remember disk settings being reset with the update, but not entirely sure, note that they are reset after a new config.

Oh, I see, you were talking about 2.5GbE support, that I don't know, very few people with 2.5GbE, don't remember anyone with 2.5GbE capability posting about that NIC in the forum.

Problems with the cache device: Sep 1 06:07:40 Tower kernel: ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Sep 1 06:07:40 Tower kernel: ata1.01: failed command: WRITE MULTIPLE EXT Sep 1 06:07:40 Tower kernel: ata1.01: cmd 39/00:d0:e0:ce:0e/00:02:00:00:00/f0 tag 0 pio 368640 out Sep 1 06:07:40 Tower kernel: res 51/84:01:00:00:00/84:00:00:00:00/f0 Emask 0x10 (ATA bus error) Sep 1 06:07:40 Tower kernel: ata1.01: status: { DRDY ERR } Sep 1 06:07:40 Tower kernel: ata1.01: error: { ICRC ABRT } Sep 1 06:07:40 Tower kernel: ata1: soft resetting link Sep 1 06:07:40 Tower kernel: ata1.01: configured for PIO0 Sep 1 06:07:40 Tower kernel: sd 1:0:1:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Sep 1 06:07:40 Tower kernel: sd 1:0:1:0: [sdf] tag#0 Sense Key : 0xb [current] Sep 1 06:07:40 Tower kernel: sd 1:0:1:0: [sdf] tag#0 ASC=0x47 ASCQ=0x0 Sep 1 06:07:40 Tower kernel: sd 1:0:1:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 00 0e ce e0 00 02 d0 00 Sep 1 06:07:40 Tower kernel: print_req_error: I/O error, dev sdf, sector 970464 It's set to IDE mode, set it to AHCI, also check connections.

Yes, as long as current one is formatted with btrfs (default).

Please post diags after booting the beta.

There's a plugin for that: https://forums.unraid.net/topic/70783-plugin-mover-tuning/

Reboot and please post new diags after array start.

Docker image is corrupt, you can easily recreate it.

Best way is to replace the cables, especially power.

Please post the diagnostics after doing this but before rebooting: Tools -> Diagnostics

No, as along as it doesn't increase, if it does replace SATA cable. You can start restoring the other config files, everything that was inside the config folder, do it a few files at a time to see if you find what was causing the issue, more info on which file does what here.

If you have vdisks there mover won't keep them sparse, you can use cp --sparse=always to "resparsify"

2. in IT mode.

The problem is with disk7 but the disk looks good, so first check/replace cables, especially the power cable.

Note also that if you were already using a pool with UD you could import it directly.

This.

It should.

NVMe dropped offline: Sep 1 22:15:36 Tower kernel: nvme nvme0: I/O 92 QID 1 timeout, aborting Sep 1 22:15:36 Tower kernel: nvme nvme0: I/O 224 QID 2 timeout, aborting Sep 1 22:15:36 Tower kernel: nvme nvme0: I/O 116 QID 3 timeout, aborting Sep 1 22:15:36 Tower kernel: nvme nvme0: I/O 90 QID 6 timeout, aborting Sep 1 22:16:06 Tower kernel: nvme nvme0: I/O 92 QID 1 timeout, reset controller Sep 1 22:16:37 Tower kernel: nvme nvme0: I/O 1 QID 0 timeout, reset controller Sep 1 22:17:39 Tower kernel: nvme nvme0: Device not ready; aborting reset Some reports that the newer kernel on the latest Unraid beta helps with this on Ryzen boards.

Difficult to say without more details, do you have a monitor connected or can get diags?

Use the same flashdrive, or you can waste a key replacement.

Backup current flash, then recreate from scratch (on the same flash) and restore just the key and super.dat, both are on the config folder.