trurl

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

32 is maximum size for FAT32

RAID is not recommended and can cause numerous problems. Unraid is NOT RAID.

USB, though allowed, is not recommended for the parity array or cache pool due to unreliable connections and other complications with some implementations.

Looks like a browser problem. Clear browser cache, try different browser, try from a different computer,...

Go to Tools - Diagnostics and attach the complete Diagnostics zip file to your NEXT post.

You should NOT use hardware RAID with Unraid. Unraid IS NOT RAID. USB drives are not recommended in the array or cache pool. They can be used with the Unassigned Devices plugin, or you can "shuck" them and use them as regular SATA drives.

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

Disk1 has some pending and other issues. I would replace it. Cache has a large number of reallocated. I would replace that one also. You should see SMART warnings about those disks on the Dashboard. Other disks SMART looks OK. Check connections, power and SATA, both ends, power splitters. Could be bad cables. Why are you using these old and unreliable disks in your server and no parity? Do you really not care about any of this data?

A simpler workaround, instead of moving from a cached share to an uncached share, copy from source share to destination share, then delete from the source share. Copy will create a new file which obeys the user share settings. Move will just attempt to rename since move and rename are the same thing on linux.

Welcome!

What is this VM engine you speak of? Are you not running Unraid?

You have an unusually large number of user shares. Is that intentional? Any top level folder on cache or array is automatically a user share even if you don't explicitly create it as a user share in the webUI.

Setting a user share to cache-no will not do anything with files that are already on cache. Mover won't move them as I said. Did you study the FAQ I linked?

You have NVME drive10. Solid State disks are not recommended in the array. They cannot be trimmed, they can't be written any faster than parity, and there is some uncertainty whether some implementations will invalidate parity. You have problems communicating with multiple disks, parity and disk1. Are these on a controller card? If so, reseat controller. Check all connections, power and SATA, both ends. Be sure to check any power splitters you may have. Also, your NVME is not reporting SMART. Not sure what to do about that, but I can't tell anything about it from the diagnostics. How large is it? You should probably consider using it for cache instead of the small 120GB cache you currently have. And, your system share has files on the array. You need to get them moved to cache. They will keep array disks including parity spinning and will not perform as well on the array.

Yes, post them. Probably you have some other things that could be set up better.

User Share settings only affect what happens with new files. And Mover only moves cache-yes shares from cache to array, or cache-prefer shares from array to cache. Mover never moves cache-no or cache-only shares. So, to get files moved from cache, you must set the user share to cache-yes and run mover. Then if you don't want any more files written to cache you would set the user share to cache-no. There is Help in the webUI for most things. You can toggle Help on/off for the entire webUI with the Help (?) on the top bar. Or you can toggle help on/off for a specific setting by clicking on its label. See this FAQ for more details about how these settings work: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#comment-537383

I guess you will have to replace it. Then assign the new disk to slot1, start the array, and Unraid will rebuild its contents from the parity calculation. Do you have another copy of anything important and irreplaceable?

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

Do you have another port to try?

Does it work with a Public share? Have you tried deleting credentials in Control Panel and then trying to access only that share?

What did you mean by this?

It means Unraid can't see the disk. Could be disk, could be cable(s), could be port... Are there any power splitters involved?

And the files likely will be open if your dockers are running. Possibly you have some of your system share not on cache also, which will make dockers not perform as well and will keep parity and other disks spinning.

No SMART report for disabled Disk1. Check connections, power and SATA, both ends, then post a new diagnostic.