trurl

You should start your own thread and post Diagnostics

Make sure your server has the correct date/time

Even though your syslog goes back many months, I only see one parity check in it. How often do you check parity? Do any of your disks have SMART warnings on the Dashboard page? After a parity check that corrects sync errors I recommend a non-correcting check to make sure there are no sync errors. If there are you still have work to do. Exactly zero is the only acceptable result.

https://wiki.unraid.net/Upgrading_to_UnRAID_v6

When mover runs, it can't move open files. The reason I said to disable dockers for him was so appdata and system shares could be moved to cache. In your case, appdata is already on cache but system share is on the array. System share is where docker.img lives, which contains the executables for all your containers. You want this share to be on cache for performance and so array disks won't stay spunup. But you have system share as cache-yes instead of prefer, which means move to array, and in fact, it is already completely on the array. When you recreate docker.img custom networks need to be recreated.

Parity and parity2 are not interchangeable. Since you are going to be rebuilding parity anyway might as well do it all at once. Make very sure you don't assign any disk with data on it to a parity slot or its data will get overwritten by parity. Stop array. Go to Tools - New Config and keep all assignments. From there it will let you make any changes to disk assignments you want. Reassign disk in parity2 slot (serial ending RV4J) to parity slot, reassign disk in parity slot (serial ending M0TN) to disk4 slot. Leave all other assignments as is. Don't check the box saying parity is valid. Start array to begin parity rebuild. Then it will let you format disk4.

Might save some questions if you would just Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

Is there no disk currently assigned as disk4?

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

Marvell according to that Amazon link

Looks like icydock has separate SATA connections, so the controller for those disks are also on motherboard or else a controller card plugged in to the motherboard. I did notice a Marvell controller in your diagnostics, they are known to cause problems for some time, though they might work if you disable IOMMU (VT-D) in your BIOS.

Disk not reporting SMART. Check all connections, power and SATA, both ends, including splitters. Why is your syslog full of failed login attempts? Are you sharing your network with hackers?

Best to use the support thread for the specific container for help on that.

Looks like the missing disks aren't connected. Are they on the same controller or same power cable?

prefer is the only setting that will move them to cache, but they can't be moved while the files are open, so you have to go to Settings - Docker and disable then run mover before enabling Docker again That only controls how it is accessed over the network, has nothing to do with dockers. You should delete them.

Where exactly are you seeing this button? Doesn't seem like anything to do with Unraid. Post a screenshot.

🖖

The disk has to be rebuilt to enable it again since it is out-of-sync with parity. Safest approach is to replace and keep the original in case of problems, but if we decide the disk is OK it is also possible to rebuild to the same disk if you don't have or don't want to buy another. For WD Reds you should also set it to monitor attributes 1 and 200. Click on the disk to get to its settings and add those Custom attributes. Looks like it recently passed extended SMART test, but it is showing those attributes non-zero, and syslog is showing IDNF and UNC errors. Run another extended test.

Maybe flash problems? If the templates for your installed containers can't be read from flash then those containers will still exist but they can't be worked with in the webUI. Go to the Docker page and move the slider at upper right from Basic to Advanced. Do you see any orphan containers in the list?

Your appdata and system shares both have files on the array.

Shouldn't cause this particular issue, but why is your system share on the array?

No, but the fact that the checks were getting different sectors is what made me suspect RAM. You might try again after checking all connections. Then controller would be next suspect I think. Tell us more about your hardware. Very difficult for us to support a version of Unraid we haven't seen in years. And latest version has a lot more to help us troubleshoot. When you get stable again you should upgrade.

Assuming you have parity you are going to rebuild the replacement so no need to restore.