JorgeB

The NIC should auto-link at the max supported speed, if it's not the cable/port it could be a switch or NIC problem.

That's a lot for 10TB, it should be around 18 to 20 hours, unless there's some bottleneck or you have a lot of different size devices in the array.

You should use for stability, I remember at least one user had issues without that cable connected. That one is IT mode only, so should be just plug and play.

Answer for that is in many places, including the wiki and the FAQ on this sub-forum.

Mover can't move data directly from one pool to another, you'd need to fist move it to the array, then to the new pool.

This is a SATA controller problem, quite common with Ryzen boards: Nov 30 13:48:22 Tower kernel: ahci 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x001a address=0x7fffffc0000 flags=0x0000] Nov 30 13:48:22 Tower kernel: ahci 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x001a address=0x7fffffc0f80 flags=0x0000] Using the latest beta usually helps, but you're already using the current one, so look for a BIOS update or disable IOMMU if not needed.

You can force a rebuild but first thing is to check if there's really a problem with disk7, swap cables with another disk, if still missing please post the diagnostics: Tools -> Diagnostics

You can try this and post that log after a crash.

Macvlan call traces are usually the result of having dockers with a custom IP address, more info here:

You can try this and post that log after a crash.

Difficult for me to say without seeing the diags to see current state.

This shows the supported speeds, including gigabit. But this shows it's only linking at 100Mbits, try a different cable or switch/port.

Yes.

Please don't double post, see reply in the other thread.

See here.

Depends if was kicked out of the pool and it re-balanced without it or not, if yes just add it back and it will be re-balanced again, if not you can make Unraid forget the old pool by unassigning all devices and starting the array, then re-assign them all and run a scrub and check that all errors were corrected, in doubt would need to see the diags, but about to leave for the rest of the day.

Are you using the docker folder plugin? If yes try without it, you should also always post the diagnostics when making a bug report.

Regular SMART tests were not really needed in the past with Unraid since a parity check is for all purposes the same as an extended test, cache devices are usually SSDs so also not really a need for SMART tests and SMART test monitoring, now with multiple pools it is some times good the run regular SMART tests (if using spinners) on those, it's possibly something that could be improved in the future, for now I have a script running an extend test for those drives once a month and it emails me the results. No, you'll need to stop the array, also make sure the removed device is not still part of the pool, if it is and you added it back it will be wiped (there's a warning when assigned).

Nope, it will show the last result on the device page, but won't notify if it fails: Possibly because since SMART tests need to be run manually one expects the user to check the results.

Best bet is to ask in the existing plugin support thread.

Cache device dropped offline again: Nov 30 09:31:45 Tower kernel: ata6: COMRESET failed (errno=-16) Nov 30 09:31:45 Tower kernel: ata6: reset failed, giving up Nov 30 09:31:45 Tower kernel: ata6.00: disabled Nov 30 09:31:45 Tower kernel: ata6: EH complete If you haven't yet replace both cables, if it continues to drop it could just be a bad SSD.

Most VMs should work after the upgrade, mine did, but there could be exceptions.

It will notify you if there's any "FAILING NOW" SMART attribute, and system notifications are enable.

Yes, for writes you'd need to enable turbo write, also note that HDD speed is not constant, they are much faster when empty and the outer tracks are used, they will get progressively slower as they fill up and start using the inner tracks, usually around half the speed as the outer tracks.

Cache filesystem is corrupt, you'll need to reformat it, some data recovery options here if needed.