trurl

no Unraid disables a disk when a write to it fails. Simple as that. Disks SMART looks OK. Are these on the same controller?

https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive

If the .plg files exist then they should reinstall themselves. In fact, the old installations are probably still on flash, but without the .plg files they won't be loaded on boot. Maybe there is something about the old installations that is breaking something. Each of those .plg files probably has a corresponding subfolder in /boot/config/plugins. You might try deleting those subfolders so they can get a clean install.

Those diagnostics are saying you have 63TB of files in user shares, with lots of user shares with files on the disks. Possibly you are having a browser issue instead. Do you have an adblocker or anything else that might interfere with accessing the webUI? If so, whitelist your server.

Make sure you don't mix disks and user shares when moving or copying.

yes Will work but not recommended.

Maybe one of your apps is storing large files directly in the database.

Very old thread but might as well use it. Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post in this thread.

Check connections then post new diagnostics.

Note that this doesn't mean it won't use any of that "Minimum Free" space. For example, Minimum is set to 4GB. The disk has 5GB remaining, so it can be chosen. You write a 3GB file. Now the disk has 2GB remaining, and won't be chosen again.

Unraid has no way to know how large a file will become when it chooses a disk for it. If a disk has more than Minimum Free (in your case zero), the disk can be chosen, and if the file won't fit you get the error. You should set Minimum Free to larger than the largest file you expect to write to the share. So if you set it to 4GB as suggested, and the disk has less than 4GB remaining when it chooses a disk to write, it will choose another disk.

What about your disabled disk? You must take care of that immediately. Post your diagnostics.

If it works in SAFE mode and not otherwise that suggests a plugin issue. Which plugins were you using? From the command line, what do you get with this? ls -lah /boot/config/plugins/*.plg

I see you did memtest several months ago. Wouldn't hurt to do it again.

Looks good 👍

Post new diagnostics

The config folder on flash contains everything needed to get going just as before from a new install. Since you say you copied that you should be good. Did you do checkdisk on it?

Fixed my post. OK. Now the way you get all your dockers back is with the Previous Apps feature on the Apps page. When you create or edit a container, those settings are stored in a template on flash. The Previous Apps feature will use those templates to create your containers just as you did before. You may have some templates you weren't using anymore but Previous Apps will let you choose which to reinstall. Try that and let us know how it goes.

You will have to recreate your custom docker network. If you were following SpaceInvader video you probably did this at the command line: docker create network proxynet Correction docker network create proxynet

Looks good. Go to Settings - Docker, change docker.img size to 20G, and enable docker. This will recreate docker.img at 20G on cache. You won't have any dockers yet. We will get to that. I'll leave it up to you whether you want to enable VMs now. Did you have any custom docker networks, such as for proxy?

Not sure why you told us this. Restarting the array isn't really necessary and won't get any of the other things taken care of.

Instead of these screenshots and text descriptions, a much more complete and unambiguous way to show us exactly how you have your dockers configured is to post their docker run commands as explained at this very first link in the Docker FAQ:

In order to change the filesystem of a disk, it has to be reformatted. So you would have to get all its data saved somewhere else before you can convert it to xfs.

OK. Let's see what we can do to get your docker / VM configuration off the array. Go to Settings - Docker, disable docker, then delete docker.img from that same page. Leave docker disabled until instructed to enable again. Go to Settings - VM Manager, disable VMs. Leave VMs disabled until instructed to enable again. Go to your User Shares and set appdata, domains, and system shares to Use cache: Prefer. Go to Main - Array Operation and click Move. Wait for it to complete. May take a while if you have a lot of appdata on the array. Then post new diagnostics so we can see how that all turned out.