HI Jonathan, with the old USB stick, I could read from it but not write to it. Tried using Disk Management under Windows (as well as a Windows app called BootICEx64), and also tried Disk Utility under macOS to try to reformat the USB stick, but it was nothing but errors so safe to say that USB is dead. However when I got the first error from Unraid OS saying it couldn't write to the USB I copied the files off of it onto my Windows PC.
I won't bore with all the details but I spent around 3 to 3 1/2 hours going through support docs to create a new USB and copying back on to it first all files, then only the "config" folder, but the server threw up all kinds of "unable to create session ID" errors. In the end I just created a new USB and in essence, a new server linked to my account. Fortunately I'm new to Unraid so still using the trail key for now so no loss of key there.
When assigning the drives again, I kept getting warnings saying data would be destroyed but just reassigning drives for testing, I realized the warning only applied to the parity drive. I assigned the drives back to where they were, noticed a tick box next to the "Start" button saying "Parity already valid" and started the array. To my relief, yes like you said, the data was there and the parity wasn't rebuilt. Though to be extra safe I'm running a parity check.
Sweats over though. I'm good.