trurl

Wifi not supported. Use ethernet

Do you mean GB?

Not necessarily related, but SSDs in the parity array cannot be trimmed, and can only be written at parity speed.

Attach Diagnostics to your NEXT post in this thread.

Looks like you attached the file before it had finished downloading

If the SMART report is bad enough, you should rebuild it to a new disk. Then you don't need to move anything. If you don't want to replace the disk, then you could move it but that might not be the best solution depending on other details. Copy instead of move would probably be more reliable. And if you didn't replace the disk, then you would need to New Config and rebuild parity without it. You shouldn't keep unreliable disks in the array. Also, you must always have another copy of anything important and irreplaceable. Parity is not a substitute for backups. If you have an actual problem you want advice on, Attach diagnostics to your NEXT post in this thread.

Attach Diagnostics to your NEXT post in this thread.

You should keep some things on fast pool, appdata, domains, system shares. Mover can move the rest to the array. Doesn't matter if the pool is actually named "cache" for it to cache user shares. https://docs.unraid.net/unraid-os/manual/shares/user-shares/ If you want more detailed advice Attach Diagnostics to your NEXT post in this thread.

Unassigned Devices plugin can read NTFS. Dynamix File Manager will let you work with folders and files directly on the server.

Connection problems with parity2

https://docs.unraid.net/unraid-os/manual/security/good-practices/ also

If you don't have parity no need to clear or rebuild. If you want to keep any data from those small disks just New Config with the disks you want in the array, and use Unassigned Devices to copy the data from those small disks to the array.

Does it work now?

Post docker run

And you would still have to rebuild parity to get those empty disks out of the array.

Probably simpler, less error-prone, and maybe not much more disk activity, to just rebuild each onto the larger disk. Your plan will move files to larger disks, which involves writing the new disk and updating parity, plus deleting from the source disk and updating parity. Plus rebuild means you will still have the original disks with their contents in case of problems, or even as backups.

You could New Config without them and rebuild parity.

If nothing was on it then I guess not

Nothing can move open files. You have to disable Docker in Settings before you can work with that.

Did you have a current flash backup?

Also the pools folder in config has the assignments for any pools.

Was your flash backup missing config/super.dat?

If you want to "fill the gap" where disk4 was by changing the assignments do so now, then While parity is rebuilding, on Main - Array Devices, you should see lots of Reads from all assigned data disks, lots of Writes to both parity disks, zeros in the Errors column. If it looks like there are problems, post new diagnostics.

right Do you have adblocker or anything else that might interfere?