trurl

It can only detect that the hash doesn't match. It isn't a backup or a way to reconstruct data.

Only those users listed as "Administrator" work for limetech. Squid is definitely not one of those. That other user you mentioned there doesn't seem to exist, perhaps a typo. There are only a few. You probably won't encounter any of them on the vast majority of threads. Just to clarify some technical details. Dockers are typically applications. They run inside a container, which you can think of as a small virtual machine with a single purpose. Other than using Unraid for storage and networking, dockers are separate things, and will often have their own webUI. Their support threads are in the Docker Support subforum. Plugins, of which this support thread is one example, are typically enhancements to Unraid functionality. They are usually accessed as addons to the Unraid webUI. Their support threads are in this subforum, Plugin Support. You can assume that all dockers except for those few in the official limetech repository, and all plugins, are written by other Unraid users for free to make Unraid more useful to everyone.

Just like almost all of the help and advice you get on the forum, almost all of the "addons" for Unraid are done by fellow users without any compensation except the occasional thanks and possibly donations. Many of these addons have an associated Donate button on the Apps page.

You can, of course, access the Unraid webUI from any web browser on another computer that has more resolution, even a VM running on Unraid.

The suggestion is in the CA screenshot you posted.

You already have a container by that name.

What version Unraid? See requirements in 1st post.

Not much can be done about how long it takes to check every bit of 10TB. If 20 hrs is what it takes on your system, that is what it takes. And that time seems good to me for that size parity. I only have 6TB and it takes a little over 14 hours.

Rebuilding a data disk or rebuilding a parity disk is exactly the same parity calculation. The concept of parity is used in many ways by computers and communications. Parity is simply a bit that allows a missing bit to be calculated from all the other bits. It is really pretty simple and understanding parity makes other things about how Unraid works with the disks easier to understand. The reason we are able to tell you what to do in these situations is mostly because we understand parity, not because we have done exactly the same thing ourselves, or memorized procedures. Here is the wiki on parity: https://wiki.unraid.net/UnRAID_6/Overview#Parity-Protected_Array

If you start the array after assigning a disk to parity, it will build parity on that disk. It can be a new disk, or it can be the same disk. The way you would use the same disk is to start the array with the parity disk unassigned. That would make Unraid update the disk assignments so that no parity is assigned. Then when you assign that disk, it will build parity on it. Stop array Unassign parity Start array with parity unassigned Stop array Reassign parity Start array with parity assigned to build parity Unraid also builds parity by default after a New Config, as long as you don't check the parity valid box.

You apparently removed a disk that had not been cleared so parity was invalid at that point. A correcting parity check will make it valid again, but a parity rebuild would probably have been faster since it doesn't bother to check before rewriting parity. After it corrects parity, you should do a noncorrecting parity check, and that one should give you exactly zero sync errors. If not then further investigation is needed.

Here is the only other thread this user ever posted in: https://forums.unraid.net/topic/77501-complete-noob/ Make of it what you will. It's unclear what problem(s) they were having with their Unraid trial. No doubt the user read other threads here, but I think most would agree they have mischaracterized our community here in this thread. I took a look at the website for the other system they are enamored with. It doesn't look like it has been around long enough for anyone to point to a 2 year old thread or video. The focus there appears to be Virtual Machines. We all know there are other ways to accomplish that feat. There is even a subforum here for users who run Virtual Machines on other platforms, and think the other features of Unraid makes it worthwhile to run in a Virtual Machine.

In fact, you could have removed disk2 (and moved disk3 to the disk2 slot if you wanted) and then New Config and upsize parity all in step 1 and that part would be done and you could then upsize disk3 (or disk2 if you had moved it to that slot). You still have options on how to proceed from here. You can try to preserve parity by using the script again to clear disk2, and then New Config, remove the disk, move disk3 down to slot 2 if you want, and parity would still be valid. Or, you could just New Config without the empty disk2, move disk3 to slot 2 if you want, and let it rebuild parity. Either way will be a similar amount of time. The script has the advantage that parity is valid throughout, but if everything else is working well, and you have backups of anything important and irreplaceable (you should regardless) then there is little risk to rebuilding parity. Let us know what you want to do, and tell us exactly how you plan to proceed so we can make sure you have it all correct.

Are you sure this is what you did? Because that can't possibly be the correct instructions. The folder path /mnt/user/disk2 (not users) is actually a user share named "disk2", not the actual disk2. And that user share named disk2 could exist on any disk. The path for disk2 would be /mnt/disk2. And the path /mnt/users/disk2 would actually be in memory. Based on everything else you said, and those screenshots, I would say that you have rebuilt the empty disk2, not cleared it. It's unclear what if anything the script could have actually done. And, in case you don't know, an empty disk is not a clear disk. An empty disk has a filesystem on it that contains an empty top level folder. A clear disk has nothing but zeros on it, so no filesystem. Personally, I usually recommend people not even bother with that "clear then remove script". It should work if you understand how to use it and do everything correctly, but it doesn't really save any time. Instead, you can just New Config and not assign the disk(s) you want to remove, then let it rebuild parity. And it would certainly be simpler and faster than what you have already done, since you still haven't accomplished anything.

I am assuming here you mean you did a data rebuild each time. Parity sync actually means a rebuild of the parity disk. Perhaps you meant you did a parity check after the data rebuild? What makes you think a parity sync is running? Are you sure your data rebuilds completed? Do you perhaps mean a parity check is running? There shouldn't be a parity sync running, but leaving aside that possible confusion. After you do a New Config, it will give you a parity valid checkbox when you go to Start the array. Since there may be some confusion, it's probably a good idea to hang on to the original disks until you make sure all your data is there.

This plugin actually installs a custom build of Unraid. Updating to a new version of Unraid means you are installing a non-custom build that doesn't have nvidia support.

How are you using those 4 SSDs in Unraid? SSDs are great for the cache pool, but SSDs are not recommended in the parity array.

You should edit your screenshot to get rid of the plex claim token.

In fact, you can see ADP (AdBlock Plus) in his screenshot.

Go To Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

Can your server reach the internet?

You can always go directly to the correct support thread for any of your dockers by simply clicking on its icon and selecting Support.

I use NTFS with this plugin all the time. For simplicity, make sure you only have one partition. Put it in Windows and use Disk Management to get it setup as a single volume NTFS disk, then you shouldn't have any problem mounting it in Unraid with Unassigned Devices.

That version is over a year old. You should make sure ALL your plugins are up-to-date.