trurl

Not really your problem or even wrong, but why do you have dual parity when you only have a single data disk? Single parity should be enough for several data disks. Not clear there is anything wrong with user shares, but I don't recommend ntfs for assigned disks, even though they are allowed. Maybe that is causing some problem for user shares. See if you can move everything off cache and reformat it as one of the more "native" Unraid filesystems - xfs, btrfs, zfs. Nothing can move open files, so you will have to disable Docker and VM Manager in Settings before you can move their related shares - appdata, domains, system - off cache. And leave them disabled until you get cache reformatted and those shares moved back to cache.

I'll let someone with more btrfs raid expertise help with your problem, but I thought I would comment on this: Only use reliable drives in your server, not just whatever you happen to have. In order to reliably rebuild a drive, Unraid must be able to reliably read all other drives in the array. So, a drive that isn't reliable could potentially compromise your ability to recover a different drive. Also, I always say, each additional drive is an additional point of failure. Use as many drives as required for your current needed capacity, plus some spare space. Don't fill up you server with drives just because you can.

Start the array in normal (not maintenance) mode and post new diagnostics

https://forums.unraid.net/topic/79530-support-ich777-gameserver-dockers/

Check filesystem on emulated disks 1 and 5 from the webUI and post the output.

You should always make sure your plugins are updated before updating Unraid. Remove Community Apps and install the latest version.

Post docker run for Palworld

You attached the download before it had completed. Try again.

then try again.

Go to User Shares page and click CLEAN UP button at bottom

Much of the webUI has help. You can toggle help for a specific setting by clicking its label. You can toggle help for the entire webUI by clicking the (?) help in the Main bar

Warnings and alerts are immediate. Unraid monitors certain SMART attributes for each disk, the default attributes are in Disk Settings, and these defaults can be overridden for each disk.

That is the same syslog that is in your diagnostics. You need to post this one

Didn't fix mine. Do you also have something entered as the label in Docker Compose?

Are these orphans? You can delete orphans from the Advanced View of Docker page.

From your earlier thread: Nothing can move or delete open files. As long as the Docker service is enabled, you can't delete or move that user share. I suggest starting over with a docker.img of about 50G. You can easily reinstall all your containers from Previous Apps. https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/

Why are you using a docker folder? Looks like you probably had 130G docker.img previously, which is much larger than should be needed, so I am guessing you switched to docker folder because you kept filling docker.img. The usual cause of filling docker.img is an application writing to a path that isn't mapped. Also, your appdata and Docker (where you have your docker folder) shares have files on the array. What dockers are you running?

And you will need to reboot to clear the logs

Setup Notifications to alert you immediately by email or other agent as soon as a problem is detected.

Linux doesn't know that user shares are just a different view of the disks. If you mix user shares and disks when moving/copying, you can lose data by specifying a source path and destination path that are actually the same files. This results in creating a new empty file at the destination, then there is nothing at the source to copy.

You don't need krusader, and if krusader is configured to allow you to access individual disks, you must be sure you don't mix disks and user shares when moving/copying. Built-in File Manager won't let you make that mistake.

It's a good idea to keep some space free on each drive in case filesystem repair needs some space to work in. Disk5 also doesn't have much free space.

Attach Diagnostics ZIP to your NEXT post in this thread.