trurl

Since the diagnostics you posted are without the array started, there are many things we can't know about your situation. Please attach new diagnostics with the array started to your NEXT post.

Do you mean you have a Windows 10 VM on Unraid?

Can you tell us more about your hardware?

as explained in the release notes: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta25-available-r990/

So you do have a Downloads share. Why do you have a Downloads folder in appdata? What dockers do you run?

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

What do you get from the command line with this? (substitute real folder / filename as appropriate) ls -lah /mnt/user0/folder/fileA

Post a screenshot of User Shares page.

Have you done memtest? Be sure to check out the link I gave.

You should post your diagnostics instead of just syslog. Tools - Diagnostics, attach complete ZIP file to your NEXT post.

Have you tried booting in SAFE mode? Many of your plugins are out-of-date.

After rebuild you can repair the filesystem on the rebuild and maybe all will be good.

Unassigned drives are not part of user shares, so if you did succeed in repairing the filesystem as Unassigned then maybe the files are there. You really should have repaired the emulated disk in the array before rebuilding. Expect the rebuild to be unmountable since the emulated disk wasn't repaired.

Power Supply?

Normally you wouldn't put downloads in appdata. Why have you done this? Downloads should probably be its own user share. I suspect you have many things configured less than ideally. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

Will have to look at the details

split level has precedence so

The usual cause is an application writing to a path that isn't mapped.

Prefer shares will overflow to the array if cache gets to Minimum Free in Global Share Settings.

There are other things to consider besides allocation method. Go to Tools-Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

You can see which disks are being used by these shares by going to the User Shares page and clicking Compute... for the share. Simply setting these to cache-only will not get their files off the array. You must set them to cache-prefer and run mover. But since mover can't move open files, you must also disable docker and VM services in Settings before running mover. And mover won't move duplicates, so it is possible you might have to do some manual cleanup after moving. If you need further help with this post new diagnostics before re-enabling dockers and VMs so we can see what remains to be done.

Your appdata, domains, and system shares have files on the array, so your docker and VM performance will be affected by the slower writes (and slower disks) in the array, and dockers and VMs will not allow array disks to spin down since they will always have open files on those shares. Whether that is enough to cause all your symptoms I don't know, but I would suggest getting those shares all on cache and configured to stay all on cache.

All the files are under /mnt/disk1, /mnt/disk2, ... , /mnt/cache, and also under /mnt/user because If the files still exist, then they are in the user shares somewhere, maybe you moved them This seems extremely unlikely According to your diagnostics, there were other shares using cache, including cache-prefer shares. Cache-prefer shares would normally have all files on cache. You also have an unassigned disk not mounted and apparently set to passthru. Did you only have disk1,2,3,4 and cache,cache2 before the New Config? If you only dropped cache why were you rebuilding parity?

root password same so you can't. Why don't you want a password for webUI?