trurl

@fluffybutt Be sure to take a new backup of flash now that you have reused parity as data. This is exactly the situation where you don't want to use an old backup and have it start writing parity data to your new data (old parity) disk. Has happened to more than one user.

Possibly issue with flash disconnecting. Be sure to boot from a USB2 port. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

Why do you have 500G allocated to docker.img? 20G should be more than enough. You must have one or more applications misconfigured and writing into docker.img instead of to mapped host storage. I am running 17 dockers and they are using less than half of 20G docker.img. But I see you are already using much more than 20G even after restarting. Making docker.img larger won't fix anything, it will just make it take longer to fill. The usual reason for filling docker.img is specifying paths in your applications that don't exactly match the container path in your mappings. Common mistakes are specifying different upper/lower case (linux is case-sensitive) than in your container mappings or specifying a relative path (a path not beginning in /). Also, your system and domains shares are on the array instead of all on cache where they belong, like your appdata. appdata, domains, system should be all on cache and set to stay on cache. If you have these on the array, your dockers / VMs will have their performance impacted by slower parity writes, and they will keep array disks spinning since these files will always be open. Do you actually have any VMs? Which dockers do you use?

It was there in the Diagnostics in your first post in this thread.

So when you say "rename and reorganize", you are just talking about the folders that contain the hardlinks?

Pretty sure this will break the torrent. How could it not since the torrent relies on nothing being changed to maintain integrity. Unless you planned to start a new torrent instead, which wouldn't contribute to your seed ratio on the original.

I think you can just unassign it and start the array. If it says it is missing then you would have to New Config without it, which is what you would have to do to remove disk2, except in the case of removing parity2 you wouldn't have to rebuild parity.

Just noticed you have dual parity. Probably make more sense to use parity2 to replace disk1

It probably would. Let's see what the test says, it will take several hours.

I wasn't trying to give you an idea about removing disk 2. If you don't think you can trust disk 1 why would you trust it for parity rebuild?

As you discovered, you can't remove disk2. You would have to rebuild parity without disk2 to get it out of the array. Which would require using disk1 for the parity rebuild. Anyway, 8 Reallocated isn't necessarily a reason to replace. Run an extended SMART test on it and if it passes and the count doesn't increase just acknowledge the warning by clicking on it on the Dashboard.

Individual docker containers are not a "feature" of the Unraid OS. I am moving have moved this to Docker Engine where maybe one of the docker developers will help.

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

Seems like everyone else that had this allowed themselves to be hacked. Are you sure that isn't what happened with you?

By looking in your post history I found an older diagnostics zip file. Let me see if I can fill in the blanks left in your post. After upsizing parity, you took the old parity disk and added it as a new disk3. Is that correct?

Still a good idea even if this was working correctly.

If you normally do monthly parity check on the first of the month like I do then just let it run at the scheduled time

I think this is the relevant point Enter diagnostics at the command line, wait for it to complete, then enter shutdown Then put your flash in your PC, get the diagnostics zip file from it, and attach it to your NEXT post in this thread.

Anyway, I am just being cautious with blowing away any libvirt.img that might be on cache or disk2. It is fine to get rid of docker.img wherever it is because its contents are easily downloaded again. Since your system files on disk2 have newer timestamps than those on cache I assume these are the ones you want to keep. But I thought cache had precedence over array disks when there are duplicates, so I am not sure which is being used. So what I am proposing is disabling VM Manager and Docker in Settings so these files won't be open and mover can move them. Then, rename system folder on cache to system1 (instead of deleting) so it won't be a duplicate anymore and mover can move system from disk2 to cache. Then, run mover so the system files on disk2 get moved to cache. Then, enable VM Manager and Docker in Settings and see if your dockers and VMs are working OK. If so, it is safe to get rid of that system1 folder on cache since it isn't needed.

Not exactly sure where you are looking to get that, but cache is part of user shares, so if there are files on cache for the user share then it is expected that the user share would be larger than just those files on disk2.

Are you sure that isn't just the RAM buffer? Does it stay at that speed all the way to the end of a very large file? How much RAM does your server have?

Are you on the "All Activity" page? It says "This stream auto-updates"

It looks like the system share on disk2 has the current version of these things. Mover won't move duplicates, so you may need to get rid of those on cache before you can get them moved to cache. Or just rename the system folder on cache to system1 for example. Do you know how to work with files directly on the disks?

Did you ever run New Permissions on the Tools menu? New Permissions shouldn't be used on appdata because it could change the owner and permissions the applications set for themselves. Why have you allocated 40G to docker.img? Have you had problems filling it? 20G should be more than enough and anytime I see a user with more than that I suspect they have made it that large because they have been filling it. Making it larger will not help, it will just make it take longer to fill. The usual reason for filling docker.img is application writing to a path that isn't mapped to host storage. The most common mistakes are specifying a path in the application that doesn't match the container path in upper/lower case, or specifying a relative path. I am running 17 dockers and they are using less than half of 20G docker.img Any idea what these are about? Aug 28 16:37:58 REBELDATA rpc.mountd[21741]: No host name given with /mnt/user/videos (ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=105,anonuid=65534,anongid=65534,sec=sys,secure,root_squash,no_all_squash), suggest *(ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=105,anonuid=65534,anongid=65534,sec=sys,secure,root_squash,no_all_squash) to avoid warning Aug 28 16:37:58 REBELDATA rpc.mountd[21741]: No host name given with /mnt/user/tv (ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=109,anonuid=65534,anongid=65534,sec=sys,secure,root_squash,no_all_squash), suggest *(ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=109,anonuid=65534,anongid=65534,sec=sys,secure,root_squash,no_all_squash) to avoid warning Aug 28 16:37:58 REBELDATA rpc.mountd[21741]: No host name given with /mnt/user/photos (ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=101,anonuid=65534,anongid=65534,sec=sys,secure,root_squash,no_all_squash), suggest *(ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=101,anonuid=65534,anongid=65534,sec=sys,secure,root_squash,no_all_squash) to avoid warning Aug 28 16:37:58 REBELDATA rpc.mountd[21741]: No host name given with /mnt/user/music (ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=106,anonuid=65534,anongid=65534,sec=sys,secure,root_squash,no_all_squash), suggest *(ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=106,anonuid=65534,anongid=65534,sec=sys,secure,root_squash,no_all_squash) to avoid warning Aug 28 16:37:58 REBELDATA rpc.mountd[21741]: No host name given with /mnt/user/movies4k (ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=102,anonuid=65534,anongid=65534,sec=sys,secure,root_squash,no_all_squash), suggest *(ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=102,anonuid=65534,anongid=65534,sec=sys,secure,root_squash,no_all_squash) to avoid warning Aug 28 16:37:58 REBELDATA rpc.mountd[21741]: No host name given with /mnt/user/movies (ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=110,anonuid=65534,anongid=65534,sec=sys,secure,root_squash,no_all_squash), suggest *(ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=110,anonuid=65534,anongid=65534,sec=sys,secure,root_squash,no_all_squash) to avoid warning Aug 28 16:37:58 REBELDATA rpc.mountd[21741]: No host name given with /mnt/user/flac (ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=107,anonuid=65534,anongid=65534,sec=sys,secure,root_squash,no_all_squash), suggest *(ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=107,anonuid=65534,anongid=65534,sec=sys,secure,root_squash,no_all_squash) to avoid warning