JorgeB

That would be cool, but since I don't know what's your backup situation make sure you don't risk your data because of that.

Have you run a single thread iperf test to confirm LAN bandwidth?

Make sure you enabled UEFI boot when creating the flash, or just rename "EFI-" to "EFI"

Unraid doesn't support ZFS, no yet anyway, if you're using the plugin you should use the existing thread for support.

You'd need to manually shrink the array by doing a new config with the old 3 tb disk (copy any missing data written since), re-sync parity to the 8tb disk then repeat the parity swap, but like mentioned it's a lot to ask.

With a single NIC only network.cfg would be re-created, if it isn't it points to a problem with the flash drive, i.e., it's not booting correctly. Yes. Backup current flash, re-create it using the USB tool then restore the config folder.

Most likely, you are using an Asmedia controller with SATA port multipliers and a Marvell controller, both are strongly not recommended for Unraid.

Delete/rename network.cfg and network-rules.cfg both in the config folder, then boot again, you still might need to change the cable to a different NIC depending on witch one gets assigned by default as eth0.

Yes. Just re-enable the service(s)

👍

It could be that it's using a different NIC or the order changed, you can boot with GUI mode and change witch NIC it eth0

Yep, I missed that part, SATA devices work with SAS controllers, but not the other way around.

It might still apply, some backplanes have internal circuitry creating 3.3v, test by putting tape on one of the disks.

Note that max cable length for SATA is 1 meter.

Unraid can't currently spindown SAS devices.

See here for some recovery options, would also recommend to upgrade Unraid first, to latest stable or even latest beta would probably best.

Please post the diagnostics: Tools -> Diagnostics

The best way you could help would be to repeat the procedure, but that's a lot to ask, I took note of your array config and going to try to compare it with other users having the same issue, maybe there will be something in common, though I'm still more inclined of this being caused by the user doing something different during the swap, but can't think of what.

Did you also set the "power supply idle control" to the recommended setting? Other than that it might be a real hardware issue.

A few sync errors are normal after an unclean shutdown.

That's why I recommended the "mover stop" post so it appears at the top of the thread

Then going to lock this one to avoid duplicate replies.

Best bet is to post on the existing Ndivia plugin support thread:

Cache SSD dropped offline: Jun 28 12:21:45 Tower kernel: ata8: hard resetting link Jun 28 12:21:50 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 28 12:21:50 Tower kernel: ata8.00: link online but device misclassified Jun 28 12:22:01 Tower kernel: ata8.00: qc timeout (cmd 0xec) Jun 28 12:22:01 Tower kernel: ata8.00: failed to IDENTIFY (I/O error, err_mask=0x4) Jun 28 12:22:01 Tower kernel: ata8.00: revalidation failed (errno=-5) Jun 28 12:22:01 Tower kernel: ata8: limiting SATA link speed to 3.0 Gbps Jun 28 12:22:01 Tower kernel: ata8: hard resetting link Jun 28 12:22:01 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sdf Jun 28 12:22:06 Tower kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jun 28 12:22:06 Tower kernel: ata8.00: link online but device misclassified Jun 28 12:22:19 Tower kernel: ata8.00: failed to IDENTIFY (I/O error, err_mask=0x100) Jun 28 12:22:19 Tower kernel: ata8.00: revalidation failed (errno=-5) Jun 28 12:22:19 Tower kernel: ata8.00: disabled This is most times a connection problem, if you haven't yet replace both cables (power + SATA) on the SSD, failing that try with a different model SSD, sometimes there are hardware compatibility issues.

Please post the diagnostics: Tools -> Diagnostics