trurl

Have you looked at the Settings for the plugin?

Wasn't really necessary to New Config, but that didn't hurt anything. Don't know about your missing data. My guess would be user error of some kind.

unRAID only requires a clear disk when it is ADDED to a NEW slot in an array that already has parity. This is so parity will remain valid. Replacement disks do not have to be clear since they will be completely overwritten from the parity calculation anyway. People often preclear new disks just to test them even if they don't require a clear disk, but this testing can be done on another computer using other software. The disk manufacturers have free downloads for testing disks.

In order to remove the failing disk, you are going to have to stop the copy and shutdown. You could then restart the copy with the missing disk emulated by the rest of the array. Then you could set a New Config without the missing disk and rebuild parity. Is this what you had in mind? If you are reasonably confident in the rest of the disks, and you have good backups of any irreplaceable files, then this might be OK. But you will be working all of the disks to emulate the missing disk, you will be operating without any protection, and it will still be slow since all disks must be read, then a data disk and parity disk must be written. It shouldn't be as slow as what you are doing now, and it might even be more reliable. I think there is a good chance unRAID will disable the failing disk before it ever completes the copy anyway. I often recommend not writing to any disk in the array when it is compromised, and instead copy data to another system or an unassigned disk. That way parity isn't written and there is less disk activity.

I would Any time you have an unreliable disk in the array you are effectively operating without protection, because ALL disks are required to rebuild a disabled or missing disk. Parity alone cannot reconstruct any data.

When you said the disk was failing, did you mean unRAID had disabled the disk (does it have a red X next to it)? Where are you seeing 27000 reallocated? I'm not sure a number that large for that attribute is actually possible. Is the disk with the read error the same disk with the large number of reallocations? Are any read/write errors being displayed for any other disks?

All writes to a disk in the parity array also updates the parity disk at the same time. This is a very basic principle of unRAID that you should always be aware of.

Unless he was using turbo write, in which case parity might be invalid since it would have been calculated by reading the bad disk.

I understand why you might want to do it this way, but trying to do extensive file operations with an unreliable disk in the array is definitely not recommended. If you were moving instead of copying, or if you were using turbo write, there is a very good chance that you would compromise parity and then rebuilding would be compromised. What console command are you using? Have you tried just aborting it with control-c?

You'll need the Unassigned Devices plugin for this.

Writes to disks in the parity array must read the data and parity drives, calculate parity change, then write data and write parity. Also, applications will often keep the drive with their working data spinning, since they are read and written often. For these reasons, most use a cache drive for applications.

Yes cache is part of user shares

You can leave Windows and the network completely out of the loop by using Krusader docker or the builtin mc (Midnight Commander) to copy files on the server.

Why do you think parity sync is needed at step 7?

1) Copy the small disks to other disks, remove them, New Config and rebuild parity. 2 ) Add a new larger disk, format as XFS. 3) Copy RFS disk to XFS disk. 4) Reformat RFS disk to XFS. Repeat 3 and 4 as needed.

Have you actually read any of this thread? I know it is long but a lot of it is just repetitive. The basic concepts are probably covered on every page. Go back one page and study it and see if you have any questions.

Parity doesn't have a filesystem. If you do everything correctly parity will be maintained and won't need to be rebuilt. Repeat 2 and 3 as needed. If you start with the drives with the most used then work your way down you shouldn't have any problem copying a disk to the most recently formatted disk.

Your screenshot indicates it is rebuilding a data disk. Let it finish obviously. Without any idea of how much free space each of your drives has, I would say add a new empty 6TB disk formatted as XFS, then copy your largest drive to it, reformat the drive to XFS, rinse, repeat.

Community Applications plugin is the way you should be installing any app.

Depends on what the "browsing" application is doing. Sometime it will try to get more data than just the directory listing, such as icons and other properties of the files. Only the directories are cached, so if it is trying to also get icons, for example, then it will have to spin up.

I think that was asked before on this thread, and maybe answered.

Have you ever assigned any disks to the array? I think there was an issue where it would check to make sure you weren't trying to clear an array disk, but if there were never any assigned the check failed.

I don't see how. Is it even possible to mount a DVD or BD drive in unRAID?

A fresh plex docker will be fresh; i.e., none of the media has been scanned into the library, there is no metadata, etc. The plex appdata from your old server has all of that. You should be able to just copy it over if your fresh plex docker is configured exactly the same and all of the media has exactly the same path.

See the Docker FAQ linked below. Lots of important information there. The very first article linked in the FAQ will tell you what we need to help you. https://forums.lime-technology.com/topic/57181-real-docker-faq/