trurl

What happens if you make it a Public share?

Good fix! Nothing got put in lost+found for that disk. Sometimes fixing "forgets" folders and filenames for some files.

Remove these plugins and don't reinstall them
ca.cleanup.appdata.plg - 2024.11.28 (Deprecated) (Up to date) NerdTools.plg - 2024.02.17 (Unknown to Community Applications)Remove these plugins for now and see what happens
gpustat.plg - 2025.11.23 (Up to date) nvidia-driver.plg - 2026.03.19 (Up to date) radeontop.plg - 2023.02.22 (Up to date)

You can always select a template from the Add Container page (ADD CONTAINER button at bottom of DOCKER page).

The list of user templates comes from flash in config/plugins/dockerMan/templates-user

Tools -> New Config
just like the other method except you do check the parity valid box.

Changing the flash device | Unraid Docs
The USB flash device is critical to your Unraid server as it stores the operating system, configuration files, and license. If this device fails or becomes unreliable, prompt replacement is essential

This is something that was "fixed" with the upgrade.
https://docs.unraid.net/unraid-os/release-notes/7.2.0/#storage

As you can see, all your user shares are lowercase, but .cfg files for user shares are uppercase.

So, your actual user shares have no corresponding .cfg file

You won't be able to directly rename those since flash (boot) isn't case sensitive.

Rename each so the extension is .bak, then copy each to the correct (lowercase) name with extension .cfg

Then you can delete the .bak files.

You will probably have to reboot to get those changes applied.

More than 20 might be OK, more than 100 no.

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

User Shares are definitely the way to go. And after you get your user shares configured, I recommend you NOT share disks on the network.

Check filesystem on disk3

Those earlier diagnostics suggests some flash corruption at some time. Maybe your docker templates were part of that.

Those you can't edit may have to be reinstalled as new, but if you make them as before they should work as before assuming their appdata is still there.

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/boot-and-startup-failures/#recovering-from-a-lost-boot-drive-and-unknown-parity-drives

https://docs.unraid.net/unraid-os/system-administration/maintain-and-update/changing-the-flash-device/

Change Music.cfg file to music.cfg, reboot, post new diagnostics.

Looks like you must have done the extended test. You didn't mention it failed.

# 1 Extended offline Completed: read failure 90% 23344 191623008You must replace, that disk isn't suitable for anything and especially not in your array.

You can probably piece a lot of that together with docker inspect at the command line.

Whether or not a user share will overflow from cache to array depends on the settings for cache Minimum Free and for Minimum Free for the user share.

https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/cache-pools/#minimum-free-space-for-a-cache-pool

https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/shares/#minimum-free-space

https://docs.unraid.net/unraid-os/system-administration/secure-your-server/user-management/#reset-your-password

You can reset that error count with the CLEAR STATS button. Not sure that will make FCP quit reporting it though, it might just be scanning syslog. Reboot will take care of it.

The reason I asked for the screenshot is because that button seems to have disappeared on some later Unraid version. I had a similar occurrence during my last monthly parity check but when I looked for that button it was gone. I rebooted to get FCP to quit reporting it.

Your Unraid version is over a year old, and has a deprecated mover tuning plugin installed.

Disk3 is disabled. Any writes to emulated disk3 are writes to parity so that is what you are seeing in that screenshot, it is still moving data to emulated disk3.

See if you can stop mover from command line with
mover stop

Looks like a flash drive problem. Do you have a current backup of flash?

Contact Support

Your user shares are still broken due to the corruption on NTFS cache. Copy what you can and reformat.

You are having problems communicating with disk5. Check connections.

Easily regenerated, we often suggest deleting it for some problems.
https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/

For getting your containers going again, appdata is the important part, along with the templates on flash at config/plugins/dockerMan/templates-user.