Yep, changing both the WebDir and ConfigTemplate variables in the config file fixed it right up.
Also had to edit my GUI fix script, same edit change bin to share.
Everything is "working", but I haven't pushed a file to it yet.
https://unraid.net/policies
All purchases are final. No refunds. We recommend you try our product for free before purchasing to ensure it meets your personal needs and use case.
The parity check tuning plugin can operate with segments of a check, so the consequences of a cancel aren't quite that dire, but your point about cancel vs proceed is definitely valid.
The reason this is not the default is the damage you can cause if you don't understand how user shares work. Don't ever copy between any /mnt/user path and any disk or pool paths, until you can articulate why and how you can cause permanent data loss copying between the two types of paths.
When a container is started, if there is an error, the container is removed. Why a specific container has an error on starting is an exercise for the reader. Perhaps a referenced device is unavailable at that specific point in time?
I don't think this is a good strategy with the current version of Unraid. There have been multiple reports of very slow speeds with ZFS single members in the parity array, encryption would just make it that much worse. ZFS' strengths are in multi member pools.
What do you mean?
The USB stick's GUID is set at the factory, and must be globally unique to qualify for an Unraid license.
That said, try using the manual install method, the creator tool doesn't work for some folks.