trurl

Attach Diagnostics to your NEXT post in this thread

Without flash or flash backup you have no existing configuration. But the data on your existing disks should be OK. https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/#what-to-do-if-you-have-no-backup-and-do-not-know-your-disk-assignments

There is nothing for you to do. The explanation of the plugin is on your Plugins page. This happens automatically when you stop the array.

Maybe GUID not unique? What brand flash drive?

You can go directly to the correct support thread for this docker by clicking its icon in your Unraid webUI and selecting Support

If you were running a correcting check when you had the large number of parity errors, then probably you have corrupted parity so rebuild will not be good.

Any parity errors at all needs to be understood and not dismissed as "nothing too strange". The screenshot suggests you have configured scheduled parity checks to correct parity errors. Better to schedule checks to not correct. If errors are found, determine the cause. After eliminating the cause, then correct parity. You don't want to allow a bad disk or connection to corrupt parity. The small number of parity errors on previous checks could be due to unclean shutdowns, or possibly RAM.

You can see how much of each disk or pool is used by each user share by clicking Compute... for the share on the User Shares page. Another advantage of having these off the array is it will allow array disks to spin down, since these files are always open.

Assign as cache then you need to move appdata domains system shares to it. Nothing can move open files so you have to disable Docker and VM Manager in Settings.

You can go directly to the correct support thread for any of your plugins by clicking its Support link on the Plugins page of your Unraid webUI.

Maybe the GUID is not unique? What brand flash drive?

Yes

https://docs.unraid.net/unraid-os/manual/shares/user-shares/#default-shares

https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/

So what did you do next? DId you rebuild after the repair was successfull?